Tony Balinski wrote: > Quoting Thorsten Haude <[EMAIL PROTECTED]>: > > > I wrote this before I even had a closer look at the code (which I > > still hadn't), just because it's 7k of manual.
Because it has a manual, it must be intimidating? I rather think it is good style to document the things, else they'll be lost -- even for oneself;-) > > For this purpose, eg. a 'Find All' and a 'Show Changes', each with > > some bells and whistles seems to be a much better choice. All it > > should say is: "Look this is what you could do with rangesets!" Honestly, I didn't pick up Uwe's macros and made some changes to contribute them to a dotNEdit release. I did it, because these macros provided all the functions I was too lazy to write myself. They missed only a single function I use often and therefore had written for myself. So, the idea was to merge it in and have it all. I won't volunteer to write macros specialized for saying "Look this is what you could do with rangesets!". IMO, the thumbs rule is the things you use yourself have the best chance to be useful for others, too. > I tend to agree with this: for rangesets I would supply a "find all", a "mark > with rangeset" (add the selection to a rangeset, like a marker pen function), > a "goto marked range" (to find one marked area among the many in the > rangeset), and the "diff current document against the last stored file". These > are essentially the functions I wanted when I first wrote the RS code, and I > think they would allow users to learn how to roll their own. Yes, if one has special needs, but why to re-invent the wheel for the functions ready to be used? The provided macros are just for the things you mention. They also provide comfortable dialogs to choose or change colors and to give names to the rangesets. Just recall the manViewer discussion about the wish to change colors. This should rather lead to the thought to use the RSI dialogs (they are really nice, letting you try out colors until you're satified) also for rangesets that were *not* defined by the RSI macros. > > (Now while I wrote the above I clicked a bit through the RSI; I think > > you could do nice things with externally stored rangesets and a hook > > which loads them. Neat.) > > Hold on there, Thorsten! Don't get carried away! Well, we don't need hooks. But who should feel disturbed when he can also store the rangeset information between sessions? All I had a problem with would be to write such macros myself, but they were already there (thanks to Uwe!), so why hiding them? Jörg -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
