Zikula Community

• **unknown user**
  
  

  • Rank: Registered User
  • Registered: Mar 16, 2002
  • Last visit: Sep 14, 2003
  • Posts: 2

  Posted: Aug 06, 2003 - 01:22 PM

  I am using AutoTheme and creating a Theme that I want it to have a different color than what the body CSS tag is set to. Is there some CSS style or something I can do to change the block title color.
  
  Thanks
  
  Eric

  • 
  •  
• Lobos
  
  

  • Rank: Expert
  • Registered: Dec 02, 2002
  • Last visit: Apr 30, 2010
  • Posts: 1474

  Posted: Aug 06, 2003 - 02:27 PM

  You could always create a new class in your style sheet:
  
  

  Code

  .blockTitle {  
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font-size: 12px;
    font-weight: bold;
    COLOR: #ffffff;
    font-style: italic;
    text-decoration: none     
  }

  
  
  If your block title will have links you should also create link, visted, hover and active classes.
  
  Call it like this <font class="blockTitle">title text
  
  Here is a list of all the PN styles I know of (AutoTheme didn't seem to have many included with the distro):
  

  Code

  /* Begin Core Styles */
  body {
    margin: 0px;
    padding: 0px;
    background-color: #E0E0E0;
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font-size: 8px;
    font-weight: none;
    color: #000000;
    scrollbar-base-color : #9393ff;
    scrollbar-arrow-color : #ffffff;  
    scrollbar-track-color : #E0E0E0
  }
  FORM {
    font-family: Geneva, Arial, Helvetica, sans-serif;
       
    font: normal 11px;
    COLOR: #000000;
  }
  OPTION {
  background-color: #ffffff;
  font-weight: normal;
  font-size: 11px;
  border: solid 1px #000000;
  color: #000000
  }
  
  TEXTAREA {
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font: 11px;
    width: 450px;
      border: solid 1px #000000;
    COLOR: #000000;
      background-color: #ffffff
  }
  LEGEND {
    font-family: Geneva, Arial, Helvetica, sans-serif;
    width: 400px;
    font: bold 11px;
    COLOR: #000000
  }
  tr {
      vertical-align: top;
  }
  TH {
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font: bold 11px;
    COLOR: #000000
  }
  INPUT {
              color: black;
              font-weight: normal;
              font-size: 11px;
              font-family: Geneva, Arial, Helvetica, sans-serif;
              background-color: #ffffff;
              text-indent: 0px;
              margin: 0pt;
              border: solid 1px #000000
  }
  INPUT.pn-text {
              color: blue;
              font-weight: bold;
              font-size: 11px;
              font-family: Geneva, Arial, Helvetica, sans-serif;
              background-color: #ccccff;
              text-indent: 2px;
              border: 1px #d9d9ee
  }
  INPUT.pn-button {
        color: black;
              font-weight: bold;
              font-size: 10px;
              font-family: Geneva, Arial, Helvetica, sans-serif;
              background-color: #ffffff;
              text-indent: 2px
               
  }
  INPUT.r-button {
        color: black;
              font-weight: normal;
              font-size: 12px;
              font-family: Geneva, Arial, Helvetica, sans-serif;
              background-color: #e7e5e0;
              text-indent: 2px;
              border: solid 1px #484973
  }
  A:link {
      COLOR: #000000;
      FONT-SIZE: 12px;
      FONT-WEIGHT: bold;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      TEXT-DECORATION: none;
      font-style: normal;
      line-height: normal;
  
  }
   A:visited {
      COLOR: #000000;
      FONT-SIZE: 12px;
      FONT-WEIGHT: bold;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      TEXT-DECORATION: none;
      font-style: normal
  }
   A:hover {
      COLOR: #FF0000;
      FONT-SIZE: 12px;
      FONT-WEIGHT: bold;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      font-style: normal
  }
   A:active {
      COLOR: #000000;
      FONT-SIZE: 12px;
      FONT-WEIGHT: bold;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      font-style: normal
  }
  .pn-normal {  
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font-size: 11px;
    font-weight: normal
    color: #000000;
  }
  .pn-normal A:link {
    COLOR: #000000;
    FONT-SIZE: 11px;
      font-weight: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      TEXT-DECORATION: none
  }
  .pn-normal A:visited {
    COLOR: #000000;
    FONT-SIZE: 11px;
      font-weight: bold;
    FONT-FAMILY:  Geneva, Arial, Helvetica, sans-serif;
    TEXT-DECORATION: none
  }
  .pn-normal A:hover {
    COLOR: #ff0000;
    FONT-SIZE: 11px;
      font-weight: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
   TEXT-DECORATION: underline
  }
  .pn-normal A:active {
    COLOR: #FF0000;
    FONT-SIZE: 11px;
      font-weight: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    TEXT-DECORATION: none
  }
  .pn-title {  
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font-size: 13px;
    font-weight: bold;
    color: #000000;
    font-style: italic;
    TEXT-DECORATION: none  
     
  }
  .pn-title A:link {
    font-size: 13px;
    font-weight: bold;
  color: #000000;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      TEXT-DECORATION: none;
      font-style: italic
  }
  .pn-title A:visited {
    font-size: 13px;
    font-weight: bold;
  color: #000000;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      TEXT-DECORATION: none;
      font-style: italic
  }
  .pn-title A:hover {
    font-size: 13px;
    font-weight: bold;
  color: #000000;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      TEXT-DECORATION: underline;
      font-style: italic
  }
  .pn-title A:active {
    font-size: 13px;
    font-weight: bold;
  color: #000000;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    TEXT-DECORATION: none
  }
  .pn-sub {  
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font-size: 10px;
    font-weight: normal;
    color: #000000
  }
  .pn-sub A:link {
    COLOR: #000000;
    FONT-SIZE: 9px;
      font-weight: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    font-style : normal;  
    TEXT-DECORATION: none
  }
  .pn-sub A:visited {
    COLOR: #000000;
    FONT-SIZE: 9px;
      font-weight: bold;
    FONT-FAMILY:  Geneva, Arial, Helvetica, sans-serif;
    TEXT-DECORATION: none;
    font-style : normal
  }
  .pn-sub A:hover {
    COLOR: #DICDD2;
    FONT-SIZE: 9px;
      font-weight: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    TEXT-DECORATION: none;
    font-style : normal
  }
  .pn-sub A:active {
    COLOR: #FF0000;
    FONT-SIZE: 9px;
      font-weight: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    TEXT-DECORATION: none;
    font-style : normal
  }
  
  .pn-logo {
    COLOR: #405490;
    FONT-SIZE: 11px;
    FONT-WEIGHT: bold;
    FONT-FAMILY: Tahoma, Geneva, Arial, Helvetica, sans-serif;
    LETTER-SPACING: 3px;
    TEXT-DECORATION: none;
    background-color : transparent
  }
  A.pn-logo:link {
    COLOR: #405490;
    FONT-SIZE: 11px;
    FONT-WEIGHT: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    LETTER-SPACING: 3px;
   
    TEXT-DECORATION: none;
    background-color : red
  }
  A.pn-logo:visited {
    COLOR: #405490;
    FONT-SIZE: 11px;
    FONT-WEIGHT: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    LETTER-SPACING: 3px;
   
    TEXT-DECORATION: none;
    background-color : red
  }
  A.pn-logo:hover {
    COLOR: #50dce0;
    FONT-SIZE: 11px;
    FONT-WEIGHT: bold;
    background-color: #444444;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    LETTER-SPACING: 3px;
    TEXT-DECORATION: none
  }
  A.pn-logo:active {
    COLOR: #405490;
    FONT-SIZE: 11px;
    FONT-WEIGHT: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    LETTER-SPACING: 3px;
    TEXT-DECORATION: none;
    background-color : transparent
  }
  .pn-logo-small  {
    COLOR: #DICDD2;
    FONT-SIZE: 11px;
    FONT-WEIGHT: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    TEXT-DECORATION: none;
    background-color : transparent
  }
  .pn-pagetitle {  
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font-size: 12px;
    font-weight: bold;
    color: #DF7B29;
    font-style: italic;
    TEXT-DECORATION: none  
     
  }
  .pn-pagetitle A:link {
      COLOR: #DF7B29;
      FONT-SIZE: 12px;
      FONT-WEIGHT: bold;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      TEXT-DECORATION: none;
      font-style: italic
  }
  .pn-pagetitle A:visited {
      COLOR: #DF7B29;
      FONT-SIZE: 12px;
      FONT-WEIGHT: bold;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      TEXT-DECORATION: none;
      font-style: italic
  }
  .pn-pagetitle A:hover {
      COLOR: #DF7B29;
      FONT-SIZE: 12px;
      FONT-WEIGHT: bold;
      FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
      TEXT-DECORATION: underline;
      font-style: italic
  }
  .pn-pagetitle A:active {
    COLOR: #DF7B29;
    FONT-SIZE: 12px;
    FONT-WEIGHT: bold;
    FONT-FAMILY: Geneva, Arial, Helvetica, sans-serif;
    TEXT-DECORATION: none
  }
  }
  .pn-content-page-body {
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font-size: 10px;
    color: #000000
  }
  .pn-content-page-title {
    font-family: Geneva, Arial, Helvetica, sans-serif;
    font-size: 12px;
    color: #30678F
  }
  /* END Core Styles */

  
  
  Kindest regards
  Lobos
  
  --
  -Lobos
  Professional PHP Framework Services: Concept, Development and Deployment

  • 
  •  
