Re: optional policy

In message <[email protected]>, Dallas Johnston
<[email protected]> writes
>Robin Becker <[email protected]> wrote:
>>I notice that we now have a direct import of frontend_wrappers and
>>dialogs.
>
>Actually, if you look at ComboBoxes.py you will notice that the frontend 
>ComboBoxWrapper is used *only* when it doesn't exist in the backend.
>

this may be true, but all the import analysers see it anyway and add it
automatically whether it's needed or not. The frontends & dialogs are
imported in __init__.py. Whether they get used or not is moot.

>I just didn't do the same with the anygui dialogs, as I thought that it would be 
>good to have a consistant dialog interface for the file dialog, no matter what 
>the widget toolkit provided (thus the original AnyguiOpenFileDlg name).
>

You might think that, but others not. It would surely be good to allow
them to make the choice.

The TODO.txt file says "- Dialogs, including native dialogs (file dialog
etc.)". I feel it would be good to make these imports very lazy indeed.
One of the main criticisms of Tk (for a long while) was non-native look
and feel.


>>My intention in writing the dwgui and ctmswgui backends was to reduce
>>the required size of a win32 gui. This kind of addition seems to be
>>going the other way, but for every platform.
>
>I don't see how having a frontend widget will add code to the backend. In fact, 
>this is quite the opposite. I.e. if we use the OpenFileDialog exclusively (not 
>that I want this, but if), then there is no need for the backend to write any 
>code.
It will if it gets imported and the backend already has native dialogs,
then it's just excess. 
-- 
Robin Becker


-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing 
your web site with SSL, click here to get a FREE TRIAL of a Thawte 
Server Certificate: http://www.gothawte.com/rd524.html