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

On 18.06.2013 06:06, Larry Reeder wrote: > > > I wonder that if Martin Davis will not make a fix into JTS, would it make > DBQuery plugin too complex if if could optionally requests geometries from > Spatialite with "select asbinary" or "aswkt" if Spatialite extension is > loaded. > > >

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

I wonder that if Martin Davis will not make a fix into JTS, would it make > DBQuery plugin too complex if if could optionally requests geometries from > Spatialite with "select asbinary" or "aswkt" if Spatialite extension is > loaded. > Hey Jukka, Like Ede said, Martin did agree to make the fix.

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

On 15.06.2013 17:57, Rahkonen Jukka wrote: > Hi, > > I believe it is good from your side. An unfortunete issue is that with JTS > 1.13 the reading of multipart geometries from Spatialite will fail. There is > an open ticket about that in http://sourceforge.net/p/jts-topo-suite/bugs/36/ > > This

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

Hi, I believe it is good from your side. An unfortunete issue is that with JTS 1.13 the reading of multipart geometries from Spatialite will fail. There is an open ticket about that in http://sourceforge.net/p/jts-topo-suite/bugs/36/ This should not prevent including DBQuery plugin into OJ Plus

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

OK, I think I've got all the DBQuery plugin changes needed to integrate it into OJ PLUS. Let me know if I missed something. On Mon, Apr 15, 2013 at 4:02 AM, wrote: > > 1. implement I18N support for language support? > Done. > 2. send the language properties file to the developer list for tr

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

I'll take a look, Ede. -lreeder On Mon, Apr 15, 2013 at 4:02 AM, wrote: > Larry, > > thanks. as we have a windows now, before 1.7.0 is released. could you > please adress the following still? > > 1. implement I18N support for language support? > 2. send the language properties file to the dev

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

Larry, thanks. as we have a windows now, before 1.7.0 is released. could you please adress the following still? 1. implement I18N support for language support? 2. send the language properties file to the developer list for translators 3. change the menu item placement to File Menu, use MenuNames

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

Right, completely switched. I updated the license and readme to indicate the plugin is now licensed as GPLv3. Also, the plugin frame is now centered on the OJ workbench frame. I uploaded release 0.8.2 to sourceforge. -lreeder On Fri, Apr 12, 2013 at 3:33 AM, wrote: > On 12.04.2013 06:0

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

On 12.04.2013 12:47, Rahkonen Jukka wrote: > Perhaps the DB Query tool can stay as it is until it becomes a default OJ > Plus plugin. Then it might be logical to find it from the same menu than the > native Run Datastore Query. definitely. i am talking about where to place it on integration i

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

edgar Soldin wrote: > On 12.04.2013 06:01, Larry Reeder wrote: > > 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 stre

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

edgar soldin wrote: > On 12.04.2013 06:00, Larry Reeder wrote: > > 2a. we already have a DB Query item under File, how do we name the > > new one :) > > Yes, that would be confusing. The main difference from the current > DBQuery that I can see is it can query multiple DBs. Maybe "Divers

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

On 12.04.2013 06:00, Larry Reeder wrote: > 2a. we already have a DB Query item under File, how do we name the new > one :) > > > Yes, that would be confusing. The main difference from the current DBQuery > that I can see is it can query multiple DBs. Maybe "Diverse DB Query"? > That's n

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

On 12.04.2013 06:00, Larry Reeder wrote: > 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

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

On 12.04.2013 06:01, Larry Reeder wrote: > > > > 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 d

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

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

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

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

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] DBQuery integration into PLUS postponed

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