On Mon, Mar 17, 2008 at 9:30 PM, Randy Kramer <[EMAIL PROTECTED]> wrote: > Bert, > > Thanks! (Some comments below.) > > > On Monday 17 March 2008 03:18 pm, Bert Wesarg wrote: > > On Mon, Mar 17, 2008 at 2:55 PM, Randy Kramer <[EMAIL PROTECTED]> wrote: > > > > * modified_rangeset_hook: which would be called after a rangeset is > > > modified (and it should report what has changed) > > the current hooks I use take no arguments, its only the 'event' that > > bothered me, not exactly what happened (like in the modified or > > cursor_moved events) > > > > Thats exactly what is needed to be done: identify hooks/events and the > > information what these should carry. > > Starting a small list: > > * modified_hook--modify it to report what has changed in the textBuf should this be fired before or after the change happen? so, should it report what will happen, or what happened?
> * modified_rangeset_hook--should report the change(s) (additions, > deletions, locations) > * cursor_moved event--should report the change (i.e., the new location) because this is fired after the actual movement, you get the new position easily with the $cursor variable. so it maybe has more value if the old position is given, or this is fired before the movement happen > * selection_change hook--should report the new selections > * scroll_change hook--should report the new scroll position (is that the > top line (or the first character) in the display?) you see, there are more questions you must think of for each hook, not just a oneliner > > I suspect I'll think of more. sure, there are plenty of things happen in a editor ;-) > > On the other hand, if we (someone) writes the backend changes necessary for > folding in C, then, presumably, these won't be required. why? how about a fold_hide/fold_unhide event? thats maybe of value too. > > Randy Kramer > > PS: A few minutes ago I checked the GSoC website to see if the list of > mentoring organizations has been posted yet--not so far (was supposed to > happen at noon, PDT (1900 UTC)). *trommelwirbel* ;-) -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
