Description


There is a subsystem mechanism for signatures, but this is merely for presentation purposes. I want to have a subsystem for components (and signatures) that can be used to identify a component and have more than 1 version of a component (or signature).

Use Case


\"I want to distribute components to growing the Uniface world. I believe the time is there to spread the Uniface word over the world and a good set of basic components can stimulate this process. I truly believe there are more initiatives out there. But what if the user wants to modify one component of a larger set and there is a new version of the complete set? The modified component is overwritten by \'my\' version. I believe this is a major issue, this all or nothing thing. What I want, to overcome this, is an extra identifier to a component (or signature): - the extra identifier is a kind of subsystem or group. I call it subsystem - subsystem must by declared by the developer in the UDE (or asn) - In the component editor the subsystem may be used (default is empty) - use this ID in the newinstance and/or activate the component or signature: activate \"\"SUBSYTEM.COMPONENTNAME\"\".operation(params) - SUBSYTEM is optional - a component can have more than 1 implementation. In every subsystem a component can have an implementation. - in the asn a setting contains the sequence of SUBSYTEMs - there is always an default subsystem. This is the \'leave it all empty\' situation. Example: there are 3 user defined subsystems: myApp (the application that is developed and used), myStandard (the modified components of the standard) and someStandard (some standard they are using) [SETTINGS] subsystem_sequence = myApp, myStandard, someStandard, default In this example all modified components of the standard must be placed in the myStandard. When the developer of the standard delivers a new version, this is placed in the someStandard. example 2: With this technique it is also possible to have some basis versioning system. Uniface will search in the most recent version at first [SETTINGS] subsystem_sequence = AppVersion1.1, AppVersion1.0b, AppVersion1.0a, AppVersion1.0, default\"

Importance


When you want to deliver standard components to the Uniface community it is very important to give the user the ability to modify this, but also the give the users the possibility to import a new version without any trouble. Now this is quiet impossible to do with ease. One has to create a new repos and lots of searching. With this wish the user can import the components in a different subsystem and have it\'s own modification in another.

Type


Uniface Development Environment

Operating System


Windows

Status


Open

Leave a Reply