Difference between revisions of "Lace support"
(→What user want?) |
(→What some users want?) |
||
| Line 4: | Line 4: | ||
You can look at [http://eiffelsoftware.origo.ethz.ch/index.php?title=ConfigurationFileFormat&oldid=1914 our file format page] for the initial three attempts for ECF. | You can look at [http://eiffelsoftware.origo.ethz.ch/index.php?title=ConfigurationFileFormat&oldid=1914 our file format page] for the initial three attempts for ECF. | ||
| − | ===What some users want?=== | + | ===What some users may want?=== |
| − | # ECF ok as long as it has a Lace like syntax (don't care about backward compatibility) | + | # ECF ok as long as it has a Lace like syntax (don't care about backward compatibility, we only read this new Lace format) |
| − | # ECF ok as long as EiffelStudio can read | + | # ECF ok as long as EiffelStudio can read the old Lace format natively (meaning that writing a modification may introduce breaking changes, or have the option to not write out what might break things, aka like a Word document when you save it for an old version of Word). |
| − | # ECF not ok we want the old Ace file with copy/paste solution to build software | + | # ECF not ok, we want the old Ace file with copy/paste solution to build software |
===Future solution=== | ===Future solution=== | ||
Provide a Lace-like syntax for which the tools can read and write directly. | Provide a Lace-like syntax for which the tools can read and write directly. | ||
Revision as of 14:37, 11 January 2007
Page to formalize how to create a Lace format that is compatible with ECF without breaking compatibility with the Lace format as implemented in version 5.6 and earlier of EiffelStudio.
Past Attempts
You can look at our file format page for the initial three attempts for ECF.
What some users may want?
- ECF ok as long as it has a Lace like syntax (don't care about backward compatibility, we only read this new Lace format)
- ECF ok as long as EiffelStudio can read the old Lace format natively (meaning that writing a modification may introduce breaking changes, or have the option to not write out what might break things, aka like a Word document when you save it for an old version of Word).
- ECF not ok, we want the old Ace file with copy/paste solution to build software
Future solution
Provide a Lace-like syntax for which the tools can read and write directly.
