XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Themes and Templates Support forums / 
  3. Theme design questions 
  4.  / define Standard Templates for theme developers - your idea
Register
21
BlueStocking
Re: define Standard Templates for theme developers - your idea

Quote:

Question: Who exactly is the "Design Team" we're hearing so much about? ...Sublime

Answer: This team will be completely functional this weekend, therefore if you are interested ... Kris_fr


DesignTeam
Aph3x, Moffawak, Pilou, Wishcraft, Ianez, Voltan, and Kris_fr Team Leader

@Kris_fr Thank you for the members list,
hhttps://xoops.org/modules/repository .. It is time to get involved - XOOPS.ORG
22
damaster
Re: define Standard Templates for theme developers - your idea

  • 2008/1/28 21:25

  • damaster

  • Just can't stay away

  • Posts: 556

  • Since: 2003/5/11


@Sublime wrote:
Quote:
The contest...is bull#OOPS#. I may as well screenshot my new theme and give that to kris and let him code it considering it would be all his code if i did it anyway.


This one was really the easiest and sublime way!


Seriously, I was expecting some more competition and fun!
I'm sure there's a good will but also a misunderstood about
User Interface and a lack of user experience studies.
Maybe the subject is confusing.
Web Standards already exist.
Templates are end-user freedom.

Maybe you should define "design" and "development" and create
a new topic "How to bridge the gap between design and development?"

Code and design have been separate environments, and the requirement
to switch between these environments has hindered developers.

Also, morpho seems to be old and to limit designers creativity as an
heavy and complex framework full of useless stuff.
That's why I never use it alike others out of contest!
I like people more than machines or money. But that's me!
Lets do something good and great: Lets do open source!
23
domecc
Re: define Standard Templates for theme developers - your idea

  • 2008/1/29 3:46

  • domecc

  • Just popping in

  • Posts: 71

  • Since: 2005/10/30


Need a language folder for theme, such as:

\htdocs\themes\default\language\english\theme.php
\htdocs\themes\default\language\schinese\theme.php
\htdocs\themes\default\language\schinese_utf8\theme.php

or

\htdocs\themes\default\language\english.php
\htdocs\themes\default\language\schinese.php
\htdocs\themes\default\language\schinese_utf8.php
XoopsChina Webmaster
24
Sublime
Re: define Standard Templates for theme developers - your idea

  • 2008/1/29 15:23

  • Sublime

  • Just popping in

  • Posts: 99

  • Since: 2006/5/23


Quote:
If you want to make party of the Design Team, you can make a candidature near the XOOPS council or of myself.

No, I think it would be a bit hypocritical of me to join a team that forces ideas I completely disagree with. I was just wondering who exactly it was, thanks for the list.
25
irmtfan
Re: define Standard Templates for theme developers - your idea

  • 2008/1/29 15:48

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


i said we should discuss in details
for example:
- all theme developers should use .footer in the css file ( of course many developers do it but they dont aware of it)

- all developers use .mainmenu and .usermenu because XOOPS Core use them in system module. so XOOPS Core force theme developers to put this codes in the css.

so why not extend it to more parts of theme? why not split theme.html to some more html files and force every developers to follow it. then every body can understand themes.
i think what kris trying to do is this kind of standard codes.
sorry i can not talk about kris templates because im not a theme developer and i dont read them. but if it stabilize as the standrad template for XOOPS even a non developer like me has to learn it.
26
Sublime
Re: define Standard Templates for theme developers - your idea

  • 2008/1/29 16:00

  • Sublime

  • Just popping in

  • Posts: 99

  • Since: 2006/5/23


Quote:
why not split theme.html to some more html files and force every developers to follow it. then every body can understand themes.


Again, it's not my job or any other themer's job to teach your new designers...WRITE DOCUMENTATION...theres your solution. Not "hey guys lets make EVERY THEME a tutorial for new users"...come on, are you serious? I couldn't care less if people "understand" my code, I shouldnt have to care, I'm theming, not writing a tutorial. However, header.html, and footer.html would make sense; i've actually been doing that in my new (unreleased) themes anyway. You can break your themes down as much as you want, that's not the point, the point is you shouldn't force people to do it just so all themes can be tutorials...the only reason to do what is being done is to avoid making theme documentation.

Quote:

- all developers use .mainmenu and .usermenu because XOOPS Core use them in system module. so XOOPS Core force theme developers to put this codes in the css.

i think what kris trying to do is this kind of standard codes.

Yes, but if you try and standardize _all_ of the code all your doing is making different flavors of the same theme. Bad code is trying to be standardized...that's why I have a problem with it. "More code" does not equal "better code" it just equals more hassle for designers....There's so many better ways to do what kris is trying to do that don't require everyone and their brother theming with his code and his code alone. One better way being USE WRAPPERS which I have repeated over and over again.
27
Burning
Re: define Standard Templates for theme developers - your idea

  • 2008/1/29 16:27

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


hi,

I give you just an example

If I want to have the same looking (just for buttons) at this page (mydownloads_ratefile.html template)

... I have to fill 3 class :
Resized Image


May be I'am wrong, the good solution should be a modification of all templates (mydownloads, mylinks, news...) and an only class for buttons ?

For me (and as long as templates are not "uniforms" ), I use this kind of declaration (that already exist in morphogenesis) :

Quote:
input[type=submit], input[type=reset], .formButton, input[type=button] {
font-family:Verdana, sans-serif;
font-weight: normal;
font-variant: small-caps;
color: #FFFFFF;
background-color: #639ace;
border: 1px solid #e8e8e8;
background-image: url(../img/bg-degrad-blue.gif);
...
}


(just a feed back of a end-user)

@+
Still learning CSS and... english
28
Sublime
Re: define Standard Templates for theme developers - your idea

  • 2008/1/29 16:47

  • Sublime

  • Just popping in

  • Posts: 99

  • Since: 2006/5/23


Quote:
(that already exist in morphogenesis)


^^ that would be unneeded if modules were templated uniformly.
29
Burning
Re: define Standard Templates for theme developers - your idea

  • 2008/1/29 17:04

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


100% agree !

But this is a hard work to template all this modules ! And I guess there will be a lot of problems :
- module developpers will be agree with new rules ?
- design team have the right to force them ?
- is there some good volunteers to template old modules (like mylinks, ...) ?

A documentation for module developpers already exist (class to use, etc...) ??
Still learning CSS and... english
30
hervet
Re: define Standard Templates for theme developers - your idea

  • 2008/1/29 17:45

  • hervet

  • Friend of XOOPS

  • Posts: 2267

  • Since: 2003/11/4


You are mixing themes and templates !
And that's not the same.
« 1 2 (3) 4 5 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

391 user(s) are online (235 user(s) are browsing Support Forums)

Members: 0

Guests: 391

more...

Donat-O-Meter

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

Latest GitHub Commits