Precisely, vClendar may not accept expense data DUH! but having xml for
everything else than contacts means we will be better off writing an XML <->
vcalender converter ;) or whatever format ppl like more.
I never went back to school afet my under-grad a couple of years ago, but on
this side of t
I was looking at xdbm and db.linux, have not compiled them so dont know the
library size yet, will try sample programs on the weekend.
-tasnim
- Original Message -
From: Micah Dowty <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTE
I've watched some discussions about PIM formats on the Agenda developers'
lists. The Agenda already exports its data in the vCalendar format. But
there's one major thing that people wanted (I think it's a feature of the
Newton): one unified database. All PIM data would be stored in a single
format
Palm also supports vCalendar. It would seem that using
a standard interface makes it easier to build solutions
that interoperate more easily.
>> It seems that one of the big issues to be decided is the file format.
>> Both the
>> Gnome and KDE PIM applications (and several others) save in the vC
Hello all,
I'd like to cast my vote for XML.
Mark
Micah wrote:
>It seems that one of the big issues to be decided is the file format. Both
>the
>Gnome and KDE PIM applications (and several others) save in the vCalendar
>format. It seems like if we used that, there wouldn't be much work at al
It seems that one of the big issues to be decided is the file format. Both the Gnome
and KDE PIM applications (and several others) save in the vCalendar format. It seems
like if we used that, there wouldn't be much work at all involved with desktop
synchronization.
I found a copy of the vCalen
let me know if you are working on PIM apps, I want to contribute but I want
to follow or set standard things everyone accepts. Major issues:
1 changing interfaces in pgui (if any)
2 data storage abstraction (xml, dbf, libdb, etc.)
3 data structure on disk (entity-relations)
I am more interested
> The new scrolling, though, is really nifty. Any widget, including
> containers with other widgets, can be scrolled. Simply create a
> scroll widget, and set it's PG_WP_BIND property to the widget to
> be scrolled. Using this method along with box, label, and button
> widgets the file picker cre
Hi everyone!
PicoGUI now has the following standard dialogs:
- pgMessageDialog()
- pgInputDialog()
- pgDatePicker()
- pgFontPicker()
- pgFilePicker()
- pgColorPicker()
It is also very easy to build custom dialog boxes using pgDialogBox(). You can see all
these dialog boxes in action in the new