• **unknown user**
  
  

  • Rank: Helper
  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 676

  Posted: Aug 06, 2003 - 08:20 PM

  First of all, the above styles are only examples. There are no default styles defined in PostNuke, it's all set in the theme stylesheet.
  Also, some of the classes listed are not core classes, only used by certain modules or themes, like for instance PN-content-page-title
  
  And of course it's entirely optional to style HTML tags, so although common in themes, not necessarily essential in all instances. Plus, the definitions can be combined like so:
  

  Code

  BODY, FONT, SPAN, TD, P, INPUT, TEXTAREA, SELECT {
      FONT: normal 11px/120% Arial, Helvetica, sans-serif;
  }
  BODY {
      background: white;
      margin: 0px;
  }

  
  Here's a list of styles used in the modules with the "PN" prefix. Can't guarantee it's complete, in the case they've deviated from their naming convention of having that prefix. Haven't checked the current PN0.726 for changes in this respect:
  

  Code

  .pn-normal | Used extensively throughout, like in the main menu and 'comments?' link (annoying if you want menu and Comments link different)
  .pn-title  | Ditto
  .pn-sub    | Extensive, like 'Posted By'
  .pn-pagetitle (Modules: Recommend Us, Submit News, NS-User, NS-Settings, NS-Help, Messages, FAQ)
  .pn-text (Modules: NS-AddStory, NS-Languages, NS-Polls, Reviews, Sections, Submit News; error.php, .includes\blocks\menu.php, includes\blocks\sms.php, includes\blocks\thelang.php)
  .pn-logo (Downloads, NS-Polls, Web Links)
  .pn-logo-small (error.php, default Postnuke theme)
  .pn-titlel (Downloads module. Spelling mistake?)
  .pn-button (Always used with <INPUT class="pn-button"  Blocks: Poll, SMS, Login and Search commands)
  
  Seabreeze theme:
  .pn-title-rblock  
  .pn-title-lblock
  .pn-art

  But just because they've applied these classes, doesn't mean you have to style them, the body style (or browser default if no font styles are set anywhere) will be used. They are applied as a matter of convenience.
  
  
  But all that is a deviation from the central question: How to style block titles.
  
  Like Lobos said, wrap the block title, which is in the themesidebox function, in a class, and style it using the stylesheet.
  
  Look for

  Code

  function themesidebox()

  under which you should find somewhere

  Code

  echo $block['title']

  
  If it happens to be in a table cell of its own, you may add a class to the table cell:
  

  Code

  <td class=\"blocktitle\">$block['title']</td>

  
  Otherwise, wrap the array in a SPAN tag (for better or worse, FONT tags are being deprecated by the W3C, but will be around for a long time yet):
  

  Code

  echo "<SPAN class=\"blocktitle\">$block['title']</SPAN>\n";

  (here with a preceding "echo" statement. \n means New Line, Semicolons are instruction separators at the end of every PHP command)
  
  and, as Lobos said, add something like this to the style/styleNN.css stylesheet:
  

  Code

  .blocktitle {
      font-size: 120%;
      color: #4C5EA8; /* Title colour */
      text-align: center;
  }

  In this example, size is in percent, so it will always be relative to the body size, but you could make it 14px or something.
  
  Martin :D

  • 
  •  
