jdam wrote:- specific start/end tags identifying the control around the statement(s) that add a control to the layout
jdam wrote:- more flexibility in choosing a localization messages class (non static get method enabling dynamic construction and separate classes or instances for different sets of fields on a screen)
jdam wrote:- optional disabling of some functionality of the designer to avoid corruption of generated code (no source view, no removal of certain controls)
Is there a particular reason for this? What do you define as "add" in this context? Just the line that instantiates the control or all of the lines that set properties for the control?
How would you handle the case where that code is not contiguous (e.g., control created in initializer and properties set elsewhere, control created in an accessor but added to parent in another method, etc.)?
Designer is already very flexible in handling different NLS patterns. If you are looking for additional choices, then we need to see examples of them.
LocalizationPropertyManager carPropmngr = new LocalizationPropertyManager(Car.class);
That would certainly possible in a customized, OEM version of the tool. What sort of "corruption" are you trying to prevent? Disallowing access to the source would also prevent you from coding event handlers or andding any logic to the class beyond that generated by the tool itself.
Users browsing this forum: No registered users and 1 guest