On Sun, Jul 25, 2010 at 1:25 PM, Zed A. Shaw <zeds...@zedshaw.com> wrote:
> On Sun, Jul 25, 2010 at 07:39:28PM +0800, Michael Richter wrote: > > Looking more into the skinning issue, it looks to me like the file > skins.c > > contains a bunch of stuff that could be generated trivially from a script > of > > some sort. Is there any interest in me making the skinning system more > > flexible so it's easier to add a new skin by basically just checking in > > three files under a new directory? The idea would be something like > this: > > I think that'd work at first, but just to be clear, this means that you > can only change the look of a fossil site by recompiling the binary > right? A more useful solution would one that doesn't require a > recompile. > You can always customize a skin, just as you do now. I think the idea is that there are more built-in prepackaged skins that you can use as starting points or templates. Only the built-ins are compiled in. Use the "fossil configuration export skin" command to export a file containing a skin for export to others. Or "fossil configuration import" to start using a skin previously exported by somebody else. > > > -- > Zed A. Shaw > http://zedshaw.com/ > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- --------------------- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
