Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [higgins-dev] fixing the component row templates

 
Jim,
 
Please provide more detail on your ideas for auto generating the dependency info.  We really want this info to be complete and up-to-date.  We had been writing dependencies used in the build process to the wiki in one iteration of the build process.
 
 


From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim
Sent: Saturday, November 17, 2007 12:37 AM
To: higgins-dev@xxxxxxxxxxx
Subject: Re: [higgins-dev] fixing the component row templates

I updated all the tables for y'all.  Some of the dependency links are broken now.  If you care, you can look at an old version of the page like http://wiki.eclipse.org/index.php?title=Components&oldid=60587 to find your old dependencies and copy them to the new dep page.


Personally, I think the dep column should go away.  I mean, the dependencies can be generated in a much easier and complete way.

>>> "Jim Sermersheim" <jimse@xxxxxxxxxx> 11/16/07 7:09 PM >>>

I did some very hacky stuff in the template using default params and got it to allow dir=<somedir at the root of the higgins tree>, appdir=<somedir under /app>, or plugindir=<somedir under /plugin>


I think people can convert over to the templates now

>>> "Jim Sermersheim" <jimse@xxxxxxxxxx> 11/16/07 2:17 PM >>>

I took a stab at changing the template to do what we want, and it works in sort of a limping way.


I really wanted to be able to have the viewcvs point at the proper place regardless of whether the project is under /api, /plugins, or at the root.  To do that, we need the mediawiki extension ParserFunctions loaded.


I logged a bug but it's one of 84 on the webmaster's plate, so I dont' know how long it will take for it to be addressed.


Jim


Back to the top