Mono是Novell公司（NetWare和SuSELinux发行商，全球第二大Linux发行商，美国上市公司）的一个项目，通过Mono就可以在Linux/Unix等其他操作系统上开发并运行.NET程序。

Mono已经发布2.4版（也是第一个正式开始得到Novell公司商业支持的版本，Novell公司也已经和Microsoft达成合作），兼容C#3.0规范，并且越来越多的公司开始使用Mono。

希望Mono能够发展的越来越好，那样.NET将和Java一样成为真正的跨平台的框架。也希望国内更多感兴趣的朋友能够开始关注Mono；）

更重要的是：Mono是一个完全开源的项目，大家可以从里面学到不少系统底层的实现机制和技术原理。

[Directives]
$include, $import,
$package, $class,
$field, $method, $property, $event

[Additional Keywords]
extend, implement,
public, protected, private, static,
get, set

[Additional Operators]
classof, raise

[Predefined Classes]
class Package extend Object {
 public :
 protected :
 private :
}
class Class extend Object {
 public :
 protected :
 private :
}
class Member extend Object {
 public :
 protected :
 private :
}
class Field extend Member {
 public :
 protected :
 private :
}
class Method extend Member {
 public :
 protected :
 private :
}
class Property extend Member {
 public :
 protected :
 private :
}
class Event extend Member {
 public :
 protected :
 private :
}

[Class Hierarchy]
OxScript.Object 
     |--OxScript.Number 
     |--OxScript.String 
     |--OxScript.Boolean 
     |--OxScript.Date 
     |--OxScript.Array 
     |--OxScript.Enumerator 
     |--OxScript.Function 
     |--OxScript.RegExp 
     |--OxScript.VBArray 
     |--OxScript.Error 
     |--OxScript.ActiveXObject 
     | 
     |--OxScript.Reflection.Package 
     |--OxScript.Class 
     |--OxScript.Reflection.Member 
          |--OxScript.Reflection.Field 
          |--OxScript.Reflection.Method 
          |--OxScript.Reflection.Property 
          |--OxScript.Reflection.Event

下面是一段代码示例：

// namespace declarations
var
LaserPackage = $package();

with(LaserPackage) {
    // define a class named OxScriptDemo in LaserPackage
    $class ([public, final], OxScriptDemo, {extend : OxScript.Object},
        // construcltor
        function OxScriptDemo() {
            // this is the constructor implementation of class LaserPackage.OxScriptDemo
        },
        {
            // public members
            public : {
                // a field with type of OxScript.Number
                field1 : $field (OxScript.Number),
                // a method definition
                method1 : $method (
                    function() {
                        // implementation of method1
                    }
                ),
                // a property of type OxScript.String having both getter and setter
                property1 : $property (
                    OxScript.String,
                    {
                        get : function() {
                            // getter of property1
                        },
                        set : function() {
                            // setter of property1
                        }
                    }
                ),
                // an event declaration
                event1 : $event (
                    function(source, eventArgs) {} // the function declaration of event1 handler
                ),
                // an event handler for event1
                event1Handler : $method(
                    function(source, eventArgs) {
                        // implementation of event handler
                    }
                ),
                // the method which demonstrats how to access the class members and raise events
                demoMethod : $method (
                    function() {
                        // assign a value to field1
                        this.field1 = 66;
                        // call method1
                        this.method1();
                        // get property1
                        var str = this.get_property1();
                        // set property1
                        this.set_property1(str);
                        // add a handler to event1
                        this.event1.add(this.event1Handler);
                        // raise event1
                        raise (this.event1);
                    }
                )
            },
            // protected members
            protected : {
                // 
            },
            // private members
            private : {
                // 
            }
        }
    );
}

1. Utilize stored procedures and functions to implement some functions in OQL.

2. Use global object version to pin a history point, instead of time.

3. Define interface IVersionable to make elements have unified versions.

4. Use serialized XML string to store queries.

5. Use temporary tables to store the query results and then provide functionality of further query on the results.

6. Each time you begin a transaction, all the unsaved data should be saved into database.

7. Use 'rowversion' column to mark the version of table records.

----SwallowMemo1

8. Enable the functionality of Schema history.

9. Maybe Swallow could consolidate some process logics into automatically generated code, and then use the compiler to build them into binary instructions.

This will avoid runtime constructions and greatly improve the performance.

10. Object pools can be divided into sub pools. Each sub pools holds the objects from a specific mapping.

