[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [jdt-core-dev] Re: formatter
|
The way we achieved this was to have our code formatter be passed a
collection of source positions it was interested in getting mapped after
formatting.
I would suggest we keep the same, just provide a formatter API we can all
agree on.
Now for the option page, I think this is somewhat tricky. Being a non-ui
person (the JDT/Core has none), I was originally thinking that if I was to
publish my favorite list of options as self-descriptive objects, then a UI
might simply render them. But that wasn't the case... I think that a code
formatter provider would have to provide both a formatter and its UI page.
So we would likely need another extension point in JDT/UI to register a
preference page as well.
The codeassist hook would need to be in JDT/UI, unless one want to redo
the codeassist engine located in the JDT/Core ?
"Rozenberg, Ilya" <IRozenberg@xxxxxxxxxxxx>
Sent by: jdt-core-dev-admin@xxxxxxxxxxx
11/29/2001 04:56 PM
Please respond to jdt-core-dev
To: "'jdt-core-dev@xxxxxxxxxxx'" <jdt-core-dev@xxxxxxxxxxx>
cc:
Subject: RE: [jdt-core-dev] Re: formatter
> 1) markers should be updated during formatting. It is
> problematic to loose breakpoints or bookmarks
> as a side effect of a format.
I hope you will try to follow where the code went after the formatting and
move the breakpoint. If this is not possible in some cases please have an
option per marker type to leave
the markers on their old places. Markers on their old places will serve as
reminder for user to deal with them.
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev
