Home » Eclipse Projects » Technology Project and PMC » New Code formatter? Why?
| New Code formatter? Why? [message #59018] |
Tue, 14 October 2003 22:30  |
Eclipse User |
|
|
|
Originally posted by: derisor.arcor.de
This is a multi-part message in MIME format.
------=_NextPart_000_00A6_01C392B3.7A869EF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
From: =
http://download2.eclipse.org/downloads/drops/S-3.0M4-2003101 01454/eclipse=
-news-part1-M4.html
The new Java code formatter can be enabled via the Java > Work in =
Progress > Code Formatter preference page. This formatter will be much =
more flexible than its predecessors, although you'll have to take that =
on faith until its new preference page is ready.=20
I am currious why they are bothering re-implementing this when there are =
already a couple of formatters available and, in fact, potentially the =
best formatter ever, Jalopy. Wouldnt it make more sense to try to =
integrate Jalopy more tightly into Eclipse and build on their successes?
-- Kraythe
------=_NextPart_000_00A6_01C392B3.7A869EF0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>From: <A=20
href=3D" http://download2.eclipse.org/downloads/drops/S-3.0M4-2003101 01454=
/eclipse-news-part1-M4.html">http://download2.eclipse.org/downloads/drops=
/S-3.0M4-200310101454/eclipse-news-part1-M4.html</A></FONT ></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV><FONT face=3DArial size=3D2>The new Java code formatter can be =
enabled via=20
the Java > Work in Progress > Code Formatter preference page. =
This=20
formatter will be much more flexible than its predecessors, although =
you'll=20
have to take that on faith until its new preference page is ready.=20
</FONT></DIV></BLOCKQUOTE>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial size=3D2>I am =
currious why=20
they are bothering re-implementing this when there are already a couple =
of=20
formatters available and, in fact, potentially the best formatter ever, =
Jalopy.=20
Wouldnt it make more sense to try to integrate Jalopy more tightly into =
Eclipse=20
and build on their successes?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>-- Kraythe</FONT></DIV></BODY></HTML>
------=_NextPart_000_00A6_01C392B3.7A869EF0--
|
|
| |
| Re: New Code formatter? Why? [message #59094 is a reply to message #59068] |
Tue, 14 October 2003 23:10  |
| Eclipse User |
|
|
|
Originally posted by: derisor.arcor.de
Thanks for the posting tip, I will cross post.
As for your bug, Jalopy will do everything you requested.
:-)
-- Robert
"Alvin Thompson" <nobody@nowhere.com> wrote in message
news:3F8C7EE4.8010901@nowhere.com...
> please remember to use the appropriate newsgroup when posting questions.
> this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> will get answers to your questions if you use the wrong newsgroup.
>
> > I am currious why they are bothering re-implementing this when there are
> > already a couple of formatters available and, in fact, potentially the
> > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > integrate Jalopy more tightly into Eclipse and build on their successes?
>
> jalopy is released under the BSD liscence, while eclipse is released
> under the...ummm...IBM liscence, i think.
>
> also, i want to torture my coworkers' eyes with my bizarre code
> formatting style. see:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
>
>
> -alvin
>
|
|
|
| Re: New Code formatter? Why? (Need a Code Presenter) [message #59115 is a reply to message #59068] |
Wed, 15 October 2003 17:42 |
| Eclipse User |
|
|
|
Originally posted by: mbrozowski.nc.rr.com
A coworker and I recently started using eclipse and were discussing code
formatting and what
options we could agree on since with both have different styles. We quicky
realized that the optimum
solution would be a code presenter that would show you the code with the
formatting you preferred without change the format of the underlying code.
This would enable individual developers to develop with their own style
without interfering with those of others. Any change the New Formatter
could begin to do things this way?
Matt Brozowski (with input from Mark Miller)
Tavve Software Company
Morrisville, NC
"Alvin Thompson" <nobody@nowhere.com> wrote in message
news:3F8C7EE4.8010901@nowhere.com...
> please remember to use the appropriate newsgroup when posting questions.
> this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> will get answers to your questions if you use the wrong newsgroup.
>
> > I am currious why they are bothering re-implementing this when there are
> > already a couple of formatters available and, in fact, potentially the
> > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > integrate Jalopy more tightly into Eclipse and build on their successes?
>
> jalopy is released under the BSD liscence, while eclipse is released
> under the...ummm...IBM liscence, i think.
>
> also, i want to torture my coworkers' eyes with my bizarre code
> formatting style. see:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
>
>
> -alvin
>
|
|
|
| Re: New Code formatter? Why? [message #59140 is a reply to message #59068] |
Wed, 15 October 2003 19:01 |
| Eclipse User |
|
|
|
Originally posted by: olivier_thomann.ca.ibm.comNOSPAM
Le Tue, 14 Oct 2003 18:55:32 -0400, dans eclipse.technology, vous
avez écrit :
>please remember to use the appropriate newsgroup when posting questions.
>this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
>will get answers to your questions if you use the wrong newsgroup.
I missed your question, because I was not following this newsgroup.
Such question should be posted in eclipse.tools.jdt. Post new
questions on this topic on eclipse.tools.jdt newsgroup.
>jalopy is released under the BSD liscence, while eclipse is released
>under the...ummm...IBM liscence, i think.
Eclipse is licenced under CPL license (Common public licence). You can
find all details on this license here:
http://www.opensource.org/licenses/index.php
If you want to use Jalopy, go ahead. We simply changed the code
formatter to give a default formatter that is more flexible. Nothing
prevents you from using Jalopy. From the author of Jalopy, he won't
fix the existing bugs in Jalopy in the free version. You will need to
purchase Jalopy to get the latest fixes. Contact the author to get a
tigher integration inside Eclipse.
>also, i want to torture my coworkers' eyes with my bizarre code
>formatting style. see:
>
>https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
All these styles are handled by the new formatter. Unfortunately the
code formatter preference page is not available yet. Should be
included for M5.
--
Olivier
|
|
|
| Re: New Code formatter? Why? (Need a Code Presenter) [message #59188 is a reply to message #59115] |
Thu, 16 October 2003 09:50 |
 Jerome Lanneluc
Messages: 572
Registered: July 2009 |
Senior Member |
|
|
That's sound like a nice idea to browse code, but when you make a change to
a .java file and save it, which format would you choose?
Jerome
"Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
news:bmk0u3$nt8$1@eclipse.org...
> A coworker and I recently started using eclipse and were discussing code
> formatting and what
> options we could agree on since with both have different styles. We
quicky
> realized that the optimum
> solution would be a code presenter that would show you the code with the
> formatting you preferred without change the format of the underlying code.
> This would enable individual developers to develop with their own style
> without interfering with those of others. Any change the New Formatter
> could begin to do things this way?
>
> Matt Brozowski (with input from Mark Miller)
> Tavve Software Company
> Morrisville, NC
>
>
>
> "Alvin Thompson" <nobody@nowhere.com> wrote in message
> news:3F8C7EE4.8010901@nowhere.com...
> > please remember to use the appropriate newsgroup when posting questions.
> > this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> > will get answers to your questions if you use the wrong newsgroup.
> >
> > > I am currious why they are bothering re-implementing this when there
are
> > > already a couple of formatters available and, in fact, potentially the
> > > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > > integrate Jalopy more tightly into Eclipse and build on their
successes?
> >
> > jalopy is released under the BSD liscence, while eclipse is released
> > under the...ummm...IBM liscence, i think.
> >
> > also, i want to torture my coworkers' eyes with my bizarre code
> > formatting style. see:
> >
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
> >
> >
> > -alvin
> >
>
>
|
|
| |
| Re: New Code formatter? Why? (Need a Code Presenter) [message #59455 is a reply to message #59188] |
Mon, 20 October 2003 17:01 |
| Eclipse User |
|
|
|
Originally posted by: mbrozowski.nc.rr.com
We parse the heck out of the file as it is? We even parse the comments now
with Javadoc.
How difficult would it be to make to determine how many spaces of indent the
existing file has and whether they like braces on the same line of the next.
It seems to me the optimimum would be to preserve the formatting of the
existing file so the 'owner/creator' would have it in the format he
originally intended while you could view it in the format you prefer. If
you preserve it as much as possible this makes merging much easier.
Our team started using eclipse here and we all had our own style conventions
which were so different that is mattered to us to standardize. But now the
formatters are rearranging the code making it difficult to merge. We're
having to standardize. Though you could argue that standardizing is good,
that's really only because we don't have a tool that makes it a non issue.
Matt Brozowski
"Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
news:bmlpk0$6ir$1@eclipse.org...
> That's sound like a nice idea to browse code, but when you make a change
to
> a .java file and save it, which format would you choose?
>
> Jerome
>
> "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> news:bmk0u3$nt8$1@eclipse.org...
> > A coworker and I recently started using eclipse and were discussing code
> > formatting and what
> > options we could agree on since with both have different styles. We
> quicky
> > realized that the optimum
> > solution would be a code presenter that would show you the code with the
> > formatting you preferred without change the format of the underlying
code.
> > This would enable individual developers to develop with their own style
> > without interfering with those of others. Any change the New Formatter
> > could begin to do things this way?
> >
> > Matt Brozowski (with input from Mark Miller)
> > Tavve Software Company
> > Morrisville, NC
> >
> >
> >
> > "Alvin Thompson" <nobody@nowhere.com> wrote in message
> > news:3F8C7EE4.8010901@nowhere.com...
> > > please remember to use the appropriate newsgroup when posting
questions.
> > > this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> > > will get answers to your questions if you use the wrong newsgroup.
> > >
> > > > I am currious why they are bothering re-implementing this when there
> are
> > > > already a couple of formatters available and, in fact, potentially
the
> > > > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > > > integrate Jalopy more tightly into Eclipse and build on their
> successes?
> > >
> > > jalopy is released under the BSD liscence, while eclipse is released
> > > under the...ummm...IBM liscence, i think.
> > >
> > > also, i want to torture my coworkers' eyes with my bizarre code
> > > formatting style. see:
> > >
> > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
> > >
> > >
> > > -alvin
> > >
> >
> >
>
>
|
|
|
| Re: New Code formatter? Why? (Need a Code Presenter) [message #59479 is a reply to message #59455] |
Tue, 21 October 2003 09:57 |
Jerome Lanneluc
Messages: 572
Registered: July 2009 |
Senior Member |
|
|
Another interresting idea. I don't know if this is feasable, how costly it
would be, how much work it would be, etc... But you could still enter a
feature request describing it.
Jerome
"Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
news:bn14bq$k5l$1@eclipse.org...
> We parse the heck out of the file as it is? We even parse the comments
now
> with Javadoc.
>
> How difficult would it be to make to determine how many spaces of indent
the
> existing file has and whether they like braces on the same line of the
next.
> It seems to me the optimimum would be to preserve the formatting of the
> existing file so the 'owner/creator' would have it in the format he
> originally intended while you could view it in the format you prefer. If
> you preserve it as much as possible this makes merging much easier.
>
> Our team started using eclipse here and we all had our own style
conventions
> which were so different that is mattered to us to standardize. But now
the
> formatters are rearranging the code making it difficult to merge. We're
> having to standardize. Though you could argue that standardizing is
good,
> that's really only because we don't have a tool that makes it a non issue.
>
> Matt Brozowski
>
> "Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
> news:bmlpk0$6ir$1@eclipse.org...
> > That's sound like a nice idea to browse code, but when you make a change
> to
> > a .java file and save it, which format would you choose?
> >
> > Jerome
> >
> > "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> > news:bmk0u3$nt8$1@eclipse.org...
> > > A coworker and I recently started using eclipse and were discussing
code
> > > formatting and what
> > > options we could agree on since with both have different styles. We
> > quicky
> > > realized that the optimum
> > > solution would be a code presenter that would show you the code with
the
> > > formatting you preferred without change the format of the underlying
> code.
> > > This would enable individual developers to develop with their own
style
> > > without interfering with those of others. Any change the New
Formatter
> > > could begin to do things this way?
> > >
> > > Matt Brozowski (with input from Mark Miller)
> > > Tavve Software Company
> > > Morrisville, NC
> > >
> > >
> > >
> > > "Alvin Thompson" <nobody@nowhere.com> wrote in message
> > > news:3F8C7EE4.8010901@nowhere.com...
> > > > please remember to use the appropriate newsgroup when posting
> questions.
> > > > this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> > > > will get answers to your questions if you use the wrong newsgroup.
> > > >
> > > > > I am currious why they are bothering re-implementing this when
there
> > are
> > > > > already a couple of formatters available and, in fact, potentially
> the
> > > > > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > > > > integrate Jalopy more tightly into Eclipse and build on their
> > successes?
> > > >
> > > > jalopy is released under the BSD liscence, while eclipse is released
> > > > under the...ummm...IBM liscence, i think.
> > > >
> > > > also, i want to torture my coworkers' eyes with my bizarre code
> > > > formatting style. see:
> > > >
> > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
> > > >
> > > >
> > > > -alvin
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: New Code formatter? Why? (Need a Code Presenter) [message #59504 is a reply to message #59479] |
Tue, 21 October 2003 20:33 |
| Eclipse User |
|
|
|
Originally posted by: derisor.arcor.de
If the backend format was consistent then the front end could be different. The
problem is that when comparing diffs you would NEED to look at the back end
format. If that isnt a compellign block then I dont see why it couldnt be done.
The buffer in the memory can show the code in whatever format it chooses to.
It would be interesting to play with it but I think very low priority.
-- Robert
"Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
news:bn2vtm$6hu$1@eclipse.org...
> Another interresting idea. I don't know if this is feasable, how costly it
> would be, how much work it would be, etc... But you could still enter a
> feature request describing it.
>
> Jerome
>
> "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> news:bn14bq$k5l$1@eclipse.org...
> > We parse the heck out of the file as it is? We even parse the comments
> now
> > with Javadoc.
> >
> > How difficult would it be to make to determine how many spaces of indent
> the
> > existing file has and whether they like braces on the same line of the
> next.
> > It seems to me the optimimum would be to preserve the formatting of the
> > existing file so the 'owner/creator' would have it in the format he
> > originally intended while you could view it in the format you prefer. If
> > you preserve it as much as possible this makes merging much easier.
> >
> > Our team started using eclipse here and we all had our own style
> conventions
> > which were so different that is mattered to us to standardize. But now
> the
> > formatters are rearranging the code making it difficult to merge. We're
> > having to standardize. Though you could argue that standardizing is
> good,
> > that's really only because we don't have a tool that makes it a non issue.
> >
> > Matt Brozowski
> >
> > "Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
> > news:bmlpk0$6ir$1@eclipse.org...
> > > That's sound like a nice idea to browse code, but when you make a change
> > to
> > > a .java file and save it, which format would you choose?
> > >
> > > Jerome
> > >
> > > "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> > > news:bmk0u3$nt8$1@eclipse.org...
> > > > A coworker and I recently started using eclipse and were discussing
> code
> > > > formatting and what
> > > > options we could agree on since with both have different styles. We
> > > quicky
> > > > realized that the optimum
> > > > solution would be a code presenter that would show you the code with
> the
> > > > formatting you preferred without change the format of the underlying
> > code.
> > > > This would enable individual developers to develop with their own
> style
> > > > without interfering with those of others. Any change the New
> Formatter
> > > > could begin to do things this way?
> > > >
> > > > Matt Brozowski (with input from Mark Miller)
> > > > Tavve Software Company
> > > > Morrisville, NC
> > > >
> > > >
> > > >
> > > > "Alvin Thompson" <nobody@nowhere.com> wrote in message
> > > > news:3F8C7EE4.8010901@nowhere.com...
> > > > > please remember to use the appropriate newsgroup when posting
> > questions.
> > > > > this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> > > > > will get answers to your questions if you use the wrong newsgroup.
> > > > >
> > > > > > I am currious why they are bothering re-implementing this when
> there
> > > are
> > > > > > already a couple of formatters available and, in fact, potentially
> > the
> > > > > > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > > > > > integrate Jalopy more tightly into Eclipse and build on their
> > > successes?
> > > > >
> > > > > jalopy is released under the BSD liscence, while eclipse is released
> > > > > under the...ummm...IBM liscence, i think.
> > > > >
> > > > > also, i want to torture my coworkers' eyes with my bizarre code
> > > > > formatting style. see:
> > > > >
> > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
> > > > >
> > > > >
> > > > > -alvin
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: New Code formatter? Why? [message #59964 is a reply to message #59140] |
Fri, 05 December 2003 15:35 |
| Eclipse User |
|
|
|
Originally posted by: jamie_bisotti.yahoo.com
Olivier Thomann wrote:
> Le Tue, 14 Oct 2003 18:55:32 -0400, dans eclipse.technology, vous
> avez écrit :
>
>>please remember to use the appropriate newsgroup when posting questions.
>>this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
>>will get answers to your questions if you use the wrong newsgroup.
>
> I missed your question, because I was not following this newsgroup.
> Such question should be posted in eclipse.tools.jdt. Post new
> questions on this topic on eclipse.tools.jdt newsgroup.
>
>
>>jalopy is released under the BSD liscence, while eclipse is released
>>under the...ummm...IBM liscence, i think.
>
> Eclipse is licenced under CPL license (Common public licence). You can
> find all details on this license here:
> http://www.opensource.org/licenses/index.php
>
> If you want to use Jalopy, go ahead. We simply changed the code
> formatter to give a default formatter that is more flexible. Nothing
> prevents you from using Jalopy. From the author of Jalopy, he won't
> fix the existing bugs in Jalopy in the free version. You will need to
> purchase Jalopy to get the latest fixes. Contact the author to get a
> tigher integration inside Eclipse.
>
>
>>also, i want to torture my coworkers' eyes with my bizarre code
>>formatting style. see:
>>
>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
>
> All these styles are handled by the new formatter. Unfortunately the
> code formatter preference page is not available yet. Should be
> included for M5.
> --
> Olivier
I don't see the new Preferences page for the new Code Formatter in M5.
Am I just missing it? If not, any idea if it will make it into M6?
Jamie
|
|
| |
| Re: New Code formatter? Why? [message #595714 is a reply to message #59068] |
Tue, 14 October 2003 23:10 |
| Eclipse User |
|
|
|
Originally posted by: derisor.arcor.de
Thanks for the posting tip, I will cross post.
As for your bug, Jalopy will do everything you requested.
:-)
-- Robert
"Alvin Thompson" <nobody@nowhere.com> wrote in message
news:3F8C7EE4.8010901@nowhere.com...
> please remember to use the appropriate newsgroup when posting questions.
> this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> will get answers to your questions if you use the wrong newsgroup.
>
> > I am currious why they are bothering re-implementing this when there are
> > already a couple of formatters available and, in fact, potentially the
> > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > integrate Jalopy more tightly into Eclipse and build on their successes?
>
> jalopy is released under the BSD liscence, while eclipse is released
> under the...ummm...IBM liscence, i think.
>
> also, i want to torture my coworkers' eyes with my bizarre code
> formatting style. see:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
>
>
> -alvin
>
|
|
|
| Re: New Code formatter? Why? (Need a Code Presenter) [message #595731 is a reply to message #59068] |
Wed, 15 October 2003 17:42 |
| Eclipse User |
|
|
|
Originally posted by: mbrozowski.nc.rr.com
A coworker and I recently started using eclipse and were discussing code
formatting and what
options we could agree on since with both have different styles. We quicky
realized that the optimum
solution would be a code presenter that would show you the code with the
formatting you preferred without change the format of the underlying code.
This would enable individual developers to develop with their own style
without interfering with those of others. Any change the New Formatter
could begin to do things this way?
Matt Brozowski (with input from Mark Miller)
Tavve Software Company
Morrisville, NC
"Alvin Thompson" <nobody@nowhere.com> wrote in message
news:3F8C7EE4.8010901@nowhere.com...
> please remember to use the appropriate newsgroup when posting questions.
> this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> will get answers to your questions if you use the wrong newsgroup.
>
> > I am currious why they are bothering re-implementing this when there are
> > already a couple of formatters available and, in fact, potentially the
> > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > integrate Jalopy more tightly into Eclipse and build on their successes?
>
> jalopy is released under the BSD liscence, while eclipse is released
> under the...ummm...IBM liscence, i think.
>
> also, i want to torture my coworkers' eyes with my bizarre code
> formatting style. see:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
>
>
> -alvin
>
|
|
|
| Re: New Code formatter? Why? [message #595742 is a reply to message #59068] |
Wed, 15 October 2003 19:01 |
Olivier Thomann
Messages: 518
Registered: July 2009 |
Senior Member |
|
|
Le Tue, 14 Oct 2003 18:55:32 -0400, dans eclipse.technology, vous
avez écrit :
>please remember to use the appropriate newsgroup when posting questions.
>this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
>will get answers to your questions if you use the wrong newsgroup.
I missed your question, because I was not following this newsgroup.
Such question should be posted in eclipse.tools.jdt. Post new
questions on this topic on eclipse.tools.jdt newsgroup.
>jalopy is released under the BSD liscence, while eclipse is released
>under the...ummm...IBM liscence, i think.
Eclipse is licenced under CPL license (Common public licence). You can
find all details on this license here:
http://www.opensource.org/licenses/index.php
If you want to use Jalopy, go ahead. We simply changed the code
formatter to give a default formatter that is more flexible. Nothing
prevents you from using Jalopy. From the author of Jalopy, he won't
fix the existing bugs in Jalopy in the free version. You will need to
purchase Jalopy to get the latest fixes. Contact the author to get a
tigher integration inside Eclipse.
>also, i want to torture my coworkers' eyes with my bizarre code
>formatting style. see:
>
>https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
All these styles are handled by the new formatter. Unfortunately the
code formatter preference page is not available yet. Should be
included for M5.
--
Olivier
|
|
|
| Re: New Code formatter? Why? (Need a Code Presenter) [message #595755 is a reply to message #59115] |
Thu, 16 October 2003 09:50 |
Jerome Lanneluc
Messages: 572
Registered: July 2009 |
Senior Member |
|
|
That's sound like a nice idea to browse code, but when you make a change to
a .java file and save it, which format would you choose?
Jerome
"Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
news:bmk0u3$nt8$1@eclipse.org...
> A coworker and I recently started using eclipse and were discussing code
> formatting and what
> options we could agree on since with both have different styles. We
quicky
> realized that the optimum
> solution would be a code presenter that would show you the code with the
> formatting you preferred without change the format of the underlying code.
> This would enable individual developers to develop with their own style
> without interfering with those of others. Any change the New Formatter
> could begin to do things this way?
>
> Matt Brozowski (with input from Mark Miller)
> Tavve Software Company
> Morrisville, NC
>
>
>
> "Alvin Thompson" <nobody@nowhere.com> wrote in message
> news:3F8C7EE4.8010901@nowhere.com...
> > please remember to use the appropriate newsgroup when posting questions.
> > this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> > will get answers to your questions if you use the wrong newsgroup.
> >
> > > I am currious why they are bothering re-implementing this when there
are
> > > already a couple of formatters available and, in fact, potentially the
> > > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > > integrate Jalopy more tightly into Eclipse and build on their
successes?
> >
> > jalopy is released under the BSD liscence, while eclipse is released
> > under the...ummm...IBM liscence, i think.
> >
> > also, i want to torture my coworkers' eyes with my bizarre code
> > formatting style. see:
> >
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
> >
> >
> > -alvin
> >
>
>
|
|
| |
| Re: New Code formatter? Why? (Need a Code Presenter) [message #595868 is a reply to message #59188] |
Mon, 20 October 2003 17:01 |
| Eclipse User |
|
|
|
Originally posted by: mbrozowski.nc.rr.com
We parse the heck out of the file as it is? We even parse the comments now
with Javadoc.
How difficult would it be to make to determine how many spaces of indent the
existing file has and whether they like braces on the same line of the next.
It seems to me the optimimum would be to preserve the formatting of the
existing file so the 'owner/creator' would have it in the format he
originally intended while you could view it in the format you prefer. If
you preserve it as much as possible this makes merging much easier.
Our team started using eclipse here and we all had our own style conventions
which were so different that is mattered to us to standardize. But now the
formatters are rearranging the code making it difficult to merge. We're
having to standardize. Though you could argue that standardizing is good,
that's really only because we don't have a tool that makes it a non issue.
Matt Brozowski
"Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
news:bmlpk0$6ir$1@eclipse.org...
> That's sound like a nice idea to browse code, but when you make a change
to
> a .java file and save it, which format would you choose?
>
> Jerome
>
> "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> news:bmk0u3$nt8$1@eclipse.org...
> > A coworker and I recently started using eclipse and were discussing code
> > formatting and what
> > options we could agree on since with both have different styles. We
> quicky
> > realized that the optimum
> > solution would be a code presenter that would show you the code with the
> > formatting you preferred without change the format of the underlying
code.
> > This would enable individual developers to develop with their own style
> > without interfering with those of others. Any change the New Formatter
> > could begin to do things this way?
> >
> > Matt Brozowski (with input from Mark Miller)
> > Tavve Software Company
> > Morrisville, NC
> >
> >
> >
> > "Alvin Thompson" <nobody@nowhere.com> wrote in message
> > news:3F8C7EE4.8010901@nowhere.com...
> > > please remember to use the appropriate newsgroup when posting
questions.
> > > this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> > > will get answers to your questions if you use the wrong newsgroup.
> > >
> > > > I am currious why they are bothering re-implementing this when there
> are
> > > > already a couple of formatters available and, in fact, potentially
the
> > > > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > > > integrate Jalopy more tightly into Eclipse and build on their
> successes?
> > >
> > > jalopy is released under the BSD liscence, while eclipse is released
> > > under the...ummm...IBM liscence, i think.
> > >
> > > also, i want to torture my coworkers' eyes with my bizarre code
> > > formatting style. see:
> > >
> > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
> > >
> > >
> > > -alvin
> > >
> >
> >
>
>
|
|
|
| Re: New Code formatter? Why? (Need a Code Presenter) [message #595880 is a reply to message #59455] |
Tue, 21 October 2003 09:57 |
Jerome Lanneluc
Messages: 572
Registered: July 2009 |
Senior Member |
|
|
Another interresting idea. I don't know if this is feasable, how costly it
would be, how much work it would be, etc... But you could still enter a
feature request describing it.
Jerome
"Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
news:bn14bq$k5l$1@eclipse.org...
> We parse the heck out of the file as it is? We even parse the comments
now
> with Javadoc.
>
> How difficult would it be to make to determine how many spaces of indent
the
> existing file has and whether they like braces on the same line of the
next.
> It seems to me the optimimum would be to preserve the formatting of the
> existing file so the 'owner/creator' would have it in the format he
> originally intended while you could view it in the format you prefer. If
> you preserve it as much as possible this makes merging much easier.
>
> Our team started using eclipse here and we all had our own style
conventions
> which were so different that is mattered to us to standardize. But now
the
> formatters are rearranging the code making it difficult to merge. We're
> having to standardize. Though you could argue that standardizing is
good,
> that's really only because we don't have a tool that makes it a non issue.
>
> Matt Brozowski
>
> "Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
> news:bmlpk0$6ir$1@eclipse.org...
> > That's sound like a nice idea to browse code, but when you make a change
> to
> > a .java file and save it, which format would you choose?
> >
> > Jerome
> >
> > "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> > news:bmk0u3$nt8$1@eclipse.org...
> > > A coworker and I recently started using eclipse and were discussing
code
> > > formatting and what
> > > options we could agree on since with both have different styles. We
> > quicky
> > > realized that the optimum
> > > solution would be a code presenter that would show you the code with
the
> > > formatting you preferred without change the format of the underlying
> code.
> > > This would enable individual developers to develop with their own
style
> > > without interfering with those of others. Any change the New
Formatter
> > > could begin to do things this way?
> > >
> > > Matt Brozowski (with input from Mark Miller)
> > > Tavve Software Company
> > > Morrisville, NC
> > >
> > >
> > >
> > > "Alvin Thompson" <nobody@nowhere.com> wrote in message
> > > news:3F8C7EE4.8010901@nowhere.com...
> > > > please remember to use the appropriate newsgroup when posting
> questions.
> > > > this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> > > > will get answers to your questions if you use the wrong newsgroup.
> > > >
> > > > > I am currious why they are bothering re-implementing this when
there
> > are
> > > > > already a couple of formatters available and, in fact, potentially
> the
> > > > > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > > > > integrate Jalopy more tightly into Eclipse and build on their
> > successes?
> > > >
> > > > jalopy is released under the BSD liscence, while eclipse is released
> > > > under the...ummm...IBM liscence, i think.
> > > >
> > > > also, i want to torture my coworkers' eyes with my bizarre code
> > > > formatting style. see:
> > > >
> > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
> > > >
> > > >
> > > > -alvin
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: New Code formatter? Why? (Need a Code Presenter) [message #595890 is a reply to message #59479] |
Tue, 21 October 2003 20:33 |
| Eclipse User |
|
|
|
Originally posted by: derisor.arcor.de
If the backend format was consistent then the front end could be different. The
problem is that when comparing diffs you would NEED to look at the back end
format. If that isnt a compellign block then I dont see why it couldnt be done.
The buffer in the memory can show the code in whatever format it chooses to.
It would be interesting to play with it but I think very low priority.
-- Robert
"Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
news:bn2vtm$6hu$1@eclipse.org...
> Another interresting idea. I don't know if this is feasable, how costly it
> would be, how much work it would be, etc... But you could still enter a
> feature request describing it.
>
> Jerome
>
> "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> news:bn14bq$k5l$1@eclipse.org...
> > We parse the heck out of the file as it is? We even parse the comments
> now
> > with Javadoc.
> >
> > How difficult would it be to make to determine how many spaces of indent
> the
> > existing file has and whether they like braces on the same line of the
> next.
> > It seems to me the optimimum would be to preserve the formatting of the
> > existing file so the 'owner/creator' would have it in the format he
> > originally intended while you could view it in the format you prefer. If
> > you preserve it as much as possible this makes merging much easier.
> >
> > Our team started using eclipse here and we all had our own style
> conventions
> > which were so different that is mattered to us to standardize. But now
> the
> > formatters are rearranging the code making it difficult to merge. We're
> > having to standardize. Though you could argue that standardizing is
> good,
> > that's really only because we don't have a tool that makes it a non issue.
> >
> > Matt Brozowski
> >
> > "Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
> > news:bmlpk0$6ir$1@eclipse.org...
> > > That's sound like a nice idea to browse code, but when you make a change
> > to
> > > a .java file and save it, which format would you choose?
> > >
> > > Jerome
> > >
> > > "Mathew Brozowski" <mbrozowski@nc.rr.com> wrote in message
> > > news:bmk0u3$nt8$1@eclipse.org...
> > > > A coworker and I recently started using eclipse and were discussing
> code
> > > > formatting and what
> > > > options we could agree on since with both have different styles. We
> > > quicky
> > > > realized that the optimum
> > > > solution would be a code presenter that would show you the code with
> the
> > > > formatting you preferred without change the format of the underlying
> > code.
> > > > This would enable individual developers to develop with their own
> style
> > > > without interfering with those of others. Any change the New
> Formatter
> > > > could begin to do things this way?
> > > >
> > > > Matt Brozowski (with input from Mark Miller)
> > > > Tavve Software Company
> > > > Morrisville, NC
> > > >
> > > >
> > > >
> > > > "Alvin Thompson" <nobody@nowhere.com> wrote in message
> > > > news:3F8C7EE4.8010901@nowhere.com...
> > > > > please remember to use the appropriate newsgroup when posting
> > questions.
> > > > > this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
> > > > > will get answers to your questions if you use the wrong newsgroup.
> > > > >
> > > > > > I am currious why they are bothering re-implementing this when
> there
> > > are
> > > > > > already a couple of formatters available and, in fact, potentially
> > the
> > > > > > best formatter ever, Jalopy. Wouldnt it make more sense to try to
> > > > > > integrate Jalopy more tightly into Eclipse and build on their
> > > successes?
> > > > >
> > > > > jalopy is released under the BSD liscence, while eclipse is released
> > > > > under the...ummm...IBM liscence, i think.
> > > > >
> > > > > also, i want to torture my coworkers' eyes with my bizarre code
> > > > > formatting style. see:
> > > > >
> > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
> > > > >
> > > > >
> > > > > -alvin
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: New Code formatter? Why? [message #596056 is a reply to message #59140] |
Fri, 05 December 2003 15:35 |
Jamie Bisotti
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
Olivier Thomann wrote:
> Le Tue, 14 Oct 2003 18:55:32 -0400, dans eclipse.technology, vous
> avez écrit :
>
>>please remember to use the appropriate newsgroup when posting questions.
>>this one probably belongs in 'eclipse.tools.jdt'. it is unlikely you
>>will get answers to your questions if you use the wrong newsgroup.
>
> I missed your question, because I was not following this newsgroup.
> Such question should be posted in eclipse.tools.jdt. Post new
> questions on this topic on eclipse.tools.jdt newsgroup.
>
>
>>jalopy is released under the BSD liscence, while eclipse is released
>>under the...ummm...IBM liscence, i think.
>
> Eclipse is licenced under CPL license (Common public licence). You can
> find all details on this license here:
> http://www.opensource.org/licenses/index.php
>
> If you want to use Jalopy, go ahead. We simply changed the code
> formatter to give a default formatter that is more flexible. Nothing
> prevents you from using Jalopy. From the author of Jalopy, he won't
> fix the existing bugs in Jalopy in the free version. You will need to
> purchase Jalopy to get the latest fixes. Contact the author to get a
> tigher integration inside Eclipse.
>
>
>>also, i want to torture my coworkers' eyes with my bizarre code
>>formatting style. see:
>>
>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=25559
>
> All these styles are handled by the new formatter. Unfortunately the
> code formatter preference page is not available yet. Should be
> included for M5.
> --
> Olivier
I don't see the new Preferences page for the new Code Formatter in M5.
Am I just missing it? If not, any idea if it will make it into M6?
Jamie
|
|
|
Goto Forum:
Current Time: Sat Nov 09 03:37:37 GMT 2024
Powered by FUDForum. Page generated in 0.04905 seconds |
] 
Search
Help
Register
Login
Home
