[JPP-Devel] how to install resource bundle editor?

2007-07-31 Thread Stefan Steiniger
Hei Michael or any other who is experienced,

how to installed the Resource Bundle Editor 
(http://resourcebundleeditor.com/) ?

It seems like i am not able to bring the editor to work..
I unziped and placed the folder (com.essiembre.blabla..) in the "plugin" 
folder of my eclipse installation, but eclipse seems not to load (i.e. 
the editor is not available in the list of editors, which can be 
assigned to file endings).
Which version of Eclipse (3.2.1) and Plugin (0.7.7) do you use?

stefan

-
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


Re: [JPP-Devel] where to commit stable/trunk? - Some questions on SVN use

2007-07-31 Thread Stefan Steiniger
Hei Paul,

thanx for your advises :)
i appreciate your help

stefan

Paul Austin schrieb:
> Stefan,
> 
> I've just realized that the branch is not an exact directory copy of the 
> trunk it has a different structure and a subset of the files.
> 
> I would manually apply your changes to trunk.
> 
> When we are ready to create another release we should create a new 
> branch from trunk into branches/1.2 that has all the files in trunk. and 
> then delete the current branch.
> 
> Paul
> 
> Paul Austin wrote:
>> Stefan,
>>
>> Here is a nice quick reference for using subclipse 
>> https://www.projects.dev2dev.bea.com/Subversion%20Clients/Subclipse.html
>>
>> For development
>>
>> 1. Checkout 
>> https://jump-pilot.svn.sourceforge.net/svnroot/jump-pilot/core/trunk/ on 
>> your machine
>> 2. Make your changes locally
>> 3. Checkin
>>
>> To merge with the branch.
>>
>> 1. Switch your local files to the stable branch ('Team>Switch to another 
>> branch tag' in eclipse)
>> 2. Merge from the trunk to the branch ('Team>Merge' in eclipse) Enter in 
>> the trunk URL with Head revision as the "FROM" URL and then the branch 
>> as the to URL
>> 3. This will copy any changes in trunk into your local copy of branch, 
>> you'll have to resolve any conflicts
>> 4. When you are happy checkin the branch
>>
>> To make a release.
>>
>> 1. Merge all the things you want from trunk into the branch as above
>> 2. Create a tag of the branch for the new release under tags/> number>, basically in SVN this just creates a copy of the branch under 
>> the tag folder
>>
>> Now because you checkin to the branch you'll have to merge those changes 
>> into the trunk. For the samll number of changes you can always just 
>> checkout trunk and manually reapply the changes.
>>
>>
>> Paul
>>
>> Stefan Steiniger wrote:
>>   
>>> Hei,
>>>
>>> I need some advise.
>>> Yesterday I made 2 changes
>>> * update of jmat library and
>>> * bugfix
>>>
>>> I made this changes in and commited to the stable version
>>> now, as I have been on the way to update the changelog file, I have 
>>> seen, that the one in the stable version is empty, while there is 
>>> another one in the trunk version that is filled.
>>>
>>> So I wonder
>>> - where to make the bugfixes (stable/trunk)?,
>>> - Have i done the bugfix in wrong place? and
>>> - which changelog file to use? Or is the empty changelog file in 
>>> "stable" just a mistake and it needs to be replaced?
>>> As far as I see the change of the librarie can only be done in the 
>>> stable version, as there are no libs in the trunk
>>>
>>> and .. when I am asking already.. how can the stuff changed in the trunk 
>>> moved to the stable version?
>>>
>>> stefan
>>>
>>> -
>>> 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


Re: [JPP-Devel] Coming off of hiatus...

2007-07-31 Thread Stefan Steiniger
Hei Guiseppe..

please send a message if you are back from your holidays and are ready 
for working on the documentation.
then i will send you some more info for uploading images and respond on 
your email

stefan

Giuseppe Aruta schrieb:
> Hi SS Hi Stefan,
> I read my mails every now and then so I took some days to answer.
> I currently finished to write the Menu bar functionalities. I detailed 
> some functions and I simly described others. My idea is to give a simple 
> description of all, nevertheless I also add, for some of functions, 
> tricks or some interiesting extra functionalities (see ECW or Clone 
> window as Navigation tool).
> I still don't know where to reach. I want to finish all the 
> functionalities (menu bar, toolbar, list view and layer view.
> I se there's a lot of documentation which can be used (ex. Uwe's manual, 
> Vivid's, OJthe Merge).
> There is also al lot of documentation which originally was extra 
> documentation of former plugin (e.g. Isa tools or Simple query) in PDF 
> which could be used in the new help documentation. I wnt to collect all 
> and ask the authors (one is you Stefan, with Isa Tools)  the permision 
> to put only the PDF on line, with links to the Help documentation (list 
> of functions). The idea is to join all the documentation alread written 
> of OJ (as Manuals, as extra description of plugin, pdf, txt, etc) to get 
> a complete documentation in few months. A sort of BETA documentation.
> By the time that  SS defines the  "New help documentation"  with the new 
> functionalities (no metter if external doc or as a wiki) all my 
> documentation could be joined with it in order to have a "robust" 
> documentation.
> My plan till October is to write those extra docs (as wiki):
> Toolbar
> List View
> Layer View
> I have an extra documentation: import/export files, which I would put on 
> line: it is a sort of table of all supported and unsupported types of 
> file in OJ. Users have information about how to convert, which extra 
> software to use, how to use (ex. DWG to DXF, DXF 2002 to DXF 2000, DGN, 
> E00 and also rasters or spatial tables).
> This is the plan for next (2) months.
> The help I need: English correction (of coarse) and Ideas and correction 
> of descriptions. SS you are very welcome if you want to correct my wiki 
> page.
> **
>  
> I think also that the general "documentation page" has to reorganize to 
> help people to fine what they want.
> A proposal is to separate it in two pages: "Onlyne documentation" (PDF, 
> DOC,TXT etc) and "Wiki". Anyhow there time to think about.
> **
>  
> Nex mail-control: in 6-7 days.
>  
> Peppe
> 
> */Sunburned Surveyor <[EMAIL PROTECTED]>/* ha scritto:
> 
> Stefan,
> 
> I will remain supportive of Peppe's documentation efforts, and will
> try to help him whenever there is a need.
> 
> Your suggestion of checking the task list on the wiki was a good one.
> 
> I'm going to try to start using OpenJUMP at my day job this week for a
> simple GIS project managing survey control monuments in my area. I
> think this might give me the opportunity to write some tutorial docs
> on using OpenJUMP on a project from start to "finish". Perhaps I'll
> work on that for my Monday and Tuesday documentation effort. :]
> 
> The Sunburned Surveyor
> 
> On 7/24/07, Stefan Steiniger wrote:
>  > > Does anyone have some ideas about our most pressing documentation
>  > > needs? Stefan, has Peppe sufficiently covered the new
> functionality in
>  > > OpenJUMP with his latest documentation efforts?
>  >
>  > mhm .. good question.
>  > I would wait if Peppe makes a proposal at which places he needs some
>  > help. I think that the doc made by Pepe needs also an english
> revision?
>  >
>  > otherwise i am not sure what is still on the todo list of the
> wiki (in
>  > the future developments section) .
>  >
>  > stefan
>  >
>  >
>  >
> -
>  > 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