Hi, >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. > > Sweet - FilteringGrid is probably the best candidate for starting this. AjaxLookup is another possibility, but I'm not quite sure about that widget - I've seen another similar one, (twAjaxTools) that may have the edge.
I've made a token effort at doc strings so far. If I could see generated docs, I think I could tweak the doc strings into a much better state quite quickly. >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. > > Ok, I've created the "paj" user on beta.toscawidgets.org. Happy for you to swing dynforms onto hg, provided you let me know as soon as you do, and I can get on ok. Don't want too much downtime between repositories. >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. > > Let me know when you do - I'm waiting with baited breath :-) >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. > > Don't worry too much about the repositories, it's a fairly small patch so far, easy enough to manage that way. I would really like your opinion on my first cut at it. My plan is to tidy it up a bit, add a clever object to replace "children" that support indexs lookup and iteration, with some jiggery pokery. How much can we break compatibility? If a little breakage is allowed, we can make this the default behaviour. Another option is to leave WidgetRepeater as is, and create a sister, something like UnlimitedWidgetRepeater (dodgy name I know :-) >>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: > > Ah, gotcha, I'd started ignoring that thread as it got so long. I'll go for toscawidgets.org and I hope Chris will too. In fact, I think tw.tools came from you being unavailable for a while, and he thought he may need to forcibly take control to avoid stagnation. Just glad you've reappeared :-) Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
