Hi,
I'm extending the widgets for my own application. I found PicoGUI seems to
have only one timer for each widget. Can I create more timers for a widget?
Thanks!
Yu-Jui Lee
_
Get Your Private, Free E-mail from MSN Hotmail
>>3) I noticed that that applications weren't always asserting themselves
>>over apps that were already running. Like when I had some bar running,
>>and the canvas animation, then tried to launch the calculator, nothing
>>appeared to happen. Although the calculator was running, so either it w
Well, I think I have finally cleared my backlog of email needing attention. If I
forgot you, just let me know. It was out of absentmindedness, not malice ;)
--
To the systems programmer, users and applications server only to provide a
test load.
___
Well, in my experience the Dragonball-based PDAs have had the longest battery life.
Then again, maybe I'm just minimalist? I just tend to think that anything over 100mhz
is severe overkill for a PDA and that 16 or 32mhz should be enough for 90% of anything
you would use a PDA for.
It would sti
Well, if a good method of uniquely identifying the widgets (converting a name or ID to
registration function pointer) can be worked out, dynamically-loaded widgets would be
a good compile-time option. It could be a lot like compiling modules for Linux.
As far as the Java goes, throughout this p
> This is what will also happen with CLDC and MIDP, the environment that Sun
> has designed for mobile appliances like cell phones.
>
> It is unlikely that existing Java applications will be run on portable
> devices of PDA size w/o partial re-implementation, in particular if they
> were initiall
Shane Nay wrote:
...
> > The same thing could be said about Java, but given the target hardware and
> > existing apps, Waba seems like a good choice for what SMARTDATA (and
> > everybody else working on a linux-based handheld) is doing.
>
> Maybe. But you are also taking away one of the main ben
> So, do you mean compile-time modularization or run-time?
Both :). Like apache.
> Compile time options would be great, a lot like the optional panelbars are
> now. Changing application managers at runtime wouldn't be too hard to
> implement, but I don't see how this is useful. As far as movin
> - I noticed that the 'make install' in cli_c doesn't install the header
> files right. It needs to copy the include/picogui/*.h files to a new
> directory, /usr/local/include/picogui, but instead it copies them to
> /usr/local/include.
It should be fixed in CVS now...
> - Tim reported problems
