| | 6 | |
| | 7 | = What is Voyager? = |
| | 8 | |
| | 9 | Voyager is the codename for the idea of reimplementing key technologies of OS/2 and its successor eComStation on top of modern technology. It basically reimplements the Workplace Shell and some other parts of the OS/2 platform. Please read the [http://wiki.netlabs.org/index.php/Voyager_FAQ Voyager FAQ] for more. |
| | 10 | |
| | 11 | So far Voyager is nothing you can see or use yet. We invest a lot of time into the design of this project and for various reasons we decided to do the core-parts of the design in private with a rather small group of people. Right now we are working on proof-of-concept code to show that the idea works out like we plan it. Later we will do a prototype that will be released to the public as well as soon as we think it is ready for it. |
| | 12 | |
| | 13 | = Voyager in a few words (for the /. crowd :) = |
| | 14 | |
| | 15 | This page got [http://slashdot.org/articles/08/01/22/0258213.shtml linked in Slashdot], that's not a problem but we are not at a stage where we wanted that much publicity yet :) So we would like to add some more explanation in a few words here: |
| | 16 | |
| | 17 | * Voyager will not be a full featured operating system. Think of it like a full object oriented workplace that will use the underlying operating system for interaction with what users need. |
| | 18 | * Voyager will be portable. A first incarnation will probably appear on normal desktop PCs but the design will permit to use it on new devices as well like mobile phones, PDAs or even game consoles. |
| | 19 | * Voyager will work for upcoming input devices as well. Keyboard and mouse were designed in the 80ies, upcoming workplaces need real support for new things like multitouch displays. |
| | 20 | * Voyager will use its own object model. Heavily influenced by IBMs SOM (System Object Model) this will allow us to create wrappers to many existing languages and still keep the full flexibility of our design. Our objects will be binary compatible unlike about every other model used nowadays on desktop environments. See the FAQ for more information about that. |
| | 21 | * Voyager will be documented. If you ever tried to code something on a free desktop environment you know what we mean... |
| | 22 | |
| | 23 | We know that our pages look rather boring right now but we will try to change that the next months. Once we have prototypes available we will announce that on the well known channels again, with a bit of luck even Slashdot will pick it up as well. So make sure to visit us again later :) |
| | 24 | |
| | 25 | |
| | 26 | = Design of Voyager = |
| | 27 | |
| | 28 | We already started to discuss the design for Voyager, see the [http://wiki.netlabs.org/index.php/Voyager Voyager Wiki] for details. It contains details on the design and first thoughts on an Implementation and Design Guide. |
| | 29 | |
| | 30 | Unlike many other ideas before we try to implement the absolute minimum necessary to reach our goal. That means we will implement our concept on top of existing and widely used open source technology. This makes sure that we can concentrate on the interesting parts of the concept instead of loosing time with things which were already done by other programmers. |
| | 31 | |
| | 32 | Please note that the public available documentation does not resemble the current state of the project, there is internal documentation as well which will be released to the public with the prototype of the project. |
| | 33 | |
| | 34 | = Take part = |
| | 35 | |
| | 36 | You can take part in the discussion of Voyager Design and other issues. Please join the [http://dir.gmane.org/gmane.org.netlabs.voyager.devel Voyager mailing list] or #netlabs IRC channel. |
| | 37 | |
| | 38 | Even if the core-team is rather small we appreciate constructive feedback to our project! |
