The first Idea of QueScript

The first idea of QueScript is came from jQuery,  which advocates the slogan of "write less do more".  I like the style in jQuery that abandon the useless "set/get" prefix.  If you want to set the value for some attributes, simply put the values in the bracket (e.g. to store an integer 16 to a value uses the syntax: value(16)) and if you want to get the value of the attributes, simply uses a pair of empty bracket (e.g. to get the value uses the syntax:  value() )

Playing "Age of Emperor"

I am a fans of a computer game called, "Age of Emperor". I enjoy selecting a group of armies and then instructing them to go to the battlefield for fighting.  The overall process is simple: 1, you select the armies, 2. you click the target location.  Similar to jQuery, QueScript allows you to select a group of objects using QueScript.query() command, then, you can further process the selected objects to do similar task as a group or collection.  I'd like to call it, "Collection Oriented Programming". 

One of the objectives of QueScript is to avoid programming individual objects. In other words, QueScript is a Collection Oriented Programming Language.

Extend the limitation

If you have experience in programming jQuery, you'll know that jQuery only serves for HTML DOM and XML DOM objects.  Although, you can extend the function of jQuery by providing plugins or selectors, you cannot extend the library to handle files, registries, etc.  The idea of QueScript is to provide an infra-structure that is expandable to every namespace including files, webpages, registries, etc.  However, QueScript is mainly designed for desktop programming, for web-page development, I don't have any plan to repeat what jQuery have done.

Why Javascript or JScript

The reason for choosing Javascript or JScript is the cross-platform nature of the programming language.  Python is my second choice.  By the way, let's build the QueScript in Javascript first.