• Lobos
  
  

  • Rank: Expert
  • Registered: Dec 02, 2002
  • Last visit: Apr 30, 2010
  • Posts: 1474

  Posted: Aug 06, 2003 - 10:11 PM

  I don't know about using percentage for font-size - mostly I have heard it is better to go with px - eg: font-size: 12px;
  
  I didn't mean to imply that the classes I had included were "core" postnuke styles - they are really core webvida styles - I use this as a template and have the comments so I can easily get rid of the classes applicable only to the last theme I was working on - why not keep it seperate and handy you might ask? Good question...
  
  <font class="wvMCblockTitle"> (don't you just love the simplicity of AutoTheme?)
  
  Kindest regards
  Lobos
  
  --
  -Lobos
  Professional PHP Framework Services: Concept, Development and Deployment

  • 
  •  
• **unknown user**
  
  

  • Rank: Helper
  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 676

  Posted: Aug 07, 2003 - 02:01 AM

  I was just trying to clarify the point to him, your answer was a little ambiguous, it's easy to forget these things are not obvious to people with little or no experience with PN, or aren't coders. And he might not know where and how to apply the classes, so was just trying to flesh it out a little more. Your point may have been lost in the long list of styles.
  
  Yes, I've dabbled a little in recent weeks with AutoTheme, it's more like what a theme system "for the masses" ought to be like. The PN developers seem to have forgot that in the past, that whereas burying HTML in PHP echo statements is fine for core modules, the themes are different. It's the front-end that the non-coding public knowing nothing of PHP, of IFs or echo statements, instruction separators, curly braces or escaping characters. How many, having some knowledge of HTML, have tried in vain to implement simple customisation only to flounder on PHP errors when they haven't escaped a double-quote or left out a semicolon? It's not conducive to creative design. To me coming from the visual and design angle, although understanding PHP, it seems fairly obvious. ColdRolledSteel's MTModular represent the opposite coder's idea of a theme, practical and logical, if you're up to playing with PHP code. Good luck customising it in a WYSIWYG HTML editor.
  
  I just had a look at the default Postnuke theme in the new PN 0.726, and was rather disappointed in finding that rather than being improved, or even staying the same, they've actually made the code more illegible. I thought at first it was a problem of Linux end-of-lines having been mistranslated by WinRAR, but evidence is to the contrary. They seem to have decided that it was more "efficient" to cut out any "unneccessary" white space, such as returns and indentations between lines, already having removed any "superfluous" explanatory comments, rather than looking at optimising the code itself. As it is, it's is riddled with outdated code, such as nested tables and spacer cells and images.
  It's supposed to be a showcase and example as to how to make a theme, but instead they have an exellent example of how not to code one! Even knowing HTML and PHP, I find this rather hard to decipher. For instance, check out line 111, which is virtually the whole of the themeindex function on one line!
  

  Code

  echo "<table width=\"100%\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n" . "<tr bgcolor=\"$GLOBALS[sepcolor]\">\n" . "<td><img src=\"themes/$GLOBALS[thename]/images/pix-t.gif\" width=\"1\" height=\"1\" alt=\"\" border=\"0\"></td>\n" . "</tr>\n" . "<tr>\n" . "<td>\n" . "<table border=\"0\" cellspacing=\"0\" cellpadding=\"3\" width=\"100%\" bgcolor=\"$GLOBALS[bgcolor4]\">\n" . "<tr>\n" . "<td width=\"100%\"><span class=\"pn-title\">$preformat[catandtitle]</span><br>\n" . "<span class=\"pn-sub\">" . _POSTEDBY . ": $info[informant] " . _ON . " $info[longdatetime]</span></td>\n" . "</tr>\n" . "</table>\n" . "</td>\n" . "</tr>\n" . "<tr style=\"bgcolor:$GLOBALS[sepcolor]\">\n" . "<td><img src=\"themes/$GLOBALS[thename]/images/pix-t.gif\" width=\"1\" height=\"1\" alt=\"\" border=\"0\"></td>\n" . "</tr>\n" . "<tr>\n" . "<td align=\"left\" valign=\"top\" class=\"pn-normal\">\n" . "$preformat[searchtopic]\n" . "$info[hometext]\n" . "<br><br>$preformat[notes]\n" . "</td>\n" . "</tr>\n" . "<tr bgcolor=\"$GLOBALS[sepcolor]\">\n" . "<td><img src=\"themes/$GLOBALS[thename]/images/pix-t.gif\" width=\"1\" height=\"1\" alt=\"\" border=\"0\"></td>\n" . "</tr>\n" . "<tr>\n" . "<td valign=\"middle\" align=\"right\" width=\"100%\">\n" . "<table width=\"100%\" border=\"0\" cellspacing=\"0\" cellpadding=\"3\" bgcolor=\"$GLOBALS[bgcolor4]\">\n" . "<tr>\n" . "<td width=\"20%\" valign=\"middle\" class=\"pn-sub\">($info[counter] " . _READS . ")</td>\n" . "<td align=\"right\" valign=\"middle\" width=\"80%\" class=\"pn-sub\">$preformat[more]</td>\n" . "</tr>\n" . "</table>\n" . "</td>\n" . "</tr>\n" . "<tr bgcolor=\"$GLOBALS[sepcolor]\">\n" . "<td><img src=\"themes/$GLOBALS[thename]/images/pix-t.gif\" width=\"1\" height=\"1\" alt=\"\" border=\"0\"></td>\n" . "</tr>\n" . "</table>\n" . "<br>\n";

  
  So if I have trouble deciphering this code soup, how the hell is a PN newbie with zero PHP skill supposed to cope? It saves a massive 2kb in the themefile, but zero in the rendered code! Maybe they could have saved another one or two kb of server space by altogether not using the now superfluous concatenation operator!
  I may have been able to believe it was a mishap if all returns and tabs were consistently mangled throughout, but it's not. Regular PHP statements are OK and indented! It's only the portions that users may wish to customise, the embedded HTML, which is rendered so. Specifically, echo statements with concatenation operators ('.').
  And this in the release before PN 0.8, which implements Xanthia as a theme engine? It's not boding well for the state of the HTML code in the included themes, I fear.
  
  I'll have a go at optimising it better soon - with superfluous indentations for formatting in plain HTML, not embedded, using DIVs and CSS as far as practicable. It's an ideal theme for a CSS makeover, as there are no images and has a lot of rules separating areas of flat colour.
  
  Sorry for getting off-topic, just had to get it out of my system :)
  
  Greetings,
  Martin :D

  • 
  •  
