Quoting Dotan Cohen, from the post of Mon, 02 Jun: > everyone, then I would expect that support for LTR, RTL, TTB, and > other methods of writing should be a core part of the UI, not tacked > on later.
haven't seen the discussion, but I'd imagine the most sensible reply from OpenMoko would be "we provide a hardware platform and a basic UI with 3(!) different toolkits. Don't make us pick sides, do your own hacking". well, sensible in the short run anyway. some people argue that the reason Linux is slow to standardize on desktops is the KDE/Gnome fight. While that's mostly behind us (workstations are RAM-rich and the look-and-feel is easy to merge, indeed I sometimes have trouble telling KDE from Gnome desktops at a glance without digging in the menues these days), remember that on a workstations it's easy and "cheap" to have a dual set of libraries loaded and cached, and all the registry daemons and d-bus and what have you, but it makes no sense on a handheld. in other words, OpenMoko offers GTK. people will write GTK apps for it. the people in Israel will want to run those apps too. it makes much more sence to go with the flow and not develop apps for an extra library because those apps will just have a much bigger RAM footprint, rather than using already-loaded DLLs and make better use of RAM, cache and all. What's wrong with RTL support in GTK? maybe I'm asking a dumb question, but I'm a CLI guy who understands zilch in graphic environments, so please educate me as needed... ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
