Tutorial - Revision history

217.71.128.84: /* Create interface definition */

2004-11-05T03:22:51Z

Create interface definition

← Older revision		Revision as of 05:22, 5 November 2004
Line 13:		Line 13:
	== Create interface definition ==		== Create interface definition ==

	As fast as you selected base class you need to define new methods and attributes of your new class. This job can be (in most cases MUST BE) done via [[Interface Definition Language]].		As fast as you selected base class you need to define new methods and attributes of your new class. This job can be (in most cases MUST BE) done via [[SOM:Interface Definition Language\|Interface Definition Language]].

213.84.84.66 at 17:55, 4 November 2004

2004-11-04T17:55:16Z

← Older revision		Revision as of 19:55, 4 November 2004
Line 6:		Line 6:


	: The '''WPUrl''' class in Warp 4 is an example for choosing an appropriate base class for the derived class. Any URL object must obviously save it's URL somewhere. So the WPUrl class is simply derived from '''WPDataFile''' and the URL is saved as normal text in the file. So every WPUrl object is in fact a normal file in your file system. You may easily ~~proove~~ that by just opening an WPUrl object in a normal text editor.		: The '''WPUrl''' class in Warp 4 is an example for choosing an appropriate base class for the derived class. Any URL object must obviously save it's URL somewhere. So the WPUrl class is simply derived from '''WPDataFile''' and the URL is saved as normal text in the file. So every WPUrl object is in fact a normal file in your file system. You may easily proof that by just opening an WPUrl object in a normal text editor.


	In general you should choose a base class which has most of the functionality you'll need so you don't have to reimplement it.		In general you should choose a base class which has most of the functionality you'll need so you don't have to reimplement it.

	== Create interface ~~definetion~~ ==		== Create interface definition ==

	As fast as you selected base class you need to define new methods and attributes of your new class. This job can be (in most cases MUST BE) done via [[Interface ~~Definetion~~ Language]].		As fast as you selected base class you need to define new methods and attributes of your new class. This job can be (in most cases MUST BE) done via [[Interface Definition Language]].

Prokushev: /* Create interface definetion */

2004-11-04T03:35:27Z

Create interface definetion

← Older revision		Revision as of 05:35, 4 November 2004
Line 13:		Line 13:
	== Create interface definetion ==		== Create interface definetion ==

	As fast as you selected base class you need to define new methods and attributes of your new class. This job can be (in most cases MUST BE) done via [Interface Definetion Language].		As fast as you selected base class you need to define new methods and attributes of your new class. This job can be (in most cases MUST BE) done via [[Interface Definetion Language]].

Prokushev at 03:34, 4 November 2004

2004-11-04T03:34:56Z

← Older revision		Revision as of 05:34, 4 November 2004
Line 10:		Line 10:

	In general you should choose a base class which has most of the functionality you'll need so you don't have to reimplement it.		In general you should choose a base class which has most of the functionality you'll need so you don't have to reimplement it.

			== Create interface definetion ==

			As fast as you selected base class you need to define new methods and attributes of your new class. This job can be (in most cases MUST BE) done via [Interface Definetion Language].

80.131.44.131 at 09:03, 2 November 2004

2004-11-02T09:03:22Z

← Older revision		Revision as of 11:03, 2 November 2004
Line 1:		Line 1:
			== Select an appropriate base class ==
	Before starting you've to think about the features of your new WPS class. Do you need persistant storage (this means data will survive a reboot), just a fancy notebook for your program or do you want to create a special filesystem class with specific behaviour?		Before starting you've to think about the features of your new WPS class. Do you need persistant storage (this means data will survive a reboot), just a fancy notebook for your program or do you want to create a special filesystem class with specific behaviour?

Line 6:		Line 7:

	: The '''WPUrl''' class in Warp 4 is an example for choosing an appropriate base class for the derived class. Any URL object must obviously save it's URL somewhere. So the WPUrl class is simply derived from '''WPDataFile''' and the URL is saved as normal text in the file. So every WPUrl object is in fact a normal file in your file system. You may easily proove that by just opening an WPUrl object in a normal text editor.		: The '''WPUrl''' class in Warp 4 is an example for choosing an appropriate base class for the derived class. Any URL object must obviously save it's URL somewhere. So the WPUrl class is simply derived from '''WPDataFile''' and the URL is saved as normal text in the file. So every WPUrl object is in fact a normal file in your file system. You may easily proove that by just opening an WPUrl object in a normal text editor.


			In general you should choose a base class which has most of the functionality you'll need so you don't have to reimplement it.

80.131.49.14 at 08:56, 28 October 2004

2004-10-28T08:56:55Z

New page

Before starting you've to think about the features of your new WPS class. Do you need persistant storage (this means data will survive a reboot), just a fancy notebook for your program or do you want to create a special filesystem class with specific behaviour?

Depending on the desired feature set you will choose the class your new class will be derived from. For example if you only need access to the WPS or want to signal something using WPS features deriving your class from '''WPTransient''' is a good idea because such a class will never save any data anywhere on your system.
If you want to save some data in your filesystem you have to derive your class from '''WPFileSystem''' or one of it's subclasses.

: The '''WPUrl''' class in Warp 4 is an example for choosing an appropriate base class for the derived class. Any URL object must obviously save it's URL somewhere. So the WPUrl class is simply derived from '''WPDataFile''' and the URL is saved as normal text in the file. So every WPUrl object is in fact a normal file in your file system. You may easily proove that by just opening an WPUrl object in a normal text editor.