Why 'CacheClass'...?

JS · Joined: 16 Oct 2007 Posts: 2

So... I have this little question about the mileScript compiler... but before I tell you, I want to say something:
This is the first JavaScript project in which I see that everything uses only one object - the 'ClassCache' object.(except for my own scripts where I use the same technique);

And here is the question:
Will it be good if you include an option in the {user.projectConfig}.xml file which will allow the developer to specify exactly what name should be used for the global object(and class) that stores every property and method(I mean 'ClassCache')?

For example:
I want instead of 'ClassCache', there to be 'system'.

One simple reason:
Imagine a project, a very complex one, in which the *.js files should be include depending on the current conditions.(A graphic library is a very good example - you include for example only the core and the model for the lines, not everything)
By using the same object every time you make it very difficult for the project to be separated on different files that could be include depending on the situation.

Husafan · Joined: 05 Oct 2007 Posts: 2 Location: Atlanta, GA

JS,

A very good question. Currently, ClassCache is an auto-generated object used to store 'class definition' files, which are then used to create instances of classes at run time. The class definitions in the ClassCache also constitute the object that static attributes are actually added to, rather than adding these attributes to each instance of a class.

Currently, Milescript applications only support static linking. However, in the very near future, you will be able to tell the compiler to 'dynamically' link your project, which means that only the code in the application you are compiling will get generated, along with a dependency file to tell the ClassCache where to find the other classes at runtime.

This means that you will be able to host your application code on your web server, but have the client browser load any libraries you might need from any other URL. At runtime, all of these libraries are put into the ClassCache so that they can interact together without interfering with the root javascript namespace.

One of the features we are currently working on implementing is obfuscation/code-compression. This feature will also allow the developer to change the name of the ClassCache. However, this is a fairly complicated step, since we have to make sure that you will be able to load and link against an obfuscated third-party library at runtime, and still have everything function as intended.

In the coming weeks, we will be planning out a road map, with dates, to let you all know when you can expect features to be added, but rest assured for now that you will soon be able to modify the name of ClassCache. Smile