Jump to: navigation, search
  • It is little strange to have Logo with wxWidgets when otherwise the computer uses GTK. Maybe some criteria that left for that original decission, appears as limitations for the Logo in addition to weight of dependencies (was that internationalization support, which desided the choice in first place?) --Tonyv 05:45, 18 January 2007 (EST)
    • The choice was made at the time without OLPC in mind. I like wxWidget's native look and feel for all platforms. It also has a lot of impressive features. Lastly, I had experience using it before. Although none of these reasons are strong enough to justify its use on the OLPC machine, I hate to tear things apart before tying it out as is. --Arnans 11:10, 18 January 2007 (EST)
    • Also, is it not true that in Linux wxWidgets utilizes GTK under the hood anyways? So, the only down side is the memory overhead it consumes? --Arnans 11:10, 18 January 2007 (EST)
    • I'm not so familiar with GTK. If we were to move to it, any recommendations for a nice cross platform Python framework? Does it support internationalization? --Arnans 11:10, 18 January 2007 (EST)
      • I only looked by search in wiki and got the page GTK. I do not know how authorative it is. There is some discussion in OLPC_Python_Environment and Getting_started_programming, but things are not so super clear at the moment, at least for me. I just want to set up the working environment to study Python, though.

--Tonyv 16:53, 18 January 2007 (EST)

      • I checked the link to wxPython and rpm for runtime unicode version was 10 MB, looks quite heavy for OLPC :-( --Tonyv 04:34, 24 January 2007 (EST)--
        • It might make sense to make the switch to GTK. Perhaps this can be done with the help of the community onces the code is released. --Roger 10:27, 29 January 2007 (EST)