On 2/13/07, Paul Benedict [EMAIL PROTECTED] wrote:
Yup. Spring uses Docbook. That's what I am going to try: single html
page (everything), multiple html pages, and PDF.
For DocBook under Windows, I've been having good luck with
* TextPad
* xlstproc
* Apache FOP
The trick is to use xmllint
Ok, any chance for a summary with roles on who's going to do what, and
in what timeframe ?
Although limited in spare time (aren't we all), I'm definitely willing
to work on this (and I assume Musachy as well), but I would appreciate
directions or a concrete plan.
Shoot.
Phil
On 2/14/07, Ted
I don't have the time to work on a significant refactoring this year.
The most I can do is help keep what we have patched and up-to-date.
As a PMC member, I would be opposed to any project-sanctioned effort
that is going to create a set of redundant documents that would be
made part of a
So, tonight is last call on 2.0.6. Please try to take a look at the
TODO list, if you have a chance.
*
https://issues.apache.org/struts/secure/IssueNavigator.jspa?mode=hiderequestId=10764
A fix for WW-1711 that didn't break the tests (or updated tests) would
be especially welcome!
-Ted.
On
I understand we don't want duplicated docs, but at the moment, we have
to realize our Developers Guide is a mix of a Users Guide, Developers
Guide and Reference Guide.
If we take the following 'definitions' into account:
- Developers: in-depth architecture, creating and extending
Interceptors,
In Struts in Action, as with many text books, we included Developer
information at the foot of a section or chapter as appropriate. So
first, we covered the user material and then we covered the
developer material, without creating two content streams. I don't
see that mixing the two is a bad
Ok, sounds fine to me. Then we'll drop the User Guide, and start
writing on those missing chapters.
Btw, the crud tutorial: should we make a part II where we use a real
database (in combination with Spring and Hibernate) ? I've updated it
and verified it to work on S2, but WW-1711 is used in the
Sadly, Hibernate's a bit of sticky wicket, because of the whole LGPL thing.
We could do iBATIS, or Spring JDBC, or JPA, or anything under a
compatible license.
* http://people.apache.org/~cliffs/3party.html
I've been wondering if Hibernate or iBATIS plugins would make any sense.
As to the
--- Ted Husted [EMAIL PROTECTED] wrote:
So first, we covered the user material and then we
covered the developer material, without creating
two content streams.
FWIW, I think two completely separate content streams
is definitely a Bad Thing. I'd rather see a tutorial
with sidebars containing
--- Niall Pemberton [EMAIL PROTECTED] wrote:
[...]
I guess there's also a {float...} element; I tried a
little test on the Result annotation page (not much in
it, proof-of-concept).
It might be a good way to get links to additional info
w/o breaking the default flow of the page.
Dave
On 2/14/07, Dave Newton [EMAIL PROTECTED] wrote:
One thing that would help clean up the wiki guides
is to format it more like a book: sidebars really work
and are much less disruptive than a browser-width
highlighted section. I don't know if that's possible
with Confluence, but it sure could be
I'm getting this again on my windows box, could this be coming from the
sitemesh plugin who has 2 optional references to velocity? :
java.lang.NoClassDefFoundError: org/apache/velocity/app/VelocityEngine
at java.lang.Class.getDeclaredMethods0(Native Method)
at
One thing that might help wiki readability is to
reduce the width of the page; it's hard to read wide
pages like that. Just an ideer.
d.
Don't get soaked. Take a quick peak at the forecast
with the Yahoo!
That's driven by the Confluence template used by the autoexport
plugin. I checked in a copy of what we are using now. I think the only
change from the default was to embed the licensing and copyright
blurbs.
* http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/site/confluence/
but, this
On Feb 14, 2007, at 2:38 PM, Ted Husted wrote:
That's driven by the Confluence template used by the autoexport
plugin. I checked in a copy of what we are using now. I think the only
change from the default was to embed the licensing and copyright
blurbs.
*
15 matches
Mail list logo
