> this is not possible because of the naming scheme ZF uses for modules.
> Module controllers are prepended with the name of their module - This
> would result in classes named like 2009_IndexController for your case,
> which is not a legal class name in PHP.
>
> And honestly, if you really think about creating a module called
> "2009" for your application, this looks like some pretty broken
> application design, at least to my eye. You might of course have valid
> reasons to do so, but I'd be interested in a use case where this
> actually makes sense. If you need this only for some pretty URLs,
> consider using routes to achieve the desired result.
Hi there,
well, I did go for routes now, which works just fine. As to my use case,
its rather simple. It is a yearly contest. Each year you have different
layouts and different application logic to some degree. Some menu items
more or less, different data display. Still the years share the same
(improved) database backend and some functionality put into action and
view helpers. So I want to reuse that existing functionality which works
very well with modules. Same codebase, just different layouts, views and
controllers. As the modules are year based, I thought it would be nice
to name them after the year. Now they got a prefix and a route.
Cheers Jan
没有评论:
发表评论