<div dir="ltr">On Sun, Oct 12, 2008 at 2:48 AM, Wade Brainerd <span dir="ltr"><<a href="mailto:wadetb@gmail.com">wadetb@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">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).<br>
</div></blockquote><div><br>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...<br><br>Marco <br></div></div><br></div>