Hi Ede
I updated ColorChooser to a new version (1.2.1).
This version will be available on OJ 6049 and it corrects the bug that you
wrote about (missing icon an commenting out codes!) plus few small ones:
now loading time seems to be reduced a little.
I also updated the source code, hopefully every
and Peppe,
please check that your local tree is _100%_ synchronized with the remote trunk.
it should match your distro which it currently doesn't obviously.
..ede
On 12/28/2018 11:39 AM, Edgar Soldin wrote:
> hey Peppe,
>
> ok got it running by commenting in the
>
> /*
> context
OK, I felt I did a mistake yesterday.
I will give a look anyhow. Regarding
OpenKlem, I am waiting the final results of an test and possibly there will
be few adjustments, just before the first weeks of Gennuary 2019.
Peppe
Il ven 28 dic 2018, 12:03 ha scritto:
> hey Peppe,
>
> ok got it running
I will give a look this afternoon.
Thanks Ede
Il ven 28 dic 2018, 11:39 Edgar Soldin ha scritto:
> hey Peppe,
>
> ok got it running by commenting in the
>
> /*
> context.getWorkbenchContext().getWorkbench().getFrame().getToolBar()
> .addSeparator();
>
> context.get
hey Peppe,
ok got it running by commenting in the
/*
context.getWorkbenchContext().getWorkbench().getFrame().getToolBar()
.addSeparator();
context.getWorkbenchContext().getWorkbench().getFrame().getToolBar()
.add(colorSetbutton
On 12/28/2018 8:47 AM, Giuseppe Aruta wrote:
> Hi Ede,
> Thanks for remind and your efforts. I made the required modifications to
> Colorchooser and OpenKLEM plugins.
thanks
>In a couple of days I will upgrade OJ.
> Color chooser: I cannot go below 2.4 seconds on loading.
have you seen my mai
Hi Ede,
Thanks for remind and your efforts. I made the required modifications to
Colorchooser and OpenKLEM plugins. In a couple of days I will upgrade OJ.
Color chooser: I cannot go below 2.4 seconds on loading.
Best regards
Peppe
Il gio 27 dic 2018, 18:48 ha scritto:
> hey All,
>
> it's turn of
hey All,
it's turn of the year and traditionally this means release time. any
objections, open building sites? looking at the changes, mostly from Peppe!,
i'd say it's going to be OJ 1.14.
..ede
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lis
Hi,
> Ok, maybe a last word from Michael?
OK, let's go for a 1.6.3.
> I would go either way. But new features/functions (maybe more than 3)
> would require 1.7.
It does not match perfectly our versionning policy,
but it seems a good compromise as we don't want to add
the overhead of managing merge
It seems that Oj development is too much fast for a sequential number. I
agree with Matthias.
Giuseppe
2013/5/22 Stefan Steiniger
> Ok, maybe a last word from Michael?
> I would go either way. But new features/functions (maybe more than 3)
> would require 1.7.
>
> Apart from that: Seems like a
Ok, maybe a last word from Michael?
I would go either way. But new features/functions (maybe more than 3)
would require 1.7.
Apart from that: Seems like at least for JPP/OJ democracy works ;)
cheers,
stefan
Am 22.05.13 07:10, schrieb Matthias Scholz:
> Am 22.05.2013 10:25, schrieb edgar.sol...@
Am 22.05.2013 10:25, schrieb edgar.sol...@web.de:
> On 22.05.2013 10:17, Matthias Scholz wrote:
>> Am 20.05.2013 21:01, schrieb edgar.sol...@web.de:
>>> i want to push out the latest fixes. especially the oj_windows.bat fix.
>>>
>>> any way, as we also added some features and changed some menu item
+1 for 1.6.3.
-Jukka-
Edgar Soldin wrote:
>
> On 22.05.2013 10:17, Matthias Scholz wrote:
> > Am 20.05.2013 21:01, schrieb edgar.sol...@web.de:
> >> i want to push out the latest fixes. especially the oj_windows.bat fix.
> >>
> >> any way, as we also added some features and changed some menu it
On 22.05.2013 10:17, Matthias Scholz wrote:
> Am 20.05.2013 21:01, schrieb edgar.sol...@web.de:
>> i want to push out the latest fixes. especially the oj_windows.bat fix.
>>
>> any way, as we also added some features and changed some menu item
>> locations, see
>> http://jump-pilot.svn.sourceforge
Am 20.05.2013 21:01, schrieb edgar.sol...@web.de:
> i want to push out the latest fixes. especially the oj_windows.bat fix.
>
> any way, as we also added some features and changed some menu item locations,
> see
> http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/core/trunk/ChangeLog
> we sh
+1 for me. These are my projects for next months,
- I am going, in the next days, to add my raster tools (raster property
plugin and pixel inspector) to OJ NB. I have to solve ony few issues. I
will probabily add "Raster properties plugin" to Sextante Raster Context
menu.
- I want to add icons to
me too, so what'd you lean to? your vote will decide. what'd you prefer
considering the changelog? ..ede
On 22.05.2013 00:32, Michaël Michaud wrote:
> Hi
>
> No strong opinion about version number, but
> +1 to make a release before OSGeoLive 7.0 freeze
> (http://lists.osgeo.org/pipermail/live-de
Hi
No strong opinion about version number, but
+1 to make a release before OSGeoLive 7.0 freeze
(http://lists.osgeo.org/pipermail/live-demo/2013-May/007432.html)
Michaël
> Hi,
>
> if there are some new features/functions - then I am fine with 1.7
>
> stefan
>
> Am 20.05.13 15:01, schrieb edgar.s
Hi,
if there are some new features/functions - then I am fine with 1.7
stefan
Am 20.05.13 15:01, schrieb edgar.sol...@web.de:
> i want to push out the latest fixes. especially the oj_windows.bat fix.
>
> any way, as we also added some features and changed some menu item locations,
> see
> http:
i want to push out the latest fixes. especially the oj_windows.bat fix.
any way, as we also added some features and changed some menu item locations,
see
http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/core/trunk/ChangeLog
we should rather opt for 1.7.0 instead of 1.6.3 according to our v
20 matches
Mail list logo
