Hi Che,
C M wrote:
Hi All,
I am about to release a new (0.4 alpha) version of GUI2Exe, in
which I changed few things from the UI perspective. I was wondering if
someone had new ideas/feature requests which he/she would like to see
included in the next release. I am open to all suggestions, as usual.
Hi Andrea. I haven't looked at the state of GUI2Exe in awhile, and I am
not sure what features and GUI layout and such it has at the moment.
Is there an already-written list of features somewhere that one can look
over? Right now I don't have time to get an SVN version and play with
it, but if there is a basic list of features, maybe just looking that over
would jog some ideas from the community?
Thanks again for this great tool,
Che
Here's what the main GUI2Exe page says (http://code.google.com/p/gui2exe/):
Thanks, Mike. I'll still just ask Andrea to confirm that this is all current to
the latest version (alpha 0.4?).
There will be some more adjustments/improvements in 0.4, namely:
- wx.lib.agw.aui is used instead of wxAUI on all platforms except Mac (done);
- I'd like to switch from using wx.ListCtrl to UltimateListCtrl for
sake of clarity in the list controls, having "import" buttons and
comboboxes coming out of nowhere when you click on a list item may be
a bit surprising for the user. But no one has tested UltimateListCtrl
on the Mac so I don't know if it works (not yet done);
- Possibility to use UPX compression on dlls/exes while compiling
(py2exe only, PyInstaller has it built-in as an option) (done);
- Automatic generation of simple Inno Setup scripts (py2exe only) (done);
- Support for more keywords in the Target class (i.e., all distutils
keywords will be supported, not only "Version", "Program Name",
"Description" and "Author" as it is right now); this will also close
Issue 4 on the bug tracker (done);
- Possibly support COM servers and Windows services: this will
probably require some big re-design so I am not sure I will be able to
do it, but I am thinking about it (not done).
Based on this list, two question/suggestions
which may or may not be coherent:
* Allows the user to add post-processing custom code, which will be
executed at the end of the building process. Useful for cleaning up;
What does "cleaning up" mean here? One thing that cleaning up reminds
me of, is: could it be possible that on the occasions when the building
process fails, the directory in which the .exe file was to be made could
be cleared? I seem to recall that when I last used it, even when it failed
to make a runnable .exe file, the file would remain, plus the two other
files (wxpopopen and a Microsoft dll). I usually manually deleted them
before another try of py2exe. Automatically clearing failed tries would
be nice.
This is a nice idea, I'll implement it as an option. BTW, "cleaning
up" in the context of post-compilation code means that, for example
using py2exe, you can delete the "build" folder when the compilation
is done. But basically the post-compile code allows you to do whatever
you like (in Python code) *after* the building process has finished.
* "Super" tooltips for the users to better understand the various options;
That would be very helpful, particularly in that in the earliest version I
had no sense of what the various flag options actually did. Like the
1, 2, or 3 settings for "optimized", "compressed" or "Bundle files".
Maybe even renaming these to something more intuitive, like "Most
compressed" or something such...with a super tooltip... Just more
explanatory here.
They are already there: if you enable the tooltips (menu "Options" =>
"Show tooltips"), almost every widget in the UI will show a
detailed-enough description of what the option associated to the
widget does.
Thanks to everyone for your comments, they are very useful, as usual.
Keep them coming 
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
···
On Mon, May 18, 2009 at 11:31 PM, C M wrote:
On Mon, May 18, 2009 at 5:19 PM, Mike Driscoll <mike@pythonlibrary.org> wrote:
On Sun, May 17, 2009 at 2:47 PM, Andrea Gavana <andrea.gavana@gmail.com> >>> wrote:
