NikiWiki - User contributions [en]

Voyager API Design Guide

2008-03-20T17:21:48Z

Simpson 2: /* The Voyager API Classes and Interface Namespace */

[[Category:Voyager]]
This page contains a first draft for the Design and Implementation Guide for the Voyager API. Please note that the codename Voyager will not appear in the resulting document anylonger, once this document has reached the final version.

Please see also the pages
* [[Voyager_API_Basics|The Voyager API Basics]] - containing the basic ideas for the Voyager API
* [[Voyager_API_Design|The Voyager API Design]] containing the design/coverage of the upcoming Voyager API

[[Voyager|Voyager Main Page]]

== Foreword ==
The Voyager API will be implemented as an object oriented class library, using the Netlabs Object Model (NOM).

In the progress of ongoing development, for different reasons it may be required that the Voyager API could use extensions, due to
* changes within the system, applications require additional interfaces to
** the underlying kernel or
** supporting libraries
* new hardware or file formats requiring support
* new concepts requiring implementation of new classes and/or frameworks (sets of classes)

In order to keep a high quality standard within the Voyager API, it is vital to ensure that contributions match the way the current Voyager API is designed and implemented. This is the task of the maintainers of the Voyager API, and is done by
* maintaining this document, defining the rules and methods for design and implementation
* providing expertise before or during the design and/or implementation of an extension (the earlier involved, the better)
* deciding if a given contribution can be accepted or has to be modified to meet the requirements for a contribution to the Voyager API

== About this document ==
This document is intended for the following people:
* developers, for understanding
** the methods and rules that are used for and apply to the task of designing and implementing additions to the Voyager API
** how to contribute extensions to the maintainers of the Voyager API
* maintainers of the Voyager API, for
** ensuring that contributed extensions apply to the rules of design and implementation described in this document and meet the requirements for a contribution
** performing the defined methods/procedures when accepting a contribution

== Design Goals for the Voyager API ==
The design goals for the Voyager API are:
* the API is implemented as an object oriented class library
* using Netlabs Object Model (NOM)
** allows bindings for non-OO compiler and script languages
** allows better binary compatibility for external extensions
* no 1-1 implementation of (one of) the underlying libraries
** trade in some flexibility for simplicity
** cover approx. 60-80% of the used cases of the supported libraries
* gain the same reputation concerning quality like the OS/2 API
** see this API as '''advertisement''' for Voyager as an '''exemplary development platform'''

== Implementing the Voyager API as an object oriented class library ==
The Voyager API will be implemented using the Netlabs Object Model (NOM), implementing a runtime for an object oriented class library. Thus the API itself will be implemented as software classes, allowing access to data and functionality by their interface, being implemented by methods (kind of functions) and members (variables).

Within the class library, all software classes are part of the class hierarchy, where specialized subclasses are derived from parent classes. Subclasses inherit the behaviour from the parent class, and extend an/or modify the behaviour of the parent class. Some of the parent classes are so-called 'abstract classes' that is they are not intended to create instances of it, but only for implementing base functionality for subclasses. A special form of this are 'virtual base classes', which do not implement any code, but only define the mandantory interface of a subclass (e.g. a virtual base class for file decoder defines that a subclass for handling of a specific file must implement the method ReadFileContents).

The complete API will be spearated into major parts by [[Voyager_API_Design|groups of classes]]. When the API is to be extended, this can happen by
* implementing the extension in a new or existing method in an existing class
* derive a new class from an existing one, and implementing the extension in this class
* define a new major API or framework and derive a complete new group of classes from the root class, implementing the extension in these classes

The following rules apply when deciding which of these options are applicable for a given extension:
* ''<not yet determined>''

Another design issue is to decide when using native compiler types (or appropriate typedef's) instead of classes for data types. In general, for maximum performance and minimum complexity, the native compiler data types should be used for simple data types. For complex data types, or where compiler implemented operators are not sufficient, data type classes should be implemented. In general, data type classes will be implemented by the Netlabs Object Model (NOM), if they are not specific to a special part of the Voyager API implemented with it.

== The Voyager API Classes and Interface Namespace ==

Cinc: this part must be reviewed and should be considered a proposal only.
 cla: all of this document must be considered as a proposal :-)

The class names and the names of the classes' methods and members are prefixed by a tag identifying the major part of the API.

the next section is not true anymore [[User:Simpson 2|Simpson 2]] 18:21, 20 March 2008 (CET) 
<strike>The reasons for the member name prefix is that the IDL compiler creates access macros with the method or member name prepended by an underscore only. If the members would not be prefixed, two classes within the entire class hierarchy could not have a method with the same name without resorting to the full method name which is built from the class name followed by the method name. </strike>
Secondly using prefixes helps identifying the class group a method belongs to.

Within a major part of the Voyager API,
* class names are prepended with an all upper case prefix, like SVC, SYS, WP, e.g. SYSObject
* member names are prepended with a lower case prefix, like svc, sys, wp, e.g. sysQueryUniverseSize()
* symbol names are prepended with an uppercase prefix with a trailing underscore, like SVC_, SYS_, WP_
* API function names are prepended with a mixed case prefix, like Svc, Sys, Wp, e.g. SysCalculateNewUniverseSize()
* Prefix for helper functions (internal, maybe static, functions not visible to the world) needs to be defined

The class hierarchy of a major part of the Voyager API starts with the class XXXObject, where XXX is the all uppercase prefix of the API Part. Most class of this API part are derived from this base class.

In addition to that the following rules apply to naming methods:
* where methods return a pointer to an object or data type
** *query* methods return a pointer to original data that may not be altered or freed
** *get* methods return a pointer to a copy of original data where the copy has to be released by the caller (destroy the object or free memory. A dedicated method to do that is ususally appropriate).

== Extending the Voyager API ==

''<to be edited>''

The following tasks are to be processed when suggesting an extension to the Voyager API:
* document new functionality
** used case
** requirements
* (*) search for (base) classes for either to
** implement it in a new or existing method in an existing class
** derive a new class from an existing one for it
** define a new major API or framework, derive from root class for it
* (*) analyse and document design options
* define testcases per design option
* (*) decide for one option, document the reasons for the decision
* implement the extension within a testcase
* perform the testcase, document results
* send contribution to the API maintainers, including
** the testcase with source
** all documentation items

For the steps marked with (*) it may make sense to discuss the existing results with the maintainers of the API, to make sure that the testcase implementation already meets all requirements and design and implementation rules.

== Accepting contributions for the Voyager API ==

''<to be edited>''

When a proposal for an extension is being sent to the maintainer team, the team will determine the maintainer for that extension (not necessarily one of the team). The proposal can be sent in as an idea only, when asking for expertise and feedback, or already as a fully implemented extension.

In order to process the extension proposal, 'the maintainer' will perform the following steps, where generally one major step will be performed only when the predecessor has been finished:
* provide expertise and feedback to the author of the extension
* review the contribution for the following aspects (if already available)
** usability of new functionality
** design options analysis and decision
** testcase implementation and results
* develop further design and implementation alternative(s), where applicable
** pass back to author for review and modification, where required
* discuss changes to this Design and Implementation Guide, where applicable/required
* perform final discussion in maintainer team
* within the maintainer team, decide to accept or reject the contribution, concerning design and implementation

* when accepted
** request further documentation for the API docs, where required
** add the extension and documentation to the Voyager API code archive
** extend the build environment in the source archive, where required
* when rejected, document reasons and, where applicable, either
** request modification
** propose design alternative(s)

It may be necessary to perform this procedure several times, before an extension is completely accepted or rejected.

== Appendix: Requirements for testcase packages ==
''<to be edited>''
* documentation
** design
** per testcase
*** description (including prerequisites)
*** how to execute
*** expected result
* compiled binaries

