[JPP-Devel] OpenJUMP wiki and sf.net interface change after 22. April

2013-04-11 Thread Rahkonen Jukka
Hi, Does the change have an effect on OJ wiki? Especially, if I make some edits now can they be loosed after couple of weeks? -Jukka Rahkonen- -- Precog is a next-generation analytics platform capable of advanced analyt

Re: [JPP-Devel] Decription of Run Datastore Query

2013-04-11 Thread Uwe Dalluege
Hi Jukka, thank you for clarification! Uwe Am 10.04.2013 16:08, schrieb Rahkonen Jukka: > Hi, > > It is just a general SQL query tool and you must, or you have a great > opportunity, to add the test directly into your SQL. This might get what you > want with PostGIS 2.x > > select st_intersect

Re: [JPP-Devel] Decription of Run Datastore Query

2013-04-11 Thread Rahkonen Jukka
Hi, I think that Run Datastore Query should also stay as a general SQL tool so that users can use exactly the same SQL in this tool, in PSQL command line or in pgAdmin SQL window and so on. It might be nice to have a spatial SQL query wizard with syntax highlight and help messages, menu for se

Re: [JPP-Devel] OpenJUMP wiki and sf.net interface change after 22. April

2013-04-11 Thread edgar . soldin
On 11.04.2013 09:12, Rahkonen Jukka wrote: > Hi, > > Does the change have an effect on OJ wiki? Especially, if I make some edits > now can they be loosed after couple of weeks? > they assured us the wiki would be untouched. also we have a daily backup. but maybe it'd make sense to keep a copy

[JPP-Devel] final steps to OJ 1.6

2013-04-11 Thread edgar . soldin
i will include DBQuery into PLUS and create the release. if the addition and updating Readme takes longer i will create the release tomorrow. ..ede -- Precog is a next-generation analytics platform capable of advanced a

Re: [JPP-Devel] final steps to OJ 1.6

2013-04-11 Thread Uwe Dalluege
Hi Ede, do you mean with "DBQuery" "Run Datastore Query" ? Uwe Am 11.04.2013 10:47, schrieb edgar.sol...@web.de: > i will include DBQuery into PLUS and create the release. if the addition and > updating Readme takes longer i will create the release tomorrow. > > ..ede > > -

Re: [JPP-Devel] final steps to OJ 1.6

2013-04-11 Thread Rahkonen Jukka
He means this http://jumpdbqplugin.sourceforge.net/ -Jukka- Uwe Dalluege wrote: > Hi Ede, > > do you mean with "DBQuery" > "Run Datastore Query" ? > > Uwe > > Am 11.04.2013 10:47, schrieb edgar.sol...@web.de: > > i will include DBQuery into PLUS and create the release. if the addition and >

Re: [JPP-Devel] Run Datastore Query - Layer Name

2013-04-11 Thread edgar . soldin
On 11.04.2013 08:34, Uwe Dalluege wrote: SNIP > >> There is no restriction too, as tables are created with quoted >> strings which accept any character (but maybe it is not a so >> common habit among DB adm, and I don't know if quoted >> strings for table or column names is part of the SQL standar

[JPP-Devel] DBQuery with/out connector jars

2013-04-11 Thread edgar . soldin
did we decide if we include them? if not, please comment. if yes, all except oracle? ..ede -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes A

Re: [JPP-Devel] How to get the Current Connection

2013-04-11 Thread Asma ouqalli
Hello, i loaded 2 tables from one database and i want to query the two tables when the user delete a feature, i want to delete it from database so i want to use a Delete Query, but to execute this query i need to get the current connection that i opened with it the database. -- *Asma OUQALLI* Él

[JPP-Devel] DBQuery license issue

2013-04-11 Thread edgar . soldin
Larry, i see you licensed your extension under LGPL3. unfortunately it is based OJ sources (plugin,extension interface, probably other code) hence it must be licensed under GPL either 2 or 3. would you be willing to relicense? while i am not in a position to force you, i assume it is just an ov

[JPP-Devel] DBQuery integration into PLUS postponed

2013-04-11 Thread edgar . soldin
just checked the latest DBQuery plugin and found the following issues: 1. wrong licensing under LGPL3 (see other mail) 2. menu item should be under "File", and not under a not translated "Tools" menu 2a. we already have a DB Query item under File, how do we name the new one :) 3. (minor) dialog sh

[JPP-Devel] SRID problem with Add Datastore Layer...

