Community
Participate
Working Groups
It should be like the other wizards where it's template based. See New Handler wizard for how users can pick from the available templates. Not critical for 0.7.0.
fix it
Should we be altering the contents of the 'new library' wizard depending on the type of project that is selected when the new wizard is invoked? It appears that the current implementation will only show the RUIPropertiesLibrary if the project is a 'RUI project'. I am thinking that we should show the option all of the time, since a user may want to create a 'basic' project that contains libraries, and this wizard would not show in that scenario. I am cc'ing Theresa for guidance. Also, the check for 'isRUIProject' does not seem entirely correct. As I mentioned above, a user may create a Basic project that is configured for JavaScript generation, but the RUIPropertiesLibrary option would not appear in the new Library wizard because this project does not reference the widget projects. In general, I think we should go with the easy solution and show the library all of the time, and remove the 'isRUIProject' check.
Based on Brian's comment, change its behavior, now basic project can also see the option for creating RUIPropertiesLibrary. But for its specific contents, please offer more feedback
Can you elaborate on what you mean by 'its specific contents'? I think showing the RUIPropertiesLibrary radio button all of the time is fine.
If showingthe RUIPropertiesLibrary radio button all of the time is fine, then the work is done. What I mean whether we should generate different library content for diffent project type.
I think the content should be the same in all projects, so we should be done for now. Theresa can comment if she things otherwise.
Should we rename RUIPropertiesLibrary to NLSPropertiesLibrary so that it won't be so confusing if another generator chooses to support it?
The RUIPropertiesLibrary stereotype is in the eglx.ui.rui package, so I think it is ok if we leave it with this name for now. In the future, if we decide that the same approach can be used for NLS in various types of applications, this can be renamed and moved to a more 'core' package.
close it
