If necessary, a whole book can be written. :) I was just curious how useful it would be over extension developers browsing the Javadoc to see what scaffolding was available.
Matt On Mon, Jul 2, 2012 at 11:41 AM, Romain Manni-Bucau <[email protected]> wrote: > Cant a single page doc be kept? > > Le 2 juil. 2012 18:30, "Matt Benson" <[email protected]> a écrit : > >> Argh, s/Javascript/Javadoc/ :P >> >> Matt >> >> On Mon, Jul 2, 2012 at 11:13 AM, Matt Benson <[email protected]> wrote: >> > Out of curiosity, how much of the developer-targeted info cannot be >> > conveyed through good old Javascript? >> > >> > Matt >> > >> > On Mon, Jul 2, 2012 at 10:48 AM, Mark Struberg <[email protected]> >> > wrote: >> >> There are definitely 2 different user groups. The ones who just like to >> >> 'use' DeltaSpike in their apps and the others who like to use DS to build >> >> own Extensions. >> >> >> >> Sometimes those 2 groups overlap, but there are imo 2 distinct target >> >> groups. >> >> We could keep the grouping via functionality and add the user vs dev >> >> for each of them. >> >> >> >> There are for sure some functionality (BeanBuilder, >> >> AnnotatedTypeBuilder) which is clearly only relevant for Extension devs. >> >> >> >> >> >> LieGrue, >> >> strub >> >> >> >> >> >> >> >> ----- Original Message ----- >> >>> From: Christian Kaltepoth <[email protected]> >> >>> To: [email protected] >> >>> Cc: >> >>> Sent: Monday, July 2, 2012 5:38 PM >> >>> Subject: Re: Add pages from old web site >> >>> >> >>>T o be honest, I don't think splitting the documentation into two >> >>> different parts ("developer" and "user") is a good idea. I >> >>> think >> >>> people may be confused which of the two documents they have to read if >> >>> they are looking for a specific information. Especially for advanced >> >>> use cases (like using extension points of the API) the difference >> >>> between the two could be not clear for everyone. >> >>> >> >>> Christian >> >>> >> >>> 2012/7/2 Charles Moulliard <[email protected]>: >> >>>> I agree on the idea to separate the user guide from developer guide >> >>>> as we >> >>>> have done that for Apache Karaf project >> >>>> (http://karaf.apache.org/manual/latest-2.2.x/users-guide/index.html, >> >>>> >> >>>> http://karaf.apache.org/manual/latest-2.2.x/developers-guide/index.html). >> >>>> And as you can see, there are no overlap between content of the 2 >> >>>> guides. >> >>>> >> >>>> Users and Developers guide will have 2 different goals. The >> >>>> developer guide >> >>>> will be focused on How to build the code, debug, maintain it and >> >>>> also How >> >>> to >> >>>> develop CDI extensions, new modules while User guide will be more >> >>>> focused >> >>> on >> >>>> providing examples of using @ConfigProperty, Running DeltaSpike with >> >>>> JavaSE >> >>>> + weld / own, OSGI. So I don't see any overlapping from this >> >>> perspective as >> >>>> they drive 2 difference scopes. >> >>>> >> >>>> ----- >> >>>> Apache Committer / Sr. Pr. Consultant at FuseSource.com >> >>>> Email: [hidden email] >> >>>> Twitter : @cmoulliard, @fusenews >> >>>> Blog : http://cmoulliard.blogspot.com >> >>>> -- >> >>>> View this message in context: >> >>> >> >>> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Add-pages-from-old-web-site-tp4652925p4652933.html >> >>>> Sent from the Apache DeltaSpike Incubator Discussions mailing list >> >>>> archive >> >>> at Nabble.com. >> >>> >> >>> >> >>> >> >>> -- >> >>> Christian Kaltepoth >> >>> Blog: http://chkal.blogspot.com/ >> >>> Twitter: http://twitter.com/chkal >> >>>
