springframework-rcp-dev — Spring Rich Client developer list

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-419) General issue to encompass ongoing improvement of existing javadoc

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-419:
-----------------------------

    Fix Version/s: No version

> General issue to encompass ongoing improvement of existing javadoc
> ------------------------------------------------------------------
>
>                 Key: RCP-419
>                 URL: http://jira.springframework.org/browse/RCP-419
>             Project: Spring Framework Rich Client Project
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 1.0.0
>            Reporter: Kevin Stembridge
>            Priority: Minor
>             Fix For: No version
>
>         Attachments: RCP-419-1.patch, RCP-419-2.patch, RCP-419-4.patch, RCP-420-3.patch
>
>
> This issue has been created to allow the submission of patches that contain updates to classes solely for the purpose of improving the Javadoc. Patches for bug fixes or other modifications to actual source code should not be submitted under this issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-481) Exceptions disappear in ApplicationLauncher

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-481:
-----------------------------

    Fix Version/s: 1.0.2

> Exceptions disappear in ApplicationLauncher
> -------------------------------------------
>
>                 Key: RCP-481
>                 URL: http://jira.springframework.org/browse/RCP-481
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>          Components: Application Framework
>    Affects Versions: 1.0.0
>            Reporter: Theo Gülcher
>            Assignee: Lieven Doclo
>            Priority: Trivial
>             Fix For: 1.0.2
>
>
> http://forum.springframework.org/showthread.php?t=40931
> ---------------------------------------------------------------------------------
> Hi,
> I discovered some strange behavior at startup of my application. After the splash screen became visible it suddenly disappeared and I did not see any exception.
> I discovered that the following piece of code was responsible for hiding any exceptions:
> Code:
>     public ApplicationLauncher(String startupContextPath, String[] rootContextConfigLocations) {
>         .....
>         .....
>         try {
>             setRootApplicationContext(loadRootApplicationContext(rootContextConfigLocations, startupContext));
>             launchMyRichClient();
>         }
>         finally {
>             destroySplashScreen();
>         }
>     }
> I think this code is very wrong, because any exceptions in the try block would just be swallowed without showing an exception in your console or log file, so I added a catch block, like this:
> Code:
>     public ApplicationLauncher(String startupContextPath, String[] rootContextConfigLocations) {
>         .....
>         .....
>         try {
>             setRootApplicationContext(loadRootApplicationContext(rootContextConfigLocations, startupContext));
>             launchMyRichClient();
>         }
>         catch (Exception e) {
>             logger.error("Application launcher", e);
>         }
>         finally {
>             destroySplashScreen();
>         }
>     }
> After that I discovered I had some exceptions in my spring xml configuration.
> Maybe a good idea if any of the contributors/submitters would change this in SVN?
> Thanks in advance,
> Theo.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-60) FileChooser - Utils with accessory component

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-60:
----------------------------

    Fix Version/s: 1.x

