Let me clerify...
I'm not interested in seeing the difference in different versions of Atlas, or even how Atlas compares with other Javascript libraries but how Atlas tries to extend/modify javascript itself. For example prototype vs class based inheritance. What advantages/disadvantages do each have? The reasoning behind the change, etc..
Samples on what a very basic class looks like, inheritance and can you do stuff like polymorphism? Take the top 5 or 10 classic (GoF) design patterns and show us the Atlas equivalent of them.
It seems that an investigation at this core level would be of greater importance than looking at the higher level stuff like client side databinding, filtering, etc..
Take thishttp://atlas.asp.net/quickstart/atlas/doc/javascript/default.aspx and give us more details!!
An advantage of "class based inheritance" over "prototype basedinheritance" is that with the former you can actually use 'privateclass variables/functions'. When using prototypes, you really only have access topublic members. Another advantage is probably that class based inheritance is a bit more compact.
The link you pasted contains some code for a basic class andinheritance. Polymorphism is possible, since you can really pass anyobject to any method - as long as it has the functions that theimplementation relies on (or otherwise it'll fail when the function iscalled)... Derived types do have all the members of its base type(s),so polymorphism is also possible when using 'Atlas types'.
I could show you how a few patterns could be implemented using Atlas,but I suppose what you really want is to have a set of examples in thequickstarts as an example for anyone starting with Atlas, right?
No comments:
Post a Comment