Permalink
Browse files

- removed XHRSync transport, as it turned out that truly synchronous …

…mode won't support files concatenation
  • Loading branch information...
Nickolay Platonov
Nickolay Platonov committed Nov 18, 2010
1 parent 3f5d063 commit ac5b3a8dafeda08fdb25c8c3e9adc6766cca90c2
View
@@ -4,16 +4,17 @@ Release history for JooseX.Namespace.Depended
- various docs updates
- - NodeJS transport made synchronous
- uncommented tests for dependencies in "Lazy" classes on NodeJS platform
- JooseX.Meta.Lazy excluded from the `Auto` bundle (was only required for testing)
- JooseX.SimpleRequest included into the `Web` bundle
+ - removed XHRSync transport, as it turned out that truly synchronous mode won't support files concatenation
+
- `use.paths` is now the preferred way to specify the INC paths instead of JooseX.Namespace.Depended.Manager.my.INC
using JooseX.Namespace.Depended.Manager.my.INC is still supported but will be removed in some of the future releases
- - improved <script> transport (still unreliable on IE)
+ - improved <script> transport (still hardly usable on IE because of lacking 'onerror' support)
- switched to 'ScriptTag' as a default materialization for Web
- added 'async' attribute for <script> transport
View
@@ -19,7 +19,6 @@ COMPONENTS = {
"JooseX.Namespace.Depended.Materialize.ScriptTag",
"JooseX.Namespace.Depended.Transport.XHRAsync",
- "JooseX.Namespace.Depended.Transport.XHRSync",
"JooseX.Namespace.Depended.Transport.ScriptTag",
"JooseX.Namespace.Depended",
@@ -48,7 +47,6 @@ COMPONENTS = {
"JooseX.Namespace.Depended.Materialize.ScriptTag",
"JooseX.Namespace.Depended.Transport.XHRAsync",
- "JooseX.Namespace.Depended.Transport.XHRSync",
"JooseX.Namespace.Depended.Transport.ScriptTag",
"JooseX.Namespace.Depended.Transport.NodeJS",
View
@@ -393,18 +393,28 @@ JooseX.Namespace.Depended is 100% compatible with &lt;script&gt; tag loading and
- Make sure you always use `presence` when loading non-joose code to avoid double-loading.
- Remember the asynchronous behavior.
-Additionally, if you will concatenate your JS files in a single one *in the correct order* (which is generally not required)
+Additionally, if you will concatenate your JS files in the single file *in the correct order* (which is not required(!))
you'll receive a synchronous execution of the whole file (no `setTimeout` delays).
+Changing the default transport/materialization (advanced)
+---------------------------------------------------------
- <!-- Joose ->
- <script type="text/javascript" src="/jsan/Task/Joose/Core.js"></script>
-
- <!-- JooseX.Namespace.Depended ->
- <script type="text/javascript" src="/jsan/Task/JooseX/Namespace/Depended.js"></script>
-
+By default, JooseX.Namespace.Depended will fetch the source files with asynchronous XHR request and materialize it by the insertion of the
+&lt;script&gt; tag in the DOM.
+
+You may want to change this behavior, for example switch to using &lt;script&gt; tags for loading as well (unreliable in IE):
+
+ <script type="text/javascript" src="/jsan/Task/JooseX/Namespace/Depended/Web.js"></script>
<script type="text/javascript">
+
+ JooseX.Namespace.Depended.Resource.JavaScript.meta.extend({
+
+ doesnt : [ JooseX.Namespace.Depended.Transport.XHRAsync, JooseX.Namespace.Depended.Materialize.ScriptTag ],
+
+ does : JooseX.Namespace.Depended.Transport.ScriptTag
+ })
+
use.paths = [ 'lib', '/jsan' ]
</script>
@@ -393,18 +393,28 @@ JooseX.Namespace.Depended is 100% compatible with &lt;script&gt; tag loading and
- Make sure you always use `presence` when loading non-joose code to avoid double-loading.
- Remember the asynchronous behavior.
-Additionally, if you will concatenate your JS files in a single one *in the correct order* (which is generally not required)
+Additionally, if you will concatenate your JS files in the single file *in the correct order* (which is not required(!))
you'll receive a synchronous execution of the whole file (no `setTimeout` delays).
+Changing the default transport/materialization (advanced)
+---------------------------------------------------------
- <!-- Joose ->
- <script type="text/javascript" src="/jsan/Task/Joose/Core.js"></script>
-
- <!-- JooseX.Namespace.Depended ->
- <script type="text/javascript" src="/jsan/Task/JooseX/Namespace/Depended.js"></script>
-
+By default, JooseX.Namespace.Depended will fetch the source files with asynchronous XHR request and materialize it by the insertion of the
+&lt;script&gt; tag in the DOM.
+
+You may want to change this behavior, for example switch to using &lt;script&gt; tags for loading as well (unreliable in IE):
+
+ <script type="text/javascript" src="/jsan/Task/JooseX/Namespace/Depended/Web.js"></script>
<script type="text/javascript">
+
+ JooseX.Namespace.Depended.Resource.JavaScript.meta.extend({
+
+ doesnt : [ JooseX.Namespace.Depended.Transport.XHRAsync, JooseX.Namespace.Depended.Materialize.ScriptTag ],
+
+ does : JooseX.Namespace.Depended.Transport.ScriptTag
+ })
+
use.paths = [ 'lib', '/jsan' ]
</script>
@@ -72,7 +72,6 @@ You can use already implemented set of roles:
> - [JooseX.Namespace.Depended.Materialize.Eval](Materialize/Eval.html) - materialization mode, which evalutes the passed blob in the `Joose.top` scope
> - [JooseX.Namespace.Depended.Transport.XHRAsync](Transport/XHRAsync.html) - tranport, which uses the asynchronous XHR to fetch the content of resource
-> - [JooseX.Namespace.Depended.Transport.XHRAsync](Transport/XHRSync.html) - tranport, which uses the synchronous XHR to fetch the content of resource
> - [JooseX.Namespace.Depended.Transport.ScriptTag](Transport/ScriptTag.html) - tranport, which uses the &lt;script&gt; tag to fetch the content of resource
See the [Synopsis][] for example
@@ -1,6 +1,6 @@
JooseX.Namespace.Depended.Resource.JavaScript.meta.extend({
- does : [ JooseX.Namespace.Depended.Transport.XHRAsync, JooseX.Namespace.Depended.Materialize.Eval ]
+ does : [ JooseX.Namespace.Depended.Transport.XHRAsync, JooseX.Namespace.Depended.Materialize.ScriptTag ]
})
File renamed without changes.

0 comments on commit ac5b3a8

Please sign in to comment.