On 3/2/07, Gav.... <[EMAIL PROTECTED]> wrote:
> -----Original Message-----
> From: Xavier Hanin [mailto:[EMAIL PROTECTED]
> Sent: Friday, 2 March 2007 6:28 PM
> To: [email protected]
> Subject: Re: [jira] Resolved: (IVY-411) review home page template
>
> On 3/2/07, Gav.... <[EMAIL PROTECTED]> wrote:
> >
> > > Good idea, I've done the update. I took the easy way, so on pages
> > > under the Home you will have "Incubator > Ivy > Home > Features",
with
> > > two links to the same page (Ivy and Home). But is doesn't hurt too
> > > much, does it?
> >
> > Doesn't hurt no but I don't like it.
> >
> > I can cure this for you no problem, but means editing the breadcrumb
> > function in xooki.js. This would mean that it would then deviate from
> > The xooki release, is this a problem ? Should I maybe send it as a
patch
> > To the xooki project first (yes I know it's your project). It would be
> > Generic code so wouldn't be tied in to Ivy, it would just need to
check
> > If the current file is in the Home tree and therefore exclude the Home
> > Link.
>
>
> If you submit a patch it's great! Deviate from the xooki release isn't
a
> problem, we are already using the HEAD version. I just try to put
changes
> in
> xooki svn before committing them in Ivy, to keep things separated, but
for
> the moment I think Ivy is the only user of xooki :-)
That's what I thought. You are going to wish I never started soon :) ,
because basically there are many other issues to do with the site, some of
It is xooki related though so tell me if you want me to create Jira Issues
For Ivy or if you want be to log them on the xooki site.
If you already know they are xooki related, I'd prefer you use the xooki
site. Indeed even if I created the project for Ivy need it may find other
users one day :-)
1. Output html does not have stylesheet in the code, instead it is hidden
Inside of the javascript. This has usability and validation problems. The
W3C validator can not see the CSS and so can not validate. Users that have
Disabilities that may want to override some of the CSS or even disable it
Altogether in favour of their own stylesheet can not, because again the
Stylesheets are hidden away in the Javascript.
2. If Javascript is turned off or blocked then the Ivy site does not
appear
At all.
3. templates are uploaded and viewable on the web.
e.g http://incubator.apache.org/ivy/template.html
(not visable from the menu, but I bet google will show it around)
Those 3 items IMO fall into the same category. And I could add more, at
least the fact that some links cannot be followed by web crawlers (all
javascript generated links, and maybe even others because they are in a
textarea). The only solution I see to all these problems is to return to
generation.
In this case you will ask me what's the advantage of using xooki instead of
other good solutions based on site generation? I'm sometimes wondering
myself, but I think that the big advantage is that it would still be
possible to use the "in browser generated" pages when browsing offline,
offering the ease of submitting patches that was the primary focus of xooki.
But the online version would be either server generated (by a servlet for
instance, not usable here at Apache AFAIK) or build generated (with an ant
task). What do you think? Do you see other solutions?
There are many HTML Validation errors, there are also Symantec errors such
as Using <h1> for headings multiple times down a page.
I didn't know it wasn't allowed. I should use validators, I know, but I'm
still a newbie with all these HTML things.
The above things may not be important to you or to the Ivy project, but I
feel it will hurt the popularity of xooki certainly.
I strongly agree, I consider them important even for the Ivy project.
As they are happening
On the Ivy site though I guess they could be deemed Ivy issues.
I don't want to burden the ivy list with such stuff, I'd rather you got on
With coding and other stuff so projects like Apache Forrest (who are
likely
To adopt Ivy soon) can benefit.
I don't think you burden the list, as soon as this conversation occurs on
ivy-dev, it's something that people involved in the development have to
consider, because documentation is an important part of the development.
OTOH, I agree that we are already pretty busy with coding and testing, so we
must set priorities. But IMO even if I'm not fan of writing doc, good
documentation is important to increase Ivy popularity, and thus increase the
chance to recruit contributors and/or commiters.
Anyway, I'll send that patch shortly :)
Great, thanks in advance,
- Xavier
Gav...
>
> - Xavier
>
> Or do you think I can create a separate js file for this and add it to
> > The config.json (not sure how that works just yet)
> >
> > Gav...
> >
> > >
> > > >
> > > > But, looks good.
> > > Thanks,
> > >
> > > Xavier
> > >
> > > >
> > > > Gav...
> > > >
> > > > >
> > > > > > review home page template
> > > > > > -------------------------
> > > > > >
> > > > > > Key: IVY-411
> > > > > > URL:
https://issues.apache.org/jira/browse/IVY-
> 411
> > > > > > Project: Ivy
> > > > > > Issue Type: Improvement
> > > > > > Components: Documentation
> > > > > > Affects Versions: 1.5
> > > > > > Reporter: Xavier Hanin
> > > > > > Assigned To: Xavier Hanin
> > > > > > Fix For: 1.5
> > > > > >
> > > > > > Attachments: ivy-home.jpg, ivy-home.patch
> > > > > >
> > > > > >
> > > > > > The home page of Ivy shows a big Ivy logo in the center, with
> > > another
> > > > > logo at the top right. Removing the top banner for the home page
> > only
> > > > > would improve its layout.
> > > > >
> > > > > --
> > > > > This message is automatically generated by JIRA.
> > > > > -
> > > > > You can reply to this email to add a comment to the issue
online.
> > > >
> > > >
> >
> >
