Sup Guys,<br><br>Maybe someone can point me to some documentation regarding all this. It is a very interesting topic and I don't even know where to start looking so I can properly follow the thread.<br><br>My concerns:
<br>First, what is the current way of doing this with the Unix? What problems does this have?<br>Second how does gconf do (in terms of data storage), and how does it go about attempting to solve the problems with the Unix way. And the same questions for how KDE/sqlite/etc do things
<br><br>This will at least give us a list of requirements for data storage needs of the OpenMoko as a platform. Which we can use to either roll our own storage/vfs/whatever, or to bring an existing project up to par with what the community thinks we need.
<br><br>Sorry if I sound ignorant about this.<br><br>-Gervais.<br><br><div><span class="gmail_quote">On 1/27/07, <b class="gmail_sendername">'Mickey' Lauer</b> <Michael> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tomasz Zielinski wrote:<br>> Most PDA applications needs save small set of data - user preferences,<br>> high score list and so on. Does the OpenMoko support such operation<br>> with it's API? If it doesn't, there is a risk developers will
<br>> implement dozens of different ways and every app will behave<br>> differently.<br><br>Yeah, it's very important.<br><br>> There is of course some problems here, but I believe OpenMoko data<br>> storage API is necessary. How do you think?
<br><br>I agree 100%. However this is one of the areas where we didn't want to<br>go forward without gathering community input -- so I'm looking forward<br>to chose either one of gconf, sqlitefs, etc. during the next weeks.
<br><br>What do you guys think?<br><br>Regards,<br><br>:M:<br>--<br>Michael 'Mickey' Lauer | IT-Freelancer | <a href="http://www.vanille-media.de">http://www.vanille-media.de</a><br><br><br></blockquote></div><br>