> FileChooser - Utils with accessory component
> --------------------------------------------
>
>                 Key: RCP-60
>                 URL: http://jira.springframework.org/browse/RCP-60
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: springtester
>            Priority: Minor
>             Fix For: 1.x
>
>
> FileChooser allows the addition of an accessory component.
> I created a simple patch and a more comlicated one which allows
> this for FileChooserUtils.
> I removed the static JFileChooser member (since an added
> accessory component would have been there even if you
> wouldn't want it).
> --simple
>  import java.awt.Component;
>  import java.io.File;
> +import javax.swing.JComponent;
>  import javax.swing.JFileChooser;
>  /**
> @@ -27,20 +28,34 @@
>   * @author Keith Donald
>   */
>  public class FileChooserUtils {
> -    private static JFileChooser fileChooser;
>      private FileChooserUtils() {
>      }
>      public static File showFileChooser(Component parent, String 
> defaultExtension, String approveButtonName,
>              String fileTypeDescription) {
> -        if (fileChooser == null) {
> -            fileChooser = new JFileChooser();
> +        JFileChooser fileChooser = new JFileChooser();
> +        DefaultFileFilter filter = new DefaultFileFilter();
> +        filter.addExtension(defaultExtension);
> +        filter.setDescription(fileTypeDescription);
> +        fileChooser.setFileFilter(filter);
> +        int returnVal = fileChooser.showDialog(parent, approveButtonName);
> +        if (returnVal == JFileChooser.APPROVE_OPTION) {
> +            return fileChooser.getSelectedFile();
>          }
> +        else {
> +            return null;
> +        }
> +    }
> +
> +    public static File showFileChooser(Component parent, String 
> defaultExtension, String approveButtonName,
> +            String fileTypeDescription, JComponent accessory ) {
> +        JFileChooser  fileChooser = new JFileChooser();
>          DefaultFileFilter filter = new DefaultFileFilter();
>          filter.addExtension(defaultExtension);
>          filter.setDescription(fileTypeDescription);
>          fileChooser.setFileFilter(filter);
> +        fileChooser.setAccessory(accessory);
>          int returnVal = fileChooser.showDialog(parent, approveButtonName);
>          if (returnVal == JFileChooser.APPROVE_OPTION) {
>              return fileChooser.getSelectedFile();
> @@ -49,4 +64,9 @@
>              return null;
>          }
>      }
> +
> +
> +
> +
> +
>  }
> \ No newline at end of file
> --complicated
> Index: FileChooserUtils.java
> ===================================================================
> RCS file: 
> /cvsroot/spring-rich-c/spring-richclient/src/org/springframework/richclient/filechooser/FileChooserUtils.java,v
> retrieving revision 1.5
> diff -u -r1.5 FileChooserUtils.java
> --- FileChooserUtils.java       31 Oct 2004 18:58:46 -0000      1.5
> +++ FileChooserUtils.java       3 Dec 2004 13:35:07 -0000
> @@ -18,6 +18,7 @@
>  import java.awt.Component;
>  import java.io.File;
>  
> +import javax.swing.JComponent;
>  import javax.swing.JFileChooser;
>  
>  /**
> @@ -27,20 +28,26 @@
>   * @author Keith Donald
>   */
>  public class FileChooserUtils {
> -    private static JFileChooser fileChooser;
> -
> + 
> 0;  
>      private FileChooserUtils() {
>      }
>  
>      public static File showFileChooser(Component parent, String 
> defaultExtension, String approveButtonName,
>              String fileTypeDescription) {
> -        if (fileChooser == null) {
> -            fileChooser = new JFileChooser();
> +       JFileChooser fileChooser = createFileChooser(parent,defaultExtension, 
> approveButtonName, fileTypeDescription, null );
> +       int returnVal = fileChooser.showDialog(parent, approveButtonName);
> +        if (returnVal == JFileChooser.APPROVE_OPTION) {
> +            return fileChooser.getSelectedFile();
>          }
> -        DefaultFileFilter filter = new DefaultFileFilter();
> -        filter.addExtension(defaultExtension);
> -        filter.setDescription(fileTypeDescription);
> -        fileChooser.setFileFilter(filter);
> +        else {
> +            return null;
> +        }
> +    }
> +    
> +    
> +    public static File showFileChooser(Component parent, String 
> defaultExtension, String approveButtonName,
> +            String fileTypeDescription, JComponent accessory ) {
> +        JFileChooser fileChooser = createFileChooser(parent,defaultExtension, 
> approveButtonName, fileTypeDescription, accessory );
>          int returnVal = fileChooser.showDialog(parent, approveButtonName);
>          if (returnVal == JFileChooser.APPROVE_OPTION) {
>              return fileChooser.getSelectedFile();
> @@ -49,4 +56,17 @@
>              return null;
>          }
>      }
> +    static JFileChooser createFileChooser( Component parent, String 
> defaultExtension, String approveButtonName,
> +            String fileTypeDescription, JComponent accessory ){
> +       JFileChooser fileChooser = new JFileChooser();
> +        DefaultFileFilter filter = new DefaultFileFilter();
> +        filter.addExtension(defaultExtension);
> +        filter.setDescription(fileTypeDescription);
> +        fileChooser.setFileFilter(filter);
> +        if( accessory != null ){
> +               fileChooser.setAccessory(accessory);
> +        }
> + 
> 0;      return fileChooser;            
> +    }
> +    
>  }
> \ No newline at end of file

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-47) translations for the RCP built in properties

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-47:
----------------------------

    Fix Version/s:     (was: 1.x)

> translations for the RCP built in properties
> --------------------------------------------
>
>                 Key: RCP-47
>                 URL: http://jira.springframework.org/browse/RCP-47
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: Marc Portier
>            Assignee: Peter De Bruycker
>            Priority: Trivial
>         Attachments: messages_de.properties, messages_es.properties, messages_es.properties, messages_fr.properties, messages_nl.properties, messages_pt_BR.properties, messages_zh_CN.properties, RCP-47_pt_BR_V_0.2.0.patch
>
>
> As proposed on the dev-list (http://sourceforge.net/mailarchive/forum.php?thread_id=6031612&forum_id=39905)
> This issue enables rcp-contributors to add their locale specific versions of built-in resource-bundles of the RCP project as attachments.
> -----------------------------------------------------------------------
> Important General Advise To Translation Contributors: 
> Files for resource-bundle properties are (per Java standard) required to be encoded in ISO-8859-1.  Characters not supported by that encoding can be entered in the file using the unicode-escape sequence (e.g. \u20AC for the euro-sign)
> ------------------------------------------------------------------------
> Currently the 'list' of resources to translate is limited to the 
> * 'messages' bundle 
>    at resource-location: org.springframework.richclient.application

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-10) Add ProviderRegistry for ViewContext

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-10:
----------------------------

    Fix Version/s: 1.x

> Add ProviderRegistry for ViewContext
> ------------------------------------
>
>                 Key: RCP-10
>                 URL: http://jira.springframework.org/browse/RCP-10
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: besbello
>            Priority: Minor
>             Fix For: 1.x
>
>         Attachments: EntornoVista.java, RegistroFuentes.java
>
>
> Extent ViewContext to
> public interface ViewContext {
>   ...
>   public ProviderRegistry getProvider(Class typeOfProvider);
> }
> public interface ProviderRegistry{
>   public Object getProvider(Object bean, String property);
>   public Ojbect getProvider(Class clazz);
> }
> It could let registry provider of objects  (Example TableCellRenderes, TreeNodes, PropertyEditors)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-3) Multiple views of the same type per application should be supported.

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-3:
---------------------------

    Fix Version/s: 1.x

> Multiple views of the same type per application should be supported.
> --------------------------------------------------------------------
>
>                 Key: RCP-3
>                 URL: http://jira.springframework.org/browse/RCP-3
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: Ronald Haring
>            Priority: Minor
>             Fix For: 1.x
>
>         Attachments: spring-rcp.diff
>
>
> It should be possible for the application, to change its complete appearance. Not only should the views be changed, but also the menu bar and toolbar should be changed.
> Currently a given view can only be displayed on a single application window; it should be possible to have the same view active on multiple windows.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-80) Provide dymanic wizard pages

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-80:
----------------------------

    Fix Version/s: 1.x

> Provide dymanic wizard pages
> ----------------------------
>
>                 Key: RCP-80
>                 URL: http://jira.springframework.org/browse/RCP-80
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: Nitin Vazarkar
>            Priority: Minor
>             Fix For: 1.x
>
>
> I tried to use the wizard framework and found it sufficient only for 'static' wizard applications (which in my view are very rare). The FW forces you to create your pages in advance including the contents of the pages. A wizard rarely is used in that manner. Typically, values from one page are used in constructing the next page (i.e. the next page is built dynamically based on the selections in the last page).
> A related issue is that the values entered by the user are only available after you 'commit' the form. This is not suitable since you would like to use the values entered by the user to construct the dynamic pages (i.e. there should be some means for partial or page level commits).
> I have 'patched' the source to allow for the first case (a dynamic wizard). However, the implementation is not very clean. It would be nice if the framework handled it transparently.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-567) New form builder for creating complex forms.

