On Sun, Oct 12, 2008 at 2:48 AM, Wade Brainerd <[EMAIL PROTECTED]> wrote:
> These issues could best be solved by a sugar-webcontent-activity package > which is shipped by default. It would contain the Browse GUI classes plus a > template Activity class. It would also provide a base WebServer class that > takes care of finding an unused port and binding to localhost. Content > bundles could use the template Activity class as is without any Python code, > or else could subclass it (and optionally the WebServer class as well). > We are planning to provide a sugar.web python package in sugar-toolkit for 0.84, which I guess is quite similar to what you are thinking about... Marco
_______________________________________________ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
