Dialog and Wizard Framework for 1.3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2006 06:05 AM
There's a new entry on my blog announcing the new dialog and wizard framework we are adding to 1.3 and the effect it will have.
Feel free to leave any feedback you have in this forum.
Cheers,
Feel free to leave any feedback you have in this forum.
Cheers,
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2006 10:09 AM
Hi Gavin,
I understand that, if I want to build a new dialog, I will define it in the file "web-client-config-dialogs.xml", is that right?
Or, since that is a file in the Alfresco distribution, is it better that I add the new dialog in "web-client-config-custom.xml" ?
I understand that, if I want to build a new dialog, I will define it in the file "web-client-config-dialogs.xml", is that right?
Or, since that is a file in the Alfresco distribution, is it better that I add the new dialog in "web-client-config-custom.xml" ?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2006 07:45 AM
Yes, it is best to put ALL your custom configuration into web-client-config-custom.xml as that file will not be touched when an upgrade is performed.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2006 04:20 AM
Personnaly, I would recommand you to override the following bean :
WebClientConfigSource within a new xxx-context.xml file.
For example : extension-context.xml
By doing this,you ensure that you can maintain more easily all your customizations instead of mixing everything in one single file.
We are no more old-fashion Cobol developers… :wink:
JM
WebClientConfigSource within a new xxx-context.xml file.
For example : extension-context.xml
<bean id="webClientConfigSource" class="org.alfresco.config.source.UrlConfigSource"> <constructor-arg> <list> <value>classpath:alfresco/web-client-config.xml</value> <value>classpath:alfresco/web-client-config-dialogs.xml</value> <value>classpath:alfresco/web-client-config-wizards.xml</value> <value>classpath:alfresco/web-client-config-properties.xml</value> <value>classpath:alfresco/web-client-config-navigation.xml</value> <value>classpath:alfresco/web-client-config-actions.xml</value> <value>classpath:alfresco/web-client-config-forum-actions.xml</value> <value>classpath:alfresco/extension/web-client-config-custom.xml</value> <value>classpath:alfresco/extension/web-client-config-dialogs-custom.xml</value> <value>classpath:alfresco/extension/web-client-config-properties-custom.xml</value> <value>classpath:alfresco/extension/web-client-config-actions-custom.xml</value> </list> </constructor-arg> </bean>
By doing this,you ensure that you can maintain more easily all your customizations instead of mixing everything in one single file.
We are no more old-fashion Cobol developers… :wink:
JM
