with the cart getting ahead of the horse then, when and if I get around to doing these upgrades, what's the best way to submit them as patches, not having push capabilities on the fossil-scm site.
Tomek On Tue, May 3, 2011 at 12:38 PM, Stephan Beal <[email protected]> wrote: > On Tue, May 3, 2011 at 4:22 PM, Tomek Kott <[email protected]> wrote: > >> If HTML + CSS is ok, would there be much opposition if I were to >> (eventually) go through and add some classes to every html output I could >> find? What I'm shooting towards is something like WordPress, which puts a >> class for every imaginable parameter in the source code. >> > > Personally i would be all for that. It would make custom JS scripting of > the repo simpler. > > > >> Not that there would be that many classes for a fossil archive, but >> especially for the html we can't change (i.e., not the main menu) it would >> be nice to have more descriptors (say timeline, tickets, etc.). >> > > Amen. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
