Forum OpenACS Q&A: Re: Current state of theming in OpenACS (without .LRN)

Collapse
10: Re: Current state of theming in OpenACS (without .LRN) (response to 3)
Posted by Jim Lynch on 12/26/12 02:35 PM
Hi,

I'm working on a script that makes a new openacs package which is a theme that can be applied to a subsite. I believe I'm at 60% before a bug shakedown of the script, this is after about 2 days, and so I expect maybe 2-3 more hack sessions before the script has generated its first working theme package.

In this thread, Dave Bauer refers to automation to make a theme package; this script is meant to fill that bill.

See the action:

git clone git://github.com/jwlynch/openacs-theme-create.git

-Jim

Collapse
11: Re: Current state of theming in OpenACS (without .LRN) (response to 10)
Posted by Jim Lynch on 12/27/12 12:33 AM
OK, the script seems to work now. Give it a shot... instructions are in the script near the top.

I'll add more stuff as I go. Next thing is a little report at the end to show the values for a subsite's theming parameters to use that theme.

-Jim

Collapse
12: Re: Current state of theming in OpenACS (without .LRN) (response to 11)
Posted by Jim Lynch on 12/27/12 06:12 PM
It does build a package, which won't install because the package pretty name must be unique... I'll look into that
Collapse
13: Re: Current state of theming in OpenACS (without .LRN) (response to 12)
Posted by Jim Lynch on 12/30/12 08:23 AM
(bugfix)

the way this script works is really simple... it copies a dirfull of files, renames a couple then points everything at the new package.

I didn't set the package-name and pretty-plural values, so they took their value from the package copied from, which means they won't be unique as required by a database constraint.

So this update makes sure there are unique string values in those two variables, and when testing by trying to install the generated package showed the package installed without any problems.

-Jim