Community
Participate
Working Groups
In preferences, user should select if he want methods private, protected or public. Example: user add an JLabel. If the preferences is to work with protected, the genereted code should be private JLabel jLabel1 = null; protected JLabel getJLabel1() { ... } User could configure events to be genereted as abstract. So, a actionPerformed for a JButton should be: jButton1.addActionListener( new ActionListener(ActionEvent e) { jButton1ActionPerformed(ActionEvent e); }); ... protected abstract jButton1ActionPerformed(ActionEvent e); ... (protected, in this case, is related to the preference of the user, again). Of course, if user choose generated abstract event handlers, VE should not enable to generate private methods.
Yes, As a matter of fact our goal it to do better; we are in the process of moving all code generation templates to be JET templates (EMF flavor of JSP syntax), and enable the user to "edit" them in the pref. page, and also optionaly drive Eclipse formating on it. currently only events generation have JET templates. See plugin org.eclipse.ve.java.core:: templates\org\eclipse\ve\internal\java\codegen\jjet\util\AnonymousEventMethodTemplate.javajet as an example
Since M1 is now complete these are being retargeted to M2.
Removing target since 1.0.0 has already passed and these weren't fixed in it.
