On Jan 12, 6:45 am, "Edward K. Ream" <[email protected]> wrote: > On Wed, Jan 11, 2012 at 4:35 PM, Juraj <[email protected]> wrote: > > *EVERY* time I got a bit creative with applying clone nodes and other > > advanced Leo features to my workflow (managing JSP files using @shadow > > nodes, sometimes I edit the files in Eclipse as well), I really ran into > > "lost data/leo crashes/unreadable files" kind of bugs. > > Thanks for these comments. The integrity of Leo's data is paramount. > Please report any kind of bug that causes lost data.
Let me amplify my thanks. I have had, for several years now, a growing sense that there could be a new, simpler, more general vision for Leo. There are many behind-the-scenes aspects of Leo that seem too complex. Perhaps chief among them are the various rules for handling conflicting clones, and multiple paths for cloned @<file> nodes. Your post was only the latest in a series of "wake up calls". The previous was Terry's comment that he doesn't use or trust clones. Coming from one of Leo's most important users this was more than a little surprising. I also share your impression that Leo is a niche product at present, although there may be thousands of people who use Leo regularly--it's hard to know. My goal is to discover some way of making Leo easily accessible for many more people. I've had this goal for at least several years. Some major new invention is likely needed. What that new invention might be is murky at present. At present I am focused on fixing all the bugs that would prevent the next "official" release. In some sense, that's not so important now that *stable* daily builds are available, but bugs have to be fixed, and the sooner the better. After the official release goes out the door I'll give more attention to the big picture. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
