> 1. wiki-20 tutorial is too complex now. > > for example, to setup the database, it could be easier with 'paster > setup-app development' and uncomment the dbsprockets in root.py. > We could move the original bootstrap script to the advanced settings > reference.
This is a good idea. dbsprockets wasn't yet stable when the wiki was finished. But if it just works, it will be a cleaner way to get some default data in the database. I think we can move the setupscript off into a seprate page, for those who want to know how to use the database from outside turbogears (which is something a lot of people ask about). > I like the way how wiki 20 tutorial organize it's models. > If this way is preferable, I think we should make it default in > quickstart template. (and reduce the scary lines of code in > _init__.py ). This is now done. I think it's nessisary to do something like this in order to get the reusable app-component stuff that we want. But I'm still not 100% clear how this is going to be done. > 2. the default templates are 'too much'(colors, words, pages). > > The default welcome page is full of contents which lead to lose the > focus. I got this as a contribution, and I just put it in. My hope is that somebody with some more design skill can clean up the TG2 icon, and help us clean up the design of the default page. I'll try to take a stab at cleaning up the text if nobody else does it at the sprint. > page params is used in header.html, so if a new user follow the wiki > 20 tutorial, he/she will find the query set is not only shown in > page.html. Not exactly sure what you mean here... Is this a problem with the default template, or with the wiki 20 tutorial? And do you have an idea of what we should do to fix it? > 3. lack of 'login'/'logout' link in template if identity is enabled This should be easy enough to fix. > 4. widget form should be introduced first, rather than 'validate' > decorators. (validate is more like a backend utility...) But validate makes a lot more sense than a widget form for this particular use case, and it's conceptually simpler. On the other hand the widget form method makes life really easy. > 5. A better way to 'reuse' the App. > > Could we find a way to develop a convention to 'drag and drop' tg2 app > package into exist project for quick reuse? > > Does paver or other make system could help us to pack a reusable > package(controllers, models, templates, static files) and install/ > config the package to proper place? I agree this is something that's needed, and it would be something to talk about at NEXT weekend's sprint. This weekend I want to focus on consolidating the ground we've made and on getting things cleaned up and ready for a release as soon as possible. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
