Difference between revisions of "Lace support"
(→Past Attempts) |
|||
| Line 3: | Line 3: | ||
===Past Attempts=== | ===Past Attempts=== | ||
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 user want?=== | ||
| + | # ECF ok as long as it has a Lace like syntax (don't care about backward compatibility) | ||
| + | # ECF ok as long as EiffelStudio can read Ace file natively (I'm not sure what it means for writing, nor what it means for backward compatiblity) | ||
| + | # 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 13:35, 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 user want?
- ECF ok as long as it has a Lace like syntax (don't care about backward compatibility)
- ECF ok as long as EiffelStudio can read Ace file natively (I'm not sure what it means for writing, nor what it means for backward compatiblity)
- 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.
