Community
Participate
Working Groups
When create a new EGL project, user can specified a base package name in the wizard: org.mycompany.myfirstapp Wizard will create below source directory structure after project creation: EGL Source org.mycompany.myfirstapp.server // configured for Java gen org.mycompany.myfirstapp.client // configured for JavaScript gen org.mycompany.myfirstapp.common // configured for both Java and JavaScript Because advanced users might consider this useless hand-holding, we should either make this easy to bypass.
I think this is another example where we want to "get this right" in 0.7, and not change it up again in 1.0. As I said in the longer version of this discussion (via email), I think being able to develop a complete app in a single project is very powerful - and also very logical. You remove a lot of the complexity for new developers if developers don't immediately have to worry about configuring build paths, etc. The way we did "RUI" projects in CE was great because it did this. I understand we can't do exactly what we did in CE since we need to port from the RBD 8 model, but as stated in my note, I think configuring a project with Java and JavaScript build descriptors (or whatever the term now is) out-of-the-box should be our plan for 0.7. This somewhat requires that we do something like is being suggested here with "default", suggested packages. This is what Google App Engine does (since they support client/server development in the same project).
See Bug 354426. Theresa and I discussed, and agreed the Base Package field belongs on the first page of the wizard, so that it is available regardless of the project type selected. For "Web client xx" projects, we should create the packages described below (client, server, common). For Basic projects, we should decide what default package(s) to create if any. We may just want to create whatever base package the user specifies. So, if the developer specifies "org.mycompany.order" and selects the "Basic" project template, a package "org.mycompany.order" would get created. Other comments: 1) We should remember the value on Finish and automatically populate the field the next time the developer starts the new project wizard. 2) The base package field should get validated (as the user types) like any EGL Package field (see EGL New Part wizard, for example).
Bug 354426 (project templates / basic project) depends on this, so this bug should also be targeted for i12.
I assume the base package field would be empty and not required. We can provide a hint in the field (that disappears when the user clicks the field) or as text (example: org.mycompany.myapp)
The patch is included in bug 354426
Verified
