[
https://issues.apache.org/jira/browse/SLING-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715868#action_12715868
]
Felix Meschberger commented on SLING-990:
-----------------------------------------
> I will modify the JSON scripts.
Cool, so we get a Resource tree explorer !
> The resources (images, css & js) are under LGPL. I took those files from
> Smart GWT 1.1 distribution. Maybe we can use others.
Could these be extracted from the artifact downloaded from the maven repository
on build time ? So that we don't have to store this in our SVN.
> If LGPL is an issue, we cannot continue to use SmartGwt because the current
> implementention requires 2 SmartGWT jars
> (see the pom.xml). Those jars are also under LGPL. There are used to run the
> application in the hosted mode and compile
> de java code into js.
Would it be a big problem to not be able to use SmartGWT ?
> Prototype for a Sling Explorer implementation based on GWT
> ----------------------------------------------------------
>
> Key: SLING-990
> URL: https://issues.apache.org/jira/browse/SLING-990
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Christophe Lombart
> Attachments: Sling Explorer.zip
>
>
> Following the Sling Explorer proposal [1], I have started an implementation
> with the SwartGwt UI framework [2] (based on GWT and under LGPL licence).
> Not sure but I think that LGPL is compatible with the Apache project.
> Until now, it is just a prototype. Can you review the code and see if this
> Gwt application is well integrated with Sling ?
> [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html
> [2] http://code.google.com/p/smartgwt/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
