On 06/08/2011 03:43 PM, thron7 wrote:
> Yes, with trunk/upcoming 1.5 you will be able to say
>
> pretty-print/comments/block/add : false
>
> in the config.json, to achieve that :).
>
> T.
That's great!
The addition of docblocks were the only reason I don't use the pretty
printer, so I'm happ
On 06/08/2011 01:57 PM, Marc Puts wrote:
> Hi all,
>
> The pretty print job will automatically add /** TODOC **/ docblocks to
> any method that has not yet been documented.
>
> Is there a way to suppress this behaviour?
Yes, with trunk/upcoming 1.5 you will be able to say
pretty-print/commen
Hi all,
The pretty print job will automatically add /** TODOC **/ docblocks to
any method that has not yet been documented.
Is there a way to suppress this behaviour?
Regards,
Marc
--
EditLive Enterprise is the world's
It is for
- easing debugging (some errors are specific to compiled or source builds),
- to open the generated file in JSEclipse, and highlight all the uses of the
method/variable under the cursor. As Javascript is a dynamic language, it's
hard to know inter-dependencies, specially when you have
Pretty printing is meant for source files. What would be the reason to
format compiled code? (which is normally optimized for size - not for
design).
Sebastian
dperez schrieb:
> Hi,
>
> I would like the generator to pretty print the compiled output script.
> Does the --pretty-print option re
Hi,
I would like the generator to pretty print the compiled output script.
Does the --pretty-print option reformat original source files or the
compiled one?
I will update the wiki with any helpful answer
(http://qooxdoo.org/documentation/0.7/custom_builds)
Regards,
David
--
View this message