11. Defined some special GUIDs for system preserved objects, like schema objects.

12. Introduce the concept of 'Module/Package' to group the persistent types and global variables.

13. Treat Arrays as collections with fixed size. And allow multi-dimensioned arrays.

----SwallowMemo2

14. Scopes should essentially be implemented and handled at the mapping layer. And, in the upper object layer, each reference field can be restricted to a

specific scope of a class.

15. Create reference views for those reference fields, and this will make reference checking much more convenient.

16. From the bottom to the top Swallow can be divided into four components. They are Laser.ToolKit, Laser.Swallow.VirtualDatabase,

Laser.Swallow.ObjectSerializer, and Laser.Swallow.ObjectDatabase. Laser.ToolKit is a reusable component which contains several useful classes including

StringOperator, ObjectReflector, Resourcer and Logger.

17. Add a virtual property IsDataRecord to class PObject.

----SwallowMemo3

18. SchemaCenter can be used to publish and synchronize schema definitions for all InterDOW/Swallow sites on the Web. The client can choose wether to import

those schema objects defined on the SchemaCenter, but can not modify them. And, once the definitions has been modified on the center, all the counter-parts

on the clients should be updated automatically. However, if you like, you can make some modifications based on a published schema object and save it as

another local one.

19. Make persistent objects independent from objectbases.

20. Define a collection class to hold the query results of a specific XRelation. Actually this class uses the cache mechenism to accelerit the speed.

----SwallowMemo4

21. Collection class for XRelation is dedicated for implementing collection property of persistent types. It can avoid requery each time the program access

the property, and provide a method named Refresh to allow requery on demand.

22. Attach a history link table to each entry of the hashed object pool. This data structure can provide convenience for retrieving historical objects.

----SwallowMemo5

23. Native Code Generation: Supports generating code directly in multiple kinds of native programming languages. This feature can automatically generate

applications that can run on their respective platform without Swallow.NET and InterDOW. Native code will run faster, but of course loose the functionality

of schema operations and some other functionalities provided by Swallow. However, still an attractive and unimaginable feature!

24. Applies Singleton pattern on each database provider class.

25. Use the base type name prefix to address the overriden members in a persistent type.

26. Introduce type indicators in the SELECT list in OQL to allow explicit type casting.

----SwallowMemo6

27. Swallow may support both Concret Tables and Extended Tables to implement type inheritances.

28. InterDOW should be able to separate into several reusable functional blocks. For example, Organization & Rights Management. Document Management, Workflow

Management, and Web Presentation System.

29. Implement a QueryDesigner to visually generate query conditions.

----SwallowMemo7

30. 'UniObject' provides the features of GLUES(Global, Localizable, Unique, Encryptable, Serializable). By UniObjects, all the resource data all over the

world can be unified and uniformed for the purpose of data exchange. PObject in Swallow derives from UniObject.

31. Mapping parts consists of two parts, the hierarchy path delimited by backward slash and the structure path delimited by forward slash. In Swallow, there

are three kinds of mappings, root mapping, branch mapping, and leaf mapping. One root mapping can span multiple tables.

32. Mapping information is necessary for many Swallow data sources or data media, it could be used to locate structured properties or distributed objects.

----SwallowMemo8

33. Mapping ID can be changed when moving or copying a persistent object from one data source to another, but not the instance ID. And the OID should refers

to the instance/record ID, the mapping/region will be involved when the full ID is required.

34. The data structure of a Swallow persistent object can be describled or rendered using the Cylinder model. The kernel is the current neutral object, the

vertical axis represents the historical time line, and the peripheral surface consists of localized resource objects for multiple cultures.

----SwallowMemo9

35. Just as the .NET Framework did, Swallow allows a persistent object to be associated with several attributes. An attribute itself is also a persistent

object. And, furthure more, user can define their own customized attributes, all the attributes must derive from class PAttribute. This feature is very

useful and powerful. For example, you specify another column data type for a primitive type field. There is another utilization of attributes in InterDOW

textual field can be distiguished among plain text, HTML, XML, or other markup texts, with the help of attributes.

36. Swallow allows customized Value Converters when maps properties of .NET types to those of persistent types.

----SwallowMemo10

37. Pointers in Swallow are global pointers, that is a pointer may not only point to a native object in the same database, but also a remote one stored in

another database/datasource. Thus, a Swallow pointer is composed of three parts, they are sequentially ObjectID, RegionID, and SourceID. The last one is

