Thank you for your answers! Are there any plans to include a more advanced formatter in PDT? And when will the PDT 2.0 included in the Zend Studio for Eclipse?
Tom On Tue, Jan 13, 2009 at 7:44 PM, Roy Ganor <[email protected]> wrote: > ZF formatter rules are applied by Zend Studio for Eclipse formatter, so > using it with PDT 2.0 formatter actually won't help anyone L. > > > > - Roy > > > ------------------------------ > > *From:* Wil Sinclair > *Sent:* Tuesday, January 13, 2009 8:32 PM > *To:* Thomas Fritz; [email protected] > *Cc:* Roy Ganor > *Subject:* RE: [fw-general] Eclipse PDT 2.0 > > > > There is a ZF formatter in Zend Studio; not sure if you can use that with > PDT 2.0. CC'ing our Studio team lead in case he's got a solution for you. > > > > ,Wil > > > > *From:* Thomas Fritz [mailto:[email protected]] > *Sent:* Tuesday, January 13, 2009 2:00 AM > *To:* [email protected] > *Subject:* [fw-general] Eclipse PDT 2.0 > > > > a little bit offtopic, but i want to ask some devs about that. > > I tried the new PDT 2.0. There is a source formatter. But it only intends > and replaces tabs with spaces or vice versa - There are no advanced settings > possible like brace policy, indentation, array syntax, etc. like in Zend > Studio (of course). > My question now to those who use PDT Eclipse: How do you format your PHP > Source Code more detailed - According to a coding style like the Zend > Framework Style? We use PHP_CodeSniffer to detect Coding Style Violations. > But is there a tool - perhaps an eclipse plugin, which formats the source > code according to a coding style definition? Is PHP_Beautifer the right tool > for me? - I can't see any advanced settings possibilities either in its > documentation. > > I found one tool which comes very close to my needs. > http://www.waterproof.fr/products/phpCodeBeautifier/ > But it is also only a compromise, because many things still missing. > > The best solution would be a Pear_CodeFormatter (does not exist) which > reads the style definition in a xml format and PHP_CodeSniffer would also be > able to understand this xml style definition file. > > > > I appreciate any tipps or suggestions. > > > Best regards > > Tom >