[Brad M. (JIRA) <no...@sp...>]

    [ http://jira.springframework.org/browse/RCP-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40233#action_40233 ] 

Brad Maupin commented on RCP-567:
---------------------------------

That will be good to see. I use mine for all of my forms and have added some more features since reporting this.

> New form builder for creating complex forms.
> --------------------------------------------
>
>                 Key: RCP-567
>                 URL: http://jira.springframework.org/browse/RCP-567
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>          Components: Dialog System
>    Affects Versions: 1.0.0
>         Environment: Windwos XP
>            Reporter: Brad Maupin
>             Fix For: 1.0.2
>
>         Attachments: orderform.jpg
>
>
> The provided TableFormBuilder is only useful for very simple forms. I was able to create a form builder that extends AbstractFormBuilder and uses the jGoodies DefaultFormBuilder for layout. The main advantage of the jGoodies form builder is the ability to override the default layout's column span and orientation in a cell on a control by control basis. It is also nice to be able to specify the column and row definitions each in one (long) string. The builder also allowed me to create a complex form that also resized sensibly (which was a major priority).
> Here is my form builder. It has the provisions to create the complex form in the attached screen shot. The functionality it provides was catered to my needs and therefore I'd expect it to be changed as necessary to be general and follow common guidelines. The "add" methods create labels for the new controls and the "cell" methods only perform layout. Column spans can be overridden by either specifying a column span value other than 1 and by using CellConstraints. The use of CellConstraints also provides the means to override cell alignment for the control being layed out. For convenience the column span value can be specified to "extend to the last column". The builder will automatically commit the row when the column span is specified as such.
> One minor downside to this implementation is that gap column and row sizes must be specified. This impl does allow defining different gaps. The builder could easy insert the gap values into the row spec, but my form requires specifying the column gaps since they are not regularly placed.
> [code]
> import javax.swing.JButton;
> import javax.swing.JComponent;
> import javax.swing.JLabel;
> import javax.swing.JPanel;
> import net.mobileworkforce.maui.app.MauiApplication;
> import org.springframework.richclient.form.binding.Binding;
> import org.springframework.richclient.form.binding.BindingFactory;
> import org.springframework.richclient.form.builder.AbstractFormBuilder;
> import org.springframework.richclient.form.builder.FormComponentInterceptor;
> import org.springframework.util.Assert;
> import com.jgoodies.forms.builder.DefaultFormBuilder;
> import com.jgoodies.forms.layout.CellConstraints;
> import com.jgoodies.forms.layout.FormLayout;
> import com.jgoodies.forms.layout.CellConstraints.Alignment;
> public class MauiFormBuilder extends AbstractFormBuilder {
> 	
> 	public static final int COL_SPAN_ALL = 0;
> 	protected FormLayout layout;
> 	protected DefaultFormBuilder builder;
> 	protected CellConstraints cc = new CellConstraints();
> 	protected FormComponentInterceptor interceptor;
> 	private String formName = null;
> 	protected MauiFormBuilder(BindingFactory bindingFactory, String colSpec, String rowSpec) {
> 		super(bindingFactory);
> 		layout = new FormLayout(colSpec, rowSpec);
> 		builder = new DefaultFormBuilder(layout);
> 		interceptor = getFormComponentInterceptor();
> 	}
> 	public JPanel getForm() {
> 		return builder.getPanel();
> 	}
> 	
> 	public void setFormPropertyName(String name) {
> 		formName = name;
> 	}
> 	
>     public JComponent[] add(Binding binding, int colSpan, int rowSpan) {
>         Assert.notNull(binding, "binding is null");
>         Assert.isTrue(getFormModel() == binding.getFormModel(),
>                 "Binding's form model must match FormBuilder's form model");
>         JComponent component = binding.getControl();
>         processComponent(binding.getProperty(), component);
>         final JLabel label = createLabelFor(binding.getProperty(), component);
>         builder.append(label);
>         boolean newRow = false;
>         if (colSpan == COL_SPAN_ALL) {
>         	colSpan = builder.getColumnCount() - builder.getColumn() + 1;
>         	newRow = true;
>         }
>         builder.setRowSpan(rowSpan);
>         builder.append(component, colSpan);
>         builder.setRowSpan(1);
>         if (newRow) {
>         	row();
>         }
>         return new JComponent[] { label, component };
>     }
>     public JComponent[] add(Binding binding, int colSpan) {
>     	return add(binding, colSpan, 1);
>     }
>     
>     public JComponent[] add(String fieldName) {
>         return add(fieldName, 1);
>     }
>     public JComponent[] add(String fieldName, int colSpan) {
>         return add(createDefaultBinding(fieldName), colSpan);
>     }
>     
>     public JComponent cellWithLabel(String labelProperty, JComponent component, int colSpan) {
>     	boolean newRow = false;
>     	if (colSpan == COL_SPAN_ALL) {
>         	colSpan = builder.getColumnCount() - builder.getColumn() + 1 - 2;
>         	newRow = true;
>         }
>     	processComponent(labelProperty, component);
>         final JLabel label = createLabelFor(labelProperty, component);
>         builder.append(label);
>         builder.append(component, colSpan);
>     	if (newRow) {
>     		row();
>     	}
>     	return label;
>     }
>     
>     public MauiFormBuilder cell(JComponent component) {
>     	builder.append(component);
>     	return this;
>     }
>     
>     public MauiFormBuilder cell(JComponent component, int colSpan) {
>     	return cell(component, cc.xyw(1, 1, colSpan));
>     }
>     public MauiFormBuilder cell(String fieldName, JComponent component, int colSpan) {
>     	processComponent(fieldName, component);
>     	return cell(component, cc.xyw(1, 1, colSpan));
>     }
>     public MauiFormBuilder cell(JComponent component, int colSpan, int rowSpan) {
>     	return cell(component, cc.xywh(1, 1, colSpan, rowSpan));
>     }
>     
>     public MauiFormBuilder cell(String fieldName, JComponent component, int colSpan, int rowSpan) {
>     	processComponent(fieldName, component);
>     	return cell(component, cc.xywh(1, 1, colSpan, rowSpan));
>     }
>     
>     public MauiFormBuilder cell(JComponent component, CellConstraints c) {
>     	c.gridX = builder.getColumn();
>     	c.gridY = builder.getRow();
>     	boolean newRow = false;
>     	if (c.gridWidth == COL_SPAN_ALL) {
>     		c.gridWidth = builder.getColumnCount() - builder.getColumn() + 1;
>     		newRow = true;
>     	}
>     	builder.add(component, c);
>     	if (newRow) {
>     		row();
>     	} else {
>     		builder.nextColumn(c.gridWidth);
>     	}
>     	return this;
>     }
>     
>     public MauiFormBuilder cell(String fieldName, JComponent component, CellConstraints c) {
>     	processComponent(fieldName, component);
>     	return cell(component, c);
>     }
>     
>     public void row() {
>     	builder.nextLine(2);
>     }
>     
>     public void setColumn(int column) {
>     	builder.setColumn(column);
>     }
>     
>     public CellConstraints cellConstraints(int colSpan, int rowSpan, Alignment colAlign, Alignment rowAlign) {
>     	return cc.xywh(1, 1, colSpan, rowSpan, colAlign, rowAlign);
>     }
>     public CellConstraints cellConstraints(int colSpan, Alignment colAlign, Alignment rowAlign) {
>     	return cc.xywh(1, 1, colSpan, 1, colAlign, rowAlign);
>     }
>     public CellConstraints cellConstraints(int colSpan, Alignment colAlign) {
>     	return cc.xywh(1, 1, colSpan, 1, colAlign, CellConstraints.DEFAULT);
>     }
>     public void processComponent(String fieldName, JComponent component) {
> 		if (interceptor != null) {
> 			interceptor.processComponent(fieldName, component);
> 		}
> 		if (formName != null) {
> 			String property = formName + "." + fieldName + ".caption";
> 			String tooltip = MauiApplication.getMessage(property);
> 			if (tooltip != null) {
> 				component.setToolTipText(tooltip);
> 			}
> 		}
>     }
>     
>     public JLabel createLabel(String fieldName) {
>     	return createLabelFor(fieldName, null);
>     }
>     
>     public JButton createButton(String fieldName) {
> 		JButton button = getComponentFactory().createButton("");
> 		getFormModel().getFieldFace(fieldName).configure(button);
> 		processComponent(fieldName, button);
> 		return button;
>     }
>     
> }
> [/code]
> The following is the code to create the attached complex form. I also used formLayoutMaker to visually create the form's layout.
> [code]
> 	public JPanel createFormControl() {
> 		FormModel formModel = getFormModel();
> 		
> 		//columns         1           2    3    4      5    6           7    8     9     10    11   12          13   14    15   16          17   18    19   20          21   22                         23   24
> 		String colSpec = "right:30dlu,3dlu,5dlu,100dlu,3dlu,right:50dlu,3dlu,10dlu,10dlu,50dlu,3dlu,right:30dlu,3dlu,10dlu,3dlu,right:65dlu,3dlu,10dlu,3dlu,right:40dlu,3dlu,right:min(10dlu;pref):grow,3dlu,max(50dlu;pref)";
> 		//rows            1    2    3    4    5    6    7    8    9    10   11          12   13   14   15    16   17   18   19   20   21  
> 		String rowSpec = "pref,3dlu,pref,3dlu,pref,3dlu,pref,3dlu,pref,3dlu,150dlu:grow,3dlu,pref,3dlu,fill:40dlu,3dlu,pref,3dlu,pref,3dlu,pref";
> 		MauiFormBuilder builder = new MauiFormBuilder(getBindingFactory(), colSpec, rowSpec);
> 		
> 		mfgImage = new JPanel();
> 		cmdClear = builder.createButton("cmdClear");
> 		cmdDelete = builder.createButton("cmdDelete");
> 		cmdSubmit = builder.createButton("cmdSubmit");
> 		cmdSave = builder.createButton("cmdSave");
> 		cmdCancel = builder.createButton("cmdCancel");
> 		lblSignature = builder.createLabel("capture");
> 		lblNotes = builder.createLabel("note");
> 		
> 		//1
> 		builder.cell(mfgImage, 5, 3);
> 		cboMfg = new ManufacturerComboBox();
> 		MauiComboBoxBinding cbBinding = new MauiComboBoxBinding(formModel, "order.manufacturer", cboMfg);
> 		builder.add(cbBinding, 7);
> 		cboShowCustOf = new SalesRepComboBox();
> 		cbBinding = new MauiComboBoxBinding(formModel, "order.showCustomersOfSalesRep", cboShowCustOf);
> 		builder.cellWithLabel("showCustOf", cboShowCustOf, MauiFormBuilder.COL_SPAN_ALL);
> 		
> 		//3
> 		builder.setColumn(6);
> 		cboCustomer = new CustomerComboBox(order.getShowCustomersOfSalesRep());
> 		//this keeps the control size to a minimum - otherwise the form is very wide because the control sizes to fit its data (long)
> 		Dimension d = cboCustomer.getPreferredSize();
> 		d.width = 300;
> 		cboCustomer.setPreferredSize(d);
> 		cbBinding = new MauiComboBoxBinding(formModel, "order.customer", cboCustomer);
> 		builder.add(cbBinding, MauiFormBuilder.COL_SPAN_ALL);
> 		
> 		//5
> 		builder.setColumn(6);
> 		cboShipTo = new LocationComboBox(order.getCustomer());
> 		cbBinding = new MauiComboBoxBinding(formModel, "order.shipToLocation", cboShipTo);
> 		builder.add(cbBinding, MauiFormBuilder.COL_SPAN_ALL);
> 		
> 		//7
> 		builder.setColumn(6);
> 		txtPO = (JTextField) builder.add("order.purchaseOrderNumber", 7)[1];
> 		
> 		SalesRepresentative defaultSalesRep = getCustomerManufacturerSalesRep(order.getCustomer());
> 		cboSalesRep = new SalesRepComboBox(order.getCustomer(), defaultSalesRep);
> 		cbBinding = new MauiComboBoxBinding(formModel, "order.salesRepresentative", cboSalesRep);
> 		builder.add(cbBinding, MauiFormBuilder.COL_SPAN_ALL);
> 		
> 		//9
> 		builder.setColumn(6);
> 		cboSurgeon = new SurgeonComboBox();
> 		builder.add(new ComboBoxBinding(cboSurgeon, formModel, "order.surgeonName"), 3);
> 		txtPatient = (JTextField) builder.add("order.patientName", 5)[1];
> 		builder.add("order.surgeryDate", MauiFormBuilder.COL_SPAN_ALL);
> 		
> 		//11
> 		LineItemsBinding lib = new LineItemsBinding(formModel, "genericLineItems");
> 		builder.cell(lib.getControl(), MauiFormBuilder.COL_SPAN_ALL);
> 		
> 		//13
> 		builder.cell(lblSignature, builder.cellConstraints(2, CellConstraints.LEFT, CellConstraints.BOTTOM));
> 		builder.setColumn(12);
> 		builder.cell(lblNotes, builder.cellConstraints(1, CellConstraints.LEFT, CellConstraints.BOTTOM));
> 		builder.setColumn(24);
> 		builder.cell(cmdDelete);
> 		builder.row();
> 		
> 		//15
> 		SignatureBinding sb = new SignatureBinding(formModel, "capture"); 
> 		capture = (Capture)sb.getControl();
> 		builder.cell("capture", capture, 10, 3);
> 		builder.setColumn(12);
> 		JComponent notesCtrl = createNotesBinding(formModel, builder);
> 		builder.cell(notesCtrl, MauiFormBuilder.COL_SPAN_ALL);
> 		
> 		//17
> 		builder.setColumn(16);
> 		ToggleButtonBinding tb = new ToggleButtonBinding(new JCheckBox(), formModel, "sendEmailFax"); 
> 		builder.cell("sendEmailFax", tb.getControl(), builder.cellConstraints(6, CellConstraints.RIGHT));
> 		builder.setColumn(24);
> 		builder.cell(cmdSubmit);
> 		builder.row();
> 		
> 		//19
> 		cboTitle = createTitleCombo();
> 		builder.add(new ComboBoxBinding(cboTitle, formModel, "title"), 6);
> 		builder.cell(cmdClear);
> 		builder.setColumn(24);
> 		builder.cell(cmdSave);
> 		builder.row();
> 		
> 		//21
> 		cboName = createNameCombo();
> 		builder.add(new ComboBoxBinding(cboName, formModel, "printedName"), 6);
> 		builder.setColumn(24);
> 		builder.cell(cmdCancel);
> 		
> 		return builder.getForm();
> 	}
> [/code]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-81) Introduce View toolBar and menu concepts

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-81:
----------------------------

    Fix Version/s: 1.x

