bneijt at gmail.com
Thu Apr 16 16:47:43 CEST 2009
Saying it is designed for handheld devices still sound to me like
focusing on reimplementing something specially for a kind/set of
devices. Instead of the much more productive (IMHO) molding technology
into a handheld.
I still can't get around the feeling that using e is like re-inventing
the wheel for a smaller car. In the end you want something that works in
the same way the user expects it to. Although e has a history of
ecstatically pleasing features, I never found it any good to work with.
I always found it to be cool but never usable (much like wobbly windows
Maybe then I will never really get the decision, but if you would like
to elaborate even further, please consider doing so.
As for SHR you mention, I didn't want to try SHR because the wiki
"GSM network is lost after one day of uptime: restart your FR once a
in the list of known issues. But maybe I should give it a try after all.
On Thu, 2009-04-16 at 00:30 +0200, Johny Tenfinger wrote:
> No, you didn't understand me. It isn't dedicated for Neo. It's
> designed for handheld devices. Like Neo. And under that environment
> you can still use other toolkits. And when I said about good apps I
> was thinking about phone apps. And it seems that SHR has really good,
> e17 phone apps. They would be perfect, if only there is opimd support
> and some "today" screen :)
> 2009/4/16, Bram Neijt <bneijt at gmail.com>:
> > Saying that the libs are dedicated to the Neo sounds like my worst
> > nightmare: no application anywhere ever uses them.. except for some of
> > the programs written specially for the Neo. That would imply that, if
> > you ever want to use an application on the Neo, you will have to port it
> > (or live with the overhead of running multiple GUI toolkits at the same
> > time).
> > Saying we only need good apps sounds like a big understatement of the
> > problem. The open source world is full of good apps, the problem is: not
> > only do we need good apps, they need to be coded from scratch.
> > I'm not familiar with the layout possibilities of e, however in my
> > experience, the more freedom you give the developers, the more horrid
> > the design :(. This often leeds to differently sized fonts, with buttons
> > sized to the text they contain, and no place for the user to start or
> > stop looking at the application. I've even seen interfaces where you
> > where never sure weather something was a button or not, let alone what
> > would happen if you tried to click on it.
> > Most developers are like people making their first Powerpoint
> > presentation. Everybody has seen those: everything has a different
> > color, size, and it all flies around with sound effects.
> > Bram
> > On Wed, 2009-04-15 at 23:35 +0200, Johny Tenfinger wrote:
> >> E libraries seems to be a fastest and lightnest on Neo hardware. When
> >> using proper theme of course. And they provide very nice way for
> >> layouting. I was sceptic about e too, but when I see that libs in
> >> action (from both user and developer side), I'm sure that was good
> >> decision. There is even Illume and Elememtary, which are dedicated to
> >> devices like Neo. We only need good apps, which are using those libs.
> >> 2009/4/15, Cedric Cellier <rixed at happyleptic.org>:
> >> > If you'd prefer using Qt or GTK, both have dedicated distros.
> >> >
> >> > For instance, hackable:1 is the continuation of the initial OpenMoko
> >> > software
> >> > stack that was based on GTK.
> >> >
> >> > As to why openmoko guys decided one day to sacrifice all the work
> >> > already
> >> > done
> >> > with GTK and to go for a plain new framework, well you should as well
> >> > ask
> >> > "Why those Moai on the Easter island" ? :-)
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > Openmoko community mailing list
> >> > community at lists.openmoko.org
> >> > http://lists.openmoko.org/mailman/listinfo/community
> >> >
> >> _______________________________________________
> >> Openmoko community mailing list
> >> community at lists.openmoko.org
> >> http://lists.openmoko.org/mailman/listinfo/community
> > _______________________________________________
> > Openmoko community mailing list
> > community at lists.openmoko.org
> > http://lists.openmoko.org/mailman/listinfo/community
> Openmoko community mailing list
> community at lists.openmoko.org
More information about the community