These are very good points and I really appreciate your input. I will research this over the next couple of days and see if I can make some sense of it.
I will again try and decipher the spice-glib part of the spice-gtk project. It would help me quite a bit if you would point me to specific files and or libraries to focus on. Thanks very much On Jul 8, 2011, at 10:47 AM, Christophe Fergeau wrote: > On Fri, Jul 08, 2011 at 10:35:54AM -0500, Cliff Sharp wrote: >> My feeling is that it would be best to totally replace/remove glib and as >> many unix libraries as makes sense; mainly from performance and cross >> platform perspectives. I feel that continuing to try and port all these >> unix based libraries to run on smart devices (even though a number of >> these smart devices contain custom unix kernels) is way too time >> consuming and down the road may lead to be counter productive due to the >> factors I mention below. Also, all these unix libraries, as part of a >> smart device bundles, require a very large memory footprint. > > Well, I specifically mentioned glib because it shouldn't have many > dependencies, is highly portable/ported, and I don't think most of your > "arguments" apply to it. And I think it the spice-glib code would handle > most of hte low-level stuff for you, "just" leaving you some opengl > rendering code to build on top of it (though the existing client in > spice/client has optional GL support already). > If even glib proves too much, then you'll have to start from scratch > (spice-protocol + protocol docs) and reimplement things yourself, which > will be much more work. > > Christophe ____ Cliff Sharp | csh...@vbridges.com
_______________________________________________ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
