On 6/8/07, Pedro Aguilar [EMAIL PROTECTED] wrote:
Hi,
Sorry being that late to reply.
We should try different options, do some serious benchmarks and based on
the results we could choose the best solution.
Some options would be:
- X11/GTK
- X11/EFL
- DirectFB/GTK
- DirectFB/EFL
Both, GTK
Following the there's much more than GFX effects in a usable UI, here's an
interesting blog post:
http://www.codinghorror.com/blog/archives/000883.html
It's not about embedded devices GUI, rather about desktop apps vs. web apps.
However, mutatis mutandis, it drives another nail in the same
Hi,
On Fri, 2007-06-08 at 15:04 +0100, Silva, Daniel wrote:
The problem with evas as i see it, is the available developer pool.
GTK as of now is more mature and has many more knowledged developers
available.
Yes, I agree, but the interesting part of Evas is the concepts it uses
for drawing
Imho the EFL are the best choise for a device like the Neo.
But, which backend for evas ? Framebuffer ? X ? OpenGL (i don't think
there's an evas Opengl ES implementation..) ?
___
OpenMoko community mailing list
community@lists.openmoko.org
Hi,
We should try different options, do some serious benchmarks and based on
the results we could choose the best solution.
Some options would be:
- X11/GTK
- X11/EFL
- DirectFB/GTK
- DirectFB/EFL
Both, GTK and EFL, have backends for X11 and DirectFB, so running demos
and apps shouldn't be a
The problem with evas as i see it, is the available developer pool.
GTK as of now is more mature and has many more knowledged developers
available.
One other problem is that i don't see many language bindings for EFL ( at
least mature )
other than Ruby, that could hinder a bit future
Openmoko has 2 goals, right? One is to make a FOSS stack for mobile
phones, and two is to make 'your parents' want it. For that last bit,
you might need to have a consistent, but also clear and fluid (direct
reaction to touch actions for example, click delay is really confusing
for people).
The
On 6/7/07, Michael 'Mickey' Lauer [EMAIL PROTECTED] wrote:
Tomasz Zielinski wrote:
If with GTK/Matchbox we cannot achieve such rich, fluid and, erm...,
fluid GUI as iPhone, maybe it's not too late to drop GTK and choose
other framework, designed for mobile devices and running quick
On Thu, 2007-06-07 at 11:29 +0200, Fabien wrote:
On 6/7/07, Michael 'Mickey' Lauer [EMAIL PROTECTED] wrote:
Tomasz Zielinski wrote:
If with GTK/Matchbox we cannot achieve such rich, fluid and,
erm...,
fluid GUI as iPhone, maybe it's not too late to drop
I would say, considering the fact that the apps ecosystem hasn't
flourished yet, is it really too late to switch? In the rest of this
mail, please assume it is not.
How detached is the underlying processes/functions and GUI from each
other? How difficult will it be to just pull a different GUI
On to, 2007-06-07 at 01:23 +0200, Michael 'Mickey' Lauer wrote:
Tomasz Zielinski wrote:
I'm 100% sure nobody will cry after pure-X11 applications we loose
this way. Almost every GTK application would require rewriting/porting
to fit OpenMoko capabilities, so it's not great loss too. Not to
I think you should... fork.
One group for GTK and other for something else.
:)
2007/6/7, Florent THIERY [EMAIL PROTECTED]:
I would say, considering the fact that the apps ecosystem hasn't
flourished yet, is it really too late to switch? In the rest of this
mail, please assume it is not.
How
You *could* do what many existing linux apps do... write the functional
part of the app as a console program, and then use many simple GUIs as
options to interface with it. Think about cdrecord and K3b as an example.
For the handful of us out there that intend to use the Neo as a remote
On Thu, 2007-06-07 at 08:19 -0700, David Schlesinger wrote:
If someone really wanted to keep things lightweight, you could even
do a
curses based interface as an option. 31337 HaXoRs and their console
based phones.
Keen. I bet you could sell _dozens_ of those.
My dad will buy one
to, 2007-06-07 kello 09:05 -0700, John Seghers kirjoitti:
I've been writing games since 1981, on Atari 5200, 8-bit NES, SFX, Genesis,
Windows, and too many cell phones to keep track of. Please, please, please
give us direct access to the frame buffer and a low level API to the Blitter
in the
On Thu, 2007-06-07 at 01:23 +0200, Michael 'Mickey' Lauer wrote:
... GameBoy provided nice full-screen animations
in 1989, eighteen years ago.
This is nothing like the GameBoy, or the C64, or the Amiga. The GB was a
single-tasking system that would always only be doing one thing at a
time.
I've been lurking, but this is something that I do have a bit of
experience
with--and definitely some opinions.
Michael 'Mickey' Lauer wrote
Tomasz Zielinski wrote:
framework, designed for mobile devices and running quick
framebuffer operations? GameBoy provided nice full-screen
to, 2007-06-07 kello 12:19 -0600, Knight Walker kirjoitti:
And you'd be 100% wrong in at least a few occasions. X11 applications
aren't just for running desktop apps on the Moko. They can also be for
running Moko apps on the desktop.
Well put there, hadn't even considered that. I'm not quite
Daniel sent his response directly instead of to the list by accident. I
confirmed that with him so I'm leaving his entire reply and adding my points
at the end...
-Original Message-
From: Silva, Daniel [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 07, 2007 10:40 AM
To: John Seghers
What I see is a situation very similar to the WinG (Windows Game)
libraries
in the Windows 95 timeframe. These allowed a Windows app to take over the
entire screen and bypass GDI--even to the point of changing screen res and
refresh rates. Then, when you Alt-Tab'd away, or some other reason
Related tutorial :
http://www.directfb.org/wiki/index.php/Projects:GTK_on_DirectFB_for_Embedded_Systems
The choice should be driven by benchmarks results. EFLs are on the row too...
Cheers
Florent
___
OpenMoko community mailing list
Hello,
I am not sure if it is a graphical framework problem after seeing how
smooth Canola[1] is in a Nokia 770 device:
http://www.youtube.com/watch?v=nV-HtJcIW-I
best regards,
[1] http://openbossa.indt.org.br/canola/
2007/6/6, Tomasz Zielinski [EMAIL PROTECTED]:
2007/6/6, Fabien [EMAIL
Hi,
An alternative could be DirectFB, it was designed specifically for
embedded systems, there is no overhead with any protocol or other things.
GDK has a DirectFB backend, so there is no problem running GTK+ apps over it.
It isn't easy to say how much the perfomance could improve, but it could
On ke, 2007-06-06 at 14:52 +0200, Tomasz Zielinski wrote:
As we know, much less powered machines (like 7MHz Amiga with Workbench
and even 1MHz C64 with Geos) had enough resources to provide rich and
usable user interface. I mentioned PalmOS some time ago - it executed
programs in-place so most
As I understand it the new GTK mobile initiative will really be focusing on
performance on mobiles. I don't think the software is there yet, or the all
of the hard ware. Personally I'm not too concerned with the speed of the
GUI... yet.
That and it sounds like the next hardware revision will
Interesting. Can I hear more supportive or counter arguments?
What do the others think?
Depends on the technical bottleneck, which i am in no position to
determine. Is GDK inherently unsufficient too ?
I am very curious about the potential of the webkit gdk qt ports, i
hope to benchmark them
26 matches
Mail list logo
