On Jun 27, 2013, at 1:16 PM, Hadrian Zbarcea wrote:
> Give the fact that it uses precious compile time, I would drop the html
> manual too. It's not as well formated as the PDF one and equally useless.
Well, it takes about 12 seconds to build, and most of that time is downloading
the thing. C
Hey guys,
Can't you use scalate for manual generation? We use it in Karaf and it does a
job. :) It's little forgotten by owners but still usable!
Listings are made by princexml or something like this.
Cheers,
Lukasz
Wiadomość napisana przez Hadrian Zbarcea w dniu 27 cze
2013, o godz. 19:16:
Give the fact that it uses precious compile time, I would drop the html
manual too. It's not as well formated as the PDF one and equally useless.
Just my $0.02,
Hadrian
On 06/27/2013 12:30 PM, Christian Müller wrote:
+1 for #5 but would like to keep html manual.
Best,
Christian
Sent from a m
+1 for #5 but would like to keep html manual.
Best,
Christian
Sent from a mobile device
Am 26.06.2013 17:38 schrieb "Daniel Kulp" :
>
> With the latest confluence (and also once they actually update to 5.1.x),
> the Camel manual is no longer producible. The main problem is the
> javascript tha
+1 #5 but would like to keep html manual.
On Thu, Jun 27, 2013 at 11:37 AM, Claus Ibsen wrote:
> I vote for #5
>
> It will just keep haunting us in the future. With new problems etc.
>
> Its 2013 and people read online docs / google / stackoverflow / watch
> videos / etc.
> The camel pdf manual
+1 for the 5.
I don't think there are lots of people are using the pdf to lookup the document
of camel.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.c
#5 +1 agree
Hadrian
On 06/27/2013 10:07 AM, Claus Ibsen wrote:
I vote for #5
It will just keep haunting us in the future. With new problems etc.
Its 2013 and people read online docs / google / stackoverflow / watch
videos / etc.
The camel pdf manual is not a good manual but just a big dump of
I vote for #5
It will just keep haunting us in the future. With new problems etc.
Its 2013 and people read online docs / google / stackoverflow / watch
videos / etc.
The camel pdf manual is not a good manual but just a big dump of the
web site, thats not readable, and I dont see any people use it
On Jun 26, 2013, at 12:28 PM, Maruan Sahyoun wrote:
> you can give wkhtmltopdf a try. Uses Webkit and is fine with JavaScript.
I did try it. (the 0.9.9 since that's what they have downloadable for the Mac)
It generates a 15MB manual (the prince generated one is 3.7MB) and is poorly
formatt
you can give wkhtmltopdf a try. Uses Webkit and is fine with JavaScript.
BR
Maruan Sahyoun
Am 26.06.2013 um 17:37 schrieb Daniel Kulp :
>
> With the latest confluence (and also once they actually update to 5.1.x), the
> Camel manual is no longer producible. The main problem is the javascrip
With the latest confluence (and also once they actually update to 5.1.x), the
Camel manual is no longer producible. The main problem is the javascript that
is used to format all the {code} and {snippet} macros. The old version of
confluence rendered them into static HTML which prince handle
11 matches
Mail list logo
