I agree, shorter names are more readable.
I used shorter names for the JavaScript samples, have a look and see if
thats better or you can suggest better names or structure:
http://svn.apache.org/repos/asf/incubator/tuscany/java/samples/JavaScript/
...ant
On 4/7/06, Jean-Sebastien Delfino <[EM
Jean-Sebastien Delfino wrote:
[snip]
ant elder wrote:
Thats what I'll start doing then, its easy enough to move them if
anyone has
a different suggestion.
If they're separate projects must they really use the
org.apache.tuscany.samples.javascript... package names or could that be
something sh
ant elder wrote:
Thats what I'll start doing then, its easy enough to move them if anyone has
a different suggestion.
If they're separate projects must they really use the
org.apache.tuscany.samples.javascript... package names or could that be
something shorter? Some of those long names are quit
Thats what I'll start doing then, its easy enough to move them if anyone has
a different suggestion.
If they're separate projects must they really use the
org.apache.tuscany.samples.javascript... package names or could that be
something shorter? Some of those long names are quite hard to read in t
ant elder wrote:
I'd like to make some more complete samples for the JavaScript componentType
so where should they go?
JavaScript works a bit differently from Java so I think there should be
separate samples for things like:
- basic helloworld
- properties
- service references
- a couple for E4X
I'd like to make some more complete samples for the JavaScript componentType
so where should they go?
JavaScript works a bit differently from Java so I think there should be
separate samples for things like:
- basic helloworld
- properties
- service references
- a couple for E4X (if thats going)
-