• Lobos
  
  

  • Rank: Expert
  • Registered: Dec 02, 2002
  • Last visit: Apr 30, 2010
  • Posts: 1474

  Posted: Aug 07, 2003 - 07:15 PM

  Oh my god, will you look at that... I would like to re code/ design the core themes, but it's no use because they wouldn't be added anyway and the new system will be out soon. I think it's time for a new bundle of core themes anyway, the originals are getting a bit "crusty" looking.
  
  I think the main thing to work to is seperation of PHP and HTML along with w3c transitional compliance - I have just coded my new template into AutoTheme and it was perfectly complient until the modules and blocks were included - then all hell broke loose.
  
  I used Xanthia for a while and while it does seperate PHP and HTML it does not let you code PHP into the templates - you have to create new functions in a couple of other files - I don't know whether this will change or not, but it is essential to me, I also had trouble using dreamweaver with the .tpl files because it didn't highlite the code properly. AutoTheme is a much better system and for me to use the new Xanthia it will have to be a hell of a lot different to the old one...
  
  Kindest regards
  Lobos
  
  --
  -Lobos
  Professional PHP Framework Services: Concept, Development and Deployment

  • 
  •  
• **unknown user**
  
  

  • Rank: Helper
  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 676

  Posted: Aug 08, 2003 - 02:15 AM

  Xaraya has the same problem of not allowing PHP, and needing a fix to allow Dreamweaver to recognise template files like HTML files, so you can view them and have code colouring. I should imagine it's the same with Xanthia, haven't actually seen it yet. But when Xanthia developers here in the forums advise people to use AutoTheme for the time being, admitting there are performance issues, though improving, is a worry.
  
  Since AutoTheme is also out on PHP-Nuke, does that mean the theme.html files work on PHP-Nuke as well? There must be some unique features of each that can't be reproduced, though...
  
  My recoded version of PostNukeBlue is in the footer of my post. A few subtle modifications, but notably it's 100% width. I noticed a thread on the pnDev mailing list before the release of PN 0.726 about whether it should be updated to full width, to which most were in favour, but LarsNeo (I believe) was against it, and as project head, his word goes. Why you'd keep a fixed-width theme around when there's no design reason for it is beyond me.
  
  Martin :D

  • 
  •  
