I'm curious as to how people break up their code when you have a site with many modules you may want to enable/disable.
I was thinking of making the modules live in subcontrollers and submodels instead of having all my admin stuff in one subcontroller. So perhaps: '//domain/news' holds all the news related methods with: news - view all news artilces news/1 - view article 1 news/1/edit - get form for news 1 news/0/new or news/new - make new news item /news/1/delete - kill it Also, what do others think of having the crud from submit back to the same method that generated the form? Remi Jolin's example solved a bunch of validation problems for me by having news/1 receive the results of the news form for item 1 and decide what to do based on presence of POST vars or not. Would be interested in hearing thoughts on these sort of resource layou ideas. I've been reading the Restful web services book too, and am curious whether TG has a good way for us to incorporate PUT/HEAD/DELETE in addition to POST and GET. Should I perhaps be looking at Routes to accomplish this kind of thing better? As usual, thanks for all the valuable input here. =) Iain the RESTful newbie. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