2013-04-11 Thread Uwe Dalluege
Hi, there is a different between Add Datastore Layer... and Open>Data Store Layer. Tested with OJ-CORE rev.3488 and PostGIS 2.0. I have a table with the SRID-value 31467. This works: 1. Open>Data Store Layer. The "Open..." window shows the correct SRID value ... srid = 31467 of the table. 2.

Re: [JPP-Devel] DBQuery integration into PLUS postponed

2013-04-11 Thread Rahkonen Jukka
Hi, How about putting it into "Plugins" once it comes the time for integration? Different main menus in CORE and PLUS versions might baffle the users. Having Aggregation tool in Plugins-Analysis is already following this model. -Jukka- edgar soldin wrote: > just checked the latest DBQuery plu

Re: [JPP-Devel] DBQuery with/out connector jars

2013-04-11 Thread Rahkonen Jukka
Hi, I would say that the plugins in Plus should mostly work out-of-the box so +1 from me for "all except oracle". Oracle would require at least a click through agreement from the users so it is "no". I made a quick test with the most recent Xerial SQLite driver and it works for me https://bitb

Re: [JPP-Devel] final steps to OJ 1.6

2013-04-11 Thread Giuseppe Aruta
Ede, before OJ 1.6, I made two upgrades of Color 2013/4/11 Rahkonen Jukka > He means this > http://jumpdbqplugin.sourceforge.net/ > > -Jukka- > > Uwe Dalluege wrote: > > > Hi Ede, > > > > do you mean with "DBQuery" > > "Run Datastore Query" ? > > > > Uwe > > > > Am 11.04.2013 10:47, schrieb edg

Re: [JPP-Devel] DBQuery integration into PLUS postponed

2013-04-11 Thread edgar . soldin
The current "Plugins" main menu item is "Tools" from my point of view. if AggregationTool is doing it differently we should think about streamlining it. we already have quite a few (too many) main menu items. from a usability standpoint it is not always clear for a new user, where to expect what

Re: [JPP-Devel] final steps to OJ 1.6

2013-04-11 Thread edgar . soldin
when is that going to happen? ..ede On 11.04.2013 13:03, Giuseppe Aruta wrote: > Ede, > before OJ 1.6, I made two upgrades of Color > > > 2013/4/11 Rahkonen Jukka > > > He means this > http://jumpdbqplugin.sourceforge.net/ > > -Jukka- > > Uwe

Re: [JPP-Devel] final steps to OJ 1.6

2013-04-11 Thread Giuseppe Aruta
Hi Ede , before OJ 1.6. I made a couple odf upgrade of ISA Feature color chooser, embedded in OJ plus Please, check here (version 0.5.2 and 0.6) https://sourceforge.net/projects/opensit/files/Openjump/PlugIn/colorchooser/ - icons resized on toolbar - new icon for "Choose color option" - (ver 0.6)

Re: [JPP-Devel] final steps to OJ 1.6

