Details
-
Type:
Task
-
Status: Open (View Workflow)
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 4.2.f Community, 4.2, 5.0
-
Fix Version/s: 5.0
-
Component/s: Share Extensions and Customisations
-
Labels:None
-
Security Severity:None
-
Code Branch:HEAD-BUG-FIX
-
Build Location:
Description
While developing extensions to Share, there is a few things in the way of having a perfect setup.
With the upcoming Alfresco SDK 2.0 release, we've shown (https://www.youtube.com/watch?v=Tu641nRGbtQ) that we have a very cool setup that allows rapid development for Alfresco.
Share is getting there, it's good, but it could be so much better.
The main thing right now is the dependency cache, which blocks editing CSS/i18N files. It works in some cases with development mode and client-debug, but it has not been reliable. Being able to configure Share to disable the dependency cache (or at least have it re-generate on every request) would improve the developer experience.
Another thing that we may be able to improve is working with forms. You can change a ton of stuff in share-config-custom.xml and if you do a refresh web scripts it will actually reload it (handy when doing forms). This must somehow be tied into a cache? Can it be reloaded on each request?
- I know that the activiti guys managed to do something similar for their kickstater project (https://gist.github.com/frederikheremans/0a525a660636b92481d4)
I'd say the share-config-custom.xml is a nice-to-have, but the dependency cache stuff needs to happen 
Activity
Ole Hejlskov It was committed to a private branch in revision 81518, it should get merged down soon - I'll let you know when it's available. There's also lots of other goodies that you'll be interested in - especially the test framework updates which might also be useful for the SDK
Ole Hejlskov, for now we are closing this issue. When you manage to build this locally and find any issues relevant to this task then please feel free to reopen this issue.
Ole Hejlskov This should now be on the main SVN trunk.
I have integrated this new parameter in the SDK 2.0.0 final build and we have some success (i.e. JS are actually reloaded without cache explicit clearing) but as per https://github.com/Alfresco/alfresco-sdk/issues/248#issuecomment-67860663 i18n and CSS are still not reloaded and require a
POST to /share/page/caches/dependency/clear
before they are actually reloaded. Reopening the issue for further review.
Ole Hejlskov feel free to share more details here.
Also while we're at it, could we talk about https://issues.alfresco.com/jira/browse/ALF-9970 ?
Without development mode and client-debug, developing custom admin console pages is a pain :/