Hello, It's quite obvious that modules are most of the time the names of the application "concepts" (as well as DB table names).
Simple examples : - "ticket", "project", "user", ... for a ticket tracker - "website", "page", "language", "user", ... for a CMS - "product", "company", "customer", "order", ... for an ERP etc. This is clearly shown here : http://www.symfony-project.org/book/1_2/14-Generators > symfony propel-generate-crud myapp article Article or here : http://www.symfony-project.org/book/1_0/14-Generators > php symfony propel:generate-admin backend BlogArticle --module=article When you create a module with the CRUD or admin generator, the module name is nearly always the DB object name. I didn't see any "guideline" for the beginner on how to name modules until chapter 14, but in my opinion this is quite important. Maybe we should tell how modules should be named here (chapter 4) : http://www.symfony-project.org/book/1_2/04-The-Basics-of-Page-Creation Is "module naming" clear enough for you, especially when you began to use Symfony ? Regards, Maxime --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
