I am still in the process of taking in all the new information found at the information hub we lovingly call WikiWorld. I want to participate in ObjectWiki but am feeling a bit overwhelmed by all the different directions of research I could explore. Could WE put together a concise list of references, either internal or external (to WikiWorld), that would bring a new or potential collaborator up to speed. Might also include just a very basic example of an instance of an object that is generally familiar.

In my newfound vernacular: { ? ? ? }

<OutputError>In trying to describe this using total system terminology (made that up), I realized we dont have a class of software that develops new software (to my knowledge). My analogy just broke down.</OutputError>

The ability to have self modifying code is what make modern computers (Von Neuman Archetecture) general purpose.

==== Object oriented principles

==

Everything is an object.
Objects communicate (send and receive messages) (i always left this one out for some reason)
Objects only respond to messages.
Object inherit behavior/attributes

WikiWorld:ObjectWikiClassroom."Object oriented principles".listSize = 4

===Exercise: Define a high level object class.

=

Define an object that represents an initiative. Will be used to describe the high level direction(s) a collaborative is taking or may take. Answers the question, "What is this collaborative working on right now?" Should include a collection of goals, objectives, <more>

===First Attempt

=

====class:WikiObject

==

====className: initiative or WikiInitiative

==

====Purpose:

==

To provide a high level summary of all the major projects(threads, discussions) the collaborative is working on. Will help existing and potential WikiUsers determine how they can best serve the collaborative.

====projectPage: CollaborativeWebObjects

==

====relatedPages:

==

HomePage
<addMore>

====author: everybody

==

====properties:

==

goals(objectives)
introduction
tasks
sponsor(s)

===Discussion:

=

This may simply become a type of page and may not need to be defined as an object. I am still trying to wrap my mind around the whole idea of ObjectWiki. One of the first methods of learning is emulation or mimicking. I have tried to mimic some of the things previously posted.

Unfortuantely, ObjectWiki is still pretty fuzzy, as soon as we specify something we start to question it. The main issue in learning object wiki now is which aspects are we keeping and which will we improve. We can explore that in ObjectWikiDesignLab and continue here with the basics.

Everything is an object, the LanguageOfObjects defines their interactions. Unlike most formal object system, ObjectWiki supports objects in the state of becomming. Thus formal class definitions are not always required and each reference to an object becomes a instance that inherits from the referenced object all that is not specifically overridden.

===Exercise: Define a small, basic set of objects from which all other objects can be defined.

=

This exercise is not required for the purposes of ObjectWiki. See OrdinalObjects and [[Meta Classes in ObjectWiki|A discussion of why metaclasses, and object classes are not needed in ObjectWiki|]].

LanguageOfObjects, ObjectWikiDesignLab, PrinciplesOfObjects.