SourceID, it has the least significance, and may be omitted. If it is omitted, the pointer will point to the local copy of the remote object in the same

database, which has the same ObjectID. An integrated global pointer also contains the version number and the culture info.

38. Fields of reference types must keep the same and get synchronized for all the cultures.

----SwallowMemo11

39. There are three kinds of modes to open a Swallow data source: Readonly, LockSchema, FullFunctioned. And there are three lock modes when connecting to a

Swallow datasource, they are Exclusive, ShareRead, ShareAll.

40. A Swallow datasource can be schema read-only by nature. In this case the schema will be unchangable whatever the connection mode is.

----SwallowMemo12

41. Fields of a persistent type can be set to three states to the outside client: Invisible, Readonly, Modifiable. In normal cases, a Field should be

modifiable, but some special cases Swallow want to make the Field invisible or readonly to the outside, and the value of this special field will be mantained

by the Swallow or some system from the inside. Futhure more, Types could also be Invisible, Readonly, Modifiable. The state can be changed when it is not

SystemPreserved. With the feature introduced above, Mapping in Swallow could be treated as a SystemPreserved Invisible Type, its Fields would also be

Invisible.

----SwallowMemo13

42. There are two pools/caches in a Swallow datasource, the DataPool and the ObjectPool. The DataPool is somewhat a copy of database tables cached in the

memory. It is composed of a set of 2-dimensional tables and all the primitive data are stored in the cells of those table. However, it is specialized in

providing the convenience to access data cells by InstanceID and MappingID. In order to save the memory, the hierarchied fields collections are prepared on

tables of the DataPool. All PObject instances that are referring to the same record will point to the same hierarchied collection in DataPool, sharing the

same copy of data. The ObjectPool caches ever built-up PObjects or .NET persistable objects.

----SwallowMemo14

43. If a table has subtables then all the version numbers in subtables should be counted into the master table. And the reference count on subtables should

also be aggregated to the master table.

44. Recursive composition of ValueTypes(includes Array, which is treated as a ValueType) must prohibited. For example, ValueType A can not contain A as its

Field. And it is also not permitted if A contains B, and then B contains A again. It is in this case A will contain itself indirectly.

45. UniqueID/Object, InstanceID, RecordID, MappingID.

----SwallowMemo15

46. Swallow will provide the security funcitonality at the database level, but it is optional considering the on execution performance. Users can decide

wether turn on the security checking when they access Swallow database. By the way, the user will also be recorded into the history table.

47. It is strongly recommended that the outside application reuse the built-in security system as their own security system. So the security system must be

designed to be open and extendable. That is users can extend the system with the customized functionalities. For example, it allows user defined operations

on data, and allows applying rules on filtering users(database accounts) or data(persistent objects).

----SwallowMemo16

48. In order to popularize the use of Swallow, develop ASP.NET Web Controls and Windows Controls to conveniently display Swallow objects on the Web pages and

Windows Forms.

49. Swallow should support connecting remote databases across the Internet.

50. Defines access level on each field of a persistent Type. Then security settings could be set on one level instead of each field.

----SwallowMemo17

51. Allows caculations on fields/properties of selected objects. Special syntax is introduced for this functionality, that is Object{Field:expression, ...}.

52. DataSlots are utilized by PObjects to store the actual data. Different PObjects can share the same DataSlot so that their data will be synchronized

automatically.

53. Unique constraints can be checked on the scope of all the concret tables of a class.

54. Not only Types and Fields have access modifiers, but also each object instance can have. This feature can flexiblly divides the access permissions of any

part of data into several kinds of permission levels. e.g. public, internal, private. Outside users can access public data by default.

----SwallowMemo18

55. Design a cache/pool sweeping strategy that allows customization on the priorities/precedences of objects being swept.

56. There may be data centers, registration centers, and authentication centers on the Internet, using Swallow databases to provide services of data sharing,

site registration and account authentication or user identification.

57. Persistent Object Locator can be an address pointer, a named variable, or even a function call which returns a temporary object.

----SwallowMemo19

58. Virtual database supports both dialect SQL and interpreted portable SQL.

59. Copying a persistent object can be shadow copy or deep copy, and referring a remote object can be direct reference or cached reference.

60. Define a standard, named GOI(Global Object Identifier) for locating an object in the global. It would also be able to locate and leverage the old legacy

data, by implementing some special object locator on specific data source and providing the same interface that conforms to GOI.

----SwallowMemo20

61. Persistent Type can have Calculated Fields defined. These are actually query fields as their values are derived by doing some calculations on the other

