Re: LineNumberText - Send your requirements...

On Wednesday 17 November 2004 03:29, Dean Arnold wrote:
> Jack D. wrote:
> > Background:
> >
> > Right now - only one type of bookmark is allowed. I modelled it after
> > Crimson and Komodo editors - so it can't be all -that- bad !
> >
> > Future requirements:
> >
> > 1. I assume you wish to allow different images/shapes/text for different
> > lines? Yes?
> >
> >   1a. If so - what would you envision "Previous" and "Next" functionality
> > to hold? Would "Next" be "next bookmark of the same type" or "next
> > bookmark no matter what the type" ? I'm thinking that both functions will
> > be necessary.
>
> Sorry, I hadn't given that feature much thought...but I'm guessing
> (assuming different bookmark types) it would be possible to
> just populate the popup with 'Prev <bookmark-type>' and
> 'Next <bookmark-type>' entries. Keybound prev/next would presumably
> use whatever the current line is bookmarked, or else raise the
> popup ?
>
> > 2. Programmatic image bookmarks will be easy. However - user-interactive
> > bookmarks will be a bit more difficult. i.e. I want to make it easy for a
> > user to bookmark a line and to search through those lines. I am now
> > envisioning that a choice must be made amongst the various bookmark types
> > available - this means that they will have to do *two* things to get one
> > bookmark. This is working against my ideals of a good UI.
>
> Not certain I fully grok a "user-interactive" bookmark...do you mean
> a key-bind sequence sets/removes a default kind of bookmark ?
> Assuming the app coder doesn't create any new kinds of bookmarks,
> then theres no issue. If there are multiple types of bookmarks, then
> either the magic key-binding would be bound to the "default" bookmark,
> or (at the app writers discretion) a popup menu, and/or defining
> new keybindings for different bookmarks.
>
> > Don't get me wrong - I can see very good uses in having multiple-type
> > bookmark functionality. For instance - say you were using this in a perl
> > coding editor:
> >
> > One might want each sub {} line to be bookmarked with a little gif image.
> > At the same time - one might want to add a search function which
> > bookmarks all lines found which contain a specific perl function. Then
> > all toggling through each line would be simple using the 'yet-to-be-done'
> > next bookmark of same type functionality (as per #2). Or you might want
> > to have an error checking routine which will bookmark all erroneous lines
> > with your "stop sign" or a "no entry" symbol. Etc. etc
> >
> > The ideas are virtually endless..so this IS a direction I want to head.
> >
> > That being said - the steps which need to be taken also need to be well
> > thought out ahead of time. Hence I am asking for more specific
> > requirements from you and anyone else who cares enough to offer them.
> >
> >
> > So - by all means - send me your comments/requirements/suggestions.
> >
> > Jack
>
> OK, you asked for it! ;^)
>
> Code folding! (Thats probably beyond the scope, and maybe needs
> to be considered for CodeText instead ?)
>

Okay, so the big word CODE FOLDING is out.
For what it's worth, i am currently busy porting the syntax highlight engine 
of KDE's Advanced Text Editor, in short Kate, to perl. I am somewhere at 
twothird and at the current pace it will take me about two more months to get 
it done. Then I will base Tk::CodeText 0.4 on this.

for more info on Kate have a look at http://kate.kde.org

The kate syntax definition files (in xml format) already contain the 
algorithms for code folding in various languages. I wanted to complete the 
syntax highlighting first and then start studying on code-folding using 
Jack's module. 

However, if you guys are willing to think and work with me maybe it could 
already be done in version 0.4.

Best regards,

Hans
-++**==--++**==--++**==--++**==--++**==--++**==--++**==
This message was posted through the Stanford campus mailing list
server.  If you wish to unsubscribe from this mailing list, send the
message body of "unsubscribe ptk" to [email protected]