ok, sounds good.
so, do we want a "src/site" under *plugins* folder, as our entry point?
http://svn.apache.org/viewvc/incubator/adffaces/trunk/plugins/
(of course, each modules has its own src/site)
That's for the plugins.
Howto do we handle the "integration" with Trinidad?
I think it would be nice if the user has the possibility to reach both
(Trinidad and Plugins) from a starter site (i.a.o/adffaces OR
m.a.o/trinidad)
-Matthias
On 8/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I always prefer compositon, I find it easier to maintain and it's also
easier to add/remove parts imho. so +1 for option 2.
Regards,
Simon Lessard
Fujitsu Consulting
"Matthias Wessendorf" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
2006-08-14 23:41
Please respond to adffaces-dev
To: [email protected]
cc:
Subject: [plugins] documentation
Hi,
this email contains two things.
a) Call for help on documentation:
If you like to provide some documentation about the Trinidad plugins,
feel free to add content to the wiki. Or provide xdoc or apt patches
;)
b) Structure:
There are two options for handling the doc structure:
1. create a site module, which contains *all* documentation
2. having each (sub)project/plugin having it's own src/site and *compose*
it.
Shale uses the first (for instance). See [1] for David Geary's remote
example. MyFaces uses the second.
What do you like more ?
-Matt
[1] http://shale.apache.org/features-remoting.html
--
Matthias Wessendorf
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
--
Matthias Wessendorf
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
