On 10 October 2011 02:02, David Crossley <cross...@apache.org> wrote: > sebb wrote: >> Christian Grobmeier wrote: >> >> >>>>> I've not started looking at generating projects/index.xml yet. >> >>> >> >>> Reading the past mails shows me you are +1 to commit the layout >> >>> changes. You are already working on the next steps :-) >> >> >> >> I'm not keen on losing the RH podling list, if that's what you mean; I >> >> think it's useful. >> > >> > You was the only one who said so so far. WIth the bootstrap layout the >> > project/index.html is even more readable than before. > > I reckon that it is important that the list of > current podlings continues to be prominently displayed. > Go to separate tables for further information. > >> >> Introducing the podlings.xml file is independent of any layout changes. >> >> The idea here is to centralise and simplify maintenance of podling >> >> summary details. >> > >> > Yes I understand that. But this thread is/was about layout changes. >> > This xml can be used for many things. >> > >> >> >> >>> BTW, I have made a copy of the podlings.xml file because probably we >> >>> want to use that for some javascript magic. Of course, transforming it >> >>> to JSON would make things easier. >> >> >> >> Easier for Javascript maybe; not so easy for XSLT, and might be harder >> >> for clutch. >> >> >> >> However, we could easily convert to JSON for the published version of the >> >> file. >> > >> > Transformation to both formats are possible of course >> >> It's really a question of which format is easiest to maintain. >> >> Although JSON is simpler, it does not allow comments AFAIK, which I >> think rules it out as a suitable original source file. >> Also, there are currently more tools to work with XML, again AFAIK. >> >> > >> >>>> >> >>>> And I won't now have time until Sunday earliest. >> >> >> >> Actually, I did already commit a sample XSLT, however it is not yet >> >> integrated into the build process. >> > >> > Yes saw it. >> > >> > I have added my layout changes too (website not updated). We need to >> > find a consens on the rh table. I am still not a fan of this, it >> > simply ugly. We have spoken on this thread about generating some kind >> > of projects list from the podlings.xml file. It could show a some kind >> > of dropdown menu from javascript. would you accept this als >> > alternative? >> >> That would probably be fine - I'd like to see it before endorsing it fully. > > It would have been better to do it in a branch.
+1 I think the style changes should be done separately from the change to use podlings.xml. They are independent changes, and the podlings/XSLT change will affect at most the formatting of the projects index.xml page. > The current half-finished changes have made it difficult for > the Incubator to operate. There are uncommitted generated docs > changes for all pages. So real content changes are troublesome. > -David > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org