tag:blogger.com,1999:blog-17426834.post114911026631745835..comments2009-09-14T17:10:09.743-07:00Tung Wai Yiphttp://www.blogger.com/profile/01409046343777567728noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-17426834.post-1149366510996348892006-06-03T13:28:00.000-07:002006-06-03T13:28:00.000-07:00I think these are great ideas. <BR/><BR/>I have a few to add:<BR/><BR/>1. When the user creates a new 'project' or new object of any sort, create a working template "hello world" program. Thus a new user can see all of the parts that a working program needs. This also cuts down the mundane details for more advanced users. At every stage of development the user can have a testable system. [Idea from ruby on rails]<BR/><BR/>2. Give a user a group of specialized components with matching APIs and allow the user to decide which ones are useful to her application. She can chose the simplest parts when they fill what she needs and use more complicated ones when additional flexibility is needed. [Idea based on my thinking about WSGI protocol] <BR/><BR/>3. The framework can be designed to encourage coding that is more flexible, and allows bugs to be caught earlier and localized more quickly. [Idea based on various sources]<BR/><BR/>4. My experience is that having 'callbacks' in a library tends to make coding/debugging more default because it forces the user to learn/know more details about how the system works then otherwise would be needed. <BR/><BR/>5. Framework should work in conjunction with existing tools. Like unit testing, HTML/XML editors and such.<BR/><BR/>6. Have good, complete documentation: tutorial & reference. :)James Grayhttp://www.blogger.com/profile/17308696738225557556noreply@blogger.com