Hi Bertrand,
thanks for your feedback, that sounds good!
If there are no objections I would commit it with SLING-4364 in the folder
/contrib/commons/js/nodetypes
with the Sling parent pom,
the ArtifactId org.apache.sling.commons.js.nodetypes
and the version 1.0.SNAPSHOT.
Does that fit in the
Hi Sandro,
On Wed, Jan 28, 2015 at 5:37 PM, Sandro Boehme sandro.boe...@gmx.de wrote:
...If there are no objections I would commit it with SLING-4364 in the folder
/contrib/commons/js/nodetypes
with the Sling parent pom,
the ArtifactId org.apache.sling.commons.js.nodetypes
and the version
Hello again,
while I think the JSNodeTypes contribution is useful I would also like
to have it in Sling to not need an OBR to install the Resource Editor.
Now that I'm a Committer in the meantime and I have written the
JSNodeTypes library solely on my own the question is if the IP clearance
Hi Sandro,
On Tue, Jan 27, 2015 at 4:51 PM, Sandro Boehme sandro.boe...@gmx.de wrote:
...Now that I'm a Committer in the meantime and I have written the JSNodeTypes
library solely on my own the question is if the IP clearance process is
still needed
IMO it's not needed in this case,
Hi Sandro,
On Thu, Dec 11, 2014 at 4:25 PM, Sandro Boehme sandro.boe...@gmx.de wrote:
...Here you find a demo of the full API and all background information:
http://www.jcrbrowser.org/sling/libs/jsnodetypes/content/documentation.html
I think it's interesting, I support accepting this donation
Am 18.12.14 14:02, schrieb Bertrand Delacretaz:
Hi Sandro,
On Thu, Dec 11, 2014 at 4:25 PM, Sandro Boehme sandro.boe...@gmx.de wrote:
...Here you find a demo of the full API and all background information:
http://www.jcrbrowser.org/sling/libs/jsnodetypes/content/documentation.html
I think
Hello,
I would like to offer the JSNodeTypes library to Apache Sling as a
contribution.
It provides a JavaScript API for JCR node types.
I use it in the new code update of the Sling Resource Editor at the Add
Node dialog to provide:
o the applicable node names
o the applicable node types
o
