On Mon, Jun 7, 2010 at 4:15 PM, Pierce Wetter wrote:
>
> On Jun 7, 2010, at 3:00 PM, Howard Lewis Ship wrote:
>
> > Yes, the basic rule for pages is that the name, beneath the root pages
> > package, is the logical page name. The logical page name appears in
> URLs.
>
> What is the rule for comp
On Jun 7, 2010, at 3:00 PM, Howard Lewis Ship wrote:
> Yes, the basic rule for pages is that the name, beneath the root pages
> package, is the logical page name. The logical page name appears in URLs.
What is the rule for components?
>
> So class appname.pages.EditUsers will have a logical
Yes, the basic rule for pages is that the name, beneath the root pages
package, is the logical page name. The logical page name appears in URLs.
So class appname.pages.EditUsers will have a logical name of "EditUsers".
You can also create a subpackage (or sub-sub-package), for example:
appname.
Ok, so I have 327 pages and 393 components in my application. (It's a crud
tool so 20 things times 20 objects = 400 pages get automatically built)
It's time to organize.
So right now, I have:
appname.pages
appname.components
There are hints here and there in the docs that if I add a
