51
aph3x
Re: New Default Theme for XOOPS 2.5
  • 2010/2/2 4:19

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


@insraq No one should start coding from a blank canvas hence the framework discussion :) cause its sort of reinventing the wheel over and over and is time consuming. But the framework trick is to serve as example to follow not example to copy and yeah its a very thin line.

About your idea yeah that's the most reasonable and pertinent suggestion about morpho yet , and to make it even more interesting and newbie friendly have few extra things like this:

Things to put in HTML:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<
html xmlns="http://www.w3.org/1999/xhtml" xml:lang="<{$xoops_langcode}>" lang="<{$xoops_langcode}>">
<
head>
<
meta http-equiv="content-type" content="text/html; charset=<{$xoops_charset}>" />
<
meta http-equiv="content-language" content="<{$xoops_langcode}>" />
<
meta name="robots" content="<{$xoops_meta_robots}>" />
<
meta name="keywords" content="<{$xoops_meta_keywords}>" />
<
meta name="description" content="<{$xoops_meta_description}>" />
<
meta name="rating" content="<{$xoops_meta_rating}>" />
<
meta name="author" content="<{$xoops_meta_author}>" />
<
meta name="copyright" content="<{$xoops_meta_copyright}>" />
<
meta name="generator" content="XOOPS" />
<
title><{$xoops_sitename}> - <{$xoops_pagetitle}></title>
<
link href="<{$xoops_url}>/favicon.ico" rel="SHORTCUT ICON" />
<
link rel="stylesheet" type="text/css" media="screen" href="<{$xoops_url}>/xoops.css" />
<
link rel="stylesheet" type="text/css" media="screen" href="<{$xoops_themecss}>" />
<{
$xoops_module_header}>
</
head>
<
body>
<!-- 
## START OF LEFT ## -->
<{foreach item=block from=$xoops_lblocks}>
<{
$block.title}>
<{
$block.content}>
<{/foreach}>
<!-- 
## END OF LEFT ## -->


<!-- ## START OF CENTER ## -->
<{foreach item=block from=$xoops_ccblocks}>
<{
$block.title}>
<{
$block.content}>
<{/foreach}>
<!-- 
## END OF CENTER ## -->

<!-- ## START OF CENTER LEFT ## -->
<{foreach item=block from=$xoops_clblocks}>
<{
$block.title}>
<{
$block.content}>
<{/foreach}>
<!-- 
## END OF CENTER LEFT ## -->


<!-- ## START OF CENTER RIGHT ## -->
<{foreach item=block from=$xoops_crblocks}>
<{
$block.title}>
<{
$block.content}>
<{/foreach}>
<!-- 
## END OF CENTER RIGHT ## -->


<!-- ## START OF CONTENT PAGES ## -->

          
<{$xoops_contents}>

<!-- 
## END OF CONTENT PAGES ## -->

<!-- ## START OF BOTTOM CENTER ## -->
<{foreach item=block from=$xoBlocks.page_bottomcenter}>
<{
$block.title}>
<{
$block.content}>
<{/foreach}>
<!-- 
## END OF BOTTOM CENTER ## -->

<!-- ## START OF BOTTOM CENTER LEFT ## -->
<{foreach item=block from=$xoBlocks.page_bottomleft}>
<{
$block.title}>
<{
$block.content}>
<{/foreach}>
<!-- 
## END OF BOTTOM CENTER LEFT ## -->

<!-- ## START OF BOTTOM CENTER RIGHT ## -->
<{foreach item=block from=$xoBlocks.page_bottomright}>
<{
$block.title}>
<{
$block.content}>
<{/foreach}>
<!-- 
## END OF BOTTOM CENTER RIGHT ## -->

<!-- ## START OF RIGHT ## -->
<{foreach item=block from=$xoops_rblocks}>
<{
$block.title}>
<{
$block.content}>
<{/foreach}>
<!-- 
## END OF RIGHT ## -->

<!-- ## START OF FOOTER ## -->
<{$xoops_footer}>
<!-- 
## END OF FOOTER ## -->

</body>
</
html>


With variations of this .. like the xo things i'll never use unless the ones i'm using will become obsolete. And with explanations of each one listed
xoops_footer prints the footer you set in admin, uname prints username and so on.

Then the css core stuff

#mainmenu {font-size: 12px}
#mainmenu a { display: block; margin: 0; padding: 4px;outline : none;}
#mainmenu a:hover {}
#mainmenu a.menuTop {padding-left: 3px; }
#mainmenu a.menuMain {padding-left: 3px;}
#mainmenu a.menuSub {padding-left: 9px;}

