iain duncan wrote: >> I think the main problem is that there seems to be no easy and efficient >> way to generate and use a form/widgetlist/validator modifiable >> *instance* at runtime. The above two problems were just the first I've >> come across with this static construction model for forms. I'm sure >> there will be others..... >> >> Most other frameworks I've used (Django, .NET, ...) construct a "form" >> instance at runtime per request. You then fiddle with this as desired >> for this specific request and get it displayed. > > I'd have to agree with that! It seems a lot more complicated to deal > with the statics, and would be much easier to extend me thinks. Does > ToscaWidgets address this at all? > > Arg, I feel like the widgets are so close to being amazing but that left > over 10% is rough going. >
I think that the widgets are definitely the way to go. It's the "big picture" that seems to be problematic. I'm not sure that ToscaWidgets fixes any of this, but I've only had a quick play with them. I think the other problem is the multi-threading stuff. In my 20 years doing software I've come across people who just cannot get it, no matter how much you explain it. Sometimes I have to just step back and re-think what is going on in a multi-thread environment and then sort the code out appropriately. In the web environment you've got this dynamic "every request is different" approach, yet with this type of framework/application you always seem to be thinking so hard about concurrent re-use of a pool of static resources. Sometimes it just makes my head hurt :) I'm sure we will get there..... Regards, Gary. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