== Appendix: Building the Voyager API ==
''<to be edited>''
* define the standard build environment for the Voyager API
** required programs
** provided methods
*** build all, docs,
*** call debugger ?
*** build/maintain release packages
* document how to technically extend the build system for to add a new class and/or method

Developers Workshop 2007

2007-05-07T19:38:55Z

Simpson 2: /* Workshop Program */

[[Image:Logodws07.png|right|frame|The workshop logo was created by [http://www.esthereberwijn.com/ Esther Eberwijn] ]]
=== Netlabs Developers Workshop 2007 7 & 8 July Amsterdam, Holland===

This page is dedicated to the OS/2 and eComStation Developers Workshop 2007!

== News Items==
08-04-2007: Sent out a message with ticket information and how to submit presentations 
29-03-2007: Added registration info

== Registration==
The registration is open at [http://www.mensys.net/DeveloperWorkshop2007/ Mensys] now, we provide the following tickets:

* netlabs.org Developers Workshop 2007, Saturday and Sunday: 45 Euro
* netlabs.org Developers Workshop 2007, one day: 25 Euro
* netlabs.org Developers Workshop 2007, students: Free

You can register at http://www.mensys.net/DeveloperWorkshop2007/

== Workshop Program ==

We are talking to some speakers, with interesting subjects to be presented. There is no schedule yet.
If you are interested in speaking please mail to: developersworkshop@netlabs.org

There will be 7 sessions per day of 45 minutes, starting at 9:00 and ending at 17:00

=== Topics ===

We already have some topics for the workshop:
* Introduction into NOM
* Utilizing multi core processors with multiple threads
* Voyager Resources
* Using USB Modules to connect to external devices.

=== Lunch ===

During the 2 days of the workshop we arranged a lunch buffet, to be payed at the location, it will be around 12,- Euro excluding bevarages.

== Workshop Location ==

This years edition will be held in the beautiful and famous city of Amsterdam in Holland.
I won't comment on some of the more well known attractions of this city, but if you have the time, I would advise you to at least spent a day there, when you are in Holland anyway!

The event location will be:
Cultural center Griffioen of the VU Amsterdam.
It is related to the VU university of Amsterdam, the seat of Dr. Andrew Tannebaum.

It is located at the border of Amsterdam and Amstelveen, but it is very easy to reach from the city center.
http://www.vu.nl/Organisatie/index.cfm/home_subsection.cfm/subsectionid/9DB86C70-F9C7-4704-8C9D9ED46EEDB063

=== Accomodation ===
Please do not wait too long before booking a hotel or hostel, Amsterdam is still a tourist magnet!

For a cheap, but good quality, hostel look at: 
http://www.stayokay.com/index.cfm?fuseaction=Herbergen.showHomeHB&lng=2&id=3

This one is located on the edge of the city center, and close to the stops of tram line 5.

If you travel by car, the following hotel may be of interest to you, the Bastion Hotel Amsterdam/Centrum-Zuidwest: 
http://www.bastionhotels.nl/en/ourhotels/amsterdamzuidwest/

If you are looking for another hotel or hostel, being close to tram line 5 or 51 makes traveling to the location very easy !

=== How to reach the workshop ===

'''By train:'''

The event is close to station 'Amsterdam - Zuid'. If you travel with an international train you need to transfer at 'Amsterdam Duivendrecht', there are 2 direct trams from 'Amsterdam - Centraal', line 5 and 51.

'''By plane:'''

Travel to 'Amsterdam Airport Schiphol' there is an enormous amount of airlines flying there. So it should be possible to get there at a reasonable price. The airport is one stop away with the train. Be sure '''NOT''' to travel into the direction of 'Amsterdam Centraal'

'''By car:'''

Although there is plenty of free parking space '''near''' the event, be aware that parking is '''expensive''' and that there are '''high fines''' on ''not'' paying if you stay in the city of Amsterdam !!.
From all directions: travel to the 'Ring A10' and take exit 'VU Hospital'. More precise directions will follow soon.

Developers Workshop 2007

2007-03-29T19:59:59Z

Simpson 2: /* Workshop Program */

[[Image:Logodws07.png|right|frame|The workshop logo was created by [http://www.esthereberwijn.com/ Esther Eberwijn] ]]
=== Netlabs Developers Workshop 2007 7 & 8 July Amsterdam, Holland===

This page is dedicated to the OS/2 and eComStation Developers Workshop 2007!

== News Items==
29-03-2007: Added registration info

== Registration==
The registration is open at [http://www.mensys.net/DeveloperWorkshop2007/ Mensys] now, we provide the following tickets:

* netlabs.org Developers Workshop 2007, Saturday and Sunday: 45 Euro
* netlabs.org Developers Workshop 2007, one day: 25 Euro
* netlabs.org Developers Workshop 2007, students: Free

You can register at http://www.mensys.net/DeveloperWorkshop2007/

== Workshop Program ==

We are talking to some speakers, with interesting subjects to talk about. There is no schedule yet.
if you are interested in speaking please mail to: developerworkshop@netlabs.org

There will be 7 session per day of 45 minutes, starting at 9:00 and ending at 17:00

== Workshop Location ==

This years edition will be held in the beautiful and famous city of Amsterdam in Holland.
I won't comment on some of the more well known attractions of this city, but if you have the time, I would advise you to at least spent a day there, when you are in Holland anyway !

The event location will be:
Cultural center Griffioen of the VU Amsterdam.
It is related to the VU university of Amsterdam, the seat of Dr. Andrew Tannebaum.

It is located at the border of Amsterdam and Amstelveen, but it is very easy to reach from the city center.
http://www.vu.nl/Organisatie/index.cfm/home_subsection.cfm/subsectionid/9DB86C70-F9C7-4704-8C9D9ED46EEDB063

=== Accomodation ===
Please do not wait too long before booking a hotel or hostel, Amsterdam is still a tourist magnet !

For a cheap, but good quality, hostel look at:

http://www.stayokay.com/index.cfm?fuseaction=Herbergen.showHomeHB&lng=2&id=3

This one is located on the edge of the city center, and close to the stops of tram line 5.

If you are looking for another hotel or hostel, being close to tram line 5 or 51 makes traveling to the location very easy !

=== How to reach the workshop ===

'''By train:'''

The event is close to the station 'Amsterdam - Zuid'. If you travel with an international train you need to transfer at 'Amsterdam Duivendrecht', there are 2 direct trams from 'Amsterdam - Centraal', line 5 and 51.

'''By plane:'''

Travel to 'Amsterdam Airport Schiphol' there is an enormous amount of airlines flying there. Soo it should be possible to get there at a reasonable price. The airport is one stop away with the train. be sure '''NOT''' to travel into the direction of 'Amsterdam Centraal'

'''By car:'''

Although there is plenty of free parking space '''near''' the event, be aware that parking is '''expensive''' and that there are '''high fines''' on ''not'' paying if you stay in the city of Amsterdam !!.
From all directions: travel to the 'Ring A10' and take exit 'VU Hospital'. More exact directions will follow soon.

Developers Workshop 2007

2007-03-29T19:49:35Z

Simpson 2: /* Workshop Location */

[[Image:Logodws07.png|right|frame|The workshop logo was created by [http://www.esthereberwijn.com/ Esther Eberwijn] ]]
=== Netlabs Developers Workshop 2007 7 & 8 July Amsterdam, Holland===

This page is dedicated to the OS/2 and eComStation Developers Workshop 2007!

== News Items==
29-03-2007: Added registration info

== Registration==
The registration is open at [http://www.mensys.net/DeveloperWorkshop2007/ Mensys] now, we provide the following tickets:

* netlabs.org Developers Workshop 2007, Saturday and Sunday: 45 Euro
* netlabs.org Developers Workshop 2007, one day: 25 Euro
* netlabs.org Developers Workshop 2007, students: Free

You can register at http://www.mensys.net/DeveloperWorkshop2007/

== Workshop Program ==

There are no registered speakers or sessions at this moment.
if you are interested in speaking please mail to: developerworkshop@netlabs.org

There will be 7 session per day of 45 minutes, starting at 9:00 and ending at 17:00

== Workshop Location ==

This years edition will be held in the beautiful and famous city of Amsterdam in Holland.
I won't comment on some of the more well known attractions of this city, but if you have the time, I would advise you to at least spent a day there, when you are in Holland anyway !

The event location will be:
Cultural center Griffioen of the VU Amsterdam.
It is related to the VU university of Amsterdam, the seat of Dr. Andrew Tannebaum.

It is located at the border of Amsterdam and Amstelveen, but it is very easy to reach from the city center.
http://www.vu.nl/Organisatie/index.cfm/home_subsection.cfm/subsectionid/9DB86C70-F9C7-4704-8C9D9ED46EEDB063

=== Accomodation ===
Please do not wait too long before booking a hotel or hostel, Amsterdam is still a tourist magnet !

For a cheap, but good quality, hostel look at:

http://www.stayokay.com/index.cfm?fuseaction=Herbergen.showHomeHB&lng=2&id=3

This one is located on the edge of the city center, and close to the stops of tram line 5.

If you are looking for another hotel or hostel, being close to tram line 5 or 51 makes traveling to the location very easy !

=== How to reach the workshop ===

'''By train:'''

The event is close to the station 'Amsterdam - Zuid'. If you travel with an international train you need to transfer at 'Amsterdam Duivendrecht', there are 2 direct trams from 'Amsterdam - Centraal', line 5 and 51.

'''By plane:'''

Travel to 'Amsterdam Airport Schiphol' there is an enormous amount of airlines flying there. Soo it should be possible to get there at a reasonable price. The airport is one stop away with the train. be sure '''NOT''' to travel into the direction of 'Amsterdam Centraal'

'''By car:'''

Although there is plenty of free parking space '''near''' the event, be aware that parking is '''expensive''' and that there are '''high fines''' on ''not'' paying if you stay in the city of Amsterdam !!.
From all directions: travel to the 'Ring A10' and take exit 'VU Hospital'. More exact directions will follow soon.

Developers Workshop 2007

2007-03-29T19:46:24Z

Simpson 2: /* Workshop Location */

[[Image:Logodws07.png|right|frame|The workshop logo was created by [http://www.esthereberwijn.com/ Esther Eberwijn] ]]
=== Netlabs Developers Workshop 2007 7 & 8 July Amsterdam, Holland===

This page is dedicated to the OS/2 and eComStation Developers Workshop 2007!

== News Items==
29-03-2007: Added registration info

== Registration==
The registration is open at [http://www.mensys.net/DeveloperWorkshop2007/ Mensys] now, we provide the following tickets:

* netlabs.org Developers Workshop 2007, Saturday and Sunday: 45 Euro
* netlabs.org Developers Workshop 2007, one day: 25 Euro
* netlabs.org Developers Workshop 2007, students: Free

You can register at http://www.mensys.net/DeveloperWorkshop2007/

== Workshop Location ==

This years edition will be held in the beautiful and famous city of Amsterdam in Holland.
I won't comment on some of the more well known attractions of this city, but if you have the time, I would advise you to at least spent a day there, when you are in Holland anyway !

The event location will be:
Cultural center Griffioen of the VU Amsterdam.
It is related to the VU university of Amsterdam, the seat of Dr. Andrew Tannebaum.

It is located at the border of Amsterdam and Amstelveen, but it is very easy to reach from the city center.
http://www.vu.nl/Organisatie/index.cfm/home_subsection.cfm/subsectionid/9DB86C70-F9C7-4704-8C9D9ED46EEDB063

=== Accomodation ===
Please do not wait too long before booking a hotel or hostel, Amsterdam is still a tourist magnet !

For a cheap, but good quality, hostel look at:

http://www.stayokay.com/index.cfm?fuseaction=Herbergen.showHomeHB&lng=2&id=3

This one is located on the edge of the city center, and close to the stops of tram line 5.

If you are looking for another hotel or hostel, being close to tram line 5 or 51 makes traveling to the location very easy !

=== How to reach the workshop ===

'''By train:'''

The event is close to the station 'Amsterdam - Zuid'. If you travel with an international train you need to transfer at 'Amsterdam Duivendrecht', there are 2 direct trams from 'Amsterdam - Centraal', line 5 and 51.

'''By plane:'''

Travel to 'Amsterdam Airport Schiphol' there is an enormous amount of airlines flying there. Soo it should be possible to get there at a reasonable price. The airport is one stop away with the train. be sure '''NOT''' to travel into the direction of 'Amsterdam Centraal'

'''By car:'''

Although there is plenty of free parking space '''near''' the event, be aware that parking is '''expensive''' and that there are '''high fines''' on ''not'' paying if you stay in the city of Amsterdam !!.
From all directions: travel to the 'Ring A10' and take exit 'VU Hospital'. More exact directions will follow soon.

Developers Workshop 2007

2007-02-07T15:50:47Z

Simpson 2: /* Netlabs Developers Workshop 2007 7 & 8 July Amsterdam, Holland */

File:Logodws07.png

2007-02-07T15:48:39Z

Simpson 2: Logo created by Esther Eberwijn

Logo created by Esther Eberwijn

Developers Workshop 2007

2007-02-01T20:08:28Z

Simpson 2:

=== Netlabs Developers Workshop 2007 7 & 8 July Amsterdam, Holland===

This page is dedicated to the OS/2 and eComStation Developers Workshop 2007!

== Workshop Location ==

This years edition will be held in the beautiful and famous city of Amsterdam in Holland.
I won't comment on some of the more well known attractions of this city, but if you have the time I would advise you to at least spent a day there when you are in Holland anyway !

The event location will be:
Cultural center Griffioen of the VU Amsterdam.
Its related to the VU university of Amsterdam, the seat of Dr. Tannebaum.

Its located at the Border of Amsterdam and Amstelveen, but its very easy reachable from the city center.

=== Accomadation ===
Please do not wait to long before booking a hotel of hostel, Amsterdam is still a tourist magnet !

for a cheap but good quality hostel look at:

http://www.stayokay.com/index.cfm?fuseaction=Herbergen.showHomeHB&lng=2&id=3

This one is located on the edge of the city center, and close to the stops of the Tram 5.

if you look for another hotel or hostel, beeing close to Tram 5 or 51 makes traveling to the location very easy !

=== How to reach the workshop ===

'''By train:'''

The even is close to the stop 'Amsterdam - Zuid WTC' If you travel with a international train you need to transfer at 'Amsterdam Duivendrecht', there are 2 direct Trams from 'Amsterdam - Centraal' 5 & 51.

'''By plane:'''

Travel to 'Amsterdam Airport Schiphol' there is a enormous amount of airlines flying there so it should be possible to get there at a reasonable price. The airport is one stop away with the train. be sure '''NOT''' to travel into the direction of 'Amsterdam Centraal'

'''By car:'''

Although there is plenty of free parking space near the event, if you stay in the city of Amsterdam be aware that parking is expensive and that there are high fines on not paying !!. From all directions travel to the 'Ring A10' and take exit 'VU Hospital' more exact directions will follow soon

Developers Workshop 2007

2007-01-20T17:10:22Z

Simpson 2:

Netlabs Developers Workshop 2007

This page is dedicated to the OS/2 and eComStation Developers Workshop 2007!

This years edition will be held 7 & 8 July in Amsterdam Holland.

more information will follow soon !

Developers Workshop 2007

2007-01-13T21:36:48Z

Simpson 2:

Netlabs Developers Workshop 2007

This page is dedicated to the OS/2 and eComStation Developers Workshop 2007!

This years edition will be held 23 & 24 June in Amsterdam Holland.

more information will follow soon !

Voyager

2006-05-05T11:19:18Z

Simpson 2: /* Technologies to study */

==Discussion==

There is now a FAQ about the Voyager project [[Voyager FAQ|here]].

This document is already some kind of discussion, you can add your comments in here as well. For real discussion please consult the [[Mailinglists | mailinglist]] <tt>voyager-dev@netlabs.org</tt>, or use the [http://dir.gmane.org/gmane.org.netlabs.voyager.devel gmane.org web/news interface] to it.

==Documentation==
===IBM Redbooks===
* SG24-4630-00 OS/2 Warp (PowerPC Edition) A First Look
* SG24-4639-00 OS/2 Warp (PowerPC Edition) Graphical Subsystem

We do have the first one digitaly, but not the second one. In case anyone finds that, let us know.

===Darwin Documentation===
There is plenty of documentation available about Darwin, a good start is [http://developer.apple.com/documentation/Darwin/Kernel-date.html Kernel Programming], which gives a nice overview about the design of the kernel.

* [http://www.kernelthread.com/software/fslogger/ Filechange notification] in Mac OSX "Tiger".

==Technologies to study==

*[http://www.opengl.org/ OpenGL], [http://freeglut.sourceforge.net/index.php FreeGLUT], [http://www.mathies.com/cpw/about.html CPW] (Application framework for windows, menus etc.). Here's a [http://www.mathies.com/cpw/textfiles/Cpw.txt Readme text].
* [http://www.freedesktop.org/wiki/Software_2fglitz glitz] - OpenGL interface for Cairo, so one could run Cairo directly on OpenGL, see [http://www.freedesktop.org/wiki/Xegl Xegl] for a diagram.
* [http://www.usenix.org/events/usenix04/tech/freenix/nilsson.html Glitz: Hardware Accelerated Image Compositing Using OpenGL] and as [http://www.cs.umu.se/~c99drn/opengl_freenix04.pdf PDF]
* [http://dri.freedesktop.org/~jonsmirl/graphics.html The State of Linux Graphics], [http://lwn.net/Articles/149917 comments] and more [http://groups.google.com/group/linux.kernel/browse_frm/thread/c2f4978ce450ed9a/2d8842acb180b581 comments]
* [http://people.redhat.com/mclasen/Usenix04/notes.pdf Current gtk+ development]- among other topics about cairo integration and a new theme system
* [http://www.gtk.org/plan/ GTK+ Planning] - a more recent plan of GTK+ development
* [http://people.freedesktop.org/~ajax/ddc2005.pdf X on GL] states very clearly, what has still to be done
* [http://www.directfb.org DirectFB] with [http://www.directfb.org/index.php?path=Development/Projects/XDirectFB rootless XServer], [http://www.directfb.org/index.php?path=Development/Projects/DirectFBGL hardware accelerated OpenGL], [http://www.directfb.org/index.php?path=Development/Projects/GTK%2B GTK+ backend], [http://www.directfb.org/index.php/viewcvs.cgi/cairodfb an experimental Cairo backend], Qt backend, DirectVNC, SDL backend
* [http://enlightenment.org/Main/Home/index.html Enlightenment] and its support libs. Here's a [http://www.elivecd.org/ Live CD].
** Why Englightenment? So far I just knew it as a fancy desktop, what makes it special? [[User:Ktk|Ktk]] 15:39, 30 October 2005 (CET)
** Cinc: it's more than just a fancy desktop. It offers quite some libs e.g. HW accelerated canvas on top of OpenGL, libs for alphachannel blending of pics, antialiased text, imlib and quite some more.
* [http://www.gnustep.org/ GNUstep.org]
* [http://www.opensolaris.org/os/ OpenSolaris]
* [http://www.ogre3d.org/ Ogre 3D] The open source real time 3D rendering engine - for nice 3D effects on the Voyager desktop
* [http://slashdot.org/article.pl?sid=05/11/03/1744230&tid=190&tid=109 Microsoft Singularity] - interesting paper by Microsoft about a concept study of a new OS
* [http://arstechnica.com/reviews/os/macosx-10.4.ars/13 Quartz and Quartz extreme], nice article giving an overview
* [http://klik.atekon.de/ Klik]: application bundles for KDE.
* More about application bundles: [http://mozart.chat.net/~jeske/unsolicitedDave/app_wrappers_yet_again.html http://mozart.chat.net/~jeske/unsolicitedDave/app_wrappers_yet_again.html], [http://mozart.chat.net/~jeske/unsolicitedDave/next_wrapper_description.html http://mozart.chat.net/~jeske/unsolicitedDave/next_wrapper_description.html], [http://mozart.chat.net/~jeske/unsolicitedDave/kde_encap_ideas.html http://mozart.chat.net/~jeske/unsolicitedDave/kde_encap_ideas.html]
* [http://rox.sourceforge.net/phpwiki/index.php/HomePage Rox] a quite nice desktop environment with features we also seek to implement
* [http://www.symphonyos.com/ Symphony OS] - a desktop in XUL. We should integrate XUL as good as possible with Firefox
* [http://www.eyeos.org/ eyeOS] - web based OS
* [http://www.novell.com/linux/xglrelease/ Novell & Xgl] - some stuff Novell did for Xgl
* [http://wiki.x.org/wiki/XDevConf X Developer Conference] - some slides about the latest one, interesting stuff there!
* [http://chabada.sk/better-desktop/ 40+ Suggestions for a Better Desktop]
* [http://www.tango-project.org The Tango Desktop Project] - exists to help create a consistent graphical user interface experience for free and Open Source software.

===Kernels===
* http://haiku-os.org - OpenBeOS successor

== Design Decisions ==
Creating a binary compatible OS/2 clone may be tempting but is not strictly necessary. Important is the user experience. Which toolkit should be used for primary development?

===Graphics Drivers===
* [http://x.org X11]
* [http://www.khronos.org/opengles OpenGL ES] (an OpenGL only desktop without X!)
* [http://directfb.org DirectFB]
* [http://www.scitechsoft.com/products/ent/snap_linux.html SciTech Snap Graphics]

These graphics engines can be emulated vice-versa: You can run X11, OpenGL, and DirectFB programs on the same graphics driver.
We should have a look at HW support when chosing the driver system. For example I've read OpenGL drivers are not that common
(often they're not HW accelerated). A viable idea may be to just use OpenGL as the core API on top of something else. There're quite a lot OpenGL implementations
running on different low level drivers or even Mesa.

===2D API===
* [http://cairographics.org Cairo]. Cairo has a PDF-like engine which seems to be inspired by Quartz of MacOS X.
* Cairo runs on almost everything, including OS/2 and X but also directly on OpenGL hardware with Glitz. So one could use it as a complete GPI replacement without the need of X one day.
* To make things easier 24Bit screens should be the primary target. Hell it's 2005 today...

It seems there are many possiblities here!
* [http://www.ggi-project.org General Graphics Interface]
* [http://www.cairographics.org Cairo] (used by GTK+)
* [http://www.enlightenment.org/Libraries/Evas Evas] (used by Enlightenment)
* [http://www.levien.com/libart libart] (used by Gnome)
* [http://antigrain.com Anti-Grain Geometry]
* [http://www.libsdl.org Simple DirectMedia Layer]
* [http://doc.trolltech.com/4.0/qt4-arthur.html Arthur] (used by KDE)

We will have to use more than one. KDE programs use Arthur, GTK+ ones use Cairo, and so on ...
These libraries are (mostly) used for display and printing. So we won't have a consistent graphical subsystem with this multitude.

All these libraries have several backends, e.g. X11, DirectFB, OpenGL, OS/2, ...

Even if we do have to use more than one we should focus on a library that is widly supported, at the moment my impression is that Cairo will win the race. Mozilla is using it for new versions, OOo will use it and GTK+ is migrating into it as well. Also projects like Glitz will dramatically speedup the rendering in the Cairo engine. See some [http://www.osnews.com/story.php?news_id=9609 comments] of one of the GTK+ developers.

===Input Handling and Event Queue===
Between the 2D API and the window manager one layer is missing
* that cares for user input by mouse, keyboard, ...
* that knows the basics about windows and controls their behaviour (A window manager only modifies this behaviour!)
* a Session manager that manages the processes which want do to screen output
* a message architecture that connects everything and enables inter-client communication

Questions:
* Should we choose X for that? Quasi-standard, but old
* modify existing(?) systems
* port Presentation Manager -> access to source code needed
* code that ourselves?

* [http://xynth.org xynth] might be an option

=== Window Manager ===
To manage the windows we need some sort of window manager. So far most implementations are done for X, we need to abstract that directly on Cairo.

* [http://www.freedesktop.org/Standards/wm-spec Window Manager Specification Project]
* [http://tronche.com/gui/x/icccm/ Inter-Client Communication Conventions Manual] - Support this standard in order to let X applications run
* [http://www.freedesktop.org/wiki/Software_2fwaimea Waimea] - WM which is using Cairo for all rendering, they write it's for X so one would have to check if this can be separated from X as well.

==== Ideas for a new Window Manager ====
What features should a new windows manager have?

Cinc: Obviously these ideas are inspired by stuff usually found on X. The WM needed for this project isn't the kind of
WM X uses. I think WM is the wrong word for it anyway. What's needed is primarily a compositing engine which is in charge
of allocating surfaces, giving them to the app, the app draws into them and the compositor puts it on the screen.
Input support is probably needed for this layer, too, so the compositor may move and stack windows correctly.
The final appearance of the graphics drawn on the surfacces is up to the applications not the compositor. It must be
that way IMHO because no compositor coder can imagine what app developer will finally do with a given infrastructure.
E.g. creating close, maximize etc. widgets in the compositor/WM effectively prevents the application developer from
adding his own widgets or removing the given one. OTOH if there's a documented way to tinker with (per window) then it's ok.

The compositor/WM should be inspired by the Presentation manager (PM) found in OS/2. Granted it's old technology it's
unbelievable flexible. It's possible for the coder to alter the handling of every window/widget by subclassing the window procedures
provided by the system. For example the information area found in [http://www.os2world.com/cdwriting WPS-wizard] uses
this feature. PM is directed to order all the window areas differently (titlebar, close/maximize, client area) to give room for the
information area. The coders of PM never thought about the possibility to add such informations to windows back when they
did PM. It's not a hack and there's no need to change any WM code to get this to work.

Lexip: What about the common look and feel of all the headers of the client windows? I'd like to have a common theme for example, and all apps should have a header (with a little icon, and the close/minimize/... buttons) that paints according to that theme file.

Cinc: ACK. What I mean is the WM should not restrict the developer from adding/removing widgets, from modifying the way how things are done for a particular window (e.g. positioning of widgets). This also applies on how things are painted. If the developer decides to remove all widgets and use an ugly custom theme (which is bad) he should be free to do so.

===== Main Features =====
* Built i18n (internationoalization)
* .prestartup and .poststartup files
* Multiscreen support (with possibility of virtual desktops 1 being on physical screen 1, while having virtual desktop 4 on screen 2)
** Preview of desktop X on desktop Y. Like you have one desktop with the presentation on desktop X and on desktop Y (your main display for example) you see a resizable preview so you could have your script on the main display and still step through the slides
* Anti aliasing
* Virtual desktops (different layouts and number of desktops - 4x2, 3x3, ...)
* Storing sessions. Cinc: not sure the WM should do that
* 100% ewmh complient. Cinc: ???? if this is some X thingie it's probably not needed -> Lexip: yeah, it's X stuff, but if we want to support starting Xapps, and we should do that, then we gotta be ewmh complient with our WM/compositor
* Large desktops (scrolling and paging)
* Themes with possibility of associating a background image or pattern (i.e. blackbox)

===== Client Window Features =====
* Client window header can be top/bottom/right/left (with vertical text if necessary).
* Window manager keeps track of stacking order of all client windows
* Sticky windows - Possibility to show clients on all or few or just one virtual desktop
* Virtual desktops with resolutions different from the physical screen resolution.
* Ability to display multiple virtual desktops on one physical screen.
* Maximization:
** Maximize to given area
** Maximize to actual screen
** Maximize to more than one screen
** Maximize vertically only
** Maximize horizontally only
* Clients can influence their states:
** Maximized
** Stacking order
** Shading
** Stickiness
** Desktop(s)
* Window in Window handling for MDI applications
* Edge snapping while move- resizing a client window
* Client window shading
* Store client window properties per application (size, position, etc)
* Client window can drop shadow
* Application icons in client window headers
* Different focus models (click to focus, focus follows mouse, ...)

===== Docking Area Features =====
* Allow having multiple docking areas
* Docking areas can be hid (approaching mouse makes them appeare)
* Transparency
* Drop shadow

Cinc: The WM should not be in charge of this. The Dock (or whatever) is just an application and should be treated as one.

Lexip: question again about the theme. If the WM/compositor is not in charge of the docker, how can we set a common theme to it?

Cinc: The WM/OS should provide the default bitmaps for it (or better any app) which can be queried by the app. Changing the theme will automatically change these BMPs. For buttons and alike the OS should provide a default drawing function which will ensure every app which uses the default automatically has a similar look and feel.

===== Menu Features =====
* Dynamically filled menus (piped menus). Cinc: That's mostly up to the application IMHO with the exception of system menus.
* Menu configuration can be separated over several files, i.e. one file for each submenu section
* All the submenues can be called separatly (by key combination for example)
* Dockable menues (like blackbox)
* Transparency
* Drop shadow
* Icons for entries

Cinc: I think the WM/compositor should only provide the infrastructure to show menus. The final appearance/usability is up to the app.

Lexip: Here I'm talking about the system menu. The menu where you can start all you apps, or anything that you'd like to have in a menu. System menu is startable by right clicking on an empty spot on the background, or by keying-in some keyboard combination.

Cinc: IMHO such a system menu also should be a dedicated app (so it is replacable without tinkering with the WM). This app monitors the input queue and reacts when the configured message arrives (keyboard/mouse/whatever). Or alternatively the WM sends a message to tell this app to show the menu .

===== Configuration Features =====
* Configuration changes take effect withou restarting the wm
* Every single command is configurable to hava a certain keyboard or mouse click shortcut.
* Shortcuts are simple keyboard shortcuts (i.e. Ctrl+F1), or so called keychains known from Emacs editor (i.e. Alt+e+x)
* The wm allows mouse gestures, and keyboard mouse combined input (i.e. ctrl+mouse1 click, etc.)
* Single, double, or even tripple clicks call different actions (attention with patent from M$ in USA)
* Clicking the client window header is a different action than clicking the clients body for example. Cinc: can easily be done by treating those two as two coupled windows.

===== Extensibility =====
* Programming interface (every single command can be called from outside).
* Allow writing modules and applications that interact with the wm. Cinc: ah ok, addresses some of my concerns from above

===== Other =====
* Ability to play (opengl) games in fullscreen on virtual desktops instead of physical screens. (Today, if a game goes fullscreen, it'll either spread over all physical screens or the other screens are switched off... which is not nice if you would like to have the server stats/a map/whatever on the secondary screen).

Lexip: that sounds as a nice idea to me. we gotta do that

==== Started development on Neptune ====
I started the development of the window manager. The project is called '''neptune''', since this planet is one of those being observed by NASA's initial Voyager I mission.
Currently I'm developing under XOrg, and have the physical screens simulated by several Cairo Surfaces (the whole window manager will be based on the multi screen design).
Neptune has a to early state to publish anything. Currently I'm just experimenting with different architecture approaches, and am trying to figure out the best way to implement the multiscreen handling.
Once everything is done, it should be easy to "port" it to run without the X server, since all the painting is done through cairo. So it should be a matter of having glitz using a framebuffer GL backend instaed of the glx.

=== CMD ===

* full capabilities of current CMD.EXE concerning
** usage of system messages and error codes
** nested io redirection
** grouping commands with round brackets
** &, && |, and || operators
** correct wildcard matching for files with multiple extensions
** PROMPT command
** keep UPPERCASE environment variable names only ! (unlike 32-bit Command Interpreter from Jonathan de Boyne Pollard)
* proper implementation of EXTPROC command (fix errors with exptproc scripts not residing in current
directory)
* new general features
** support extended command set of Win NT CMD.EXE
*** at least include string functions with extended SET command
** extend IF clause with new conditions
*** os version match
*** free space on a drive
*** is drive removeable
*** is drive USB mass storage
*** more ?
*** easy syncing/unmounting for usb mass storage devices
** support PATHEXT variable
*** start files with their associated program
** automatic environment vars
*** DATE, DATE_SORTED, TIME, TIME_SORTED, WEEKDAY, DAY, MONTH, YEAR, YEARDAY
*** CMDLINE, ERRORLEVEL
*** OS, OSVER
*** BOOTDRIVE
** support filename completion
* new internal or extended commands
** INITVIOCMD determines a command being executed when initialized as a VIO session
** INITPMCMD determines a command being executed when initialized as a PM session
** SET allows to include equal signs in value of environment var
** SET /P retrieves value of environment var from keyboard
** SHIFT xx shifts parameter by positive number
** ECHO /N does not append CRLF to output
** CDD command changes directory and drive
** TIMER command starts, stops or displays the value of a timer
** SLEEP n waits for n secs
** PAUSE n waits for n secs
** implement START command with all features of DosStartSession, among others implement
*** /WAIT (synchronous start)
*** /NC (NoAutoClose)
*** /DOS[:settings.dat] (if DOS-Box still available)
*** /POS:x,y,x1,y1 (initial window position)
*** /ICON:icon.ico (system menu icon)
** MOVE files with implicit copy/delete across partitions
** exlicit UNLOCK command
** implicit unlock with COPY, DEL, REN, MOVE (very usefull, but also dangerous ?)
** macro support with ALIAS command
* new batch handling or batch commands
** %* specifies all parameters (like %1, %2 etc)
** in for loops support %%a%f, %%a%p, %%a%d and more for specifying filename, path and driveletter of matching file
** GOSUB - executes a subroutine
** RETURN [xx] - exits a batchfile or subroutine [with errorlevel]
** CANCEL (ends batch processing, but does not close window as EXIT does)
* Integration of any REXX replacement like with current CMD.EXE
** call of REXX Scripts with CMD
** usage of exit handlers
** manipulation of environment vars within REXX (changes remain after end of script, unless setlocal/endlocal() is called), including BEGINLIBPATH and ENDLIBPATH
** readonly access to the LIBPATH value as an environment variable

=== MM ===
* The concept of IO procedures should be retained at least for file IO and format converting.

===Toolkits===

*GTK+
*GnuStep (look at Apples programs to see what's possible. Yes I know Apple uses Cocoa not Gnustep)
*other?

===SOM===

Dropping SOM for something better? Creating a poor mans SOM kernel isn't too difficult (Cinc: there's already a working prototype for the basic functionality).

If SOM is dropped, no binary compatibility for old WPS enhancements is given. This may break a considerable amount of OS/2 apps. This may not be an issue if applications have to be recompiled anyway for a new plattform. Cinc: I don't see many OS/2-apps which are worth to be supported no matter how much work it needs. Binary compatibility is out
of sight IMHO. Nobody really needs it (anyone really using OD nowadays?).

Cinc: Note for those with reading (well more with comprehension problems): I'm talking here about SOM and WPS programs, '''not''' OS/2 programs in general (maybe someone noticed the headline which says "SOM"). Anyone knows any widespread commercial WPS extension except ObjectDesktop??? I don't. I don't believe it's worth to support the almost not existant WPS integration of StarOffice5.xx. Geez, that thing is from the computer stoneage now. So before whining about missing WPS binary compatibility first try to find something needing it...
The remaining critics are invited to add binary compatibility if they want it. Nobody will hinder them. Quite the opposite, the toolkit comes with every eCS so just join the effort.

=== Desktop (WPS) ===

* The WPS should be designed with REXX scriptability in mind (like WPS-wizard addon)

Work is in progress. See the [[desktop]] page.

'''Note:''' Don't use the linked page for discussion. If you want to discuss use this section or the discussion page (hey that's what it was made for).

==== Spirit and Purpose of the WPS ====
The WPS only shows those parts of the computer system you have to deal with as a user.

Its objects are taken from the user's world of experience. The implementation details are hidden.

It is very intuitive to use. A Graphical GUI shows you, what is possible to do and what not. (Unlike a command line! The unix shell TAB key is a notable exception. But generally this can easier shown with graphics.)

The WPS is only for the user! Programs have DLLs and APIs of their own. (If not, then there is something missing on the system.)

Some WPS objects show or represent system details. That is, because daily administration tasks can also be regarded as "usage".

==== Security ====

Security should be a concern when creating the desktop application. GTK isn't secure by design so the desktop won't be either. Nevertheless we shouldn't open additional holes. The concept of the desktop allows arbitrary class and method replacement. So trojans can do whatever they want with it when they manage to get into the desktop app.

Ideas:

* Only allow signed/hashed classes to be loaded
* Maybe require that every author uses GnuPG to sign his/her class
* User has to allow loading any additional classes once
* "Save" classes will be listed in the users save class list
* The save class list is signed (GnuPG) to prevent altering

Is this sufficient?

=== REXX ===
* REXX should be implemented like AppleScript so controlling of applications from other apps is possible (commands not tied to one process).
* [http://regina-rexx.sourceforge.net/ Regina] may be used as an interpreter.
* any REXX replacement should implement the following
** true CMD integration like under OS/2
*** access to environment vars of the calling interpreter. Cinc: ???
** support of the full REXX C API or an equivalent concept (macro space control, app handlers, WPS object access API etc). Most of this is supported by Regina AFAIK.
** complete reimplementation of REXXUTIL ! I seem to remember having seen such a project for Windows and Unix.
* It should be possible to write GUI based apps with REXX, a bit [http://www.edm2.com/0601/drdialog.html Dr.Dialog] like

=== Network Transparency ===
It would be cool to execute applications remotely.

What we don't want is a distributed operating system like Amoeba or Inferno.

The network transport would be inside Cairo or between Cairo and OpenGL.
(Above Cairo makes no sense, because Cairo can also manipulate memory-stored images; below OpenGL is too much data overhead.)

When a user runs an application remotely, he wants to access devices on the client and the server. Examples for devices are
* printers
* mice, keyboard
* audio
* screens
* hard disks
* USB attached devices
* DVD burners

We need some kind of abstraction layer. It would be nice, if everything can be controlled by WPS objects:
* drag application on computer -> application gets executed there
* double-click (or also drag'n'drop) keyboard object -> this keyboard works for my console session

=== Backward Compatibility ===
The question about backward compatibility is indeed a good one, it's risky to break with the current OS/2 API for religious reasons but one should have a look at that more from a technical point of view. The OS/2 API is not really modern anymore, programming directly on PM is much more work than using a modern toolkit like GTK+.

At the moment it's unfortunately unlikely that PM and WPS source get released by IBM.

Options:

* implement parts of PM and GPI on top of the new 2D API and try to integrate it with the toolkit choosen (same look & feel, clipboard support, D&D, etc. That's a lot of work, the question is if this is really necessary. We would have to do the same for supporting other toolkits like qt (which is a requirement).
* Implement only some crucial parts to ease source code migration. For example message queues, concept of object windows (often used to comunicate with background threads).
* Map often used PM-functions to counterparts of the chosen toolkit.
* Use a VM and run OS/2 or eCS inside the VM. There are very promising opensource VMs like
** [http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ XEN]
** [http://fabrice.bellard.free.fr/qemu/ QEMU]

XEN seems to be the most promising one at the moment because it will support dual core CPUs in the future so one can run the guest OS on a separate CPU core. So far one had to alter the guest OS in sourcecode but that changes at the moment because they integrate parts of QEMU sourcecode inside XEN to emulate those parts (memory allocation and such stuff).

== Stuff ==
* With the advance of virtualization technologies like XEN, Vanderpool and multicore cpus it becomes more and more common to have a second, virtual computer running in a VM. It should be possible to map the virtual screen of the VM to a physically existing display. (The idea is to give the user the feeling that he actually has two different computers (with a shared set of input devices). It might even be possible to add another set of input devices, so that two users could work on one computer. (one or maybe even both using an emulated computer...)

Lexip: I think this should be no problem, since the WM will feature virtual desktops, which can be placed on any physical screen. Thus, if one places the virtual desktop holding the VM on a physical screen, you have what you want to. It will even be possible to split screens, and let several virtual desktops share one screen.

* [http://herpolhode.com/rob/ugly.pdf What's bad about Unix]. Nice reading
* [http://en.wikipedia.org/wiki/Plan_9_(operating_system) Plan 9]. The system the author of the reading above advocates to some degree. Not compatible enough, but interesting concepts.

== Questions==
* the Xegl diagram mentioned above only shows the path of the graphics; the path of e.g. mouse and keyboard input is missing; that's not as trivial as it sounds (it has been [http://lwn.net/Articles/149783 missing in Xegl], when that was stopped); will we use OS/2-like driver model or wait for x.org 7.0 (currently RC1!) and take out the input system from there? Other sources (hotplug, ...)?
* one good thing about OS/2 are the fast interactions when you click somewhere, like opening a folder or getting the focus on a window. Why is that like this? We should try to keep that stuff fast.
** I think the problem of current user interfaces is that they have a lot data dependencies. This increases the response time as they often have to wait for the data to become available before they can start to draw. Data dependencies mostly stem from an overdose of flexibility (I'm talking windows xp now).
*** XP's start menu: it is based on the directory structure in the startmenu folder. So in order to draw the menu it has to read from the hard disk several times as it needs to find out the structure and load the icons of the programs (they are mostly cached after the first time).
*** Drive windows, where the window needs to gather/update the drive information before it can be drawn the first time.
*** Explorer windows that display extended file info (eg id3 tags of mp3s) need to parse the files first. (in xp a corrupt media file can block the explorer, before you even get the chance to touch it)

Short:
Eyecandy and advanced/unnecessary features (even when switched off) waste cpu time.

* do we want the traditional window manager<->application scheme? With the Gnome/KDE interfaces? Then we are deep in X again ...
** the question is if we can incooperate the WM functionality in GTK somehow. As far as I remember [http://fresco.org/ Fresco] implemented GTK API as well so one might have a look at that.
** IMO GTK runs on top of a WM. The WM just gives GTK a surface to work with but manages where on screen this surface will be painted. Even OS/2 has something like a WM managing the windows for us.

* As soon as we further expand the usage of WPS objects, the templates folder will grow and likewise the number of possible interactions and combinations of objects.
** How can the objects be sorted or structured so that the template folder won't scare of casual users? Answer: Just use the means of the WPS to do so. Override the right methods and use your programming brain. It's all documented int the WPS Programming Reference.
** How can we tell the users about interactions?
*** Example Drag'n'Drop: When the user starts dragging, display possible targets with arrows, colors, or other marks?

Or even let the objects come out of their hiding place, if they are not visible on the screen or in subfolders?
*** Example Creating of structures: XWorkplace has "Create new" in the context menu with the entries "Data File", "Folder", "Url Folder", "Program Object" as standard. The idea is good, but can be better. Take a strategy game you don't know and build up a base very fast. Now let an OS/2 newbie do the same with OS/2 objects. It is much more complicated. There is no way to see what objects fit into each other and you have to know that there is a templates folder and there is a system setup folder with palettes and themes. You could sum up these sentences as the demand for "Feedback for the Users".

== Implementation ==
You will find links to pages with some beef here later on. While the Voyager page is mainly for discussion and brainstorming the following pages go into detail and present the actual design decisions, roadmaps etc.

* Information about the [[desktop]] development.

== Press coverage ==
We slowly start to get some press:

* [http://slashdot.org/article.pl?sid=06/02/17/1423225 Slashdot - Keeping the OS/2 Flame Alive]
* [http://software.newsforge.com/software/06/01/30/192226.shtml?tid=150&tid=132&tid=16 And the original at Newsforge]

Xmltools

2006-03-26T10:33:23Z

Simpson 2:

== XML Tools available on netlabs ==

this page is intended to give a list of XML tools available at netlabs, and a description on how to build these libraries, since most of them come from the unix world.

== xmlsoft.org Libraries ( libxml2, libxslt and libexslt ) ==

Tools needed:
- GCC 3.5.5
- Libc 0.6.1
- Make 3.81
- Unix like shell

User:Simpson 2

2005-08-29T08:35:18Z

Simpson 2:

Bart van Leeuwen

blah

Main Page

2005-04-24T09:02:47Z

Simpson 2: Spam removed

Welcome to the Wiki at netlabs.org. You will find a lot of interesting information about OS/2 and [http://www.ecomstation.com eCS] on this page. 
If you are interested in joining the '''community mailinglist''' please have a look [[Mailinglists | here]]!

== New Logo and Redesign ==
* [[Redesign]] - The new logo is choosen and a first and hopefully final draft for the new site layout has been created - check it out ;)

== Development ==

NOTE: This section should not be extended anymore. We reloaded the [http://www.edm2.com EDM/2 magazine] and we recommend to put all developer stuff in there. This wiki is a mess at the moment and we will clean that up one day and migrate the stuff that makes sense to EDM/2. Thanks!

This section contains hints and tricks and descriptions of undocumented
stuff. Undocumented means there's no official documentation or the
documentation (for example included on DevCon CDs) isn't available to
the public anymore. But DON'T JUST COPY any documentation you may have into the Wiki. Keep in mind it's copyrighted!

* [[Undocumented stuff]]
* [[Mozilla]] - some stuff regarding building Mozilla on OS/2
* [http://www.edm2.com/index.php/SDL SDL] - some tips & tricks about how to port applications using SDL to OS/2
* [http://www.edm2.com/index.php/How_to_program_for_the_WPS WPS] - how to program for the [http://en.wikipedia.org/wiki/Workplace_Shell WPS]. Note: the german Wikipedia may have more information about the WPS. Go [http://de.wikipedia.org/wiki/Workplace_Shell here].

==netlabs.org Community==
===Resources===
* [http://www.netlabs.org netlabs.org] itself, the main page :-)
* [[IRC server settings]] - chat with netlabs.org coders
* [[Mailinglists]] - support for our projects per mailinglist or news-reader

===Developers===
We also hire a developer at the moment, to show you what he does we provide a small weekly list of his progress on various projects.
*[[Vladest]]
*[[Samm]]

===Publicity===
* [[Presentations]] about netlabs.org (prepared for Warpstock Europe)
* [[Logos]] in different resolutions, free to use

==OS/2 and eCS resources==
===Drivers===
*Visit http://www.os2warp.be if you want to know if your hardware is supported.
*See a [http://www.ecomstation.it/pido2/home/mircomir/fixpak.php?lang=en driver list] generated from eCSoft/2 database.

===Software===
For software have a look here:

* http://hobbes.nmsu.edu
* http://en.ecomstation.ru/apecs.php
* http://www.ecomstation.it/ecsoft2/
* http://www.unixos2.org - ported *nix tools. A little bit cumbersome to find stuff there but nevertheless worth the effort

===Programs===
How to use specific programs, HowTos, FAQs etc.

(nothing yet)

==netlabs.org Servers==
===ToDo's & History===
This is the list of tasks for netlabs.org Webservers & the history of what I (ktk) did
*[[netlabs.org]]

===Mail account===
Some information for those who own a mailbox at netlabs.org
*[[netlabs.org Mailing]]

===Admin Guide===
So far it's more or less just me who does all the work on netlabs.org webpages and this somewhat sucks because like this a lot of stuff depends on my lazyness. The following document explains the tasks necessary to create a new project at netlabs.org, including setting up CVS repositories, creating webpages and so on. I hope that I will find some volunteers one day who help me on doing that.
*[[Admin Guide]]

== What is a Wiki ==
*If you don't know the concept of a Wiki yet we recommend you to have a look at the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide MediaWiki User's Guide].
*If you just want to add some content without much reading read the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide:_Editing_overview#The_wiki_markup Markup Overview].
*If you have no clue about Wiki you might first check [http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page how to edit a page].

Main Page

2005-04-23T08:10:38Z

Simpson 2: Spam removed

Welcome to the Wiki at netlabs.org. You will find a lot of interesting information about OS/2 and [http://www.ecomstation.com eCS] on this page. 
If you are interested in joining the '''community mailinglist''' please have a look [[Mailinglists | here]]!

== Shop ==
We do have a shop for shirts and more ... [http://shop.netlabs.org shop.netlabs.org]! Prices include a small extra to support netlabs.org's future... (Does anyone know how to add an image here :-P ?)

== New Logo and Redesign ==
* [[Redesign]] - The new logo is choosen and a first and hopefully final draft for the new site layout has been created - check it out ;)

== Development ==

NOTE: This section should not be extended anymore. We reloaded the [http://www.edm2.com EDM/2 magazine] and we recommend to put all developer stuff in there. This wiki is a mess at the moment and we will clean that up one day and migrate the stuff that makes sense to EDM/2. Thanks!

This section contains hints and tricks and descriptions of undocumented
stuff. Undocumented means there's no official documentation or the
documentation (for example included on DevCon CDs) isn't available to
the public anymore. But DON'T JUST COPY any documentation you may have into the Wiki. Keep in mind it's copyrighted!

* [[Undocumented stuff]]
* [[Mozilla]] - some stuff regarding building Mozilla on OS/2
* [http://www.edm2.com/index.php/SDL SDL] - some tips & tricks about how to port applications using SDL to OS/2
* [http://www.edm2.com/index.php/How_to_program_for_the_WPS WPS] - how to program for the [http://en.wikipedia.org/wiki/Workplace_Shell WPS]. Note: the german Wikipedia may have more information about the WPS. Go [http://de.wikipedia.org/wiki/Workplace_Shell here].

==netlabs.org Community==
===Resources===
* [http://www.netlabs.org netlabs.org] itself, the main page :-)
* [[IRC server settings]] - chat with netlabs.org coders
* [[Mailinglists]] - support for our projects per mailinglist or news-reader

===Developers===
We also hire a developer at the moment, to show you what he does we provide a small weekly list of his progress on various projects.
*[[Vladest]]
*[[Samm]]

===Publicity===
* [[Presentations]] about netlabs.org (prepared for Warpstock Europe)
* [[Logos]] in different resolutions, free to use

==OS/2 and eCS resources==
===Drivers===
*Visit http://www.os2warp.be if you want to know if your hardware is supported.
*See a [http://www.ecomstation.it/pido2/home/mircomir/fixpak.php?lang=en driver list] generated from eCSoft/2 database.

===Software===
For software have a look here:

* http://hobbes.nmsu.edu
* http://en.ecomstation.ru/apecs.php
* http://www.ecomstation.it/ecsoft2/
* http://www.unixos2.org - ported *nix tools. A little bit cumbersome to find stuff there but nevertheless worth the effort

===Programs===
How to use specific programs, HowTos, FAQs etc.

(nothing yet)

==netlabs.org Servers==
===ToDo's & History===
This is the list of tasks for netlabs.org Webservers & the history of what I (ktk) did
*[[netlabs.org]]

===Mail account===
Some information for those who own a mailbox at netlabs.org
*[[netlabs.org Mailing]]

===Admin Guide===
So far it's more or less just me who does all the work on netlabs.org webpages and this somewhat sucks because like this a lot of stuff depends on my lazyness. The following document explains the tasks necessary to create a new project at netlabs.org, including setting up CVS repositories, creating webpages and so on. I hope that I will find some volunteers one day who help me on doing that.
*[[Admin Guide]]

== What is a Wiki ==
*If you don't know the concept of a Wiki yet we recommend you to have a look at the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide MediaWiki User's Guide].
*If you just want to add some content without much reading read the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide:_Editing_overview#The_wiki_markup Markup Overview].
*If you have no clue about Wiki you might first check [http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page how to edit a page].

Wpstkvsxwphelpers

2005-04-02T15:15:27Z

Simpson 2:

=== WPSTK vs. xWPHelpers ===

This page is intended to discuss features of xwphelpers to be merged into WPSTK. It is also a place for dicussing shortcommings in XWPhelpers and how we could fix them.

=== xWPHelper functions not in WPSTK ===

* Container Control helpers, I can't live without them !
* Dialog Formater helpers, I takes a bit getting used to, but then they are really handy !

=== xWPHelper implementation problems ===

* NLS code is not using the locale when available [[user:Simpson_2|I'm]] working on this

User:Simpson 2

2005-04-02T15:14:53Z

Simpson 2:

Bart van Leeuwen

XWorkplace

2005-03-25T13:03:11Z

Simpson 2: /* XWorkplace: Future plan */

=== XWorkplace: Future plan ===

This page is intended to dicsuss future updates or additions to XWP.

* Create a logoff feature, which basicly does everything shutdown does, but afterwards exits the WPS, like with restart WPS, instead of shutting the machine down. This way you could return to a login dialog easily.
* Finish the font dialog ( use ft2lib ? )
* Finish the file dialog, or better fix it, and implement it as discussed in: [[ideas#wps]]
* Make XWP and WPSWizzard/CWMM/ADC aware of eacht other. Please point out which problems arise when these packages are installed in parallel so we have point for starting discussion ;-).
* Extend Program object to allow for env variables to be set
* Add the possibilty to save the application settings '''once'''. So you can do your setup like you want it, you logoff once and it will be saved but it won't save it each time you logoff.
* Compile against GCC

XWorkplace

2005-03-24T09:09:41Z

Simpson 2: /* XWorkplace: Future plan */

XWorkplace

2005-03-24T09:06:40Z

Simpson 2: