I totally agree with you, it may seem totally weird to cut the way back to leo, unless you have to confront great resistance against the "suspicious additional cryptic comment lines in the code".
People sometimes simply focus on the wrong things :) But we can't just declare leo as the measure of all things and ignore arguments like "what if every developer's favorite editor put additional structural information in the code" . You may get problems to find the actual code. I mean, let's face it. One argument for good test frameworks is that they are "non-intrusive" means you do not have to hold special information in the code. A shadow node seems one way how to address that, just you more than double the amount of data to handle and don't really know how leo handles major code changes in a node.. Your approach to "sentinels light" is the best I could think of so far, because they kind of just blend in. You still have the problem of conventions and people not working with leo may not follow them, or accidently destroy the intended information. I also see no real solution to this (there may be none because it has to do with people's preferences) so the best way to handle it would be to blend in as much as we can, or work alone :) or in a leo dev group. -- Stefan ------- Original message ------- > From: Ville M. Vainio <[email protected]> > To: [email protected] > Sent: 27.6.'09, 21:06 > > > On Sat, Jun 27, 2009 at 9:25 PM, Stefan on GMail<[email protected]> > wrote: > >> When I want sentinel free source I just change the @thin to @nosent and >> save the files. >> >> The sentinels are gone then, wish I had find a "macro" for that to put >> that >> on a button. > > Despite the fact that I question your motives for this, you could try > creating > > @button thin-to-nosent > > for p in c.find_h('@thin(.*)'): > matchobj = p.mo > tail = matchobj.group(1) > p.h = '@nosent ' + tail > >> I would wish even more for @thin / @file nodes that respect a @silent >> directive in the body like in @root nodes. Same applies for an @path and >> @root-code directive in the body lsomething like ike @thin-code and/or >> @file-code. > > Making @thin nodes silent would be completely against the point of > @thin nodes in the first place. > > -- > Ville M. Vainio > http://tinyurl.com/vainio > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
