Voyager API Design - Revision history

Cinc: /* highlevel GUI - GUI */ Stub page for classes

2007-08-30T20:22:10Z

highlevel GUI - GUI: Stub page for classes

← Older revision		Revision as of 22:22, 30 August 2007
Line 75:		Line 75:
	* text window (support for terminal window)		* text window (support for terminal window)
	* Add more...		* Add more...

			[[Gui_class_list\|Preliminary list of GUI classes]] to be implemented.

	== Desktop Objects - WP ==		== Desktop Objects - WP ==

Cla: /* System Component Configuration - SYS or CFG */ added comment on driver config

2007-08-26T10:56:20Z

System Component Configuration - SYS or CFG: added comment on driver config

← Older revision		Revision as of 12:56, 26 August 2007
Line 45:		Line 45:
	Here is a list of goals:		Here is a list of goals:
	* encapsulates any kernel specific means of configuration		* encapsulates any kernel specific means of configuration
			** like driver config (per config.sys, registry, ini file ...)
	* implements an internal (?) database for configuration data (like OS2.INI or Registry)		* implements an internal (?) database for configuration data (like OS2.INI or Registry)
	* may superseed DMI, and a DMI implementation may use this part of the API		* may superseed DMI, and a DMI implementation may use this part of the API

Cinc: Typo police...

2007-08-21T05:14:16Z

Typo police...

← Older revision		Revision as of 07:14, 21 August 2007
Line 7:		Line 7:

	'''Please note'''		'''Please note'''
	* The page is organized as a list of sections, where each section names a specific major part of the Voyager API (with the ~~excetipon~~ of the section ''Virtual Base Classes'')		* The page is organized as a list of sections, where each section names a specific major part of the Voyager API (with the exception of the section ''Virtual Base Classes'')
	* The title of the major part includes the proposed prefix for class/method/Symbol names (here: class name prefix, all uppercase)		* The title of the major part includes the proposed prefix for class/method/Symbol names (here: class name prefix, all uppercase)
	* Each section API may be used as a base for an API of another section, where applicable		* Each section API may be used as a base for an API of another section, where applicable

Cla: added proposals for class prefixes per major API part

2007-08-18T15:01:39Z

added proposals for class prefixes per major API part

← Older revision		Revision as of 17:01, 18 August 2007
Line 8:		Line 8:
	'''Please note'''		'''Please note'''
	* The page is organized as a list of sections, where each section names a specific major part of the Voyager API (with the excetipon of the section ''Virtual Base Classes'')		* The page is organized as a list of sections, where each section names a specific major part of the Voyager API (with the excetipon of the section ''Virtual Base Classes'')
			* The title of the major part includes the proposed prefix for class/method/Symbol names (here: class name prefix, all uppercase)
	* Each section API may be used as a base for an API of another section, where applicable		* Each section API may be used as a base for an API of another section, where applicable
	* Take into account that the API will likely be implemented as an object oriented class library. Using the Netlabs Object Model this will be compiler and language independent (so e.g. C and Classic REXX can also be used)		* Take into account that the API will likely be implemented as an object oriented class library. Using the Netlabs Object Model this will be compiler and language independent (so e.g. C and Classic REXX can also be used)
Line 16:		Line 17:
	[[Voyager\|Voyager Main Page]]		[[Voyager\|Voyager Main Page]]

	== System Resources & Management ==		== System Resources & Management - SYS ==
	This section implements system near resource handling (including kernel related hardware)		This section implements system near resource handling (including kernel related hardware)
	* Wrapper for Kernel Services, Memory, Interrupts, Timer, ACPI		* Wrapper for Kernel Services, Memory, Interrupts, Timer, ACPI
Line 24:		Line 25:
	* Add more...		* Add more...

	== Basic Device Input/Output ==		== Basic Device Input/Output - DEV ==
	This section implements input and output from and to peripheral hardware for applications, and encapsulates existing APIs (where possible, in a unified manner)		This section implements input and output from and to peripheral hardware for applications, and encapsulates existing APIs (where possible, in a unified manner)
	* Keyboard, Mouse		* Keyboard, Mouse
