Patrick Malley

Thank you, Petr.

I noticed in the Theme_changes doc above that you plan to only include 4-5 basic themes in the core download with more in a separate install repository somewhere. Is this correct? If so, how will we determine which themes to include in this repository? Will the repository be like the open database as we have now?

I certainly don't need to be done with all my themes before beta, but it would be nice to have most of them in for testing and feedback ... especially those themes that rely most heavily on new features.

I have about 10 designs right now that are ready to code for 2.0. I also have a small handful of people waiting for documentation to create themes themselves. I'd then ideally like to create some 2.0 themes that show it's full set of capabilities. Doing this will require some pretty solid documentation.

Essentially, I've committed myself to creating a lot of themes and I'm concerned that I won't be able to deliver as promised if the themes engine is not nailed down sooner than later.

That's a bit of a panicky statement, I realize. I appreciate all that has been done and do not mean to gripe. I'm simply concerned that I won't have enough time to get these themes together for a 2.0 beta release.

Specifically, I need

- one theme in the core that is considered beta to use as a template.
- theme documentation explaining the full capabilities to non-programmers like me.
- two to three months to play around and code.

Hello Pepijn,

I'm not a programmer, so I can't speak directly to the methods involved in creating session themes. However, from experience I can say that logging in creates a new session. This, I think, is why the theme reverts back to the default theme after your users login. I know of no way to change or alter this behavior without hacking the code.

I also don't think that the theme variable is available for CSV input. At least, if there is it is not documented.

Probably the elusive:

#layout-table {margin-top:0;}