I am trying to use weblocks for a payroll application but I am frustrated by the lack of features that I would expect for some of the widgets.
I know it is supposed to be simple to whip up your own widgets and go on with life but I have this nagging feeling that this would be re-inventing the wheel. What I propose is that we create a list of most often requested features (simple stuff) for exiting widgets, stuff like the readonly for input boxes etc. Once we have a list like that agreed on we can ask for contributions from people that have handled these scenarios in there own code already. The more knowledgable weblocks hackers could maybe review the list of contributions and make suggestions or comments that would be needed to accept it into the dev tree. We can then all contribute to getting these features cleaned up to go into the dev. I feel this way we can make a structured effort to improving the out of the box usability of weblocks a lot. What do you think? Is this a good idea? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