fields. These fields are not updatable, they are dedicated for convenient queries.

62. Uni-Object/UuObject represents that the object is Uniformed and Unique.

----SwallowMemo21

63. A persistent object can be SystemPreserved, ApplicationPreserved, Synchronized or Local.

64. A persistent pointer can be NullPointer, InvalidPointer, and ValidPointer.

65. PVariable is somehow like static PField, except its declaring type is null. So, maybe in Swallow, all static fields are treated as variables. That is

static fields will be represented using PVariable in Swallow.

66. If a reference typed object occurred in the SELECT list, return the address(ObjectID) together with the version number.

67. Swallow may provide the automatic incremental service for user to get a unique integer as an ID.

----SwallowMemo22

68. Two manners to synchronize remote objects: real time synchronization, delayed or scheduled synchronization(more exactly, this is an asynchronized mode).

As there must be a local copy of the remote object, we also call the local one 'Shadow Object'.

69. U = Unified / Unique / Uniformed.

70. GLUES = Global + Localizable + Unified + Encryptable + Serializable.

1. Provide external interface for searching. Based on this functionality multiple

InterDOW systems can be joined to provide world wide content searching.

2. Organize a web site as the same as a directory tree in an operating system. All the

web pages and subsites are managed as a node of the tree.

3. In order to support multiple languages more easily, organize and store all the used

titles and captions and other strings that would appear on the UI in a resource table,

mostly like what have been done in VC.

4. In the InterDOW system, some condition judgements or rules should be able to be

applied to each actions or operations, such as inserting, updating, and deleting an

object.

----InterDOWMemo1

5. Use the unique OID for object comparison by default.

6. Each article should and must be under any one of the three state during its life time

in InterDOW system. They are state under editing, approved state for publishing, and

finally in the trash after deleting. And once an article is published to the web site,

it must be bound to at one node in the site map tree.

----InterDOWMemo2

7. Add User as a system class, and Permission as a system relation, so that authorities

and privileges can be handled at the system level.

8. In addition, extend class and relation as system class. As a result of this, all the

class and relation definitions can be accessed and treated as normal objects, and this

indeed enhanced the system greatly! A system class means a class which is preserved and

protected by the system. As a user maybe you have only read permission on it.

9. Add a new base data type as Pointer, which is composed of an ObjectID and a ClassID.

10. An InterDOW site should be able to be configured as a subsite of another one.

11. Attributes should be ordinal.

---InterDOWMemo3

12. Add an extra index table that stores shortcut entries to all the objects. Using this

indexed table, you can access a specific object directly and quickly by providing the

object's OID.

13. Finite State Machine is god-given methodology in resolving complex logical processes

or protocols.

14. Enhance the functionalities of doing statistics. Need annual, monthly, weekly, and

daily statistics on the whole site and each page, each article and even each object, and

also the statistics on each IP address.

15. An InterDOW system should be able to communicate with the other data source. At

least, data communications between two InterDOW systems are necessary and unlackable.

----InterDOWMemo4

16. Treat relation as a system class. And relations are specialized object that can

automatically join all related role objects together for query.

17. Each article can have an index string, and we could gather these index strings

together into one table with each index string having direct pointer to the coresponding

article, so that users can search articles very quickly and conveniently by index, and

also the returned search results would be more meaningful and make more senses.

18. Classes and Templates can only be reused in the same InterDOW system, but can also

be exported outside for backup, and the exported classes and templates can be imported

and reused by other systems.

----InterDOWMemo5

19. We can change the font size of the current page dynamically by using JScript.

20. The InterDOW system should have the functionality of displaying information of

online visitors.

21. WODMark can be executed recursively. That is the result of one mark can still

contain marks, and also need futhure recursive replacement. This feature is convenient

for an atomic string field to contain dynamic informations.

----InterDOWMemo6

22. A purely script-coded version of InterDOW is necessary, as it does not need the

additional DLL support and can run smoothly in most virtual hosts of web-space

providers. The light-weight edition, however, is a functionality restricted edition for

it can only read the contents and execute the functions that have already been developed

by others. I call this restricted edition as 'InterDOW Reader', while the fully

functional edition as 'InterDOW Developer' or just 'InterDOW'.

----InterDOWMemo7

23. Append a ReferenceCounter field, right after the UID field, to each data resource

table.

24. It's necessary to extend SQL and implement OQL, that is the short of Object Query

Language. Use the 'Subclass OF Class' or 'Mapping OF Class' syntax in OQL to represent

