Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of nad.morozova@googlemail.com
 designates 66.249.92.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=HRWZP0mJAqGsCjtalSv9YVOB9Yplv+n6FlAvB8UaQlgfBmHLNBvEsm80p53BgNQirclikDcGBBlb9LFpEk0AuOMWqwBMO4zmqDPXszHHWG0I9AwNi79wttYTa1vcjd0CNsXbzua9WRWnSA8mxzQAy4S5TYYr1s9/IjNOHeUfJjc=
Message-ID: <a7fa4e070710040724t2802d3fbi8f05d035a11d5c83@mail.gmail.com>
Date: Thu, 4 Oct 2007 18:24:53 +0400
From: "Nadya Morozova" <nad.morozova@googlemail.com>
To: dev@harmony.apache.org
Subject: Re: [site] add automatic out-of-date notice to the old pages
In-Reply-To: <c30d70960710040720n5e89dfd6n52d423209cbca1f6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_29910_22996230.1191507893154"
References: <a7fa4e070710040403h4ca97147p2f2c5dac37c4f228@mail.gmail.com>
	 <906dd82e0710040715h777f9a55m15d5f992a7c40e18@mail.gmail.com>
	 <c30d70960710040720n5e89dfd6n52d423209cbca1f6@mail.gmail.com>

------=_Part_29910_22996230.1191507893154
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

ok, a more complicated status algorithm:

<status=current> - no notice
<status=old> Warning: this page is out of date and currently being revised.
<status=incomplete>Warning: this page is under construction, additions are
being made.

On 10/4/07, Alexei Fedotov <alexei.fedotov@gmail.com> wrote:
>
> I like original Nadya's idea. If there would be other supporters, I
> would gladly help her with the script.
>
> On 10/4/07, Mikhail Loenko <mloenko@gmail.com> wrote:
> > I agree that we need to distinguish somehow the pages that are perfect
> > from the pages that are out of date. Ideally we should not have out of
> > date pages though...
> >
> > I think that it should not be something automatic: for example for
> > the page that describes command line option we can say that we plan
> > to add more options soon. So the text of the notice might differ
> >
> > Thanks,
> > Mikhail
> >
> > 2007/10/4, Nadya Morozova <nad.morozova@googlemail.com>:
> > > Hi,
> > > What do you think of this:
> > > Let's add a notice at the top of evidently old pages on the website to
> warn
> > > readers that the docs are out-of-date and currently being revised?
> Some of
> > > the DRLVM component descriptions, such as the threading module, and
> the
> > > developer's guide (see bug HARMONY-4646 for report on wrong bits).
> > >
> > > we could perhaps automate adding some notice by editing the site.vslfile?
> > > for example, we could add a new property of "status" or something to
> xml
> > > pages, and when the status is "outofdate", the processing engine will
> add
> > > some notice to the top of the corresponding html page. At least,
> that's how
> > > i see this from the technical standpoint. if somebody could come up
> with a
> > > better solution or add a new macro to site.vsl with this
> functionality, that
> > > would be real nice.
> > >
> > > --
> > > Cheers,
> > > Nadya
> > >
> >
>
>
> --
> With best regards,
> Alexei,
> ESSD, Intel
>


-- 
Cheers,
Nadya

------=_Part_29910_22996230.1191507893154--