• markwest
  
  

  • Rank: Team Member
  • Registered: Mar 18, 2002
  • Last visit: Oct 21, 2009
  • Posts: 6606

  Posted: Aug 08, 2003 - 02:36 AM

  Martin
  
  Not sure how that screw up with the themes happend. Definately unintentional. I wish someone had pointed it out during the RC stage so it could have been sorted properly.
  
  With regard to Xanthia and it's developers recommeding AutoTheme if you mean Greg (MediaTech) then he's not involved with Xanthia anymore. I don't think either Larry (phpnut) or Brook (webmedic) would be recommending this.
  
  If anyone wants to help the team on theming, CSS, design issues then give us a shout. I certainly am not very capable in this area.
  
  -Mark
  
  --
  Visit My homepage and Zikula themes.

  • 
  •  
• Lobos
  
  

  • Rank: Expert
  • Registered: Dec 02, 2002
  • Last visit: Apr 30, 2010
  • Posts: 1474

  Posted: Aug 08, 2003 - 02:41 AM

  Apperently Shawn is going to make AutoTheme across the board compatible with PN, phpNuke, envolution and a few others. This is great because you build one theme and you can distribute it to several CMS's - I can't wait *rubbing hands together*.
  
  I think people are suffering from a bit of nostalga concerning the core themes...
  
  --
  -Lobos
  Professional PHP Framework Services: Concept, Development and Deployment

  • 
  •  
