Fork me on GitHub

Theme upgrade-safe path and BlankTheme poll  Bottom

  • Hi all!
    i open this thread to discuss two points:
    * How to drive a safe upgrade-path for themes? and
    * A name change in BlankTheme.


    Well, the first point may apply for everybody using Zikula. If i customize a theme, how i sync bugfixes and improvements? In BlankTheme we have a common structure, we can add features and share stuff with ease, but when we've customized some sections, we need to sync the changes carefully, to not lose our custom stuff...
    SVN is a great tool to do this task,
    and Theme developers should know how to use it to update the latest changes in the "main" theme,
    and if we add new features, new zones, SVN simplify a lot the upgrade safe process,
    but do we all use SVN?
    it's really easy, so, if not using it yet should begin to icon_smile
    opinions?


    Currently i have no clue of how many users aprox are using BlankTheme in this moment, or if were interested but leave it (if any)... but there's an issue with the BlankTheme architecture and would be good to hear some points of view:

    Currently BT uses "base" templates, that supports different layouts and zones. Ok, those are the basic concepts. In the latest commit, i've centralized all the HTML HEAD in the head.htm template, and this lead me to thing in centralize all the BODY code in the "base" templates. As a consequence, the better name to "base" templates is "body" templates, and from my point of view this is good to understand clearly the BT structure just relating the HTML concepts with the templates: HEAD => head.htm and BODY => /templates/body/$body.htm, where the $body can be a 2col, 3col or a grid template.

    Is easy to understand that body templates can support many layouts and special zones. The "base" word has no 'previous significance' as "body" has when you know HTML. This can lead to rename the folder /templates/base to /templates/body and change the $base variable to $body, and it's more meaningful, but how can we sync those changes without troubles?
    how we'll add new features to the main BlankTheme and sync our copies?
    SVN does a great job and saves a lot of time doing this process
    but it takes time if the changes are many...

    anyways, the project is now mature enough to not have more major changes, and this can be the last "big movement" in the BT structure, but this open a discussion of how we can have a clean upgrade path to have the "always great" latest stuff.

    I hope to see your points of view guys!
    And as always, Enjoy zk and bt! icon_cool



    edited by: nestormateo, Oct 20, 2008 - 03:15 AM

    --
    - Mateo T. -
    Mis principios... son mis fines
  • Hey, using BT and part of the BT team icon_smile

    1. This is hard, but will me easier over time. For zikula.nl I've done the BT theme, but have to sync to the latest still. This is a lot of work depending on the changes and of course the changes in BlankTheme revisions. The project is now becoming more and more stable so big changes are not likely any more and syncing should become more easy.
    2. this name change is a lot less work than syncing a customized theme IMO. And easier to verify. Search for base and see if you've forgotten any references to the old name.

    erik

    --
    campertoday.nl, Module development, Dutch Zikula Community
  • Yes,
    i hope too that from here the project be easier to sync,
    just have to stop some ideas to not add too much features icon_razz JK

    And about the rename of the base templates to body templates,
    it'll broke the SVN customizations because SVN doesn't handle renames icon_frown
    It just delete and add then custom base/* will be deleted and
    body/* templates will be created "from scratch".

    I'll write some Docs in our Wiki about -How to customize BlankTheme-
    and add a warning to learn and maintain BlankTheme updated with SVN.

    --
    - Mateo T. -
    Mis principios... son mis fines
  • nestormateo

    I'll write some Docs in our Wiki about -How to customize BlankTheme-
    and add a warning to learn and maintain BlankTheme updated with SVN.


    Please! That would be great, I've made several attempts to use BlankTheme for a new site and had to fall back to more traditional Xanthia format. And that's after studying the Yaml docs to understand the concepts. There are just so many more files to deal with, and I'm still not sure of how to customize the theme and then still be able to update it with SVN as nestormateo suggests.

    Right now if you go to the Wiki and search for BlankTheme nothing comes up at all.


    --
    Damon
    Catamaran Sailing at TheBeachcats.com
  • The docs for BlankTheme are in code.zikula.org. Not in the Zikula Wiki. (Right now Cozi is being hardware upgraded, so it is not online). http://code.zikula.org/blanktheme
    The concepts of BlankTheme are much more clear in those docs then in the YAML docs. We have adapted the YAML framework and the concepts and how to work with it are described in the BlankTheme Cozi Wiki.
    In the latest versions, not so many files have to be dealt with since we cleaned upt eh install and moved parts to examples. What files you have to edit is also described in the "how to use" docs.
    So when Cozi is fully bck online again check the docs over there.

    --
    campertoday.nl, Module development, Dutch Zikula Community

This list is based on users active over the last 60 minutes.