> Introduce View toolBar and menu concepts
> ----------------------------------------
>
>                 Key: RCP-81
>                 URL: http://jira.springframework.org/browse/RCP-81
>             Project: Spring Framework Rich Client Project
>          Issue Type: New Feature
>            Reporter: Peter De Bruycker
>            Assignee: Peter De Bruycker
>            Priority: Minor
>             Fix For: 1.x
>
>
> As in Eclipse, a View should have a toolBar and a pulldown menu to which it can contribute.
> Work to be done:
> - add 2 methods to the ViewContext interface:
>           public CommandGroup getToolBar();
>           public CommandGroup getViewMenu();
> - The DefaultViewContext implementation, should create the commandgroups with id = view.getId()+".toolBar" and id = view.getId()+".viewMenu" resp.
> - Adapt the PageComponentPane class, so its createToolBar method is implemented by returning a JToolBar.
> The programmer can contribute to the toolBar and the viewMenu in the createControl method, or we can add a template method for convenience.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-82) ValidationEvent should not require anything to be passed in

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-82:
----------------------------

    Fix Version/s: 1.x

> ValidationEvent should not require anything to be passed in
> -----------------------------------------------------------
>
>                 Key: RCP-82
>                 URL: http://jira.springframework.org/browse/RCP-82
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: Jim Moore
>            Priority: Minor
>             Fix For: 1.x
>
>
> For example: you have a screen that has a list (no FormModel) in a panel, and you want the WizardPage to be enabled or disabled based on whether or not the panel is valid (ie, something is selected in the list).  The selection/deselection is, logically, a valid/invalid event.
> Currently, you have to pass in a FormModel and the Constraint involved.  However, as the example illustrates, neither may be relivant to something being valid or invalid.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-92) Rich Client Support For Jasper Reports

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-92:
----------------------------

    Fix Version/s: 1.x

