Hey Jukka,

Thanks for testing the new version of the plugin.   Some comments below:

>I have the previous version installed on top of OJ 1.3 and using jre 1.5.  I 
>could not use that installation by slipping the new plugin in.  I did not get 
>errors but the Database Query tool just did not appear after starting OJ.  I 
>did not investigete the reasons for that.

Version 0.8.0 of the plugin depends on some libraries that are
compiled with JDK 1.6 and so the plugin also only supports JRE 6 and
above.  This is probably why the plugin didn't start with JRE 1.5.  I
didn't warn about this in the release notes, but will add it to future
versions' release notes.  If you need to use JRE 1.5, an older version
of the plugin like 0.7.3 should continue to work.

>
> Then I tool OJ 1.4.3 and new version and jre 1.7 and plugin works both with 
> Spatialite and Oracle.  It starts slower, and the query window really stays 
> open now. Sometimes it cannot be selected with a mouse when swithing from map 
> window to query window.  The query window just disappears, but it is possible 
> to select it for use by switching from one window to another with alt-tab 
> keys on Windows.

I also noticed some slowdown when starting up the plugin window, but
it wasn't bad (about 1 second on my PC).  It's probably the loading
time for the syntax highlighting classes and configuration.   I'll see
if it can be optimized.   I haven't noticed the problem you described
where the query window disappears, but I'm on Linux using JDK 1.6.
Did you try selecting Tools->Datatabase Query?  That should bring the
plugin window to the foreground.  I'll try with Windows and JRE 1.7
and see if I can reproduce it.

>
> Despite the window playing hide and seek the new version works OK. It is nice 
> to have query history because it can save some SQL writing. One minory 
> problem is the new layer name which is the whole SQL query used.  If it is 
> very long then it can make some windows which are opened later to be very 
> wide.  Text input box letting user to select the new layer name already 
> before running the query might be good but perhaps it could break the 
> Resfresh Layer option.

Great suggestion.   I'll add that in the next release.

Regards............            Larry


>
> -Jukka Rahkonen-
>
>

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to