Good question... Here are some recommendations --
There are a number of companies that interface to spicec programmatically. These companies right now do a fork exec or whatever to run spicec from within their software products. There are a number of reasons why they do not implement the spice protocol within their products and why they don't include the spicec software as part of their code base for their projects. So, firstly I feel we should support command line with spice-gtk so these people can switch over quickly. Then I recommend that we create a library/framework/API so that companies can use spice much easier programmatically. What do you think? On Apr 29, 2011, at 7:39 AM, Christophe Fergeau wrote: > On Fri, Apr 29, 2011 at 07:22:12AM -0500, Cliff Sharp wrote: >> I never said that spice-gtk is bad for me. >> There are companies that need and use spicec. > > Once again, why do they *need* it as opposed to "they need a spice client, > they don't really care if it's C, python, raw X, Qt, ..." > Saying these (hypothetical so far) companies that on OSX they won't get > spicec but spice-gtk or whatever we come up with would be a deal breaker? > If so, again, why? > > Christophe ____ Cliff Sharp | csh...@vbridges.com
_______________________________________________ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
