I've been testing on the user guide, not the modeler guide.. so its
not really affecting me
In fact, the user guide changes aren't affecting me dramatically since
its not 100% updated :) Plenty of good examples, just difficult to get
a nice page that has lots of unmatched examples.
Anyway, I think we're going to end up having some sort of mnemonic
like !!DataContext!! to trigger a javadoc reference, but I'm not quite
there yet. Soooo as far as the modeler guide goes, at some point it
will need changed, but I think its just as good to wait until you know
what it needs changed to.
Cris
On 2/28/06, Kevin Menard <kmenar..ervprise.com> wrote:
> When I did up the modeler docs, I made javadoc links. There are only a
> few of them in the modeler documentation, however. Do you want me to roll
> those back now (I liked that they were links at least so we'd know where
> to change later on) or just wait until you have your macro all set?
>
> --
> Kevin
>
> On Tue, 28 Feb 2006 15:01:33 -0500, Cris Daniluk <cris.danilu..mail.com>
> wrote:
>
> > I noticed some people have been making edits to the cayenne docs under
> > the CAYDOC space in Confluence. While this is helpful, I'd like to ask
> > that everyone leave the docs alone at the moment. I am currently
> > working on some plugins to help improve their usefulness, so I'm
> > depending on a relatively stable base.
> >
> > Specifically, Malcom updated a bunch of class refs to link to the
> > javadocs. However, since the javadoc links aren't necessarily static
> > (particularly as we move into 1.2, etc), this adds potentially severe
> > overhead. If you could roll these changes back, I would really
> > appreciate it. Once I finish my work, class names should automatically
> > (or at least semi-automatically) resolve themselves to the most up to
> > date javadoc location available.
> >
> > Thanks all!
> >
> > Cris
>
>
>
This archive was generated by hypermail 2.0.0 : Tue Feb 28 2006 - 17:13:12 EST