Modify DocumentLibrary on Alfesco 3.4d Share [SOLVED]
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2012 03:56 AM
Hello forum,
I am struggling to customize the document library in Share in order NOT to show when a document has been changed and who has changed the document, i.e. it should show the description and a different property only.
Until now I kind of understand view compostion techniques with the SpringSource SURF Framework. However I do not find the relevant pages/templates where to change the document library.
1. Is there a best practise for modifying the document library?
2. Is it recomended to leave the document library as is and write a dashlet like the on in the knowledgebase example instead?
Your answer is higly appreciated!
Thanks in advance!
I am struggling to customize the document library in Share in order NOT to show when a document has been changed and who has changed the document, i.e. it should show the description and a different property only.
Until now I kind of understand view compostion techniques with the SpringSource SURF Framework. However I do not find the relevant pages/templates where to change the document library.
1. Is there a best practise for modifying the document library?
2. Is it recomended to leave the document library as is and write a dashlet like the on in the knowledgebase example instead?
Your answer is higly appreciated!
Thanks in advance!
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2012 07:22 AM
Hello,
in Alfresco 3.4, the document library is (still) managed primarily via client-side JavaScript (documentlist.js). If you want to change how documents are displayed, this is the place to go. On the other hand, Alfresco 4 provides configuration for this type of customization and if you want to code something that is future-proof (from the current perspective), you should consider using Alfresco 4 as your base platform.
Until 3.4, best practices would be to create a custom documentlist component and provide some selective overrides for the client side documentlist.js. Starting from 4.0, best practice is to configure the document library via the extension points provided by Alfresco.
Regards
Axel
in Alfresco 3.4, the document library is (still) managed primarily via client-side JavaScript (documentlist.js). If you want to change how documents are displayed, this is the place to go. On the other hand, Alfresco 4 provides configuration for this type of customization and if you want to code something that is future-proof (from the current perspective), you should consider using Alfresco 4 as your base platform.
Until 3.4, best practices would be to create a custom documentlist component and provide some selective overrides for the client side documentlist.js. Starting from 4.0, best practice is to configure the document library via the extension points provided by Alfresco.
Regards
Axel
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-19-2012 04:35 AM
Dear AFaust,
thank you for your input.
Manipulating documentlist.js and then copying the contents of documentlist.js to documentlist-min.js did the trick. (As an alternative you can also compress the contents with a javascipt minifier.)
Custom metadata can be "injected" this way https://forums.alfresco.com/en/viewtopic.php?f=48&t=38217.
However I am wondering whether share is suited at all to manage properties from asscociations. I'll open another thread for that.
Best regards,
Dominik
thank you for your input.
Manipulating documentlist.js and then copying the contents of documentlist.js to documentlist-min.js did the trick. (As an alternative you can also compress the contents with a javascipt minifier.)
Custom metadata can be "injected" this way https://forums.alfresco.com/en/viewtopic.php?f=48&t=38217.
However I am wondering whether share is suited at all to manage properties from asscociations. I'll open another thread for that.
Best regards,
Dominik