Fork me on GitHub

Which theme engine do you use?  Bottom

Go to page [-1] 1 - 2:

  • alarconcepts


    1) A new learning curve...which is not conducive to learning by newbies or even novices (like myself).

    Unless you happen to already be familiar with any of the many open source applications that already use Smarty as the base of thier templating systems. So in a sense xanthia by virture of Smarty is cross platform (but obviously not to the same level as AutoTheme). Xoops and tikiwiki both make use of Smarty.

    alarconcepts


    2) Same for AT. is wherever it's used.

    This wasn't my point. If you use PN you will, at some, point come across a Smarty template because of pnRender. More and more modules are being written using pnRender. So you have two skills sets to learn if you use AutoTheme - one for themes, one for blocks and modules.

    alarconcepts


    3) AutoTheme uses HTML...which is far more widely used than Smarty...and easier.

    Smarty embeds it's commands into HTML identically to AutoTheme but I feel that Smarty's in-built commands are much wider and varied that autothemes.

    alarconcepts


    4) AutoTheme allows you to build your own custom commands as well.

    While you can define commands in the AutoTheme admin/config files this isn't as simple as developing a plugin which is a straight PHP file. Plugins are more like AutoTheme extras - in fact AutoTheme extra are probably based on Smarty pliugins. The difference our setup (and i'm sure shawn can code this easily) is that AutoTheme extras currently have to be part of the AutoTheme module. With xanthia plugins can exist as part of the theme - no need to spread files across your PN install for a theme.

    alarconcepts


    8) This is the beauty of AutoTheme. It gets the job done without a lot of bloat on the learning curve.

    There are some things can can be trimmed from xanthia but, as i've said already, there are features in AutoTheme (saying alternating summaries) that can be done in xanthia without the need for the engine to have this feature coded.

    alarconcepts


    ...while I understand some of your points, I still feel that the ease of use, the sheer number of supporting sites & free themes, and quick learning curve of AutoTheme makes it the superior solution for newbies. For those who don't have any trouble learning the Smarty linguistics, as well as the structure of files->plugins->templates, maybe XTE is a good solution...but it just seems that newbies aren't those people IMHO.

    In some respects i'm entirely happy for xanthia to be considered 'the power solution'. <joke>When a user outgrows AutoTheme they can move onto somemore more capable</joke>

    alarconcepts


    Thanks for your reply...perhaps we can agree to disagree.
    )

    Of course. I'm not here to convince anyone - i'll make the case but, ulimately, it's up to others to make thier own decision and do what they think it right - the PN dev team have done that.

    Having the two systems is actually good for both - a healthy bit of competition never hurt anyone. You may not have template compilation, page caching, extras in AutoTheme if it wasn't for xanthia - these features come directly from thier Smarty equivalents....

    -Mark

    --
    Visit My homepage and Zikula themes.
  • Lobos

    I use AutoTheme simply becuase it is cross platform, maybe the same reason why lots of people use adoDB.

    What I really think all templating / theme systems should look into is containing the whole page in one HTML document as opposed to seperate files for blocks, news, etc - I understand that this is important for customisation, but I think there should be the option of all contained in one file. I also think this file should be able to work independantly of any CMS or PHP. eg:

    Get my drift?

    -Lobos


    Lobos,

    Absolutely.... I could probably code this architecure into PN fairly quickly if I didn't have to be concerned with support for legacy themes and AutoTheme itself.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • A question of my own....

    For those of you that use AutoTheme what are you current feature requests? What things can't you achieve in AutoTheme that you'd like to be able too?

    If you say 'nothing' I won't believe you ;) - everyone has some kind of feature request regardless of the module......

    -Mark

    --
    Visit My homepage and Zikula themes.
  • I honestly can't think of anything. I have some requests for the OSC version, but the nuke version do everything my clients have requested.
  • markwest

    A question of my own....

    For those of you that use AutoTheme what are you current feature requests? What things can't you achieve in AutoTheme that you'd like to be able too?

    If you say 'nothing' I won't believe you ;) - everyone has some kind of feature request regardless of the module......

    -Mark


    The main thing that I think would be great is module templating - along with my request that it be possible to have a theme as one complete HTML file without sperate blocks, etc - the more I think about this, the more it appeals to me - imagine how easy it would be for users to customise there themes - even make them themselves, this would make the design process much more intuitive for knoobs :)

    -Lobos

    --
    -Lobos
    Professional PHP Framework Services: Concept, Development and Deployment
  • I disagree 100%. Your thinking about this from a template designer perspective and being able to sell more because its compatible with more CMS's. As an admin that creates themes for myself and not for distro just to make money. I would rather have an engine that has been streamlined and created specifically for a CMS's. That way it can take full advantage of the API of the CMS. As far as a single file, why would you ever want that? The current site im working on has about 20 different block templates and about 10 module templates. One page might have 10 different block templates in it. I absolutely hate the idea of having it all in one file. Might as well be the PN themes with just a theme.php file that controls everything. Ewww.
  • MACscr

    I would rather have an engine that has been streamlined and created specifically for a CMS's. That way it can take full advantage of the API of the CMS.


    This would still be the case with the OPTION of only using one file for the template... you could still add as many commands / etc as you like.

    MACscr

    As far as a single file, why would you ever want that? The current site im working on has about 20 different block templates and about 10 module templates. One page might have 10 different block templates in it. I absolutely hate the idea of having it all in one file. Might as well be the PN themes with just a theme.php file that controls everything. Ewww.


    I did not say that this should be the only option - it would be foolish to take away the flexibility that we have now - I just think it would be nice to have the option of only using one template.

    MACscr


    Your thinking about this from a template designer perspective and being able to sell more because its compatible with more CMS's.


    Damn right I am ;)

    --
    -Lobos
    Professional PHP Framework Services: Concept, Development and Deployment
  • I like Jelly Beans.


    ..that's a trick question. there's only one theme "engine" listed .. :) ..which meeeeaanns: there's only one correct answer. ;)
  • alarconcepts


    2) Same for AT. is wherever it's used.

    But can only be used in Theme templates, not in Module templates at this point, and to make a module other than AT rely on AT would be foolish for a PN developer.

    Quote

    3) AutoTheme uses HTML...which is far more widely used than Smarty...and easier.

    Smarty uses HTML too, what's your point?

    Quote

    8) This is the beauty of AutoTheme. It gets the job done without a lot of bloat on the learning curve.

    If I didn't already know AT, I think X and AT would be about on par for doing what they share.

    Quote

    I still feel that the ease of use, the sheer number of supporting sites & free themes, and quick learning curve of AutoTheme makes it the superior solution for newbies.

    Then we should have never forked from PHP-Nuke and we should have never even bothered with CMSes, the learning curve for a CMS is higher than that of making HTML sites.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • Hi,
    my concern is about Multisite handling: does AutoTheme have a Multisite feature or it uses the PN module?
    Also i asked in other thread but without answer: Is PN Multisite feature going to change on PN 0.8? Is it better to wait or it or the upgrading from PN 0.76 to 0.8 will be easy?
    Tx
  • awillys

    Hi,
    my concern is about Multisite handling: does AutoTheme have a Multisite feature or it uses the PN module?
    Also i asked in other thread but without answer: Is PN Multisite feature going to change on PN 0.8? Is it better to wait or it or the upgrading from PN 0.76 to 0.8 will be easy?
    Tx


    Multisites are multisites - both AutoTheme and xathia correctly handle themes in a multisite (I believe). For .8 there is a new multisite module that should be a lot easier to work with - you define new sites and set what tables are shared/not shared from the admin panel. The module is still in it's very early stages at the moment.

    The main problem will be that is a completely different approach to the problem and I don't yet know how simple a multisite migration will be. Regardless we'd always recommend using the latest stable release (multisites has no change for .76).

    -Mark

    --
    Visit My homepage and Zikula themes.
  • Thanks
  • where is the option "classic theme"?
  • A classic theme is one that doesn't use Xanthia or AutoTheme, that's all.

    --
    itbegins.co.uk - Zikula Consulting

    birtwistle.me.uk - Personal Blog


    Please read the Support Guide

Go to page [-1] 1 - 2:

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