an exact base table in SQL.

25. In OQL, the 'OF' syntax can be used in SELECT and UPDATE statements, and is illegal

in INSERT and DELETE statements.

----InterDOWMemo8

26. The two folders, named 'Files' and 'Assemblies', are necessary to store files

outside the database and assemblies that would be loaded dynamically at runtime.

27. Task and Message Notifications must be provided as a built-in functionality. Thus,

all tasks and messages including those of their derived type can be toally retrieved to

their respective owner.

28. Develop a trivial readonly edition of InterDOW for ASP environment.

----InterDOWMemo9

29. Use the ProfileCenter to provide the service of SSO(Single Sign-On). All the

InterDOW sites that are registered on the same profile center can share their profile

data among each other.

30. Each state node has a counter to statistic how many times it has been continuously

recycled on.

31. Provide the functionality of statistic the percentages each approval result.

32. Each persistent object including Page should have a Viewer and an Editor. Template

and Library should have a counterpart for each Skin. There is a set of styles, each skin

should all themes, and choose one theme to apply at one time. And, also, Controls,

Viewers and Editors are Skin and Theme awareness.

----InterDow10

33. Process can define parameters for the purpose of communicating with the callers

outside. And parameters can have in/out modifiers. This feature is very useful when a

sub process is being called.

34. Each Viewer/Editor must be bound to a specific persistent Type. And, a persistent

type can have multiple viewers and editors. Objects of extended types can be processed

by the base type's Viewers and Editors.

35. InterDOW will use two databases to respectively store the content to be published on

the web and the draft that is currently being edited. Meanwhile, it will also provide

the functionality of synchronizing these two databases.

----InterDOW11

36. InterDOW should allow some pages or some web elements to be shown using other skins

or themes that are different to the currently selected skin or theme.

37. Viewers and Editors should be able to be parameterized, and able to indicate the

visibility & editability of sub fields.

38. Some rights settings conform to specific environments or contexts, there is no need

to load all the rights settings every time InterDOW makes a security judgement.

39. You can define resource closures in InterDOW, and then assign a user the rights to

do administrative operations on that closure.

40. InterDOW should support the union of sub systems outside.

41. InterDOW need a HelpSystem.

----InterDOW12

42. Online Documents; Distributed Computing; Globalized Site.

43. M.V.C Model, the three aspects/factors should be separated completely and entirely.

44. Supports various presentation forms, e.g. HTML, XML, WML, WinForm, XAML, Flash,

plain text or even binary stream, etc.

45. The Flow Control, Security, and Reporting System is very important and necessary!

----InterDOW13

46. Viewers & Editors for persistent objects will have verbs, for instance, Hide() and

Lock(). A Viwer can Hide, and an Editor can Hide and Lock. These verbs can be invoked at

run time, and furture more, they can be used to set the access modifier on Viewers &

Editors, thus they can be hidden or locked. This feature allows some furture

customization and adjustment. These access modifiers are not stored in Viewers & Editors

themselves, actually they are specified when Viewer & Editor instances are dropped onto

the designer surface, that is they are stored in the pages or other Viewers/Editors that

contain or involve them.

----InterDOW14

47. Use Dynamic Compilation technology in Pages, Viewers and Editors for ouput the

presentation interfaces programmatically.

48. Various kinds of tags are available in InterDOW: Data Tag, Control Tag, and

Logical/Flow Tag.

49. A Directory can have some groups and a group can be bound to a list, and a list can

be static or dynamic.

50. Virtual Driectory can link to another directory, but directory linking can not be

passed on, that is referred directory will be omitted when a virtual directory is

expanded. And, virtual directory can still have child directories, and they would

override or hide the referred sub directory with the same name.

----InterDOW15

51. Design the run time Document Object Model for InterDOW pages and other presentation

elements. By this DOM, users can access any elements in the document hierarchy tree,

modify them, and even add new elements, delete existing ones, and all the operations

will immediately be updated to the presentaion surface. Quite a flexible programming

model it will be!

52. An Editor has a collection of client submitted values. Before the submitted input

values are updated to the bound object you can do some verifications/validations on

them, or do some other operations on them. By the way, if you want, you can also ask

either Viewers or Editors to store the values displayed in the previous response.

----InterDOW16

53. MVC = DataEngine(Swallow) + RepresentationEngine + FlowControlEngine. Other systems

are SecuritySystem, OrganizationSystem, SitePublicationSystem.