Line 34:		Line 35:
	* more...		* more...

	== System Security ==		== System Security - SYS or SEC ==
	This section implements access restrictions and other security methods.		This section implements access restrictions and other security methods.
	* refer to Security/2 design ?		* refer to Security/2 design ?
	* Add more...		* Add more...

	== System Component Configuration ==		== System Component Configuration - SYS or CFG ==
	This section implements configuration of system components (possibly also application components via a framework ?)		This section implements configuration of system components (possibly also application components via a framework ?)

Line 49:		Line 50:
	* Add more...		* Add more...

	== System Service Management ==		== System Service Management - SVC ==
	This section implements the means for managing system or application services		This section implements the means for managing system or application services
	* see the design sketch from Warpstock Europe 2005 as a proposal: [http://www.clanganke.de/os2/pres/wse2005/all04_en.sdd ALL04 - Service Management for OS/2 and eComStation] (requires StarOffice 5.1 or OpenOffice.org)		* see the design sketch from Warpstock Europe 2005 as a proposal: [http://www.clanganke.de/os2/pres/wse2005/all04_en.sdd ALL04 - Service Management for OS/2 and eComStation] (requires StarOffice 5.1 or OpenOffice.org)
	* Add more...		* Add more...

	== Unified Data Access ==		== Unified Data Access - ??? ==
	This section implements a unified view on data (fuse alike)		This section implements a unified view on data (fuse alike)
	* Filesystem Protocols incl. Named Pipes (Samba, NFS, more...)		* Filesystem Protocols incl. Named Pipes (Samba, NFS, more...)
Line 60:		Line 61:
	* Add more...		* Add more...

	== lowlevel graphics ==		== lowlevel graphics - GPI ==
	This section implements basic GUI stuff.		This section implements basic GUI stuff.
	* primitives (lines, circles, more...)		* primitives (lines, circles, more...)
Line 67:		Line 68:
	* Add more...		* Add more...

	== highlevel GUI ==		== highlevel GUI - GUI ==
	This section implements highlevel GUI features used for creating windows, controls and so forth.		This section implements highlevel GUI features used for creating windows, controls and so forth.
	* frame window		* frame window
Line 74:		Line 75:
	* Add more...		* Add more...

	== Desktop Objects ==		== Desktop Objects - WP ==
	This section implements nothing less than all classes that implement the workplace Shell replacement.		This section implements nothing less than all classes that implement the workplace Shell replacement.
	* (a.k.a. Workplace Shell Replacement and its objects)		* (a.k.a. Workplace Shell Replacement and its objects)

Ktk at 09:18, 31 July 2007

2007-07-31T09:18:59Z

← Older revision		Revision as of 11:18, 31 July 2007
Line 1:		Line 1:
			[[Category:Voyager]]
	Welcome to the Wiki Page explaining the design of the Voyager API.		Welcome to the Wiki Page explaining the design of the Voyager API.

Cinc: Added link to support class list

2007-07-31T07:35:14Z

Added link to support class list

← Older revision		Revision as of 09:35, 31 July 2007
Line 88:		Line 88:
	Here is a first list:		Here is a first list:
	* [http://svn.netlabs.org/v_nom Netlabs Object Model (NOM)], runtime for the Voyager specific API (see the [[Voyager_API_Basics#Design_goals_for_the_Voyager_API\|Design goals for the Voyager API]])		* [http://svn.netlabs.org/v_nom Netlabs Object Model (NOM)], runtime for the Voyager specific API (see the [[Voyager_API_Basics#Design_goals_for_the_Voyager_API\|Design goals for the Voyager API]])
	* support classes (strings, arrays)		* support classes (strings, arrays). [[support_class_list\|Preliminary list of classes]] to be implemented.
	* application protocols (including filesystem access)(see section Application protocols)		* application protocols (including filesystem access)(see section Application protocols)
	* Resource Management<br>see design proposal from netlabs.org Developers Workshop 2007: [http://www.clanganke.de/os2/pres/dws2007/resources/index.html Managing Sets of Program Resources]		* Resource Management<br>see design proposal from netlabs.org Developers Workshop 2007: [http://www.clanganke.de/os2/pres/dws2007/resources/index.html Managing Sets of Program Resources]

Cla: modified comment on link to Voyager Basics

2007-07-30T18:49:05Z

modified comment on link to Voyager Basics

← Older revision		Revision as of 20:49, 30 July 2007
Line 2:		Line 2:

	Please see also the pages		Please see also the pages
	* [[Voyager_API_Basics\|The Voyager API Basics]] - containing the basic ideas ~~and design goals~~ for the Voyager API		* [[Voyager_API_Basics\|The Voyager API Basics]] - containing the basic ideas for the Voyager API
	* [[Voyager_API_Design_Guide\|The Voyager API Design and Implementation Guide]] - containing the methods and rules for implementing the Voyager API		* [[Voyager_API_Design_Guide\|The Voyager API Design and Implementation Guide]] - containing the methods and rules for implementing the Voyager API

Cla: added link to "The Voyager API Design and Implementation Guide"

2007-07-30T14:25:10Z

added link to "The Voyager API Design and Implementation Guide"

← Older revision		Revision as of 16:25, 30 July 2007
Line 1:		Line 1:
	Welcome to the Wiki Page explaining the design of the Voyager API.		Welcome to the Wiki Page explaining the design of the Voyager API.

	Please see also the ~~page~~ [[Voyager_API_Basics\|The Voyager API Basics]], containing the basic ideas and design goals for the Voyager API.		Please see also the pages
			* [[Voyager_API_Basics\|The Voyager API Basics]] - containing the basic ideas and design goals for the Voyager API
			* [[Voyager_API_Design_Guide\|The Voyager API Design and Implementation Guide]] - containing the methods and rules for implementing the Voyager API

	'''Please note'''		'''Please note'''

Cla: /* (Virtual) Base Classes */ extended title with "frameworks", added NOM and Resource Management, including hyperlinks

2007-07-28T20:35:45Z

(Virtual) Base Classes: extended title with "frameworks", added NOM and Resource Management, including hyperlinks

← Older revision		Revision as of 22:35, 28 July 2007
Line 77:		Line 77:
	[[Desktop_class_list\|Preliminary list of desktop classes]] to be implemented.		[[Desktop_class_list\|Preliminary list of desktop classes]] to be implemented.

	== (Virtual) Base Classes ==		== (Virtual) Base Classes & Frameworks ==
	This is not a real major API part, but a placeholder for all parts of the API, where we could create (virtual) base classes to allow easy and future safe extension of the Voyager API~~. The topics listed here~~ could be ~~included in some~~ of the ~~major~~ sections, ~~the reason to summarize it here is to make clear that we need to have a method to create such classes as little frameworks~~ in a ~~consistent way~~.		This is not a real major API part, but a placeholder for all parts of the API, where we could either
			* create (virtual) base classes to allow easy and future safe extension of the Voyager API or
			* create a general framework for a given purpose

			Depending on the issue, a given framework or (set of) base classe(s) possibly could be put into one of the above main sections as well, or end up in a completely new section. This may happen during the discussion.

	Here is a first list:		Here is a first list:
			* [http://svn.netlabs.org/v_nom Netlabs Object Model (NOM)], runtime for the Voyager specific API (see the [[Voyager_API_Basics#Design_goals_for_the_Voyager_API\|Design goals for the Voyager API]])
	* support classes (strings, arrays)		* support classes (strings, arrays)
	* application protocols (including filesystem access)(see section Application protocols)		* application protocols (including filesystem access)(see section Application protocols)
			* Resource Management<br>see design proposal from netlabs.org Developers Workshop 2007: [http://www.clanganke.de/os2/pres/dws2007/resources/index.html Managing Sets of Program Resources]
	* file or stream format encoder/decoder		* file or stream format encoder/decoder
	* System Configuration Components		* System Configuration Components

Cinc: /* Desktop Objects */

2007-07-25T06:35:07Z

Desktop Objects

← Older revision		Revision as of 08:35, 25 July 2007
Line 74:		Line 74:
	This section implements nothing less than all classes that implement the workplace Shell replacement.		This section implements nothing less than all classes that implement the workplace Shell replacement.
	* (a.k.a. Workplace Shell Replacement and its objects)		* (a.k.a. Workplace Shell Replacement and its objects)

			[[Desktop_class_list\|Preliminary list of desktop classes]] to be implemented.

	== (Virtual) Base Classes ==		== (Virtual) Base Classes ==