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"

interesting discussion...I think it will be great if morph is packed into the default archive...for experienced designer, they can always start with a blank html/css anyway...

@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:



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



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 ;)

@aph3x:

You provide a very good framework example. Morpho may be more like a multi-functional theme, but it is a good learning material. If I write my own theme, I would prefer to use your code as it is simple and primitive. I can visualize my idea on that. However, your framework might not be very appropriate to be packed into the default archive as themes, as it might be misleading for newbies. Perhaps If the default archive can set up a separate folder called "resources", your framework should definitely go in there.

P.S. Those xo_ stuff is said to be a better way, although it confuse me sometimes.

hello all,
I think with XOOPS 2.5 the current design is no longer suits it. We need a design that reflects the capacity of the new version.
So let us discuss the design specifications and keeping in mind several facts:
- Easy to edit (like default theme)
- Well organized (like morpho)
- To minimize the files Style and maintain a single file if possible
- Add jquery and mototools files if possible.

I agree with aph3x that none will code from zero , and I think the best way is to merge between default and morpho to code one theme that can be used as default one and every designer feel free to use his own methode to add or to edit

Morphogenesis is great, but it's like they say about Elastic for WordPress: it's too heavy for a default theme.

Look at Kubrick for WordPress: it was revolutionary, but it has grown old. But that's a design anyone can use - Morphogenesis is great, but I see it a bit as "too grayish" and the default theme still makes me think from 2.0.13.1's default theme with another header. We got to get something refreshing, new and something that anyone can use.

And we'll need to use jquery - maybe even a cool pop-down login box?
And well... I think we can do like we did for the new XOOPS.org theme.. hold a contest ;D

And that xo-stuff... I can't understand ????? from it. How many of those are there that you can use XD? It's very unclear... and Aphex, your themes are understandable :p

The xo- namespace will be dropped off in X3

Well, that's good news Phppp ^^

Now, any news about theming in XOOPS 3?

Topic bump...any design from insraq/krisfr will be nice to be made as default theme for xoops 2.5

very bad ...