Is this still valid code (3y old)

> Rich Client Support For Jasper Reports
> --------------------------------------
>
>                 Key: RCP-92
>                 URL: http://jira.springframework.org/browse/RCP-92
>             Project: Spring Framework Rich Client Project
>          Issue Type: New Feature
>            Reporter: Joe Kelly
>            Priority: Minor
>             Fix For: 1.x
>
>         Attachments: ConfigurableJRViewer.java, DefaultJasperReportGenerator.java, DefaultJasperReportGenerator.java, DefaultJasperReportGeneratorTest.java, HtmlReportDisplayer.java, JasperReportGenerator.java, JasperReportGenerator_usageNotes.txt, JRReportDisplayer.java, JRViewerOptions.java, MyPersonBean.java, MyPersonBean_JavaBeanNamingConvention.jasper, MyPersonBean_JavaBeanNamingConvention.jasper, MyPersonBean_JavaBeanNamingConvention.jrxml, ReportDialogPage.java, ReportException.java
>
>
> While the Spring Framework has some support classes for JasperReports, they seem to be tailored towards web apps, not rich client apps. I would like Spring Rich Client to have some support for JasperReports. See this forum topic for some discussion of this:
> http://forum.springframework.org/viewtopic.php?t=3276
> For my application, I have made a few classes that make it a bit easier to use JasperReports within a Spring Rich Client app. I will attach those classes to this feature request. They are very basic implementations but they could be a good starting point for a Spring Rich Client project developer.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-99) Multiple resource base path for images

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-99:
----------------------------

    Fix Version/s: 1.x

