Re: [Openev-discuss] Updated OpenEV Interface?

[<eco...@gm...>]

Hi Mario (and Frank, Yann and Matt):

Gary and I managed to place a test release onto a SourceForge Project we
created, so you can access a bundled installer from: 

https://www.sourceforge.net/projects/paa 

- on the download page is an .exe called "TerraLookv0.9_Setup.exe". Note
that this is only a test release: still working on some things (labels can
now be edited on my dev version), and the Spanish translations are
incomplete etc.

>I've been dying to respond to this all weekend but I had swore to
>myself I wouldn't do or talk about anything work related this weekend
>;)

Good for you! Wish I could say and do the same!

> 1. Gvviewwindow.py

>In GTK2, this has all changed. There are now Actions and ActionGroups
>and the UIManager. I've rewritten this aspect completely for the
>CIETmap main window and was planning to do the same for the OpenEV2
>main window.

I think this is where most of the work will be required... waiting with
bated breath for a release of OpenEV2!

> 2. Layerdlg.py

>This one has also been rewritten to use the TreeView widget and
>Actions. But adding a signal should not be a prob.

Have you integrated the LM into the main window for CIETmap and enabled
drag-and-drop? And will you incorporate into OpenEV2?

> 3. Gviewapp.py

> These won't be needed with the UIManager.

Don't understand enough about the UIManager yet...

> 4. Gvvectorpropdlg.py

> This one also has been rewritten for CIETmap (see screenshots).

Saw your screenshots and drooled!

> 5. Openev.py

>CIETmap also has a "splash-box" which I was planning to use for
>OpenEV2 as well... only need to change the pixmax. The world MODIS
>image is a good idea, although I added this feature to the WMS tool.

I guess this will be a trivial change. Not that the MODIS image is ~2.5MB so
the installer size will increase. Add World Country Boundaries and that's
another couple of megs.

> 6. Tool_ShapesGrid.pyc

>This one will definitely be replaced because it uses the now antiquated
>pgugrid.

Saw something called PyTables (www.pytables.org) that might interest you...
was just beginning to explore this myself.

> LOCALE for the .mo files to handle translations

>All the translation stuff was handled by the nls.py module (unused in
>OpenEV but a big part of CIETmap). The problem here is that in GTK2,
>all the i18n stuf has changed significantly and I don't even know how
>I will go from the nls way to the .po way...

Took me a while, but I found the .po way pretty easy - you need to check all
your code to change all 'strings' that need translation to _('strings').
Python's TOOLS folder contains an 'i18n' directory with 2 files:
'pygettext.py' and 'msgfmt.py'. Having converted the strings, I use the
command:

#> pygettext "path/to/code_files_folder/*.py" "path/to/output/openev.po"

This generates a POT file which is distributed to translators. On receipt of
the translated strings, I use:

#> msgfmt "path/to/pot_files_folder/openev_es.po"
"path/to/mo_output/openev_es.mo"

gettext is imported by openev.py, defining LOCALE as the folder containing
translations. Subfolders in LOCALE are two-letter Unicode abbreviations of
languages, which contain sub-folders called LC_MESSAGES into which the .mo
files go. I then wrote a few lines into gvviewwindow.py to handle language
switching on-the-fly.

That's it! It works!! Will be glad to help with OpenEV2 translations if you
need it...

> SPECTRAL under PYMOD...

>I don't know about those...

SPy is a really neat lib for image classification. Brought SPy v1+ (v2.0 is
out) in while working with Ned on an interface to handle classifications. At
the moment, I'm working on bringing in other functions and algorithms from
the lib - spectral angles, pca, linear unmixing etc.

> EASYDIALOGS and CTYPES

>What does this do exactly?

There was an issue users had with the GTK1 file selection dialogs - they
wanted the 'more familiar' windows native file and directory selections to
be called. EasyDialogs provides these by calling the Windows API directly,
and is dependent on CTypes. For those used to Windows, it's apparently been
a big help!

>Well, that's a lot of extra packages... my plan was to reduce
>dependencies, not increase them ;)

Was worried about the same thing - I know the GTK2 file/dir selection dlgs
are MUCH better, but since 'they are not windows' I'm not sure how the
user-base we're developing for (mostly Protected Area managers) will react! 

> ...and of course the tool files:

> I have no idea how easy or difficult those would be to port to OpenEV2...
> As long as I don't have the code (and the time!), I can't say...

All the tools mentioned have been bundled into the executable available on
SF. I'm pretty sure porting code to 2 will take a while! Hope you can find
time to check it out and comment.

> I won't get involved at all on the OpenEV1 front...

Will not trouble you on this - but I will for the port! ;)

Was also wondering if you had considered introducing splines and
text-to-path functions for OpenEV2. Would appreciate a pointer on how much
work this might entail.

Best
Sujoy