2013-04-11 Thread edgar . soldin
sorry, i am confused. what is it you want me to do? update ISA Feature color chooser in PLUS? ..ede On 11.04.2013 13:10, Giuseppe Aruta wrote: > Hi Ede , > before OJ 1.6. I made a couple odf upgrade of ISA Feature color chooser, > embedded in OJ plus > Please, check here (version 0.5.2 and 0.6

Re: [JPP-Devel] Run Datastore Query - Layer Name

2013-04-11 Thread Uwe Dalluege
Hi Ede, maybe this helps: http://pubs.vmware.com/vfabric5/index.jsp?topic=/com.vmware.vfabric.sqlfire.1.0/reference/language_ref/sql_identifiers.html All I like to say is that delimited identifiers can cause problems. If you like delimited identifiers use them! Uwe Am 11.04.2013 11:19, schrie

Re: [JPP-Devel] Run Datastore Query - Layer Name

2013-04-11 Thread edgar . soldin
thanks, while not the standard document itself, at least they claim to cite it. anyway, i am on par with Michael on that. it should be optional and implemented on writing to a DBMS connection. ..ede PS: i am totally with that using alnum and underscore is the most common denominator and usuall

Re: [JPP-Devel] Run Datastore Query - Layer Name

2013-04-11 Thread Uwe Dalluege
I agree! We should not force people to use a special name-convention! But, IMHO, if we know, from long time of experience, that a table-name like New Query Layer can cause problems we should not force to use this name by offer them as a good table-name. uwe Am 11.04.2013 13:35, schrieb edgar.so

Re: [JPP-Devel] final steps to OJ 1.6

2013-04-11 Thread Giuseppe Aruta
Sorry Ede, Bad Internet Connection OpenJUMP NB (and stable realize 1.5) has ISA Feature Color Chooser version 0.5.1 (ColorChooser0_5_1.jar). The main (stylistic) problem of this plugin was that the icons of this plugin on toolbar were smaller than closer other plugin icons. There must be a post of

[JPP-Devel] SQL test for tablenames

2013-04-11 Thread Uwe Dalluege
Hi, I have made some tests for tablenames in PostgreSQL. This works (name without delimiter): create table Abc ( id int ); select * from abc; select * from ABC; select * from abC; --- This causes problems: create table "Def" ( id int ); select * from "Def"; // this is ok! --Problems: --select *

[JPP-Devel] About new shortcuts

2013-04-11 Thread Rahkonen Jukka
Hi, I noticed only now that with the new keyboard shortcuts the good old Zoom, Pan, Select and Info (Alt, Shift-Alt, Ctrl, Ctrl-Alt) do only work when some editing tool is selected. In a normal map view for example Zoom in works with Ctrl-Plus which is not as easy to do with one-hand and it is

Re: [JPP-Devel] About new shortcuts

2013-04-11 Thread edgar . soldin
On 11.04.2013 15:53, Rahkonen Jukka wrote: > Hi, > > I noticed only now that with the new keyboard shortcuts the good old Zoom, > Pan, Select and Info (Alt, Shift-Alt, Ctrl, Ctrl-Alt) do only work when some > editing tool is selected. In a normal map view for example Zoom in works > with Ctrl-

Re: [JPP-Devel] About new shortcuts

2013-04-11 Thread edgar . soldin
and racing the clock.. *drumroll* fixed in under 30m minutes.. committing it later. ..ede On 11.04.2013 16:00, edgar.sol...@web.de wrote: > On 11.04.2013 15:53, Rahkonen Jukka wrote: >> Hi, >> >> I noticed only now that with the new keyboard shortcuts the good old Zoom, >> Pan, Select and Info (

Re: [JPP-Devel] About new shortcuts

2013-04-11 Thread Stefan Steiniger
nice! :) Am 11.04.13 10:24, schrieb edgar.sol...@web.de: > and racing the clock.. *drumroll* fixed in under 30m minutes.. committing it > later. ..ede > > On 11.04.2013 16:00, edgar.sol...@web.de wrote: >> On 11.04.2013 15:53, Rahkonen Jukka wrote: >>> Hi, >>> >>> I noticed only now that with the

Re: [JPP-Devel] Run Datastore Query with no error-message

2013-04-11 Thread Michaël Michaud
Hi, With OJ rev. 3459 and W7 (64 bit) I do not see errors or exceptions. There is no dialog window or a message in the status-line. I tested "Run Datastore Query" with this simple query: select * from xyz The table xyz does not exists in my database! But there

[JPP-Devel] OpenJUMP 1.6.0 released

2013-04-11 Thread edgar . soldin
Good things come to those who wait. Find the latest, greatest OpenJUMP here http://sourceforge.net/projects/jump-pilot/files/OpenJUMP/1.6.0/ Thank you all who contributed, filed bugs, fixed things, designed icons etc. etc. This release is the result of all your efforts. Thanks! Now everybody - J

Re: [JPP-Devel] DBQuery license issue

2013-04-11 Thread Larry Reeder
Hey Ede, Too late for the 1.6 release, but, sure, I am fine to relicense as GPL3. I'll create a new version of the plugin this weekend with a new license. -lreeder On Thu, Apr 11, 2013 at 4:01 AM, wrote: > Larry, > > i see you licensed your extension under LGPL3. unfortunately it is base

Re: [JPP-Devel] DBQuery integration into PLUS postponed

2013-04-11 Thread Larry Reeder
On Thu, Apr 11, 2013 at 4:33 AM, wrote: > just checked the latest DBQuery plugin and found the following issues: > > 1. wrong licensing under LGPL3 (see other mail) > Addressed this- the plugin can switch to GPL3 > 2. menu item should be under "File", and not under a not translated > "Tools" m

Re: [JPP-Devel] DBQuery integration into PLUS postponed

2013-04-11 Thread Larry Reeder
On Thu, Apr 11, 2013 at 5:04 AM, wrote: > The current "Plugins" main menu item is "Tools" from my point of view. if > AggregationTool is doing it differently we should think about streamlining > it. > I don't have a strong opinion about where this goes, but I don't see the problem with putting i