> Multiple resource base path for images
> --------------------------------------
>
>                 Key: RCP-99
>                 URL: http://jira.springframework.org/browse/RCP-99
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>         Environment: java 1.4.2, Suse 9.2
>            Reporter: Thomas Corbin
>            Assignee: Geoffrey De Smet
>            Priority: Minor
>             Fix For: 1.x
>
>         Attachments: ResourceMapFactoryBean.java
>
>
> I have icons in multiple jar files and would like to avoid having to put them all in one jar file. So, I need to specify multiple resourceBasePath properties somehow. 
>  
> I would kind of like something like this:
> <bean id="imageResourcesFactory" 
>          class="org.springframework.context.support.ResourceMapFactoryBean"> 
>          <property name="locations"> 
>              <list> 
>                  <value>classpath:org/springframework/richclient/image/images.properties</value> 
>                  <value>classpath:com/coned/config/images.properties</value> 
>              </list> 
>          </property> 
>          
>          <property name="resourceBasePath"> 
>              <list> 
>                  <value>com/coned/images/</value> 
>                  <value>incorsIcons/</value> 
>              </list> 
>          </property> 
>      </bean> 
> Note the <list> item for the resourceBasePath.  I envision a search through the base paths, until an image is found.  Maybe some debug logging just in case there's the same icon in multiple paths and the programmer is getting confused.
> Thanks.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-98) Flexdock integration

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-98:
----------------------------

    Fix Version/s: 1.x

> Flexdock integration
> --------------------
>
>                 Key: RCP-98
>                 URL: http://jira.springframework.org/browse/RCP-98
>             Project: Spring Framework Rich Client Project
>          Issue Type: New Feature
>            Reporter: Claudio Romano
>            Assignee: Peter De Bruycker
>            Priority: Minor
>             Fix For: 1.x
>
>         Attachments: ClosableDockingPanel.java, FlexApplicationPage.java, FlexApplicationWindow.java, FlexComponentDelegate.java, FlexComponentPane.java, FlexConfigurationManager.java, FlexDockingPort.java, FlexPageDescriptor.java
>
>
> - ClosableDockingPanel, FlexDockingPort and FlexComponentDelegate 
> These are flexdock related classes, should be moved to flexdock later on.
> - FlexApplicationWindow 
> Create a FlexApplicationPage instead of DefaultApplicationPage.
> - FlexApplicationPage
> Handles page components inside flexdock (open, close)
> - FlexConfigurationManager
> Handle the layout configuration of the flexdock. It also loads and save the flexdock configuration into a file. A default layout can be provided in the classpath. (Better integration to the preferences package)
> - FlexPageDescriptor
> Holds a FlexConfigurationManager and builds the initial page layout.
> - DesktopPageDescriptor
> http://opensource.atlassian.com/projects/spring/browse/RCP-56
> - FlexComponentPane extends DesktopPageDescriptor
> This class is in the org.springframework.richclient.command.support and not in org.springframework.richclient.command.support.flexdock beacause it uses the protected method PageComponent.fireFocus... 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-94) FileChooserComboBox improvements

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-94:
----------------------------

    Fix Version/s: 1.x

> FileChooserComboBox improvements
> --------------------------------
>
>                 Key: RCP-94
>                 URL: http://jira.springframework.org/browse/RCP-94
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: Scott Russell
>            Assignee: Oliver Hutchison
>            Priority: Minor
>             Fix For: 1.x
>
>         Attachments: DefaultPropertyEditorRegistry.java, FileChooserComboBox.java
>
>
> Please find attached some improvements to FileChooserComboBox and DefaultPropertyEditorRegistry that makes using the FileChooserComboBox easier.
> 1. DefaultPropertyEditor installs a FileEditor by default for editing java.io.File.
>    This was necessary because I found that I was getting problems using FileChooserComboBox with a ValidatingFormModel in a SwingFormModel. The problem was that because no property editor was installed by default for File objects, the SwingFormModel was trying to cast the File values returned into strings for setting in a text field.
>    One could configure a propertyEditorRegistry bean in the application context to handle this, but I found that this solution would be non-obvious for a casual user of this control object. So alternatively I have modifed DefaultPropertyEditorRegistry to install a default editor for File types.
> 2. FileChooserComboBox exposes its file chooser variable for customisation.
>     This helps eg. if you want to select only directories, or want to set the file filters to use, etc.
> 3. Minor bug fixed in getSelectedFile() method. See the notes in the text.
> -Scott

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-102) Wizard improvement - delegate back and next to Wizard

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-102:
-----------------------------

    Fix Version/s: 1.x

> Wizard improvement - delegate back and next to Wizard
> -----------------------------------------------------
>
>                 Key: RCP-102
>                 URL: http://jira.springframework.org/browse/RCP-102
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: Scott Russell
>            Assignee: Oliver Hutchison
>            Priority: Minor
>             Fix For: 1.x
>
>         Attachments: AbstractWizard.java, Wizard.java, WizardDialog.java
>
>
> Currently WizardDialog calls performCancel and performFinish on the Wizard to allow wizard to perform custom processing, and possibly veto the call.
> A similar mechanism of passing the back and next calls to the Wizard should also exist, to allow the possibility of custom processing occurring between pages, moderated by the Wizard.
> -Scott

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-120) AutomaticTableModel

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-120:
-----------------------------

    Fix Version/s: 1.x

> AutomaticTableModel
> -------------------
>
>                 Key: RCP-120
>                 URL: http://jira.springframework.org/browse/RCP-120
>             Project: Spring Framework Rich Client Project
>          Issue Type: New Feature
>            Reporter: Stephan Schmidt
>            Priority: Minor
>             Fix For: 1.x
>
>
> As posted on the ML, here is the code for the AutomaticTableModel
> svn co http://snipforge.org/svn/so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-127) support glue in ButtonBarGroupContainerPopulator

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-127:
-----------------------------

    Fix Version/s: 1.x

