I was able to use a custom script with the standard css files or with
"custom" css files. Cascading Style Sheets do not handle all the look of
the site.
The script controls the content that is not configurable through
properties.
The current paradigm for the xdoc plugin where the formatting is done with
jelly script and css could be quite flexible and easy to use. I did have
to learn jelly first, which had a short learning curve.
If in making this faster you lose flexibility I would think we are
diverting away from the initial benefit of Maven of making, building and
documenting a project. It would be nice to be faster but it is currently
faster than using many of these reporting tools separately and then
consolidating these reports into one look and fell.
Regards,
Garvin LeClaire
Anthem Inc.
Senior Technical Architect
Technology Architecture and Infrastructure
Tel: 513-336-3305
Jason van Zyl
<[EMAIL PROTECTED] To: Maven Developers List
<[EMAIL PROTECTED]>
g> cc:
Subject: RE: xdoc with custom
templates and/or navigation
05/05/2004 07:39
PM
Please respond to
"Maven Developers
List"
On Wed, 2004-05-05 at 19:18, Brett Porter wrote:
> I'm a little confused on this thread. The fast xdoc plugins sounds good
and
> using *Mesh sounds like a neat idea, but I still don't understand why we
> need things to conform to a certain XHTML output format.
>
> Surely the inputs are the page body (xdoc), the navigation (xml), and
> perhaps some other metadata files we have come up with along the way, and
> any plugins should work with that transforming xdoc -> xdoc, with the
> actualy xdoc -> xhtml being the last stage of the pipeline?
>
> And the xdoc plugin, while it should have a fast, standard
implementation,
> should definitely be able to read an XSLT file and use that instead if
that
> is what the user really wants to do.
That can be an add-on, something that won't go in xdoc plugin. If
someone wants to munge the xdoc into some other xhtml format so that
they can use a custom css then they can do that outside the xdoc plugin.
The xdoc plugin creates xhtml from the xdoc format so that it conforms
to the css provided by the xdoc plugin. But there is no reason someone
couldn't make a component that took the xdoc and performed an xslt
transformation to produce a different xhtml format which was then styled
by a custom css.
All the navigation, header, footer and body elements produced by the
xdoc are rendered in certain format so they can be rendered with the
supplied css. The new xdoc plugin performs a relatively simple task
> That's my understanding, let me know if I'm missing something.
> Cheers,
> Brett
>
> > -----Original Message-----
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, 5 May 2004 10:24 PM
> > To: Maven Developers List
> > Subject: RE: xdoc with custom templates and/or navigation
> >
> >
> > On Wed, 2004-05-05 at 04:38, Maczka Michal wrote:
> >
> > > Jason!
> > >
> > >
> > > It's not just a question of the "theme".
> > > Some organization have already their own standards which define
> > > precisly how their intranet pages are looking. Often thy
> > have alredy
> > > hundreds of pages with spcific layout which is completly different
> > > then this one which proposed by maven (for example some of them are
> > > using html frames) For them it might not only be attrative
> > but simply
> > > necessry to have much higher level of customization which
> > will allow
> > > to generate what they want.
> >
> > That's fine, they can use tools like StaticMesh or SiteMesh
> > alter anything they like, or integrate whatever portions of
> > the maven generated sites they like.
> >
> > > I understand that you intention is to have quite simillar
> > (standard)
> > > sites which are easy to browse. It's an appealing goal but I think
> > > that most of the users will use the default theme anyway. But if
> > > somebody cannot do this or he does not want he should be
> > free to go
> > > with his own solution.
> >
> > They can, it's just not something I want baked in. I also say
> > this because the new xdoc plugin is blindingly fast because
> > I'm directly writing out the xhtml from xml by passing the
> > use of any other tools which is why it is so fast and so
> > small. This is I will not sacrifice for users every whim for
> > customization. This level of customization is entirely, and
> > easily possibly with the StaticMesh/SiteMesh tools.
> >
> > > BTW: in maven1 there are strange relations between site and xdoc
> > > plugins. We might imagine that somebody will be able to
> > write his own
> > > replecment for xdoc plugin and use it from site plugin.
> >
> > Yes, but ultimately the must conform to the xdoc style of
> > document or they basically get no benefit from any of the
> > plugins that produce the xdoc style. At any rate, these cases
> > will be few and far between and for those cases tools exist
> > to munge the generated xdoc or style xhtml in anyway shape or form.
> >
> > --
> > jvz.
> >
> > Jason van Zyl
> > [EMAIL PROTECTED]
> > http://maven.apache.org
> >
> > happiness is like a butterfly: the more you chase it, the
> > more it will elude you, but if you turn your attention to
> > other things, it will come and sit softly on your shoulder ...
> >
> > -- Thoreau
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise protected by law. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