• AbraCadaver
  
  

  • Rank: Expert
  • Registered: Aug 20, 2002
  • Last visit: Jan 12, 2010
  • Posts: 1219

  Posted: Aug 08, 2003 - 04:31 AM

  Lobos

  Apperently Shawn is going to make AutoTheme across the board compatible with PN, phpNuke, envolution and a few others. This is great because you build one theme and you can distribute it to several CMS's - I can't wait *rubbing hands together*.
  
  I think people are suffering from a bit of nostalga concerning the core themes...

  
  
  Yes, should be out this weekend (?) or shortly after. Compatibilty libraries built-in for PN, PHP-Nuke, eNvo. Plus some suprises that just popped out of my fingers while coding!
  
  I considered Xaraya (which still may happen) but the file naming is much different and it doesn't recognize my "legacy" module file naming, plus I haven't used or coded for Xaraya.
  
  Thanks!
  Shawn
  
  --
  Get the Revolutionary AutoTheme HTML Theme System! Currently for Zikula, PHP-Nuke, CRE Loaded, osCommerce and Wordpress!

  • 
  •  
• Lobos
  
  

  • Rank: Expert
  • Registered: Dec 02, 2002
  • Last visit: Apr 30, 2010
  • Posts: 1474

  Posted: Aug 08, 2003 - 09:21 AM

  LOL. And you say thanks! It is I who is thankful...
  
  Best of luck with your coding this weekend!!!
  
  Kindest regards
  Lobos
  
  --
  -Lobos
  Professional PHP Framework Services: Concept, Development and Deployment

  • 
  •  
• **unknown user**
  

  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 124

  Posted: Aug 08, 2003 - 01:30 PM

  Lobos

  
  I used Xanthia for a while and while it does seperate PHP and HTML it does not let you code PHP into the templates - you have to create new functions in a couple of other files - I don't know whether this will change or not, but it is essential to me, I also had trouble using dreamweaver with the .tpl files because it didn't highlite the code properly. AutoTheme is a much better system and for me to use the new Xanthia it will have to be a hell of a lot different to the old one...
  

  
  
  Xanthia has always allowed PHP in the templates if the designer wanted to use it. Old version of Xanthia would use
  
  

  Code

  [-php-]
  all php code
  [-/php-]

  
  
  New version allows it like this.
  
  

  Code

  <!--[php]-->
  all php code
  <!--[/php]-->

  
  
  And the .tpl extension would work with Xanthia or you could use the .htm extension either one the system would see them both J next version only allows .htm though.
  
  As for the look, and features of the New Xanthia contact me in private and I can show you what is in store. Release on 726 is delayed a little while we work on a few things with rendering of .8 modules. When Xanthia is released on 726 you will be able to start coding modules on the .8 code that will work in 726 installs as long as Xanthia in installed on the system. It will not have to be used, just installed.
  
  Larry E. Masters
  Xanthia Developer
  PostNuke Development Team

  • 
  •  
• **unknown user**
  

  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 124

  Posted: Aug 08, 2003 - 01:39 PM

  msandersen

  ...But when Xanthia developers here in the forums advise people to use AutoTheme for the time being, admitting there are performance issues, though improving, is a worry.
  

  
  
  Until Xanthia was included with the PostNuke core Xanthia was only being developed by me. And even now their is only one other person, Brook aka webmedic, who is doing any of the coding of Xanthia.
  
  The person you may be referring to was not a developer of Xanthia, just a user who had input on the features a long time ago :) Things have changed a lot since then.
  
  Contact me in private
  ICQ 533133
  or nut _ at _ phpnut.com
  
  I will show you what Xanthia will do now.
  
  Larry E. Masters
  Xanthia Developer
  PostNuke Development Team

  • 
  •  
•  
•  

Users on-line

• craigh

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