Talk:Deprecated Features: Difference between revisions

From Planimate Knowledge Base
Jump to navigation Jump to search
(Created page with 'This pages docuemtnts features which are due to be removed from Planimate. Please discuss any thoughts or concerns with Rick. FEATURE REPLACE WITH STATUS <br>DATASET1 to …')
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
This pages docuemtnts features which are due to be removed from Planimate. Please discuss any thoughts or concerns with Rick.
This page docuents features which are due to be altered/removed from Planimate. Please discuss any thoughts or concerns with Rick.  


FEATURE
{| cellspacing="1" cellpadding="1" border="1"
|-
| Feature
| Replaced By
| Remove<br>
|
Comments<br>


REPLACE WITH
|-
|
DataSet 1


STATUS
(Scenario)<br>


Saving<br>


| DataSet2
|
Q1 '10<br>


|
A DataSet2 configuration table can be created from a DataSet1 definition.


Ability to load DataSet1 will persist beyond DataSet1 saving for 6 months.<br>


<br>DATASET1 to DATASET2 migration support<br>(builds a dataset2 table from a dataset1 selection)<br>Discuss phasing out of dataset1<br>PHASE1: phase out saving / UI<br>PHASE2: phase out dataset1 loading<br>Move compatability window forward - currently PL can load from version 390 which is version 4.33i. A lot has changed and become obsolete and it would be good to discard compatibility code, particularly the View Panel load code and old track code.<br>This process should only occur once a stable current version is established, then that version acan become a “rosetta” version used in bringing models forward in the future.
|-
| Model Version Loading<br>  
| -<br>
| Q1 '10<br>  
| Nearly 300 versions supported including many obsolete objects and constructs. A&nbsp;"rosetta"&nbsp;version will be declared after which all compatibility will be removed except that version.<br>
|-
| Dialog Box defined in Routine and Paint Buttons<br>  
| Named Dialog Boxes defined in panel.<br>  
| Q1 '10<br>  
|
Currently dialog boxes are defined within routine code. It is desirable for them to be defined outside of the routine and then just "called up" by name.  


This is needed if routines are to be made pasteable as text.


This does create some scope issues since the scope of the dialog might differ from the scope of the routine calling it.


|-
| Panel Label List
| Object Labels
| Q1 '10
| With the removal of view panels, there is no need to have a panel label list since all panels can be identified using the object-index of their owning portal.
|-
| Shared routines
| Messages,messages with parameters.
| Q1 '10
|
Shared routines currently allow one description of a routine to be copied to many locations automatically. In practice, the copy process (at the start of the run) is too slow and they dont save memory.


It is intended to remove them.


<br>
|}


<br>
[[Category:~TBD]]
 
[[Category:Obsolete]]

Latest revision as of 18:38, 20 December 2009

This page docuents features which are due to be altered/removed from Planimate. Please discuss any thoughts or concerns with Rick.

Feature Replaced By Remove

Comments

DataSet 1

(Scenario)

Saving

DataSet2

Q1 '10

A DataSet2 configuration table can be created from a DataSet1 definition.

Ability to load DataSet1 will persist beyond DataSet1 saving for 6 months.

Model Version Loading
-
Q1 '10
Nearly 300 versions supported including many obsolete objects and constructs. A "rosetta" version will be declared after which all compatibility will be removed except that version.
Dialog Box defined in Routine and Paint Buttons
Named Dialog Boxes defined in panel.
Q1 '10

Currently dialog boxes are defined within routine code. It is desirable for them to be defined outside of the routine and then just "called up" by name.

This is needed if routines are to be made pasteable as text.

This does create some scope issues since the scope of the dialog might differ from the scope of the routine calling it.

Panel Label List Object Labels Q1 '10 With the removal of view panels, there is no need to have a panel label list since all panels can be identified using the object-index of their owning portal.
Shared routines Messages,messages with parameters. Q1 '10

Shared routines currently allow one description of a routine to be copied to many locations automatically. In practice, the copy process (at the start of the run) is too slow and they dont save memory.

It is intended to remove them.