GPMSWiki/DeveloperDocumentation/MigrationHelp/APIChanges - Revision history

Admin: 4 revisions

2011-10-26T06:17:51Z

4 revisions

← Older revision	Revision as of 08:17, 26 October 2011
(No difference)

imported>MichaelDondrup at 14:03, 6 November 2008

2008-11-06T14:03:42Z

← Older revision		Revision as of 16:03, 6 November 2008
Line 8:		Line 8:
	== Changes ==		== Changes ==

			* Dokumentation is improved, all packages contain POD documentation.
	* Method '''project''' is now: '''init_project''' and '''release_project'''. Use init to connect to a project and release to disconnect prior to changing to another project. You '''must''' release before you can init a second time, otherwise risking malfuncton. Be careful: method ''project'' still exists but does something different /!\ Don't use it /!\		* Method '''project''' is now: '''init_project''' and '''release_project'''. Use init to connect to a project and release to disconnect prior to changing to another project. You '''must''' release before you can init a second time, otherwise risking malfuncton. Be careful: method ''project'' still exists but does something different /!\ Don't use it /!\
	* All attribute accessor methods use consistent spelling: lowercase		* All attribute accessor methods use consistent spelling: lowercase
Line 44:		Line 45:

	</nowiki></pre>		</nowiki></pre>


			To demonstrate a full-blown Application_Frame with the use of callbacks, have a look at ''share/perl/GPMS/Application_Frame/Sample.pm'' (GPMS::Application_Frame::Sample) in the cvs repository.

imported>MichaelDondrup at 13:59, 6 November 2008

2008-11-06T13:59:09Z

← Older revision		Revision as of 15:59, 6 November 2008
Line 12:		Line 12:
	* All attributes returning arrays are consistenly plural syntax, all scalar values singular		* All attributes returning arrays are consistenly plural syntax, all scalar values singular
	* All Classnames are consistently named in singular: '''Rights''' --> '''Right'''		* All Classnames are consistently named in singular: '''Rights''' --> '''Right'''
			* Own Application_Frame is now mandatory: Now you '''must''' have your own subclass of GPMS::Application_Frame. Put this module into the share/perl/GPMS/ folder within '''your''' application path.
			Don't put it into the GPMS module. Naming covention should follow GPMS::Application_Frame::<[[ProjectClass]]>

			A minimal Application_Frame should look like this:


			<pre><nowiki>

			Example: The Minimal Application_Frame

			package GPMS::Application_Frame::Minimal;

			use strict;

			use base('GPMS::Application_Frame');

			1;

			sub master_class {

			return 'Minimal::DB';

			}

			sub db_type {

			return 'MinimalDB';

			}


			</nowiki></pre>

imported>MichaelDondrup at 13:45, 6 November 2008

2008-11-06T13:45:21Z

← Older revision		Revision as of 15:45, 6 November 2008
Line 8:		Line 8:
	== Changes ==		== Changes ==

	* Method '''project''' is now ~~use~~: '''init_project''' and '''release_project'''. Use init to connect to a project and release to disconnect prior to changing to another project. You '''must''' release before you can init a second time, otherwise risking malfuncton. Be careful: method ''project'' still exists but does something different /!\ Don't use it /!\		* Method '''project''' is now: '''init_project''' and '''release_project'''. Use init to connect to a project and release to disconnect prior to changing to another project. You '''must''' release before you can init a second time, otherwise risking malfuncton. Be careful: method ''project'' still exists but does something different /!\ Don't use it /!\
			* All attribute accessor methods use consistent spelling: lowercase
			* All attributes returning arrays are consistenly plural syntax, all scalar values singular
			* All Classnames are consistently named in singular: '''Rights''' --> '''Right'''

imported>MichaelDondrup at 13:39, 6 November 2008

2008-11-06T13:39:51Z

New page

__NOTOC__
= List of Changes in the GPMS API =

This list is non exhaustive and Perl only although we try.....

More or less sorted by frequency of occurance in our code:

== Changes ==

* Method '''project''' is now use: '''init_project''' and '''release_project'''. Use init to connect to a project and release to disconnect prior to changing to another project. You '''must''' release before you can init a second time, otherwise risking malfuncton. Be careful: method ''project'' still exists but does something different /!\ Don't use it /!\