> support glue in ButtonBarGroupContainerPopulator
> ------------------------------------------------
>
>                 Key: RCP-127
>                 URL: http://jira.springframework.org/browse/RCP-127
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: Peter De Bruycker
>            Priority: Minor
>             Fix For: 1.x
>
>         Attachments: bad.png, good.png
>
>
> I tried to add a help button to the left of a buttonbar in an application dialog, but the help button was not placed to the left of the dialog, but was located just next to the ok button. (see screenshot1). See the 2nd screenshot for the expected result
> This is caused by:
> 1. the ButtonBarGroupContainerPopulator always inserts glue before inserting buttons (this is to align all buttons to the right).
> 2. the JGoodies ButtonBarBuilder ignores Box.Filler elements (as created by the GlueGroupMember)
> I propose the following solution:
> Create the method addGlue() in GroupContainerPopulator
> SimpleGroupContainerPopulator implementation:
>     public void addGlue() {
>         container.add(Box.createGlue());
>     }
> ButtonBarGroupContainerPopulator:
>     public void addGlue() {
>         buttons.add(CommandGroupFactoryBean.GLUE_MEMBER_CODE);
>     }
>     public void onPopulated() {
>         if (!buttons.contains(CommandGroupFactoryBean.GLUE_MEMBER_CODE)) {
>             builder.addGlue();
>         }
>         int length = buttons.size();
>         for (int i = 0; i < length; i++) {
>             Object o = buttons.get(i);
>             if (o instanceof String) {
>                 if (o == CommandGroupFactoryBean.SEPARATOR_MEMBER_CODE) {
>                     builder.addUnrelatedGap();
>                 }
>                 else if (o == CommandGroupFactoryBean.GLUE_MEMBER_CODE) {
>                     builder.addGlue();
>                 }
>             }
>             else if (o instanceof AbstractButton) {
>                 AbstractButton button = (AbstractButton) o;
>                 if (minimumSize != null) {
>                     addCustomGridded(button);
>                 }
>                 else {
>                     builder.addGridded(button);
>                 }
>                 if (i < buttons.size() - 1) {
>                     builder.addRelatedGap();
>                 }
>             }
>         }
>     }
> The GlueGroupMember also has to be changed:
>     protected void fill(GroupContainerPopulator parentContainer, Object factory, CommandButtonConfigurer configurer, List previousButtons) {
>         parentContainer.addGlue();
>     }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-129) Modifier util methods in ActionCommand

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-129:
-----------------------------

    Fix Version/s: 1.0.2

> Modifier util methods in ActionCommand
> --------------------------------------
>
>                 Key: RCP-129
>                 URL: http://jira.springframework.org/browse/RCP-129
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>            Reporter: Peter De Bruycker
>            Priority: Trivial
>             Fix For: 1.0.2
>
>
> These methods should be added for easier modifier key detection
>     /**
>      * Returns <code>true</code> if the shift key was down when invoking this
>      * <code>ActionCommand</code>.
>      * @return <code>true</code> if the shift key was down, <code>false</code>
>      * otherwise
>      */
> 	protected boolean isShiftDown() {
> 		return (getModifiers() & ActionEvent.SHIFT_MASK) != 0;
> 	}
>     
> 	/**
> 	 * Returns <code>true</code> if the control key was down when invoking this
> 	 * <code>ActionCommand</code>.
> 	 * @return <code>true</code> if the control key was down, <code>false</code>
> 	 * otherwise
> 	 */
> 	protected boolean isControlDown() {
> 		return (getModifiers() & ActionEvent.CTRL_MASK) != 0;
> 	}
>     
> 	/**
> 	 * Returns <code>true</code> if the meta key was down when invoking this
> 	 * <code>ActionCommand</code>.
> 	 * @return <code>true</code> if the meta key was down, <code>false</code>
> 	 * otherwise
> 	 */
> 	protected boolean isMetaDown() {
> 		return (getModifiers() & ActionEvent.META_MASK) != 0;
> 	}
>     
> 	/**
> 	 * Returns <code>true</code> if the alt key was down when invoking this
> 	 * <code>ActionCommand</code>.
> 	 * @return <code>true</code> if the alt key was down, <code>false</code>
> 	 * otherwise
> 	 */
> 	protected boolean isAltDown() {
> 		return (getModifiers() & ActionEvent.ALT_MASK) != 0;
> 	}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-108) Add collection support to FormModel architecture

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-108:
-----------------------------

    Fix Version/s:     (was: 1.0.2)
                   1.x

> Add collection support to FormModel architecture
> ------------------------------------------------
>
>                 Key: RCP-108
>                 URL: http://jira.springframework.org/browse/RCP-108
>             Project: Spring Framework Rich Client Project
>          Issue Type: New Feature
>          Components: Binding System
>            Reporter: Scott Russell
>            Assignee: Oliver Hutchison
>             Fix For: 1.x
>
>
> Currently, the creation of Forms and FormModels centres around a single form object being edited. Validation and commit/revert logic also revolve around this principle.
> At least two use cases exist where one would want to have a FormModel wrapping a collection of form objects, rather than a single form object.
> a) User edits a (top-level) collection of form objects (eg. in an editable JTable), then wants to commit/revert all edited objects. Validation rules should be able to apply to all elements in collection, and to the collection as a whole. Thus validation feedback, and form guards, can be aware of validation state of all form objects.
> b) User edits a top-level form object, which has a (detail) property of type Collection. This property  could for example be displayed in an editable JTable (or JTree or TreeTable). Validation rules should be able to be applied to all elements in the collection individually, and to the collection as a whole (eg. size must > 1, etc). This allows for validation feedback and enablement/disablement of form guards.
> -Scott 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-565) Windows taskbar entry at startup is not configured

