TGL does one thing: it lets you design Windows/Dialog boxes and then builds them for you at runtime.
Currently, only Win32::GUI is supported. I don't see that changing in the near future.
The problem with chosing one GUI toolkit is that you have to buy into the whole framework. Even if TGL could be made to create other types of windows, the event model and lots of other things would be very different.
If Windows is you desktop OS, then Win32::GUI is a good choise. For me and many other people, the corporate environment makes Windows a constant, so cross-platform is a non-issue.
So if you need a cross-platform GUI, then Win32::GUI is obviously not a very wise choise :) I would probably go with wxWindows/wxPerl because of the decent native look-and-feel on the most widely used desktop platform (yeah, that would be Windows).
However, regardless of the GUI toolkit you chose, keeping the presentation logic separated from the application- and business logic as much as possible is a good design which will help the application grow gracefully. (Compare the approach with the use of templates when doing web development -- code in the template is okay as long as it's related to presentation logic.) If you do that, porting the application to another windowing toolkit wouldn't be that difficult, should the need arise.
/J
In reply to Re: WinLoft - Can we port it to Linux?
by jplindstrom
in thread WinLoft - Can we port it to Linux?
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |