Hello all,

I was a GSoC student for Openmoko who got the chance to work on the vala 
implementation of odeviced this summer. As frameworkd matured, I started 
working on the vala implementation of the entire framework daemon called 
'fsod' (FSO daemon) as some sort of a testing ground. Here is a short status 
of the current codebase[1],

1.) Device subsystem written in C/vala implementing odeviced interface
2.) A rudimentary python scripting interface that allows python subsystems to 
be loaded in its entirety with little changes.
3.) onetworkd and otimed python subsystems from frameworkd which is loaded by 
the vala daemon.
One of the good things about fsod is the faster startup and the small memory 
footprint. 

Now at this point I would like to know what the community here feels about the 
little project since people here are definitely far more experienced than me 
when it comes to writing code.

I would love to have some comments/suggestions on fsod, maybe design issues, 
but *especially* if the need for a C/vala implementation is justified given the 
fact that frameworkd is really turning out to be a wonderful piece of code and 
if it makes sense to continue working on fsod. (I must say, I did work hard on 
the code considering my programming standards, but I rather go with what the 
core developers and the other contributors here think rather than bitching 
about it. :P)

[1] The code can be found here
http://git.freesmartphone.org/?p=openmoko-gsoc2008.git;a=summary

There is also a recipe in OE for fsod (thanks mickey) in case someone wants to 
build the code pulled fresh from the git tree.

-- 
Thanks and Regards,
Sudharshan S
Blog : http://www.sudharsh.wordpress.com
IRC   : Sup3rkiddo @ Freenode, Gimpnet

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
smartphones-standards mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-standards

Reply via email to