[
https://issues.apache.org/jira/browse/SLING-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640018#comment-13640018
]
Bob Paulin commented on SLING-2805:
-----------------------------------
I've been able to accommodate most of the requests above. I think there is
still room for improvement in the caching and consolidation of the compiled
files. A couple of design decisions I'm especially interested in feedback on.
a) Is using JCR nodes and properties for Compile Options and Cache locations
too klunky?
b) Is the taglib the right way to trigger compilations and caching? Would
using sling eventing be better?
c) Is there a better way to package the code? Having to install bundles for
each compiler seems like a good module design but requires more work.
I've also created another project to demonstrate the framework:
https://github.com/bobpaulin/sling-chaplin-boilerplate.git
Chaplin is a popular framework for building JavaScript applications
(https://github.com/chaplinjs/chaplin).
> Sling Web Resource Cache and Compiler
> -------------------------------------
>
> Key: SLING-2805
> URL: https://issues.apache.org/jira/browse/SLING-2805
> Project: Sling
> Issue Type: New Feature
> Components: Samples
> Reporter: Bob Paulin
> Priority: Minor
>
> Implemented contrib project to allow for the development web resource
> compiler plugins for languages such as CoffeeScript to compile and cache
> content on the JCR. This might make a nice addition to the contrib section.
> See implementations at
> https://github.com/bobpaulin/sling-web-resource.git
> Example implementation for CoffeeScript. Includes CoffeeScript unit tests.
> https://github.com/bobpaulin/sling-coffee.git
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