#usermenu {font-size: 12px}
#usermenu a {display: block; margin: 0; padding: 4px;outline : none;}
#usermenu a:hover {}
#usermenu a.menuTop {}
#usermenu a.highlight {}

.item {font-size14px;}
.
itemHead {padding3pxbackground-color#212121; color: #373737;font-size: 12px}
.itemInfo {text-alignrightpadding3px;}
.
itemTitle a {font-size20pxfont-weightboldfont-variantsmall-capscolor#ffffff; background-color: transparent;}
.itemPoster {font-size90%; font-style:italic;}
.
itemPostDate {font-size90%; font-style:italic;}
.
itemStats {font-size90%; font-style:italic;}
.
itemBody {padding-left5px;}
.
itemText {margin-top5pxmargin-bottom5pxline-height1.5em;font-size12px;}
.
itemFoot {text-alignrightpadding3px;}
.
itemAdminLink {font-size90%;}
.
itemPermaLink {font-size90%;}

table {width100%;}

th {background-color#ddd;height: 25px; padding: 5px;font-size: 14px;color: #454444}

table td {padding0border-width0vertical-aligntop; }
div.xoopsCode width:680px;background#e3e9ef; border: 1px inset #000080; font-family: "Courier New",Courier,monospace; padding: 0px 6px 6px 6px;}
div.xoopsQuote width:680px;background#e3e9ef; border: 1px inset #000080; font-family: "Courier New",Courier,monospace; padding: 0px 6px 6px 6px;}

.outer {border1px solid #d2d2d2;}
.head {background-color#ddd; padding: 5px; font-weight: bold;color: #fff}
.even {background:silverpadding5px;color#fff}
.even a {color#545454;line-height: 180%}
.odd {background#737474;padding: 5px;color: #fff}
.odd a{color#fff}
.odd a:hover{colorsilver}
.
foot {background-color#e3e9ef; padding: 5px; font-weight: bold;}
tr.even td {background-color#b8b9b9; padding: 5px;}
tr.odd td {background-color#979797; padding: 5px;}


Again with little explanations here and there so a newbie won't have to start from scratch and won't have to waste time asking in forums how to display this and that in the theme and they will have more time available to actually build something.

Now unless i left out something from css then both from above makes you a skeleton XOOPS theme where one can add its truly creativity and that's as basic as you can get...one html file and one css file ;)



52
aph3x
Re: New Default Theme for XOOPS 2.5
  • 2010/2/1 22:23

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


Wait i didn't say i support morpho as being default :)

And you did prove at least one of my points..each one works with whatever makes him/her excel and in your case is morpho ;)

I use something else much much simpler than that and it takes me 10minutes to convert a theme from html or any cms to xoops, so that's my way of working.

One that starts to make themes for XOOPS shouldn't go blind into it and say hey if morpho is pushed then this is the correct/only way cause is not and if you have trouble using a tool then you should change it cause its wasting your potential

Requests is an issue and framework is um i don't know?OLD?!..skalpa left around 2years ago? and he was working on umm xoopsphere whatever with at least 6months before he left? while data stuff is always in the move (while i'm releasing this week my 3rd HTML5 theme, but thats for another topic).

And bringing snow77 again proves my point all her themes look and follow the same pattern...If you would've said Bassman would've been a whole different story cause each theme that guy released was unique from header to footer and the way he incorporated the graphic stuff its what made me wanna learn themes.

Leaving that aside i learned to make themes from a theme snow77 did..BEFORE the morpho era

Regardless the cache you sitting at the computer wait for the browser to request the file, get the file, render the file (there's more but i listed the most important) and that happens for everything outside the main requested file which is the "theme.html"



53
aph3x
Re: New Default Theme for XOOPS 2.5
  • 2010/2/1 21:24

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


With the risk of being chastised ...not that i'm not used to it

morpho is JUST a theme is NOT a framework, that being said.. all themes are frameworks and no themes are framework.

Each dev should develop on whatever makes him/her comfortable with keeping in mind the productivity time

Altho a Framework shouldn't be pushed is advised to be available for occasional consulting.

A true framework is a skeleton and its purpose is only to offer a Frame(work) of designer's pieces...if you ever took a Rubik cube appart then you know what i mean.

About the endless number of files in a theme that is supposed to be standard...that is not the way

A theme should have a minimum number of requests as possible to try and compensate the number of requests a CMS has.
No more then 1style, no more then theme.html file. If you comment the documents where an area starts and where it ends then newbies shouldn't have any problem.

Most that come to a CMS have a minimum understanding of at least one area :server stuff, html, php, basic UI admin settings knowledge.

Now, how many requests a theme like that has? let me count.. 10 that is absurd and thats only for HTML files..there extra 7 css requests...nevermind the images i'm way to scared to count

Now me as a newbie looking at 17 files i gotta modify ..i simply get goosebumps.

Theme should be theme.html + style.css + whatever scripts you have included in it...minified if possible

Theme should use css sprites where appropriate to also have a minimum number of requests of images.

Framework again...because Kris pushes morpho as one, all you devs using it are missing the point and the point is that he took the time to put all the "shortcuts" via smarty in it so you can see and use them wisely by creating orginal stuff and not take them ad litteram ending up in +1k themes looking about the same with user menu in the same place for ALL and login box in the same place for ALL..where's your creativity?

Morpho merely shows you an example how to add stuff in the theme that doesn't mean that if you change the bg, the color of body, the image of header you have a new theme, NO but it means you made a new skin for morpho

I'll stop here, but there are many many other guiding umm stuff to make a cms bit faster bit less bloated with unnecessary files. And they are guiding things not rules but they fall under common sense. Is not the large amount of files in a theme that makes it great..its the less amount of files that makes it




54
aph3x
Re: theme APH002
  • 2010/1/31 20:11

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


my pleasure :)

Most things are more simple then they look and that applies to overall XOOPS stuff.
B'sides my site support forums are almost empty and you can't find real issues posted about themes i make either here or anywhere else cause they just work



55
aph3x
Re: theme APH002
  • 2010/1/31 19:49

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


You don't have to do anything...altho the theme has 3 columns, the right column is not visible if no blocks are set to appear there.
Classes of center elements change to suit your column selection so if you have blocks only on left and center then center is bit bigger to fill the space and of right column. If you have blocks on both left and right column then the center will be smaller to fit in between

style.css if right column: center top/center bottom blocks width: 550px

style.css if no right column: center top/center bottom blocks width: 730px

same for the center-l, center-r, bottom-l, bottom-r they increase/decrease width to fit the theme.

So if you modified the theme files...you really didn't have to :)




56
aph3x
Re: theme APH002
  • 2010/1/31 16:13

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


The short version:

you can't

The long version:

You will have to rethink the theme and putting aside the fact the 100% aren't used anymore as they used to because they aren't practical as despite the fact that might sound as "unlimited width" is the most limited when it comes to customization for your visitors..picture you spend half a day making your site look good on your screen.. do you think it will have same visual impact on people using larger resolutions, or smaller?
However you will need to use a different method of slicing the PSD and again a different method to recode the body and the center area of blocks(center, center-right, center-left..and same for bottom)



57
aph3x
Re: Theme problem when upgrade to 2.4.4
  • 2010/1/27 19:18

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


Resized Image


And here's my screenshot



58
aph3x
Re: Theme problem when upgrade to 2.4.4
  • 2010/1/27 19:14

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


I see what you mean, i just checked a zetagenesis "out of the box" version in firebug and all seems fine from my end and it is an upgraded version of system for many times since the 2.0.14 up till current version so umm i'd say at least 3 upgrades



59
aph3x
Re: Theme problem when upgrade to 2.4.4
  • 2010/1/27 17:55

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


If you can provide us with a link and even some screenshots of your code outputs it will be great



60
aph3x
Re: Theme problem when upgrade to 2.4.4
  • 2010/1/27 17:30

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


Let me see if i get this right...before upgrade, all meta, scripts and stuff were correctly in the head area...after the upgrade they were somehow moved into the body area?!

Its unlikely for that to happen because when you upgrade XOOPS (And any cms for that matter), it doesn't affects how your theme is coded unless its/or has same name with one of the default themes contained by the package so if your theme was a 3rd party one and NOT one distributed with the core, the upgrade process doesn't replaces files in your theme.

Long story short..unless its a default theme included in the upgrade package and files were rewritten on upgrade then it can't happen




TopTop
« 1 ... 3 4 5 (6) 7 8 9 ... 38 »



Login

Who's Online

179 user(s) are online (121 user(s) are browsing Support Forums)


Members: 0


Guests: 179


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Mar 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits