[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Framers@xxxxxxxxxxxxxx, Framers@xxxxxxxxx
Subject: FM and Revision Control Systems
From: eric.dunn@xxxxxxxxxxxxxxxxxxxxxxxxxxx
Date: Wed, 1 May 2002 11:55:10 -0400
Sender: owner-framers@xxxxxxxxx
Following Chris' suggestion/musings about the effect of UIDs on MIF files stored in versioning systems, the following idea struck me. Why not script FM to save as MIF and then strip the MIF of ALL MIF code that is not absolutely necessary (PERL or other tool). This would remove some of the conflicts and difficulties identifying changed content and it would have the advantage of greatly reducing the amount of data stored by the versioning system. The versioning system could also control template use. If you strip the MIF of all catalogues and formatting information this information would be replaced by the contents of the template used when opeinthe MIF file. With appropriate programming it should be possible to link MIF files in the versioning system with FM template files that could alos be checked into the system. Another thought: As long as you're scripting and manipulating the FM file and resultant MIF, some standards enforcement could be accomplished at the same time. For example, ensuring charater formats are used instead of manual overrides. Eric L. Dunn ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **