I think right now the Dev track is to keep with WxWidgets (specifically wrapped as WxPython) (and eventually Tk and Qt) because it is cross platform and produces nice native GUIs on a variety of OSs (Paul, Ed, correct me if I am wrong about this). The problem with Portland that I see is that it only applies to linux and X windows. I think it would be best to wait and see if is established as a standard GUI kit like GTK. The last problem I see is that it doesn't have Python bindings, which is a major hinderance.
My $.02. Take it for what it's worth. Cheers, Nate L. On 10/12/06, Carl Karsten <[EMAIL PROTECTED]> wrote:
For all I know I may be creating spam here, cuz all I know is what is below and what I saw when I clicked the link and thought, "no time to get into this, but maybe dabo folks would like to know." so here you go. Carl K The OSDL has released Portland 1.0, its set of common interface for GNOME and KDE. Because Portland will be found in many Linux distros, such as Debian, Fedora and SUSE, it could help solve some of the forking problems that we're seeing on the desktop. Let's hope that the Linux community embraced Portland, and that other distros climb on board -- because that, in turn, will encourage third-party app development. http://ztrek.blogspot.com/2006/10/portland-common-set-of-linux-uis.html _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
-- Nathan Lowrie Systems Engineer Sandia National Laboratories 717.269.2605 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
