Aside: I've modified the writeup of the Nedit Folding: Design: "Back End" document (http://twiki.org/cgi-bin/view/Wikilearn/NeditFoldingDesignBackEnd). One set of revisions was aimed at taking out at least some of the "I"s and "me"s, so it may be more comfortable to read now. I have put some new very rough stuff in (rough in the interest of time) which may have put some of those back. It is still a very rough document, with some misleading wording.
However, for the approach to a folding back end which may need little or no C code (the "Proof of Concept" approach), I have a question (or two) for Bert about the Macro Hook/Event Binding System. Quoting from the Talk (Discussion) page: http://nedit.hackvalue.nl/niki/index.php/Talk:GSoC2008IdeaPage#Macro_Hook.2FEvent_Binding_System: <quote> I (Bert) needed other types of hooks, so I added more, which are now integrated into the Patch Collection: * modified_hook: called after the text buffer is modified </quote> Does that hook tell what has been changed, or must one do things like compare the textBuf before and after to see what has changed? Also, you mention "identify more useful hooks" as one of the ToDos--I have one to propose (that would be useful if we (I) try to do the "Proof of Concept" folding back end by simply having a document open in two places (more description buried in the back end design document)). That woud be: * modified_rangeset_hook: which would be called after a rangeset is modified (and it should report what has changed) There may be others that would be useful if: * I (or anyone else) pursues that "unusual" "Proof of Concept" approach * if they are not already covered by the (textBuf) modified_hook For example, are changes in the selection(s) saved in the textBuf and reported in the modified_hook? How about changes in the scroll position of the document? Randy Kramer -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
