I am not sure what to think about this yet. I am in a middle of some experimenting/researching of reading and writing external files. The aim of my research is to make a good use of new v.lines property. Right now, I don't see great benefit of having it because in current Leo's code it is hard to make any substantial improvement by using this property. Mostly improvements would be just in better readability (which is a good thing to have, but not a must).
There are several possibilities for gently introduction of this property. One would be to replace attribute `_bodyString` with yet another property which when set directly can issue a warning to user and set the `_sync` attribute accordingly. That way we can keep backward compatibility and prepare for transition, and what is more important give users time to find good use of this new property. The other possibility is to make `v.lines` property one way synchronized i.e. when set it can adjust immediately _bodyString, and when read it can use g.splitLines(v._bodyString). It can however keep a copy of last _bodyString that was split, and when asked again if _bodyString is still the same value, then return last tuple of lines. That can be solution for a while. It won't break anyone's code, but it can give opportunity to users to get used on new property. I shall write more about my research once when I have something to show. One question: Do we have somewhere examples of external files that use all of Leo's directives that can be used for testing? If we don't have it yet, is anybody willing to make or share such examples files in this forum or on github. Vitalije -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