[Brad M. (JIRA) <no...@sp...>]

    [ http://jira.springframework.org/browse/RCP-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40231#action_40231 ] 

Brad Maupin commented on RCP-565:
---------------------------------

Jan's help fixed the issue. I am used to setting the application name and icon once and it is used everywhere, but I can see that some may want to set a different icon and application name for each main window.

> Windows taskbar entry at startup is not configured
> --------------------------------------------------
>
>                 Key: RCP-565
>                 URL: http://jira.springframework.org/browse/RCP-565
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>          Components: Application Framework
>    Affects Versions: 1.0.0
>         Environment: Windows XP
>            Reporter: Brad Maupin
>            Assignee: Lieven Doclo
>             Fix For: 1.x
>
>
> During application startup the application entry in Windows' task bar is blank and shows the Java icon - I'd like it to show the application's name and icon. Of course it would be fine to be able to set these seperately from the main window.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-164) Improve abstraction of Application.services and Application.instance singletons

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-164:
-----------------------------

    Fix Version/s:     (was: 1.0.2)
                   1.x

> Improve abstraction of Application.services and Application.instance singletons
> -------------------------------------------------------------------------------
>
>                 Key: RCP-164
>                 URL: http://jira.springframework.org/browse/RCP-164
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>          Components: Application Framework
>            Reporter: Oliver Hutchison
>            Assignee: Oliver Hutchison
>             Fix For: 1.x
>
>
> We need to make these 2 singleton service locators *much* more abstract so that it's possible to use the various components of Spring Rich independently.
>  
> As a first step I think we should move Application.services into it's own class so you can have services with out requiring an Application we should then extract and ApplicationServices interface and remove all of the strongly typed getters replacing them with a single getService(Class serviceClass) method and ideally we should also start pushing the use of ApplicationObjectConfigurer by having ApplicationServices extend this interface.
> A similar set of refatorings should also be applied to Application.instance 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-161) Multiple page support

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-161:
-----------------------------

    Fix Version/s: 1.x

> Multiple page support
> ---------------------
>
>                 Key: RCP-161
>                 URL: http://jira.springframework.org/browse/RCP-161
>             Project: Spring Framework Rich Client Project
>          Issue Type: New Feature
>          Components: Application Framework
>            Reporter: Peter De Bruycker
>            Assignee: Peter De Bruycker
>            Priority: Minor
>             Fix For: 1.x
>
>         Attachments: multi1.png, multi2.png, MultiPageApplicationWindow.java, PageSelector.java
>
>
> Support for multiple pages in an application (similar to perspectives in Eclipse).
> Configuration is as follows:
> in ctx file:
> <bean id="applicationWindowPrototype" class="org.springframework.richclient.application.test.MultiPageApplicationWindow" singleton="false">
>   <property name="pageIds">
>     <list>
>       <value>pageId or viewId</value>
>       <value>pageId or viewId</value>
>       ...
>     </list>
>   </property>
> </bean>
> in images.properties:
> showPageMenu.icon=file/new_persp.gif
> in messages.properties:
> showPageMenu.label=Open page
> showPageMenu.caption=Open a page

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-166) BufferedValueModel relations with innerValueModel not separated

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-166:
-----------------------------

    Fix Version/s:     (was: 1.x)
                   1.0.2

> BufferedValueModel relations with innerValueModel not separated
> ---------------------------------------------------------------
>
>                 Key: RCP-166
>                 URL: http://jira.springframework.org/browse/RCP-166
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>          Components: Binding System
>            Reporter: Jan Hoskens
>            Assignee: Oliver Hutchison
>            Priority: Minor
>             Fix For: 1.0.2
>
>         Attachments: rcp-166-test.txt, rcp-166.txt, rcp-66-test.txt
>
>
> The relation between the innerValueModel and the BufferedValueModel are not clearly separated as described on the mailling list:
> http://sourceforge.net/mailarchive/forum.php?thread_id=7986845&forum_id=39905

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-175) Image and title in TitledPageApplicationDialog when using CompositeDialogPage

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-175:
-----------------------------

    Fix Version/s: 1.x

> Image and title in TitledPageApplicationDialog when using CompositeDialogPage
> -----------------------------------------------------------------------------
>
>                 Key: RCP-175
>                 URL: http://jira.springframework.org/browse/RCP-175
>             Project: Spring Framework Rich Client Project
>          Issue Type: Improvement
>          Components: Dialog System
>            Reporter: Peter De Bruycker
>            Assignee: Oliver Hutchison
>            Priority: Minor
>             Fix For: 1.x
>
>
> When putting a CompositeDialogPage in a TitledPageApplicationDialog, the image and title text in the title-area of the dialog are not updated when another DialogPage is made active.
> (The image is always the default image, not the image of the DialogPage, and the title text is always the title of the Dialog)
> This fixes it:
> in CompositeDialogPage add these methods:
>     public Image getImage() {
>         if (activePage != null) {
>             return activePage.getImage();
>         }
>         return super.getImage();
>     }
>     public String getTitle() {
>         if (activePage != null) {
>             return activePage.getTitle();
>         }
>         return super.getTitle();
>     }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Springframework-rcp-dev] [Spring-JIRA] Updated: (RCP-182) Support for "no value"

[Lieven D. (JIRA) <no...@sp...>]

     [ http://jira.springframework.org/browse/RCP-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lieven Doclo updated RCP-182:
-----------------------------

    Fix Version/s:     (was: 1.0.2)
                   1.x

> Support for "no value"
> ----------------------
>
>                 Key: RCP-182
>                 URL: http://jira.springframework.org/browse/RCP-182
>             Project: Spring Framework Rich Client Project
>          Issue Type: New Feature
>          Components: Binding System
>            Reporter: Oliver Hutchison
>            Assignee: Oliver Hutchison
>             Fix For: 1.x
>
>
> We need a way to tell a form model that it currently represents "no value". A form with "no value" being a form that does not have a backing object. 
> The question is how do we represent this? I'd imagine we could simply introduce a new class NoValue which when set into a form model causes all of the form model's property values to also become NoValue, you'd then need some logic in the bindings to detect no value so that they can modify themselves to display "nothing" however is appropriate.
> This idea can also be extended to the form's properties .

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira