On Thu, 2005-04-28 at 08:08 -0400, Eric M. Ludlam wrote: > Hi, > To be clear, is it just the header line, and semantic decorations > that scare people away, or the whole set of code helpers including > imenu, summary-mode, completion mode, and what-not.
It's different.
The header line is most problematic in my case (and maybe others) as I
use the very cool tabbar.el by David Ponce (which is unexplainable to me
still not part of standard emacs...) - So putting something there
exclusively doesn't work for me.
Semantic decorations of methods would be nice, but I never understood
the somehow arbitrary exclusion of "small" methods/functions, but as
Nascif said in another mail, it would be ever so much nicer to use the
fringe to have e.g. clickeable markers for methods which could be used
to show/hide them on demand.
Completion mode is quite nice, but seems to have problems, e.g. (or it's
a problem of semantic/java - I can't decide) the following construct,
point at end of "it" in second line, will not complete as it doesn't
seem to recognize iter to be in scope:
for (Iterator iter = in.iterator(); iter.hasNext();) {
it<point>
}
Another thing from a users point of view is that it would be really cool
to have jde's class file based completion of methods and semantics
source based completion of in-scope variables merged into _one_. The
problem of semantic in this regard (and the problem many of my coworkers
seem to have with it) is that it has some GUI related features, that
somehow "peek through" the tools that use it (like JDE, ECB) without
really integrating with them.
Please don't take this as an insult to your great work (and the great
work the ECB and JDE guys do) - it's just the impression of the user
visible parts and how they interact.
Thanks,
jtl
> Thanks
> Eric
>
> >>> "Nascif Abousalh-Neto" <[EMAIL PROTECTED]> seems to think that:
> >Hi Eric,
> >
> >This approach can also be overwhelming and frustrating - I saw it
> >first hand with some co-workers, having to stop their work to find out
> >and turn off new features they didn't want in the first place.
> >
> >Another tactic might be to start with the more powerful features
> >disabled and provide documentation on them, including
> >screenshots. Curious users will find the info and tinker with them,
> >and spread the word in wikis and mailing lists; less sophisticated
> >users won't be frustrated with all the colors and extra fontification
> >getting in their way, coming from nowhere, as soon as they install the
> >new library. They might them be more receptive to turn them on later.
> >
> >Best regards,
> > Nascif
> >
> >
> >> -----Original Message-----
> >> From: Eric M. Ludlam [mailto:[EMAIL PROTECTED]
> >> Sent: Saturday, April 23, 2005 8:46 AM
> >> To: Felix Dorner
> >> Cc: jde@sunsite.dk
> >> Subject: Re[2]: "header line" bugs and artifacts
> >>
> >> Hi,
> >>
> >> Stickyfunc mode puts the first line of the method/class
> >> that is on the top line of the window into the header line.
> >> That way you can always see what function you are working on.
> >> It's something I always thought would be useful.
> >>
> >> The overline is simply a decoration to help divide
> >> different types of tags from eachother in the buffer. I
> >> copied the idea from some Java editor I saw a coworker using.
> >> It is a part of semantic-decoration-mode. You can concoct
> >> your own decorations with `define-semantic-decoration-style'.
> >>
> >> I have seen several times that people look at these things
> >> and go "Eeww! What's all this?" and after a little bit
> >> change their minds and think they are useful.
> >>
> >> You can turn all the "code-helpers" off and suffer no ill
> >> effect. I turn most things on in the default so you get
> >> exposed to them, and can later choose which tools you like
> >> and turn off the others.
> >>
> >> Eric
> >>
> >> >>> Felix Dorner <[EMAIL PROTECTED]> seems to think that:
> >> >>
> >> >>
> >> >>That's the because of semantic stickyfunc mode. Try M-x
> >> >>global-semantic-stickyfunc-mode.
> >> >>
> >> >>
> >> >
> >> >OK thanks. With that, the header-line disappeared.
> >> >I guess it appeared because I have
> >> (semantic-load-enable-code-helpers)
> >> >(as in the cedet INSTALL file), do I really need this?
> >> >
> >> >another artifact that appeared yesterday too was an overline right
> >> >above a class body, just like this:
> >> >
> >> >__________________________
> >> >class TestSocket extends Socket{...
> >> >
> >> >
> >> >and a similar overline right above the main method of that class
> >> >
> >> >So what are those lines meant for?
> >> >Felix
> >> >
> >>
> >> --
> >> Eric Ludlam: [EMAIL PROTECTED],
> >> [EMAIL PROTECTED]
> >> Home: http://www.ludlam.net Siege: www.siege-engine.com
> >> Emacs: http://cedet.sourceforge.net GNU: www.gnu.org
> >>
> >
>
>
--
jtl
signature.asc
Description: This is a digitally signed message part
