Paul Johnston wrote: > Hi, > > >> These last few days I've been working on the toscawidgets.org >> infrastructure to host widget docs, Hg repositories and Tracs. >> >> >> > Wow! I'm loving the sphinx generated docs. Gonna have a bash and see if > I can do something similar for tw.dynforms. >
I'll lend you a hand on this one if you'd like. The next thing I want to implement for the widget browser (those tabs inside the sphinx docs that show the source, template and live widget) is a way to register tiny controllers to feed data to demo the ajax enabled widgets. dynforms would be a perfect use-case. If you give me the green light I can import dynforms into mercurial tomorrow (hopefully) and set up a skeleton tw-enabled sphinx doc root to try make a demo of some ajax widget. Currently the widget browser live insdie the site's egg but i plan to extract it to a separate egg that can be used to try out widgets locally and preview the docs. > Like the registration too... blatent toscawidgets-ism :-) > hehe, tw.org eats its own food ;) > >> Mercurial). If you have any uncommitted changes (I'm looking at you Paul >> ;) in SVN its better to commit them sooner than later. >> >> >> > Oooh, the no max_reps work. Still a little hacky for committing. If I > make a branch in svn, will that propagate to hg ok? I've never actually > done an svn branch, but I guess it's not so hard. I'll get on the case. > Nope, a branch would not propagate unless one uses hgsvn to import it to a new mercurial repository. However, I don't think it would be possible to merge the two unrelated (to hg's eyes) repositories later. I think the easiest thing would be to clone the new tw.forms hg repository (making an effective branch) and then apply a unified diff of the last svn revision that has been imported into hg till where you are and patch the hg checkout with it. Then you can work on it with full version control until it can be merged. >> This infrastructure is open to anyone who wants to host their widgets >> code. If anyone wants to come on board be sure to ping me so I can set >> things up and explain how to use the uber-cool documentation facilities ;) >> >> >> > How does this stack up against twtools.googlecode.com? I'm all for a > community widgets area, but I think we're better off having just one. > We discussed this in tw-discuss a couple of days ago [1] and I explained why I like toscawidgets.org better for that purpose. Summing up: * The infrastructure is more flexible: can run trac, hg, sphinx, custom code... * The docs can be generated from each project's repository in the same server (with commit hooks, etc) so they're always up to date. * Docs can have a widget browser to see how the widget looks live and interact with it. * I like the theme better :) Regards, Alberto [1] http://groups.google.com/group/toscawidgets-discuss/browse_thread/thread/a2700123b7f0b9e0 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
