What is an Xoops?

SS

On 8/22/07, Stefan Steiniger <[EMAIL PROTECTED]> wrote:
> great ;)
>
> and before i forget: Thanx for your contributions.
> I suppose OJ 1.2 will be a promising release. Maybe we should just
> switch to 1.3 :o)
> (but on the other hand I may never reach to get all the issues solved
> for a final release .. so we will always end-up with OJ beta-delta
> versions ;)
>
>  will check out the forum thing on the weekend - i hope
> (puhh.. today rank 164 on SF.. but still pretty good thanx to your's and
> Michaels work)
>
> stefan
>
> PS: I am actually wondering if we may release a seperate jython plugin?
> But we also need to thin about how to organize the external plugins.
> Michael proposed to make a new project. While i could imagine that too..
> it may be another way to start setting up an new xoops on the SF website
> space.
>
> Larry Becker wrote:
>
> >Hi Stefan,
> >
> >   You're right.  Now that I have located the Edit button, I can make
> >changes. 8-)
> >
> >thanks,
> >Larry
> >
> >On 8/22/07, Stefan Steiniger <[EMAIL PROTECTED]> wrote:
> >
> >
> >>mhm.. you don't  have write access?
> >>but you should have ;) There are no restrictions, as far as I know.
> >>
> >>stefan
> >>
> >>Larry Becker wrote:
> >>
> >>
> >>
> >>>I'll be glad to help keep it up if I can get write access to the wiki.
> >>>
> >>>Right now I'm working through the wiki page on OpenJump-SkyJUMP 
> >>>synchronization:
> >>>http://openjump.org/wiki/show/SkyJUMP+-+OpenJUMP+Synchronization
> >>>
> >>>Larry Becker
> >>>
> >>>On 8/22/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>This is awesome Larry.
> >>>>
> >>>>I was wondering if we might start a quick page on the wiki to track
> >>>>new functionality in OpenJUMP that needs to be documented. I think
> >>>>this would help Peppe and I in our documentation efforts.
> >>>>
> >>>>Note that this would be different from the Change Log for programmers.
> >>>>
> >>>>Would anyone have a problem with adding this to the OpenJUMP wiki.
> >>>>
> >>>>The Sunburned Surveyor
> >>>>
> >>>>On 8/22/07, Michaël Michaud <[EMAIL PROTECTED]> wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>Thanks for the french translation
> >>>>>
> >>>>>We generally use something like :
> >>>>>"Derniers projets utilisés"
> >>>>>
> >>>>>Note that in french, we don't use to capitalize all the words in
> >>>>>menus... (it reminds me a recent and interseting discussion :-) )
> >>>>>
> >>>>>Thanks for all the improvements
> >>>>>
> >>>>>Michaël
> >>>>>
> >>>>>Larry Becker a écrit :
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Added an "Open Recent Project" submenu to the File menu that will
> >>>>>>remember the last 8 tasks opened.  Tentative translations were made
> >>>>>>for French, German, and Spanish.
> >>>>>>
> >>>>>>In trying out various translations I had trouble deciding between, for
> >>>>>>example (in French)
> >>>>>>
> >>>>>>Ouvrir Des Projets Récents  (To open Recent Projects)
> >>>>>>
> >>>>>>Projets Récemment Ouverts (Recently Open Projects)
> >>>>>>
> >>>>>>I decided on the later, but would appreciate any insight on the
> >>>>>>preferred form of menu commands in various languages.  In English, we
> >>>>>>almost always go with "verb noun" or "verb adjective noun".
> >>>>>>
> >>>>>>regards,
> >>>>>>Larry Becker
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>-------------------------------------------------------------------------
> >>>>>This SF.net email is sponsored by: Splunk Inc.
> >>>>>Still grepping through log files to find problems?  Stop.
> >>>>>Now Search log events and configuration files using AJAX and a browser.
> >>>>>Download your FREE copy of Splunk now >>  http://get.splunk.com/
> >>>>>_______________________________________________
> >>>>>Jump-pilot-devel mailing list
> >>>>>Jump-pilot-devel@lists.sourceforge.net
> >>>>>https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>-------------------------------------------------------------------------
> >>>>This SF.net email is sponsored by: Splunk Inc.
> >>>>Still grepping through log files to find problems?  Stop.
> >>>>Now Search log events and configuration files using AJAX and a browser.
> >>>>Download your FREE copy of Splunk now >>  http://get.splunk.com/
> >>>>_______________________________________________
> >>>>Jump-pilot-devel mailing list
> >>>>Jump-pilot-devel@lists.sourceforge.net
> >>>>https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>-------------------------------------------------------------------------
> >>This SF.net email is sponsored by: Splunk Inc.
> >>Still grepping through log files to find problems?  Stop.
> >>Now Search log events and configuration files using AJAX and a browser.
> >>Download your FREE copy of Splunk now >>  http://get.splunk.com/
> >>_______________________________________________
> >>Jump-pilot-devel mailing list
> >>Jump-pilot-devel@lists.sourceforge.net
> >>https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>
> >>
> >>
> >
> >
> >
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to