You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ra...@apache.org on 2016/04/18 13:45:59 UTC
svn commit: r1739748 -
/sling/site/trunk/content/documentation/bundles/scripting/scripting-sightly.mdtext
Author: radu
Date: Mon Apr 18 11:45:59 2016
New Revision: 1739748
URL: http://svn.apache.org/viewvc?rev=1739748&view=rev
Log:
CMS commit to sling by radu
Modified:
sling/site/trunk/content/documentation/bundles/scripting/scripting-sightly.mdtext
Modified: sling/site/trunk/content/documentation/bundles/scripting/scripting-sightly.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/scripting/scripting-sightly.mdtext?rev=1739748&r1=1739747&r2=1739748&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/scripting/scripting-sightly.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/scripting/scripting-sightly.mdtext Mon Apr 18 11:45:59 2016
@@ -208,6 +208,11 @@ The following table summarises the pros
</ul>
</td>
<td>
+ <p>Use-objects provided through bundles:</p>
+ <ul>
+ <li>lacks flexibility in terms of component overlaying</li>
+ </ul>
+
<p>Use-objects backed by <code>Resources</code>:</p>
<ul>
<li>cannot extend other Java objects</li>
@@ -220,6 +225,7 @@ The following table summarises the pros
<td>
<ul>
<li>allows JavaScript developers to develop component logic</li>
+ <li>can be reused through the dependency mechanism provided by the <code>use</code> function</li>
</ul>
</td>
<td>
@@ -229,4 +235,17 @@ The following table summarises the pros
</ul>
</td>
</tr>
+ <tr>
+ <td>Script Use Provider</td>
+ <td>
+ <ul>
+ <li>allows the usage of Use objects evaluated by other Script Engines available in the platform</li>
+ </ul>
+ </td>
+ <td>
+ <ul>
+ <li>like in the case of the JavaScript Use Provider, the performance is influenced by the Script Engine's implementation</li>
+ </ul>
+ </td>
+ </tr>
</table>