4 votesEsteban Montecristo commented
I'd like to suggest:
1.a way to identify a value's kind at the i6 level.
2.a way to create kinds of lists or indexed text, etc... It would allow the author to easily override standard phrases. For example, if one want to be able to store style instructions into indexed texts:
A styled text is a kind of indexed text.
The example styled text is a styled text. It is "/b/bold/i/italic/r/roman".
To say (ST - styled text):
write a routine that converts /b/ or /i/ etc into the corresponding style instruction.
One would also need to write: let T be "/b/Yo !/r" (styled text).
3. Why not turn all the values into objects ? I think that would be easier for both the newbie and the programmer : inform 7 would get smoother (there are still problems with rules or activities "on values".
4. also, more flexibility with the property kind would be cool. I've already written code that allows one to set the P property of an object to a value. I still have to find a way to repeat through the properties of an object.
18 votesEsteban Montecristo supported this idea ·
3 votesEsteban Montecristo shared this idea ·