Michal, you hit it right on. If we do not give it a look and feel to match
our corporate standards our Technical Steering Commitee will see the
product as not being appropriate to use.
We all know this is technically wrong, but perception is reality when the
business people in the company are involved.
Yes I can use stylesheets for some but I also need the scripts to finish
the job.
Regards,
Garvin LeClaire
Anthem Inc.
Senior Technical Architect
Technology Architecture and Infrastructure
Tel: 513-336-3305
Maczka Michal
<[EMAIL PROTECTED] To: "'Maven Developers List'"
<[EMAIL PROTECTED]>
tf.ch> cc:
Subject: RE: xdoc with custom
templates and/or navigation
05/05/2004 04:38
AM
Please respond to
"Maven Developers
List"
> -----Original Message-----
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 05, 2004 2:14 AM
> To: Maven Developers List
> Subject: RE: xdoc with custom templates and/or navigation
>
>
> On Tue, 2004-05-04 at 20:07, Brett Porter wrote:
> > The wiki has instructions on submitting patches.
> >
> > You need to do cvs diff -u against CVS HEAD for
> maven-plugins/xdoc, ie:
> >
> > 1. cvs checkout maven-plugins
> > 2. make changes in xdoc plugin there
> > 3. create issue in JIRA (MPXDOC-<NUMBER> returned)
> > 4. do this:
> > cd maven-plugins
> > cvs diff -u xdoc >MPXDOC-<NUMBER>.diff
> > 5. attach MPXDOC-<NUMBER>.diff to the issue
> > 6. wait for it to be applied
> >
> > Remember to change <NUMBER> to the number given by JIRA.
> >
> > But on a side note - I'm not exactly sure why you want to
> override these?
>
> It's not one I'd like to see applied. Changing the structure of the
> output is not a good idea. If required I think it's just indicative of
> the stylesheet lacking certain elements. The application of the theme
> should be entirely possible via the stylesheets. If you want
> completely
> different output then do it with something else. This is not
> the sort of
> customization I want to see in any of the plugins.
>
> --
> jvz.
>
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.
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.
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.
Michal
---------------------------------------------------------------------
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]
