Menu
▾
▴
springframework-rcp-dev — Spring Rich Client developer list
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(37) |
Jun
(141) |
Jul
(111) |
Aug
(91) |
Sep
(79) |
Oct
(151) |
Nov
(161) |
Dec
(93) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(40) |
Feb
(60) |
Mar
(43) |
Apr
(90) |
May
(31) |
Jun
(114) |
Jul
(35) |
Aug
(112) |
Sep
(305) |
Oct
(151) |
Nov
(122) |
Dec
(103) |
| 2006 |
Jan
(65) |
Feb
(57) |
Mar
(475) |
Apr
(276) |
May
(482) |
Jun
(134) |
Jul
(127) |
Aug
(188) |
Sep
(271) |
Oct
(220) |
Nov
(74) |
Dec
(41) |
| 2007 |
Jan
(121) |
Feb
(50) |
Mar
(36) |
Apr
(11) |
May
(31) |
Jun
(12) |
Jul
(73) |
Aug
(41) |
Sep
(59) |
Oct
(33) |
Nov
(60) |
Dec
(111) |
| 2008 |
Jan
(139) |
Feb
(49) |
Mar
(87) |
Apr
(43) |
May
(10) |
Jun
(25) |
Jul
(114) |
Aug
(17) |
Sep
(25) |
Oct
(199) |
Nov
(94) |
Dec
(45) |
| 2009 |
Jan
(36) |
Feb
(14) |
Mar
(29) |
Apr
(32) |
May
(49) |
Jun
(18) |
Jul
(68) |
Aug
(34) |
Sep
(34) |
Oct
(11) |
Nov
(10) |
Dec
(14) |
| 2010 |
Jan
(35) |
Feb
(12) |
Mar
(23) |
Apr
(17) |
May
(4) |
Jun
(1) |
Jul
(4) |
Aug
|
Sep
(2) |
Oct
|
Nov
(10) |
Dec
|
| 2011 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2012 |
Jan
(2) |
Feb
(1) |
Mar
(8) |
Apr
(3) |
May
|
Jun
|
Jul
(4) |
Aug
(3) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(8) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(3) |
Dec
(4) |
| 2014 |
Jan
(2) |
Feb
(2) |
Mar
(3) |
Apr
(1) |
May
(5) |
Jun
(1) |
Jul
(13) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(15) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-13 07:30:05
|
[ http://jira.springframework.org/browse/RCP-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-170.
---------------------------
Assignee: Jan Hoskens (was: Larry Streepy)
Resolution: Fixed
Added a default instance class that can be set on the formmodel. If not null, this will be used to instantiate an object when null is set, if null the old way will still apply.
Fixed in:
http://spring-rich-c.svn.sourceforge.net/spring-rich-c/?rev=2011&view=rev
(wasn't explicitly mentioned in commit message but it is there)
> AbstractFormModel.reset() needs default constructor on current FormObject
> -------------------------------------------------------------------------
>
> Key: RCP-170
> URL: http://jira.springframework.org/browse/RCP-170
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Binding System
> Reporter: Jan Hoskens
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
> Attachments: patch-RCP-170-fix.txt, patch-RCP-170-test.txt
>
>
> When FormModel is constructed, any Object that has the same properties can be set as FormObject. This object does not need to have a defaultcontructor. Resetting the formModel triggers the creation of a new instance of the current FormObject's class, that may not have a default constructor.
> eg:
> - create form with object Person (has default constructor)
> - set formobject Administrator (has no default constructor, hey no easy way of creating an admin! ;-) )
> - set formobject null or reset -> last formobject Administrator is used to create new instance, but no default constructor is found -> exception
--
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
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-12 16:02:09
|
[ http://jira.springframework.org/browse/RCP-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-323.
---------------------------
Assignee: Jan Hoskens
Resolution: Fixed
Fix Version/s: 1.0.0
Validating event forwarded between parent-child. If parent isn't validating, child form should not validate. When parent is validating, the former state of the child will apply.
Fixed in:
http://spring-rich-c.svn.sourceforge.net/spring-rich-c/?rev=2011&view=rev
> In FormModel, setValidating and setEnabled should invoke child form methods
> ---------------------------------------------------------------------------
>
> Key: RCP-323
> URL: http://jira.springframework.org/browse/RCP-323
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Binding System
> Affects Versions: 0.1.0
> Reporter: Frank Bowers
> Assignee: Jan Hoskens
> Priority: Minor
> Fix For: 1.0.0
>
>
> When the formModel methods setValidating and setEnabled are called the same methods on each of the child forms should also be called otherwise the child forms get out of sync with the parent form.
> setValidating is in DefaultFormModel and setEnabled is in AbstractFormModel
--
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
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-11 15:50:10
|
[ http://jira.springframework.org/browse/RCP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-202.
---------------------------
Assignee: Jan Hoskens (was: Oliver Hutchison)
Resolution: Won't Fix
Fix Version/s: 1.0.0
The convertor is actually a part of the spring-binding library not of Spring Richclient. If the issue is still surfacing while using the latest version of that library, create an issue in the jira of spring-webflow which contains the spring-binding lib.
> Binding to a superclass should be possible
> ------------------------------------------
>
> Key: RCP-202
> URL: http://jira.springframework.org/browse/RCP-202
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Binding System
> Reporter: Geoffrey De Smet
> Assignee: Jan Hoskens
> Priority: Minor
> Fix For: 1.0.0
>
>
> The follow code should called for a conversion from Dog to Animal:
> // Dog extends Animal
> public class TextToAnimal extends AbstractConverter {
> public TextToAnimal () {
> }
> public Class[] getSourceClasses() {
> return new Class[]{String.class}; // subclasses count here
> }
> public Class[] getTargetClasses() {
> return new Class[]{Animal.class}; // subclasses don't count (while they should)
> }
> protected Object doConvert(Object source, Class targetClass) throws Exception {
> // ...
> }
> }
--
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
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-11 15:18:10
|
[ http://jira.springframework.org/browse/RCP-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-309.
---------------------------
Assignee: Jan Hoskens (was: Geoffrey De Smet)
Resolution: Fixed
Fix Version/s: 1.0.0
Added version in website url:
http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1986
As this issue concerns the archiving and the added version doesn't override previous deployments, I consider this as fixed. At the moment of deployment we should point the site url to the new version.
> Archive the website for each release
> ------------------------------------
>
> Key: RCP-309
> URL: http://jira.springframework.org/browse/RCP-309
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Build System
> Affects Versions: 0.1.0
> Reporter: Larry Streepy
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
>
> Original issue:
> 1. Look at the deployed RCP website on sourceforge at http://spring-rich-c.sourceforge.net, nevigate to any of the module, support for example.
> 2. On that page, navigate to the javadocs.
> 3. Note the title Spring richclient support 0.2.0-SNAPSHOT API instead of Spring richclient support 0.1.0-SNAPSHOT API
> New issue:
> Archive the website on every release and place a link in site.xml
--
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
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-11 14:59:07
|
[ http://jira.springframework.org/browse/RCP-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-428.
---------------------------
Assignee: Jan Hoskens
Resolution: Fixed
Fix Version/s: 1.0.0
Fixed in
http://spring-rich-c.svn.sourceforge.net/spring-rich-c/?rev=2007&view=rev
Thanks for the patch
> Problem with comparators in ShuttleSortableTableModel when TableColumnModel is changed
> --------------------------------------------------------------------------------------
>
> Key: RCP-428
> URL: http://jira.springframework.org/browse/RCP-428
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Affects Versions: 0.1.0, 0.2.0, 0.2.1, 1.0.0, 2.0.0
> Environment: Fedora Core 3, JDK 1.5.0_09
> Reporter: Mauro Ransolin
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
> Attachments: RCP-428.patch
>
>
> When the TableColumnModel have its columns changed (added, removed, moved), the Comparators of ShuttleSortableTableModel should be affected to avoid ClassCastException when the objects are sorted.
> Like the ShuttleSortableTableModel and the TableColumnModel can't see each other, the Comparators should be reseted manually.
--
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
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-11 11:03:12
|
[ http://jira.springframework.org/browse/RCP-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-546.
---------------------------
Assignee: Jan Hoskens
Resolution: Fixed
Fix Version/s: 1.0.0
Removed StatusBarCommandGroup reference from ApplicationLifecycleAdvisor and added a note to the upgrading doc.
http://spring-rich-c.svn.sourceforge.net/spring-rich-c/?rev=2005&view=rev
> Document upgrade path for custom StatusBar implementations
> ----------------------------------------------------------
>
> Key: RCP-546
> URL: http://jira.springframework.org/browse/RCP-546
> Project: Spring Framework Rich Client Project
> Issue Type: Task
> Components: Documentation
> Environment: All
> Reporter: Craig Holbrook
> Assignee: Jan Hoskens
> Priority: Minor
> Fix For: 1.0.0
>
>
> In release 0.2.1 the org.springframework.richclient.progress.StatusBarCommandGroup was used for specifying StatusBar implementations. In the latest snapshot, this has now been replaced by the org.springframework.richclient.application.statusbar.StatusBar interface. A concrete implementation of this interface is required by the ApplicationLifecycleAdvisor.
> The documentation needs to be updated to advise the user on the correct upgrade path, and references to the deprecated StatusBarCommandGroup need to also be updated / removed.
--
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
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-10 17:18:05
|
[ http://jira.springframework.org/browse/RCP-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-482.
---------------------------
Assignee: Jan Hoskens
Resolution: Fixed
Fix Version/s: 1.0.0
As we were currently already hosting the 2.1.3 library, I updated our repository to include the 2.1.4 jar. Additionally I've added a comment in the pom's for users to be aware of the license.
> VLDocking throws a NullPointerException, on closing a duplicate window
> ----------------------------------------------------------------------
>
> Key: RCP-482
> URL: http://jira.springframework.org/browse/RCP-482
> Project: Spring Framework Rich Client Project
> Issue Type: Bug
> Components: Application Framework
> Environment: Windows XP SP2, Java 1.5, Spring-RCP 0.3.0-SNAPSHOT current SVN Head (Revision 1785)
> Reporter: Tobias Vogel
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
>
> I integrated VLDocking into my application. So far it works pretty well, besides one thing:
> - I open the application with one (or multiple) views (described in the context by VLDockingViewDescriptor") open
> - I choose the "NewWindowCommand" from the window menu (already integrated in a vanilla rcp project)
> - I then again try to close the window again which leads to the NullPointerException
> The relevant line in the DockViewTitleBar (see stacktrace below) looks like this:
> > tb.target.getDockKey().setNotification(false);
> Seems like the dock keys don't get duplicated while duplicating the windows, as the original window doesn't show this behaviour.
> Here's the stacktrace:
> [ERROR,MessagesDialogExceptionHandler,AWT-EventQueue-0] Uncaught throwable handled
> java.lang.NullPointerException
> at com.vlsolutions.swing.docking.DockViewTitleBar$FocusHighlighter.propertyChange(DockViewTitleBar.java:743)
> at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
> at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:347)
> at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276)
> at java.awt.KeyboardFocusManager.firePropertyChange(KeyboardFocusManager.java:1387)
> at java.awt.KeyboardFocusManager.setGlobalFocusOwner(KeyboardFocusManager.java:525)
> at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:469)
> at java.awt.Component.dispatchEventImpl(Component.java:4282)
> at java.awt.Container.dispatchEventImpl(Container.java:2116)
> at java.awt.Component.dispatchEvent(Component.java:4240)
> at java.awt.KeyboardFocusManager.processCurrentLightweightRequests(KeyboardFocusManager.java:2590)
> at java.awt.KeyboardFocusManager.retargetFocusEvent(KeyboardFocusManager.java:2837)
> at java.awt.Component.dispatchEventImpl(Component.java:4275)
> at java.awt.Container.dispatchEventImpl(Container.java:2116)
> at java.awt.Window.dispatchEventImpl(Window.java:2429)
> at java.awt.Component.dispatchEvent(Component.java:4240)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
> at java.awt.SequencedEvent.dispatch(SequencedEvent.java:98)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
> at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
> at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:177)
> at java.awt.Dialog$1.run(Dialog.java:1039)
> at java.awt.Dialog$3.run(Dialog.java:1091)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.awt.Dialog.show(Dialog.java:1089)
> at javax.swing.JOptionPane.showOptionDialog(JOptionPane.java:853)
> at org.springframework.richclient.exceptionhandling.AbstractDialogExceptionHandler.notifyUserAboutException(AbstractDialogExceptionHandler.java:77)
> at org.springframework.richclient.exceptionhandling.AbstractLoggingExceptionHandler.uncaughtException(AbstractLoggingExceptionHandler.java:48)
> at org.springframework.richclient.exceptionhandling.delegation.AbstractExceptionHandlerDelegate.uncaughtExceptionPurged(AbstractExceptionHandlerDelegate.java:70)
> at org.springframework.richclient.exceptionhandling.delegation.AbstractExceptionHandlerDelegate.uncaughtException(AbstractExceptionHandlerDelegate.java:66)
> at org.springframework.richclient.exceptionhandling.delegation.DelegatingExceptionHandler.uncaughtException(DelegatingExceptionHandler.java:66)
> at org.springframework.richclient.exceptionhandling.AwtExceptionHandlerAdapterHack.handle(AwtExceptionHandlerAdapterHack.java:48)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at java.awt.EventDispatchThread.handleException(EventDispatchThread.java:389)
> at java.awt.EventDispatchThread.processException(EventDispatchThread.java:295)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:287)
> at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
--
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
|
|
From: Fritz R. <fr...@wo...> - 2008-03-10 11:17:46
|
Hi Lieven, I had another try with a new windows system and it works. I think my Apple was not able to do these things due to the strange not published Java6 Version. Thanks for your help. Fritz Am 10.03.2008 um 08:27 schrieb Lieven Doclo: > What was the command you used to build? Did you skip the tests? Did > you > try to build spring-richclient-support separately? > > try a simple 'mvn clean install' on the parent project, it should > work. > > Greetz, > > Lieven > > Fritz Richter schreef: >> Hi, >> when I try to build the newest snapshot, i get the following error: >> >> [INFO] Using default encoding to copy filtered resources. >> Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-resources/0.3.0-SNAPSHOT/spring-richclient-resources-0.3.0-SNAPSHOT-tests.jar >> Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-core/0.3.0-SNAPSHOT/spring-richclient-core-0.3.0-SNAPSHOT-tests.jar >> Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-binding/0.3.0-SNAPSHOT/spring-richclient-binding-0.3.0-SNAPSHOT-tests.jar >> Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-form/0.3.0-SNAPSHOT/spring-richclient-form-0.3.0-SNAPSHOT-tests.jar >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] BUILD ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Failed to resolve artifact. >>> Missing: >>> ---------- >>> 1) org.springframework.richclient:spring-richclient-resources:test- >>> jar:tests:0.3.0-SNAPSHOT >>> >>> Try downloading the file manually from the project website. >>> >>> Then, install it using the command: >>> mvn install:install-file - >>> DgroupId=org.springframework.richclient -DartifactId=spring- >>> richclient-resources -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >>> Dpackaging=test-jar -Dfile=/path/to/file >>> >>> Alternatively, if you host your own repository you can deploy the >>> file there: >>> mvn deploy:deploy-file - >>> DgroupId=org.springframework.richclient -DartifactId=spring- >>> richclient-resources -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >>> Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - >>> DrepositoryId=[id] >>> >>> Path to dependency: >>> 1) org.springframework.richclient:spring-richclient- >>> support:jar:0.3.0-SNAPSHOT >>> 2) org.springframework.richclient:spring-richclient- >>> resources:test-jar:tests:0.3.0-SNAPSHOT >>> >>> 2) org.springframework.richclient:spring-richclient-core:test- >>> jar:tests:0.3.0-SNAPSHOT >>> >>> Try downloading the file manually from the project website. >>> >>> Then, install it using the command: >>> mvn install:install-file - >>> DgroupId=org.springframework.richclient -DartifactId=spring- >>> richclient-core -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >>> Dpackaging=test-jar -Dfile=/path/to/file >>> >>> Alternatively, if you host your own repository you can deploy the >>> file there: >>> mvn deploy:deploy-file - >>> DgroupId=org.springframework.richclient -DartifactId=spring- >>> richclient-core -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >>> Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - >>> DrepositoryId=[id] >>> >>> Path to dependency: >>> 1) org.springframework.richclient:spring-richclient- >>> support:jar:0.3.0-SNAPSHOT >>> 2) org.springframework.richclient:spring-richclient- >>> core:test-jar:tests:0.3.0-SNAPSHOT >>> >>> 3) org.springframework.richclient:spring-richclient-binding:test- >>> jar:tests:0.3.0-SNAPSHOT >>> >>> Try downloading the file manually from the project website. >>> >>> Then, install it using the command: >>> mvn install:install-file - >>> DgroupId=org.springframework.richclient -DartifactId=spring- >>> richclient-binding -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >>> Dpackaging=test-jar -Dfile=/path/to/file >>> >>> Alternatively, if you host your own repository you can deploy the >>> file there: >>> mvn deploy:deploy-file - >>> DgroupId=org.springframework.richclient -DartifactId=spring- >>> richclient-binding -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >>> Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - >>> DrepositoryId=[id] >>> >>> Path to dependency: >>> 1) org.springframework.richclient:spring-richclient- >>> support:jar:0.3.0-SNAPSHOT >>> 2) org.springframework.richclient:spring-richclient- >>> binding:test-jar:tests:0.3.0-SNAPSHOT >>> >>> 4) org.springframework.richclient:spring-richclient-form:test- >>> jar:tests:0.3.0-SNAPSHOT >>> >>> Try downloading the file manually from the project website. >>> >>> Then, install it using the command: >>> mvn install:install-file - >>> DgroupId=org.springframework.richclient -DartifactId=spring- >>> richclient-form -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >>> Dpackaging=test-jar -Dfile=/path/to/file >>> >>> Alternatively, if you host your own repository you can deploy the >>> file there: >>> mvn deploy:deploy-file - >>> DgroupId=org.springframework.richclient -DartifactId=spring- >>> richclient-form -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >>> Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - >>> DrepositoryId=[id] >>> >>> Path to dependency: >>> 1) org.springframework.richclient:spring-richclient- >>> support:jar:0.3.0-SNAPSHOT >>> 2) org.springframework.richclient:spring-richclient- >>> form:test-jar:tests:0.3.0-SNAPSHOT >>> >>> ---------- >>> 4 required artifacts are missing. >>> >>> for artifact: >>> org.springframework.richclient:spring-richclient-support:jar:0.3.0- >>> SNAPSHOT >> >> What can I do? >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev |
|
From: Lieven D. <ld...@sc...> - 2008-03-10 07:27:54
|
What was the command you used to build? Did you skip the tests? Did you try to build spring-richclient-support separately? try a simple 'mvn clean install' on the parent project, it should work. Greetz, Lieven Fritz Richter schreef: > Hi, > when I try to build the newest snapshot, i get the following error: > > [INFO] Using default encoding to copy filtered resources. > Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-resources/0.3.0-SNAPSHOT/spring-richclient-resources-0.3.0-SNAPSHOT-tests.jar > Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-core/0.3.0-SNAPSHOT/spring-richclient-core-0.3.0-SNAPSHOT-tests.jar > Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-binding/0.3.0-SNAPSHOT/spring-richclient-binding-0.3.0-SNAPSHOT-tests.jar > Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-form/0.3.0-SNAPSHOT/spring-richclient-form-0.3.0-SNAPSHOT-tests.jar > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. >> Missing: >> ---------- >> 1) org.springframework.richclient:spring-richclient-resources:test- >> jar:tests:0.3.0-SNAPSHOT >> >> Try downloading the file manually from the project website. >> >> Then, install it using the command: >> mvn install:install-file - >> DgroupId=org.springframework.richclient -DartifactId=spring- >> richclient-resources -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >> Dpackaging=test-jar -Dfile=/path/to/file >> >> Alternatively, if you host your own repository you can deploy the >> file there: >> mvn deploy:deploy-file - >> DgroupId=org.springframework.richclient -DartifactId=spring- >> richclient-resources -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >> Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - >> DrepositoryId=[id] >> >> Path to dependency: >> 1) org.springframework.richclient:spring-richclient- >> support:jar:0.3.0-SNAPSHOT >> 2) org.springframework.richclient:spring-richclient- >> resources:test-jar:tests:0.3.0-SNAPSHOT >> >> 2) org.springframework.richclient:spring-richclient-core:test- >> jar:tests:0.3.0-SNAPSHOT >> >> Try downloading the file manually from the project website. >> >> Then, install it using the command: >> mvn install:install-file - >> DgroupId=org.springframework.richclient -DartifactId=spring- >> richclient-core -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >> Dpackaging=test-jar -Dfile=/path/to/file >> >> Alternatively, if you host your own repository you can deploy the >> file there: >> mvn deploy:deploy-file - >> DgroupId=org.springframework.richclient -DartifactId=spring- >> richclient-core -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >> Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - >> DrepositoryId=[id] >> >> Path to dependency: >> 1) org.springframework.richclient:spring-richclient- >> support:jar:0.3.0-SNAPSHOT >> 2) org.springframework.richclient:spring-richclient- >> core:test-jar:tests:0.3.0-SNAPSHOT >> >> 3) org.springframework.richclient:spring-richclient-binding:test- >> jar:tests:0.3.0-SNAPSHOT >> >> Try downloading the file manually from the project website. >> >> Then, install it using the command: >> mvn install:install-file - >> DgroupId=org.springframework.richclient -DartifactId=spring- >> richclient-binding -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >> Dpackaging=test-jar -Dfile=/path/to/file >> >> Alternatively, if you host your own repository you can deploy the >> file there: >> mvn deploy:deploy-file - >> DgroupId=org.springframework.richclient -DartifactId=spring- >> richclient-binding -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >> Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - >> DrepositoryId=[id] >> >> Path to dependency: >> 1) org.springframework.richclient:spring-richclient- >> support:jar:0.3.0-SNAPSHOT >> 2) org.springframework.richclient:spring-richclient- >> binding:test-jar:tests:0.3.0-SNAPSHOT >> >> 4) org.springframework.richclient:spring-richclient-form:test- >> jar:tests:0.3.0-SNAPSHOT >> >> Try downloading the file manually from the project website. >> >> Then, install it using the command: >> mvn install:install-file - >> DgroupId=org.springframework.richclient -DartifactId=spring- >> richclient-form -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >> Dpackaging=test-jar -Dfile=/path/to/file >> >> Alternatively, if you host your own repository you can deploy the >> file there: >> mvn deploy:deploy-file - >> DgroupId=org.springframework.richclient -DartifactId=spring- >> richclient-form -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - >> Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - >> DrepositoryId=[id] >> >> Path to dependency: >> 1) org.springframework.richclient:spring-richclient- >> support:jar:0.3.0-SNAPSHOT >> 2) org.springframework.richclient:spring-richclient- >> form:test-jar:tests:0.3.0-SNAPSHOT >> >> ---------- >> 4 required artifacts are missing. >> >> for artifact: >> org.springframework.richclient:spring-richclient-support:jar:0.3.0- >> SNAPSHOT > > What can I do? > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ |
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-08 19:09:08
|
[ http://jira.springframework.org/browse/RCP-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-331.
---------------------------
Assignee: Jan Hoskens (was: Geoffrey De Smet)
Resolution: Fixed
Artifacts removed from the Spring RCP repository as they are available in the general maven repository.
> activation and mail are now available in Ibiblio
> ------------------------------------------------
>
> Key: RCP-331
> URL: http://jira.springframework.org/browse/RCP-331
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Components: Build System
> Affects Versions: 0.1.0
> Reporter: Geoffrey De Smet
> Assignee: Jan Hoskens
> Priority: Minor
> Fix For: 1.0.0
>
>
> The two jars that were uploaded to Ibiblio:
> <dependency>
> <groupid>javax.activation</groupid>
> <artifactid>activation</artifactid>
> <version>1.1</version>
> </dependency>
> <dependency>
> <groupid>javax.mail</groupid>
> <artifactid>mail</artifactid>
> <version>1.4</version>
> </dependency>
> We probably no longer need them in our own repo.
--
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
|
|
From: Fritz R. <fr...@wo...> - 2008-03-07 15:32:16
|
Hi, when I try to build the newest snapshot, i get the following error: [INFO] Using default encoding to copy filtered resources. Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-resources/0.3.0-SNAPSHOT/spring-richclient-resources-0.3.0-SNAPSHOT-tests.jar Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-core/0.3.0-SNAPSHOT/spring-richclient-core-0.3.0-SNAPSHOT-tests.jar Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-binding/0.3.0-SNAPSHOT/spring-richclient-binding-0.3.0-SNAPSHOT-tests.jar Downloading: http://spring-rich-c.sourceforge.net/maven2snapshotrepository/org/springframework/richclient/spring-richclient-form/0.3.0-SNAPSHOT/spring-richclient-form-0.3.0-SNAPSHOT-tests.jar [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. > > Missing: > ---------- > 1) org.springframework.richclient:spring-richclient-resources:test- > jar:tests:0.3.0-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file - > DgroupId=org.springframework.richclient -DartifactId=spring- > richclient-resources -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - > Dpackaging=test-jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the > file there: > mvn deploy:deploy-file - > DgroupId=org.springframework.richclient -DartifactId=spring- > richclient-resources -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - > Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - > DrepositoryId=[id] > > Path to dependency: > 1) org.springframework.richclient:spring-richclient- > support:jar:0.3.0-SNAPSHOT > 2) org.springframework.richclient:spring-richclient- > resources:test-jar:tests:0.3.0-SNAPSHOT > > 2) org.springframework.richclient:spring-richclient-core:test- > jar:tests:0.3.0-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file - > DgroupId=org.springframework.richclient -DartifactId=spring- > richclient-core -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - > Dpackaging=test-jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the > file there: > mvn deploy:deploy-file - > DgroupId=org.springframework.richclient -DartifactId=spring- > richclient-core -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - > Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - > DrepositoryId=[id] > > Path to dependency: > 1) org.springframework.richclient:spring-richclient- > support:jar:0.3.0-SNAPSHOT > 2) org.springframework.richclient:spring-richclient- > core:test-jar:tests:0.3.0-SNAPSHOT > > 3) org.springframework.richclient:spring-richclient-binding:test- > jar:tests:0.3.0-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file - > DgroupId=org.springframework.richclient -DartifactId=spring- > richclient-binding -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - > Dpackaging=test-jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the > file there: > mvn deploy:deploy-file - > DgroupId=org.springframework.richclient -DartifactId=spring- > richclient-binding -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - > Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - > DrepositoryId=[id] > > Path to dependency: > 1) org.springframework.richclient:spring-richclient- > support:jar:0.3.0-SNAPSHOT > 2) org.springframework.richclient:spring-richclient- > binding:test-jar:tests:0.3.0-SNAPSHOT > > 4) org.springframework.richclient:spring-richclient-form:test- > jar:tests:0.3.0-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file - > DgroupId=org.springframework.richclient -DartifactId=spring- > richclient-form -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - > Dpackaging=test-jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the > file there: > mvn deploy:deploy-file - > DgroupId=org.springframework.richclient -DartifactId=spring- > richclient-form -Dversion=0.3.0-SNAPSHOT -Dclassifier=tests - > Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] - > DrepositoryId=[id] > > Path to dependency: > 1) org.springframework.richclient:spring-richclient- > support:jar:0.3.0-SNAPSHOT > 2) org.springframework.richclient:spring-richclient- > form:test-jar:tests:0.3.0-SNAPSHOT > > ---------- > 4 required artifacts are missing. > > for artifact: > org.springframework.richclient:spring-richclient-support:jar:0.3.0- > SNAPSHOT What can I do? |
|
From: Jim M. <jim...@sp...> - 2008-03-06 19:00:16
|
Fyi: I contacted Greg Schott, our VP of Marketing: Thanks Jim. Yes, we are all over it. We plan to get all the sites re-skinned in the next 8 weeks. The color blind issue is new. Greg -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Lieven Doclo Sent: Thursday, March 06, 2008 10:06 AM To: spr...@li... Subject: Re: [Springframework-rcp-dev] new skin for the website You're totally right. I never disagreed with the fact that the Spring products' sites should look alike. I just don't agree with the current look. Spring Richclient is all about looks and at the moment, it looks way nicer than its website :). I did know 1.0 was going to be a quiet launch (although I don't believe a 1.0 release of a Spring-branded product will go unnoticed nor quiet). And people will be enticed to use Spring RC (at least I hope so, I know people who haven't been able to sell Spring RC to their management due to its 0.x status), even just to have a hint on what's coming with Spring Desktop. Spring RC's success (or, let's hope not, lack of) after its 1.0 release will felt by Spring Desktop. Just for that reason I'd want to revamp the site. You only get one chance at a first impression. Secondly, I really hope after the release, Spring RCP will go in a higher gear, community wise, including me. And again, the entry point for the community... is the website. I was fortunate to have the project lead as a colleague, but when you're trying to find out how RCP works by the website, it's a lot harder to learn and almost impossible to master. But it's great that you'll raise the issue further up the ladder. I appreciate it a lot. I use Spring RC daily, and try to promote it wherever and whenever I can. I am looking forward to October. Kind regards, - Lieven Doclo Java Developer @ Schaubroeck Jim Moore schreef: > Lieven, it does look nicer, and I agree about the importance of the look > of the website. Geoffrey's also right, though, that all the "Spring" > products really should look the same. To resolve that conflict, (and > the discrepancy in looks between projects) I'm raising the issue within > SpringSource about getting the "main" look updated as well. (As a > side-note, Acegi wasn't officially "Spring" which is why Spring doesn't > appear in the name and it doesn't use the Spring look. But when Spring > Security 2 is released, it will have the Spring look.) > > > For clarification: Spring Richclient 1.0 is going to be a "quiet > launch", just to get a stable version out there for the existing code > base. It's going straight into maintenance mode and is not meant to > entice new people to the platform. The big "marketing" push is meant > for Spring Desktop 1.0, which will be released with Spring 3.0 and a > number of other Spring products in October. > > > -Jim Moore > SpringSource Senior Consultant (and Spring Rich/Desktop liason) > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On Behalf > Of Lieven Doclo > > Sent: Thursday, March 06, 2008 5:21 AM > To: spr...@li... > Subject: Re: [Springframework-rcp-dev] new skin for the website > > Thanks Peter! > > @Geoffrey: > > Since almost none of the other spring projects are using maven to > generate their site (I just checked, except for Acegi, of whom I think > they're using Maven, and they're not using the "Spring" sking). > > I have a firm belief that a website is a 'make-or-break' thing when it > comes to a product (especially a first launch). Someone new to RCP > entering our current site isn't overwhelmed with a 'Nice!' feeling. The > site is the ad for RCP, and bad ads don't sell products, even if the > product is good. I have the same feeling about the main Spring site, but > they can afford it so to speak. RCP, for it's first release, can't > afford that. We need all the publicity we can get. > > When Spring RCP 1.0 is announced, a lot more people will come to the > site. A that point, appearance does matter. > > But you're right about one thing, the main Spring site is in need for > refurbishing... > > Greetz, > > Lieven > > Geoffrey De Smet schreef: > > Looks great, but shouldn't this be fixed upstream? > > At the moment, we use the maven-spring-skin, just like all the other > > spring projects. > > > http://www.mvnrepository.com/artifact/org.springframework.maven.skins/maven- spring-skin > > > That skin could definitly be improved, for example with those changes. > > > > -0 as I don't think we should deviate from the general spring skin site > > convention. > > > > With kind regards, > > Geoffrey De Smet > > > > Peter De Bruycker schreef: > >> looks great! > >> > >> regards, > >> > >> Peter > >> > >> On 3/6/08, *Lieven Doclo* <ld...@sc... > >> <mailto:ld...@sc...>> wrote: > >> > >> I managed to put up part of the site online, just to give you an > idea: > >> > >> http://www.doclo.be/spring/ > >> > >> Yes, I know there are still bugs, but they'll be fixed ASAP :). > >> > >> Greetz, > >> > >> Lieven > >> > >> > >> Lieven Doclo schreef: > >> > >> > Hi everybody, > >> > > >> > Since Spring RCP is heading for it's first release, perhaps it's > >> time to > >> > change the way the site looks too. > >> > Granted, the current look resembles the look of the Spring > Framework > >> > site, but let's face it, that site isn't going to win any beauty > >> contests. > >> > Therefor I created a maven skin for the current site that > looks a bit > >> > more modern and keeps the following in mind: > >> > - sites should be totally viewable on 1024x768 screens, the > >> current site > >> > is not (screenshots in the pages result in a larger page) > >> > - sites should not stretch horizontally (see SpringSource site) > >> > - clear visual signs for links that take you outside the website > >> > > >> > There still is some work to be done on the skin (the > powered-by icons > >> > are gone and other bugs). I haven't gotten around to uploading a > >> sample > >> > (my ftp isn't working correctly), but I did post a screenshot > on my > >> > Picasa site: > >> > > >> > http://picasaweb.google.nl/doclolieven/SpringRCP > >> > > >> > Tell me what you think. I'll put up a sample site ASAP. The > >> website is > >> > the postersign for RCP, the first thing people see, and a > modern site > >> > helps with the image of the product. The current site... > well, let's > >> > just say there's room for improvement, shall we :). > >> > > >> > Grtz, > >> > > >> > Lieven > >> > > >> > > >> > > >> > ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > >> > >> > ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Springframework-rcp-dev mailing list > >> Spr...@li... > >> <mailto:Spr...@li...> > >> > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > >> > >> > >> > >> > ------------------------------------------------------------------------ > >> > >> > ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > >> > >> > ------------------------------------------------------------------------ > >> > >> _______________________________________________ > >> Springframework-rcp-dev mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Springframework-rcp-dev mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev |
|
From: Lieven D. <ld...@sc...> - 2008-03-06 15:07:01
|
You're totally right. I never disagreed with the fact that the Spring products' sites should look alike. I just don't agree with the current look. Spring Richclient is all about looks and at the moment, it looks way nicer than its website :). I did know 1.0 was going to be a quiet launch (although I don't believe a 1.0 release of a Spring-branded product will go unnoticed nor quiet). And people will be enticed to use Spring RC (at least I hope so, I know people who haven't been able to sell Spring RC to their management due to its 0.x status), even just to have a hint on what's coming with Spring Desktop. Spring RC's success (or, let's hope not, lack of) after its 1.0 release will felt by Spring Desktop. Just for that reason I'd want to revamp the site. You only get one chance at a first impression. Secondly, I really hope after the release, Spring RCP will go in a higher gear, community wise, including me. And again, the entry point for the community... is the website. I was fortunate to have the project lead as a colleague, but when you're trying to find out how RCP works by the website, it's a lot harder to learn and almost impossible to master. But it's great that you'll raise the issue further up the ladder. I appreciate it a lot. I use Spring RC daily, and try to promote it wherever and whenever I can. I am looking forward to October. Kind regards, - Lieven Doclo Java Developer @ Schaubroeck Jim Moore schreef: > Lieven, it does look nicer, and I agree about the importance of the look > of the website. Geoffrey's also right, though, that all the "Spring" > products really should look the same. To resolve that conflict, (and > the discrepancy in looks between projects) I'm raising the issue within > SpringSource about getting the "main" look updated as well. (As a > side-note, Acegi wasn't officially "Spring" which is why Spring doesn't > appear in the name and it doesn't use the Spring look. But when Spring > Security 2 is released, it will have the Spring look.) > > > For clarification: Spring Richclient 1.0 is going to be a "quiet > launch", just to get a stable version out there for the existing code > base. It's going straight into maintenance mode and is not meant to > entice new people to the platform. The big "marketing" push is meant > for Spring Desktop 1.0, which will be released with Spring 3.0 and a > number of other Spring products in October. > > > -Jim Moore > SpringSource Senior Consultant (and Spring Rich/Desktop liason) > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On Behalf > Of Lieven Doclo > > Sent: Thursday, March 06, 2008 5:21 AM > To: spr...@li... > Subject: Re: [Springframework-rcp-dev] new skin for the website > > Thanks Peter! > > @Geoffrey: > > Since almost none of the other spring projects are using maven to > generate their site (I just checked, except for Acegi, of whom I think > they're using Maven, and they're not using the "Spring" sking). > > I have a firm belief that a website is a 'make-or-break' thing when it > comes to a product (especially a first launch). Someone new to RCP > entering our current site isn't overwhelmed with a 'Nice!' feeling. The > site is the ad for RCP, and bad ads don't sell products, even if the > product is good. I have the same feeling about the main Spring site, but > they can afford it so to speak. RCP, for it's first release, can't > afford that. We need all the publicity we can get. > > When Spring RCP 1.0 is announced, a lot more people will come to the > site. A that point, appearance does matter. > > But you're right about one thing, the main Spring site is in need for > refurbishing... > > Greetz, > > Lieven > > Geoffrey De Smet schreef: > > Looks great, but shouldn't this be fixed upstream? > > At the moment, we use the maven-spring-skin, just like all the other > > spring projects. > > > http://www.mvnrepository.com/artifact/org.springframework.maven.skins/maven-spring-skin > > > That skin could definitly be improved, for example with those changes. > > > > -0 as I don't think we should deviate from the general spring skin site > > convention. > > > > With kind regards, > > Geoffrey De Smet > > > > Peter De Bruycker schreef: > >> looks great! > >> > >> regards, > >> > >> Peter > >> > >> On 3/6/08, *Lieven Doclo* <ld...@sc... > >> <mailto:ld...@sc...>> wrote: > >> > >> I managed to put up part of the site online, just to give you an > idea: > >> > >> http://www.doclo.be/spring/ > >> > >> Yes, I know there are still bugs, but they'll be fixed ASAP :). > >> > >> Greetz, > >> > >> Lieven > >> > >> > >> Lieven Doclo schreef: > >> > >> > Hi everybody, > >> > > >> > Since Spring RCP is heading for it's first release, perhaps it's > >> time to > >> > change the way the site looks too. > >> > Granted, the current look resembles the look of the Spring > Framework > >> > site, but let's face it, that site isn't going to win any beauty > >> contests. > >> > Therefor I created a maven skin for the current site that > looks a bit > >> > more modern and keeps the following in mind: > >> > - sites should be totally viewable on 1024x768 screens, the > >> current site > >> > is not (screenshots in the pages result in a larger page) > >> > - sites should not stretch horizontally (see SpringSource site) > >> > - clear visual signs for links that take you outside the website > >> > > >> > There still is some work to be done on the skin (the > powered-by icons > >> > are gone and other bugs). I haven't gotten around to uploading a > >> sample > >> > (my ftp isn't working correctly), but I did post a screenshot > on my > >> > Picasa site: > >> > > >> > http://picasaweb.google.nl/doclolieven/SpringRCP > >> > > >> > Tell me what you think. I'll put up a sample site ASAP. The > >> website is > >> > the postersign for RCP, the first thing people see, and a > modern site > >> > helps with the image of the product. The current site... > well, let's > >> > just say there's room for improvement, shall we :). > >> > > >> > Grtz, > >> > > >> > Lieven > >> > > >> > > >> > > >> > ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > >> > >> > ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Springframework-rcp-dev mailing list > >> Spr...@li... > >> <mailto:Spr...@li...> > >> > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > >> > >> > >> > >> > ------------------------------------------------------------------------ > >> > >> > ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > >> > >> > ------------------------------------------------------------------------ > >> > >> _______________________________________________ > >> Springframework-rcp-dev mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev |
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-06 14:31:05
|
[ http://jira.springframework.org/browse/RCP-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-542.
---------------------------
Assignee: Jan Hoskens
Resolution: Fixed
Fix Version/s: 1.0.0
Fixed in:
http://spring-rich-c.svn.sourceforge.net/spring-rich-c/?rev=1999&view=rev
Thanks for the patch.
> Create more advanced toolbars by adding components.
> ---------------------------------------------------
>
> Key: RCP-542
> URL: http://jira.springframework.org/browse/RCP-542
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Components: Command System
> Reporter: Nils Olsson
> Assignee: Jan Hoskens
> Priority: Minor
> Fix For: 1.0.0
>
> Attachments: RCP-542.patch
>
>
> By adding this patch it will be possible to add Components to the toolbar through a CommandGroupFactoryBean.
> <bean id="toolBar" class="org.springframework.richclient.command.CommandGroupFactoryBean">
> <property name="members">
> <list>
> <ref bean="yourComponent"/>
> </list>
> </property>
> </bean>
--
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
|
|
From: Jim M. <jim...@sp...> - 2008-03-06 12:52:54
|
RE: [Springframework-rcp-dev] new skin for the website Lieven, it does look nicer, and I agree about the importance of the look of the website. Geoffrey's also right, though, that all the "Spring" products really should look the same. To resolve that conflict, (and the discrepancy in looks between projects) I'm raising the issue within SpringSource about getting the "main" look updated as well. (As a side-note, Acegi wasn't officially "Spring" which is why Spring doesn't appear in the name and it doesn't use the Spring look. But when Spring Security 2 is released, it will have the Spring look.) For clarification: Spring Richclient 1.0 is going to be a "quiet launch", just to get a stable version out there for the existing code base. It's going straight into maintenance mode and is not meant to entice new people to the platform. The big "marketing" push is meant for Spring Desktop 1.0, which will be released with Spring 3.0 and a number of other Spring products in October. -Jim Moore SpringSource Senior Consultant (and Spring Rich/Desktop liason) -----Original Message----- From: spr...@li... [ mailto:spr...@li... ] On Behalf Of Lieven Doclo Sent: Thursday, March 06, 2008 5:21 AM To: spr...@li... Subject: Re: [Springframework-rcp-dev] new skin for the website Thanks Peter! @Geoffrey: Since almost none of the other spring projects are using maven to generate their site (I just checked, except for Acegi, of whom I think they're using Maven, and they're not using the "Spring" sking). I have a firm belief that a website is a 'make-or-break' thing when it comes to a product (especially a first launch). Someone new to RCP entering our current site isn't overwhelmed with a 'Nice!' feeling. The site is the ad for RCP, and bad ads don't sell products, even if the product is good. I have the same feeling about the main Spring site, but they can afford it so to speak. RCP, for it's first release, can't afford that. We need all the publicity we can get. When Spring RCP 1.0 is announced, a lot more people will come to the site. A that point, appearance does matter. But you're right about one thing, the main Spring site is in need for refurbishing... Greetz, Lieven Geoffrey De Smet schreef: > Looks great, but shouldn't this be fixed upstream? > At the moment, we use the maven-spring-skin, just like all the other > spring projects. > http://www.mvnrepository.com/artifact/org.springframework.maven.skins/maven-spring-skin > That skin could definitly be improved, for example with those changes. > > -0 as I don't think we should deviate from the general spring skin site > convention. > > With kind regards, > Geoffrey De Smet > > Peter De Bruycker schreef: >> looks great! >> >> regards, >> >> Peter >> >> On 3/6/08, *Lieven Doclo* <ld...@sc... >> < mailto:ld...@sc... >> wrote: >> >> I managed to put up part of the site online, just to give you an idea: >> >> http://www.doclo.be/spring/ >> >> Yes, I know there are still bugs, but they'll be fixed ASAP :). >> >> Greetz, >> >> Lieven >> >> >> Lieven Doclo schreef: >> >> > Hi everybody, >> > >> > Since Spring RCP is heading for it's first release, perhaps it's >> time to >> > change the way the site looks too. >> > Granted, the current look resembles the look of the Spring Framework >> > site, but let's face it, that site isn't going to win any beauty >> contests. >> > Therefor I created a maven skin for the current site that looks a bit >> > more modern and keeps the following in mind: >> > - sites should be totally viewable on 1024x768 screens, the >> current site >> > is not (screenshots in the pages result in a larger page) >> > - sites should not stretch horizontally (see SpringSource site) >> > - clear visual signs for links that take you outside the website >> > >> > There still is some work to be done on the skin (the powered-by icons >> > are gone and other bugs). I haven't gotten around to uploading a >> sample >> > (my ftp isn't working correctly), but I did post a screenshot on my >> > Picasa site: >> > >> > http://picasaweb.google.nl/doclolieven/SpringRCP >> > >> > Tell me what you think. I'll put up a sample site ASAP. The >> website is >> > the postersign for RCP, the first thing people see, and a modern site >> > helps with the image of the product. The current site... well, let's >> > just say there's room for improvement, shall we :). >> > >> > Grtz, >> > >> > Lieven >> > >> > >> > >> ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Springframework-rcp-dev mailing list >> Spr...@li... >> < mailto:Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev >> >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Springframework-rcp-dev mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Springframework-rcp-dev mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev |
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-06 12:21:09
|
[ http://jira.springframework.org/browse/RCP-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-508.
---------------------------
Assignee: Jan Hoskens (was: Peter De Bruycker)
Resolution: Fixed
Fix Version/s: 1.0.0
Fixed in
http://spring-rich-c.svn.sourceforge.net/spring-rich-c/?rev=1998&view=rev
Thanks for the patch
> Improve configurability of toolbar creation
> -------------------------------------------
>
> Key: RCP-508
> URL: http://jira.springframework.org/browse/RCP-508
> Project: Spring Framework Rich Client Project
> Issue Type: Improvement
> Components: Command System
> Affects Versions: 0.2.1
> Reporter: Jonny Wray
> Assignee: Jan Hoskens
> Fix For: 1.0.0
>
> Attachments: spring-rcp-support-relative.patch.txt, spring-rcp-support.patch
>
>
> In attempting to integrate the Jide action framework into Spring RCP I've come across a number of places where the configuration of the toolbars could be improved.
--
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
|
|
From: Lieven D. <ld...@sc...> - 2008-03-06 12:17:38
|
Granted, you got me there, but even then there are differences: - top text is different font and alignment - spring-ws has powered-by icons, batch has none (this is a part of the skin, so I doubt if they use the same) - menu naming is completely different If you want, I can whip up a variant that uses the same colours as the current spring site. By the way, did you know 5% of the male population has problem seeing the colour green, and 1% percent can't see green at all? So a green skin is an overall bad idea... Grtz, :ldo: Geoffrey De Smet schreef: > These use it too :) > http://static.springframework.org/spring-batch/ > http://static.springframework.org/spring-ws/site/ > > With kind regards, > Geoffrey De Smet > > Lieven Doclo schreef: >> Thanks Peter! >> >> @Geoffrey: >> >> Since almost none of the other spring projects are using maven to >> generate their site (I just checked, except for Acegi, of whom I think >> they're using Maven, and they're not using the "Spring" sking). >> >> I have a firm belief that a website is a 'make-or-break' thing when it >> comes to a product (especially a first launch). Someone new to RCP >> entering our current site isn't overwhelmed with a 'Nice!' feeling. The >> site is the ad for RCP, and bad ads don't sell products, even if the >> product is good. I have the same feeling about the main Spring site, but >> they can afford it so to speak. RCP, for it's first release, can't >> afford that. We need all the publicity we can get. >> >> When Spring RCP 1.0 is announced, a lot more people will come to the >> site. A that point, appearance does matter. >> >> But you're right about one thing, the main Spring site is in need for >> refurbishing... >> >> Greetz, >> >> Lieven >> >> Geoffrey De Smet schreef: >>> Looks great, but shouldn't this be fixed upstream? >>> At the moment, we use the maven-spring-skin, just like all the other >>> spring projects. >>> http://www.mvnrepository.com/artifact/org.springframework.maven.skins/maven-spring-skin >>> That skin could definitly be improved, for example with those changes. >>> >>> -0 as I don't think we should deviate from the general spring skin site >>> convention. >>> >>> With kind regards, >>> Geoffrey De Smet >>> >>> Peter De Bruycker schreef: >>>> looks great! >>>> >>>> regards, >>>> >>>> Peter >>>> >>>> On 3/6/08, *Lieven Doclo* <ld...@sc... >>>> <mailto:ld...@sc...>> wrote: >>>> >>>> I managed to put up part of the site online, just to give you an idea: >>>> >>>> http://www.doclo.be/spring/ >>>> >>>> Yes, I know there are still bugs, but they'll be fixed ASAP :). >>>> >>>> Greetz, >>>> >>>> Lieven >>>> >>>> >>>> Lieven Doclo schreef: >>>> >>>> > Hi everybody, >>>> > >>>> > Since Spring RCP is heading for it's first release, perhaps it's >>>> time to >>>> > change the way the site looks too. >>>> > Granted, the current look resembles the look of the Spring Framework >>>> > site, but let's face it, that site isn't going to win any beauty >>>> contests. >>>> > Therefor I created a maven skin for the current site that looks a bit >>>> > more modern and keeps the following in mind: >>>> > - sites should be totally viewable on 1024x768 screens, the >>>> current site >>>> > is not (screenshots in the pages result in a larger page) >>>> > - sites should not stretch horizontally (see SpringSource site) >>>> > - clear visual signs for links that take you outside the website >>>> > >>>> > There still is some work to be done on the skin (the powered-by icons >>>> > are gone and other bugs). I haven't gotten around to uploading a >>>> sample >>>> > (my ftp isn't working correctly), but I did post a screenshot on my >>>> > Picasa site: >>>> > >>>> > http://picasaweb.google.nl/doclolieven/SpringRCP >>>> > >>>> > Tell me what you think. I'll put up a sample site ASAP. The >>>> website is >>>> > the postersign for RCP, the first thing people see, and a modern site >>>> > helps with the image of the product. The current site... well, let's >>>> > just say there's room for improvement, shall we :). >>>> > >>>> > Grtz, >>>> > >>>> > Lieven >>>> > >>>> > >>>> > >>>> ------------------------------------------------------------------------- >>>> > This SF.net email is sponsored by: Microsoft >>>> > Defy all challenges. Microsoft(R) Visual Studio 2008. >>>> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.net email is sponsored by: Microsoft >>>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> _______________________________________________ >>>> Springframework-rcp-dev mailing list >>>> Spr...@li... >>>> <mailto:Spr...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev >>>> >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.net email is sponsored by: Microsoft >>>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Springframework-rcp-dev mailing list >>>> Spr...@li... >>>> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ |
|
From: Geoffrey De S. <ge0...@gm...> - 2008-03-06 11:10:24
|
These use it too :) http://static.springframework.org/spring-batch/ http://static.springframework.org/spring-ws/site/ With kind regards, Geoffrey De Smet Lieven Doclo schreef: > Thanks Peter! > > @Geoffrey: > > Since almost none of the other spring projects are using maven to > generate their site (I just checked, except for Acegi, of whom I think > they're using Maven, and they're not using the "Spring" sking). > > I have a firm belief that a website is a 'make-or-break' thing when it > comes to a product (especially a first launch). Someone new to RCP > entering our current site isn't overwhelmed with a 'Nice!' feeling. The > site is the ad for RCP, and bad ads don't sell products, even if the > product is good. I have the same feeling about the main Spring site, but > they can afford it so to speak. RCP, for it's first release, can't > afford that. We need all the publicity we can get. > > When Spring RCP 1.0 is announced, a lot more people will come to the > site. A that point, appearance does matter. > > But you're right about one thing, the main Spring site is in need for > refurbishing... > > Greetz, > > Lieven > > Geoffrey De Smet schreef: >> Looks great, but shouldn't this be fixed upstream? >> At the moment, we use the maven-spring-skin, just like all the other >> spring projects. >> http://www.mvnrepository.com/artifact/org.springframework.maven.skins/maven-spring-skin >> That skin could definitly be improved, for example with those changes. >> >> -0 as I don't think we should deviate from the general spring skin site >> convention. >> >> With kind regards, >> Geoffrey De Smet >> >> Peter De Bruycker schreef: >>> looks great! >>> >>> regards, >>> >>> Peter >>> >>> On 3/6/08, *Lieven Doclo* <ld...@sc... >>> <mailto:ld...@sc...>> wrote: >>> >>> I managed to put up part of the site online, just to give you an idea: >>> >>> http://www.doclo.be/spring/ >>> >>> Yes, I know there are still bugs, but they'll be fixed ASAP :). >>> >>> Greetz, >>> >>> Lieven >>> >>> >>> Lieven Doclo schreef: >>> >>> > Hi everybody, >>> > >>> > Since Spring RCP is heading for it's first release, perhaps it's >>> time to >>> > change the way the site looks too. >>> > Granted, the current look resembles the look of the Spring Framework >>> > site, but let's face it, that site isn't going to win any beauty >>> contests. >>> > Therefor I created a maven skin for the current site that looks a bit >>> > more modern and keeps the following in mind: >>> > - sites should be totally viewable on 1024x768 screens, the >>> current site >>> > is not (screenshots in the pages result in a larger page) >>> > - sites should not stretch horizontally (see SpringSource site) >>> > - clear visual signs for links that take you outside the website >>> > >>> > There still is some work to be done on the skin (the powered-by icons >>> > are gone and other bugs). I haven't gotten around to uploading a >>> sample >>> > (my ftp isn't working correctly), but I did post a screenshot on my >>> > Picasa site: >>> > >>> > http://picasaweb.google.nl/doclolieven/SpringRCP >>> > >>> > Tell me what you think. I'll put up a sample site ASAP. The >>> website is >>> > the postersign for RCP, the first thing people see, and a modern site >>> > helps with the image of the product. The current site... well, let's >>> > just say there's room for improvement, shall we :). >>> > >>> > Grtz, >>> > >>> > Lieven >>> > >>> > >>> > >>> ------------------------------------------------------------------------- >>> > This SF.net email is sponsored by: Microsoft >>> > Defy all challenges. Microsoft(R) Visual Studio 2008. >>> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Springframework-rcp-dev mailing list >>> Spr...@li... >>> <mailto:Spr...@li...> >>> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Springframework-rcp-dev mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ |
|
From: Lieven D. <ld...@sc...> - 2008-03-06 10:22:04
|
Thanks Peter! @Geoffrey: Since almost none of the other spring projects are using maven to generate their site (I just checked, except for Acegi, of whom I think they're using Maven, and they're not using the "Spring" sking). I have a firm belief that a website is a 'make-or-break' thing when it comes to a product (especially a first launch). Someone new to RCP entering our current site isn't overwhelmed with a 'Nice!' feeling. The site is the ad for RCP, and bad ads don't sell products, even if the product is good. I have the same feeling about the main Spring site, but they can afford it so to speak. RCP, for it's first release, can't afford that. We need all the publicity we can get. When Spring RCP 1.0 is announced, a lot more people will come to the site. A that point, appearance does matter. But you're right about one thing, the main Spring site is in need for refurbishing... Greetz, Lieven Geoffrey De Smet schreef: > Looks great, but shouldn't this be fixed upstream? > At the moment, we use the maven-spring-skin, just like all the other > spring projects. > http://www.mvnrepository.com/artifact/org.springframework.maven.skins/maven-spring-skin > That skin could definitly be improved, for example with those changes. > > -0 as I don't think we should deviate from the general spring skin site > convention. > > With kind regards, > Geoffrey De Smet > > Peter De Bruycker schreef: >> looks great! >> >> regards, >> >> Peter >> >> On 3/6/08, *Lieven Doclo* <ld...@sc... >> <mailto:ld...@sc...>> wrote: >> >> I managed to put up part of the site online, just to give you an idea: >> >> http://www.doclo.be/spring/ >> >> Yes, I know there are still bugs, but they'll be fixed ASAP :). >> >> Greetz, >> >> Lieven >> >> >> Lieven Doclo schreef: >> >> > Hi everybody, >> > >> > Since Spring RCP is heading for it's first release, perhaps it's >> time to >> > change the way the site looks too. >> > Granted, the current look resembles the look of the Spring Framework >> > site, but let's face it, that site isn't going to win any beauty >> contests. >> > Therefor I created a maven skin for the current site that looks a bit >> > more modern and keeps the following in mind: >> > - sites should be totally viewable on 1024x768 screens, the >> current site >> > is not (screenshots in the pages result in a larger page) >> > - sites should not stretch horizontally (see SpringSource site) >> > - clear visual signs for links that take you outside the website >> > >> > There still is some work to be done on the skin (the powered-by icons >> > are gone and other bugs). I haven't gotten around to uploading a >> sample >> > (my ftp isn't working correctly), but I did post a screenshot on my >> > Picasa site: >> > >> > http://picasaweb.google.nl/doclolieven/SpringRCP >> > >> > Tell me what you think. I'll put up a sample site ASAP. The >> website is >> > the postersign for RCP, the first thing people see, and a modern site >> > helps with the image of the product. The current site... well, let's >> > just say there's room for improvement, shall we :). >> > >> > Grtz, >> > >> > Lieven >> > >> > >> > >> ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Springframework-rcp-dev mailing list >> Spr...@li... >> <mailto:Spr...@li...> >> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev >> >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Springframework-rcp-dev mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ |
|
From: Geoffrey De S. <ge0...@gm...> - 2008-03-06 10:01:47
|
Looks great, but shouldn't this be fixed upstream? At the moment, we use the maven-spring-skin, just like all the other spring projects. http://www.mvnrepository.com/artifact/org.springframework.maven.skins/maven-spring-skin That skin could definitly be improved, for example with those changes. -0 as I don't think we should deviate from the general spring skin site convention. With kind regards, Geoffrey De Smet Peter De Bruycker schreef: > looks great! > > regards, > > Peter > > On 3/6/08, *Lieven Doclo* <ld...@sc... > <mailto:ld...@sc...>> wrote: > > I managed to put up part of the site online, just to give you an idea: > > http://www.doclo.be/spring/ > > Yes, I know there are still bugs, but they'll be fixed ASAP :). > > Greetz, > > Lieven > > > Lieven Doclo schreef: > > > Hi everybody, > > > > Since Spring RCP is heading for it's first release, perhaps it's > time to > > change the way the site looks too. > > Granted, the current look resembles the look of the Spring Framework > > site, but let's face it, that site isn't going to win any beauty > contests. > > Therefor I created a maven skin for the current site that looks a bit > > more modern and keeps the following in mind: > > - sites should be totally viewable on 1024x768 screens, the > current site > > is not (screenshots in the pages result in a larger page) > > - sites should not stretch horizontally (see SpringSource site) > > - clear visual signs for links that take you outside the website > > > > There still is some work to be done on the skin (the powered-by icons > > are gone and other bugs). I haven't gotten around to uploading a > sample > > (my ftp isn't working correctly), but I did post a screenshot on my > > Picasa site: > > > > http://picasaweb.google.nl/doclolieven/SpringRCP > > > > Tell me what you think. I'll put up a sample site ASAP. The > website is > > the postersign for RCP, the first thing people see, and a modern site > > helps with the image of the product. The current site... well, let's > > just say there's room for improvement, shall we :). > > > > Grtz, > > > > Lieven > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > <mailto:Spr...@li...> > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev |
|
From: Peter De B. <pet...@gm...> - 2008-03-06 09:46:19
|
looks great! regards, Peter On 3/6/08, Lieven Doclo <ld...@sc...> wrote: > > I managed to put up part of the site online, just to give you an idea: > > http://www.doclo.be/spring/ > > Yes, I know there are still bugs, but they'll be fixed ASAP :). > > Greetz, > > Lieven > > > Lieven Doclo schreef: > > > Hi everybody, > > > > Since Spring RCP is heading for it's first release, perhaps it's time to > > change the way the site looks too. > > Granted, the current look resembles the look of the Spring Framework > > site, but let's face it, that site isn't going to win any beauty > contests. > > Therefor I created a maven skin for the current site that looks a bit > > more modern and keeps the following in mind: > > - sites should be totally viewable on 1024x768 screens, the current site > > is not (screenshots in the pages result in a larger page) > > - sites should not stretch horizontally (see SpringSource site) > > - clear visual signs for links that take you outside the website > > > > There still is some work to be done on the skin (the powered-by icons > > are gone and other bugs). I haven't gotten around to uploading a sample > > (my ftp isn't working correctly), but I did post a screenshot on my > > Picasa site: > > > > http://picasaweb.google.nl/doclolieven/SpringRCP > > > > Tell me what you think. I'll put up a sample site ASAP. The website is > > the postersign for RCP, the first thing people see, and a modern site > > helps with the image of the product. The current site... well, let's > > just say there's room for improvement, shall we :). > > > > Grtz, > > > > Lieven > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Springframework-rcp-dev mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev > |
|
From: Lieven D. <ld...@sc...> - 2008-03-06 09:39:16
|
I managed to put up part of the site online, just to give you an idea: http://www.doclo.be/spring/ Yes, I know there are still bugs, but they'll be fixed ASAP :). Greetz, Lieven Lieven Doclo schreef: > Hi everybody, > > Since Spring RCP is heading for it's first release, perhaps it's time to > change the way the site looks too. > Granted, the current look resembles the look of the Spring Framework > site, but let's face it, that site isn't going to win any beauty contests. > Therefor I created a maven skin for the current site that looks a bit > more modern and keeps the following in mind: > - sites should be totally viewable on 1024x768 screens, the current site > is not (screenshots in the pages result in a larger page) > - sites should not stretch horizontally (see SpringSource site) > - clear visual signs for links that take you outside the website > > There still is some work to be done on the skin (the powered-by icons > are gone and other bugs). I haven't gotten around to uploading a sample > (my ftp isn't working correctly), but I did post a screenshot on my > Picasa site: > > http://picasaweb.google.nl/doclolieven/SpringRCP > > Tell me what you think. I'll put up a sample site ASAP. The website is > the postersign for RCP, the first thing people see, and a modern site > helps with the image of the product. The current site... well, let's > just say there's room for improvement, shall we :). > > Grtz, > > Lieven > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ |
|
From: Lieven D. <ld...@sc...> - 2008-03-05 12:20:38
|
Hi everybody, Since Spring RCP is heading for it's first release, perhaps it's time to change the way the site looks too. Granted, the current look resembles the look of the Spring Framework site, but let's face it, that site isn't going to win any beauty contests. Therefor I created a maven skin for the current site that looks a bit more modern and keeps the following in mind: - sites should be totally viewable on 1024x768 screens, the current site is not (screenshots in the pages result in a larger page) - sites should not stretch horizontally (see SpringSource site) - clear visual signs for links that take you outside the website There still is some work to be done on the skin (the powered-by icons are gone and other bugs). I haven't gotten around to uploading a sample (my ftp isn't working correctly), but I did post a screenshot on my Picasa site: http://picasaweb.google.nl/doclolieven/SpringRCP Tell me what you think. I'll put up a sample site ASAP. The website is the postersign for RCP, the first thing people see, and a modern site helps with the image of the product. The current site... well, let's just say there's room for improvement, shall we :). Grtz, Lieven |
|
From: Jan H. <jh...@sc...> - 2008-03-05 10:58:54
|
> In order to get something usable by October, I assume that the plan is > to migrate a lot of the existing code from Spring RCP? We would prefer narrowing the scope to provide a solid release instead of migrating bags of code to have all the features in a so-so state. We also want to align the code with the current technologies and have a modular approach from the start. This doesn't mean that we won't to port any code at all but that it should be reviewed as thoroughly as possible and with a clean view. > > Any thoughts on how folks should migrate their applications? i.e. how > much change to you expect to see between the current (1.0) RCP and the > future Desktop? > > Do you intend to create a whole new package structure (e.g. > org.springframework.desktop)? That will obviously mean a fair amount of > work for people moving over (unless the actual class names stay the > same, then maybe the IDE's can resolve them automatically). You could look upon the Spring Desktop as a new project with a lot of influence from Spring Richclient. We don't want to have all the bagage of the current codebase and have our hands tied. This is the moment to fix things at the core where needed. So there will probably be a lot of changes, but I can't predict the future and put a number on how much of a change it will be. A few remarks if you're using Spring Richclient now: - I too am using the current framework in several products, so I'll be thinking of the migration issue as well. I would like to have a migration guide between the two as our company will have to make this step too. - current codebase is not going to abandoned, maintenance will continue during the development of the new project as needed - packages/modules will probably be renamed I'll collect any concerns/remarks that are made so that these won't get lost. Thanks for sharing yours. Kind Regards, Jan **** DISCLAIMER **** http://www.schaubroeck.be/maildisclaimer.htm |
|
From: Rogan D. <ro...@da...> - 2008-03-05 10:14:43
|
Jan Hoskens wrote: > Hi, > > As you may know, we had planned to have a Spring Richclient 1.0 release > somewhere at the end of Januari. It's March already and no release has > been pushed out. Don't start to panic just yet, I'll let you in on the > details. > > Somewhere in Januari I contacted the people of SpringSource to discuss > the position of Spring Richclient within the Spring universe. As we're > in different parts of the world, it takes some time to schedule a > meeting online and contact the right people, thus time was creeping past > the previously set release date. Our goal with this meetings was to not > only discuss the present and future of the project but also the > involvement of SpringSource. The outcome is the following. > > Current codebase: > > We have set a new target date for the release: March 17. All bugs should > be fixed while documentation will be provided as needed. We don't want > this to delay the release date anymore and interfere with our future > plans. If documentation is requested at some point, we'll provide this > on the developer blog. This release will have maintenance updates as > requested. > > Future plans: > > We've decided to start a new codebase and re-brand the project to Spring > Desktop. One of the reasons behind this is the possibility to update the > existing core techniques after some research. The current codebase core > is about two years old, quite stable but not state-of-the-art anymore. > Another reason is that this allows us to start with the modularity in > mind and review the existing codebase. In order to get something usable by October, I assume that the plan is to migrate a lot of the existing code from Spring RCP? Any thoughts on how folks should migrate their applications? i.e. how much change to you expect to see between the current (1.0) RCP and the future Desktop? Do you intend to create a whole new package structure (e.g. org.springframework.desktop)? That will obviously mean a fair amount of work for people moving over (unless the actual class names stay the same, then maybe the IDE's can resolve them automatically). Regards, Rogan |
406 messages has been excluded from this view by a project administrator.
