31
damaster
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/12 11:04

  • damaster

  • Just can't stay away

  • Posts: 556

  • Since: 2003/5/11




wanikoo, Quote:

P.S.My grandfather died a few days ago. so...
I'm so depressed now.



He would be proud of you, as some of us, for sure...
I still having my grand-father who teach me so much about life and sometimes i ask my self why ... why to spend such time here, better would be, with him...

shine, Quote:

I understand your hesitation about becoming one of the core developpers. But, looking at your input..... how about the suggestion Herko made at you Wanikoo?
Quote:

Quote:
I suggest Wanikoo joins as a virtual member so we can examine his team player qualities as well as his programming skills



I think this would be a nice 'in between step' for you! Sometimes people underestimate their own skills and experiences. By becoming a virtual coremember the devteam can examine your skills, experiences and teamplay. By following this roadmap you continue your personal development also


That also supposes certain people have some specific skills and especially a wise human experience!

Don't misunderstood me... somebody said, through an ergonomicist point of view, it seems some people working or managing with machines end up thinking and acting as machines themselves, forgetting the human one and his real needs.
Wanikoo give us his time and knowledge for free! What else can we see here?

Machine Skills vs Humain Skills !?

He don't need to be part of them, already being part of XOOPS community, he's free.

Wanikoo acts in the noblest way.
Thank you to give us the example.

Here your action has more value for all XOOPS users.
As your knowledge it's not lost and benefits all.

Thank you!

I like people more than machines or money. But that's me!
Lets do something good and great: Lets do open source!

32
giba
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/12 11:32

  • giba

  • Just can't stay away

  • Posts: 638

  • Since: 2003/4/26


Quote:

wanikoo wrote:
but...my answer is "NO...more exactly NOT YET"
because I don't have enough skill and experience yet.
but
I will continue to develop myself more and more....for D-day(--;;)

Umm..
Anyway..
It's off the topic^^;;


@off topic for my friend wanikoo

Sorry, in portuguese.

Eu compreendo você.
For?a, esperan?a, vá em frente, ele se foi mas com certeza deve ter deixado uma história de vida belissima.
História esta que estamos vendo você escrever aqui.
O XOOPS será diferente do que é hoje na parte de valida??es de xhtml e provavelmente de RSS também e você terá participado desta mudan?a pessoalmente.
Alguns n?o gostam de mim por falar o que penso realmente, mas isto é verdade e as mudan?as est?o ai.
Continue, for?a, obrigado Amigo


by google translation.

I understand you.
Force, hope, it goes in front, was itself but with certainty belissima must have left a life history.
History this that we are seeing you to write here.

The XOOPS will be different of that it is today in the part of validations of xhtml and probably of RSS also and you it will have participated of this change personally.

Some do not like me for speaking what I really think, but that is truth and the changes are ai.

It continues, force, debtor Friend: -)


Ps: @Saloma ai no Brasil, se a tradu??o estiver muito errado, da uma for?a ai para o véio aqui

33
Herko
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/12 13:10

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


Quote:
Damaster wrote:
Wanikoo give us his time and knowledge for free! What else can we see here?

Machine Skills vs Humain Skills !?

He don't need to be part of them, already being part of XOOPS community, he's free.

Wanikoo acts in the noblest way.

Don't we all do everything for free, for the benefit of everyone, in our own free time? I don't see the need, and I think Wanikoo agrees with me on this, to put Wanikoo on a pedestal any more then he is now. Everyone appreciates his work and the effort he puts into this (my granddad died 2 weeks ago too), but we appreciate all contributions, large or small. So lets keep this realistic

Herko

34
damaster
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/12 13:33

  • damaster

  • Just can't stay away

  • Posts: 556

  • Since: 2003/5/11


@Herko

As i mention above, Don't misunderstood me... , being fair, that's all!

I'm sorry for your grand-father and sorry for you Herko.


You're young, ambitious, you don't have reasons to be jealous, you have an opportinity, since you had 'took' the XOOPS Project, to show your competences. And "keep this realist" does it means less humain ?

I know, you're the Head.
And it's obvious that you consider history, utopia, hope, and wise leaders to have people following "some idea" of what it should be, don't you!?

I like people more than machines or money !
But that's me, Herko.



Any way, good work All XOOPS users !
I like people more than machines or money. But that's me!
Lets do something good and great: Lets do open source!

35
Herko
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/12 14:10

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


Quote:

Damaster wrote:
@Herko

As i mention above, Don't misunderstood me... , being fair, that's all!

I know I wanted to explain my motivations, not attack yours. If I did, I'm deeply sorry

Quote:

I'm sorry for your grand-father and sorry for you Herko.


You're young, ambitious, you don't have reasons to be jealous, you have an opportinity, since you had 'took' the XOOPS Project, to show your competences. And "keep this realist" does it means less humain ?

He died old and peacefully, surrounded by those he loved. What more could one want?

I'm not jealous. I'm not even a member of the Core Development Team. In fact, I'd love to have a larger group of core developers working on creating the next step in XOOPS evolution. And Wanikoo is a part of that already, by his contributions here. Wanikoo's skills and expertise are being monitored, and if they match the (highest) standards (for the core this is VERY important), he is more then welcome to join that team. In the meantime, his contributions are focussed on improving the core, and we take those seriously, making him a virtual member of the core devedlopment team.

Quote:

I know, you're the Head.
And it's obvious that you consider history, utopia, hope, and wise leaders to have people following "some idea" of what it should be, don't you!?

I like people more than machines or money !
But that's me, Herko.



Any way, good work All XOOPS users !

I like people more then machines too. I listen to a lot of signals from inside and outside this community. XOOPS has to set the bar high, set some provocative standards to claim it's place in the world of CMS's. That is the future I see for XOOPS. For it to grow and become an example that inspires others to grow into what they can become. To provide the tools and inspiration for that. Being realistic in this means that we need to allow people to grow to higher levels of sophistication, adding their own flavor to the project and the products. That starts, not ends with what Wanikoo is doing

So, in short, I think we agree on this, we both want to give Wanikoo a chance to add his flavor to XOOPS. Lets just give him a chance to grow

Herko

36
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/12 14:45

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


Quote:

I mentioned like this:
-----------------------------------
pages with form class (ex: edituser.php)
--------------------------------


or

or

or


This kind of coding above always give us some error message like this....

document type does not allow element "input" here

Refer to this page
http://www.w3.org/TR/2002/REC-xhtml1-20020801/DTD/xhtml1-transitional.dtd

So..
If we use form classes such as XoopsTableForm(tableform.php), XoopsThemeForm(themeform.php) with XoopsFormHidden(formhidden.php),
we can never get the message," "This Page Is Valid XHTML 1.0 Transitional!" from W3 validator.

Umm...
I think there are some solutions for this problem..


fixed in XOOPS 2.1.0 dev like this.

tableform.php
$hidden "";
        
$ret $this->getTitle()."n.$this->getName()."' id='".$this->getName()."' action='".$this->getAction()."' method='".$this->getMethod()."'".$this->getExtra().">nn";
        foreach ( 
$this->getElements() as $ele ) {
            if ( !
$ele->isHidden() ) {
                
$ret .= "".$ele->getCaption();
                if (
$ele->getDescription() != '') {
                    
$ret .= ''.$ele->getDescription().''
;
                }
                
$ret .= "".$ele->render()."";
            } else {
                
$hidden .= $ele->render()."n";
            }
        }
        
$ret .= "".$hidden."nn";

themeform.php
$hidden "";
        
$required =& $this->getRequired();
        
$ret ".$this->getName()."' id='".$this->getName()."' action='".$this->getAction()."' method='".$this->getMethod()."' onsubmit='return xoopsFormValidate_".$this->getName()."();'".$this->getExtra().">n".$this->getTitle()."";
        
//$count = 0;
        
foreach ( $this->getElements() as $ele ) {
            if (!
is_object($ele)) {
                
$ret .= $ele;
            } elseif (!
$ele->isHidden()) {
                
//if ($count % 2 == 0) {
                    
$class 'even';
                
//} else {
                //    $class = 'odd';
                //}
                
$ret .= "".$ele->getCaption();
                if (
$ele->getDescription() != '') {
                    
$ret .= ''.$ele->getDescription().''
;
                }
                
$ret .= "$class'>".$ele->render()."";
                
//$count++;
            
} else {
                
$hidden .= $ele->render()."n";
            }
        }
        
$ret .= "".$hidden."nn";
        
$ret .= $this->renderValidationJStrue );

Yeah...
fixed^^...cool~~~
but not complete...

/class/xoopsform/grouppermform.php
this file also needs the same fix.

foreach (array_keys($elements) as $i) {
            if (!
is_object($elements[$i])) {
                
$ret .= $elements[$i];
            } elseif (!
$elements[$i]->isHidden()) {
                
$ret .= "$elements[$i]->getCaption();
                if (
$elements[$i]->getDescription() != '') {
                    
$ret .= '$elements[$i]->getDescription() . ''
;
                }
                
$ret .= "nn" $elements[$i]->render() . "nn";
            } else {
                
$ret .= $elements[$i]->render();
            }
        }


and
in case that we use assign() ,I think, we also should be careful to avoid this kind of mistake.

ex) contact module
/modules/contact/index.php
~~
    
$xoopsOption['template_main'] = 'contact_contactusform.html';
~~
    
$contact_form->assign($xoopsTpl);
~~

/modules/contact/templates/contact_contactusform.html
<{$contactform.javascript}>
<
form name="<{$contactform.name}>" action="<{$contactform.action}>" method="<{$contactform.method}>" <{$contactform.extra}>>
  <
table class="outer" cellspacing="1">
    <
tr>
    <
th colspan="2"><{$contactform.title}>th>
    tr>
    
    <{foreach 
item=element from=$contactform.elements}>
      <{if 
$element.hidden != true}>
      <
tr>
        <
td class="head"><{$element.caption}>td>
        <
td class="<{cycle values="even,odd"}>"><{$element.body}>td>
      tr>
      <{else}>
      <{
$element.body}>
      <{/if}>
    <{/foreach}>
    
  table>
form>


PS:
from
http://www.w3.org/TR/2002/REC-xhtml1-20020801/DTD/xhtml1-transitional.dtd

(caption?, (col*|colgroup*), thead?, tfoot?, (tbody+|tr+))>









37
damaster
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/12 14:52

  • damaster

  • Just can't stay away

  • Posts: 556

  • Since: 2003/5/11


That's right, Herko!
I think we agree on this, we both want to give Wanikoo or any other user a chance to improve XOOPS - powered by all !
And thanks for the words Herko, you know that's not the only reason i like you, we both like XOOPS and the people who made it.

Be fair, be honest, be a wise headleader, that's all i wish you and all XOOPS users!



As Wanikoo still pointing out,
let's do something good and great!

- Xoops.

I like people more than machines or money. But that's me!
Lets do something good and great: Lets do open source!

38
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/13 15:38

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


Quote:

An XML declaration is not required in all XML documents; however XHTML document authors are strongly encouraged to use XML declarations in all their documents. Such a declaration is required when the character encoding of the document is other than the default UTF-8 or UTF-16 and no encoding was determined by a higher-level protocol. Here is an example of an XHTML document. In this example, the XML declaration is included.
Quote:


PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">


Virtual Library


Moved to example.org.






Umm...
How about adding the XML declaration ??
(I mean:)
Is there any reason that XOOPS omit this line ??

Umm..
as for mambo
echo '$iso[1] .'"?' .'>';
    
?>
    
    


as for xaraya
echo "1.0"?>n-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">nnError$msg";


As for mambo,xaraya, all pages(maybe--;;) are strictly conforming documents..although they're pages for error message.

but... as for xoops, I think it still lacks consistency.
Quote:

A Strictly Conforming XHTML Document is an XML document that requires only the facilities described as mandatory in this specification. Such a document must meet all of the following criteria:
1,It must conform to the constraints expressed in one of the three DTDs found in DTDs and in Appendix B.

2,The root element of the document must be html.

3,The root element of the document must contain an xmlns declaration for the XHTML namespace [XMLNS]. The namespace for XHTML is defined to be http://www.w3.org/1999/xhtml.

4,There must be a DOCTYPE declaration in the document prior to the root element. The public identifier included in the DOCTYPE declaration must reference one of the three DTDs found in DTDs using the respective Formal Public Identifier. The system identifier may be changed to reflect local system conventions.

5, The DTD subset must not be used to override any parameter entities in the DTD.


ex)
-----------------------
#debug popup window

in case of XOOPS 2.0.10
/html/footer.php
$content '._LANGCODE.'" />'</span><span style="color: #007700">.</span><span style="color: #0000BB">$xoopsConfig</span><span style="color: #007700">[</span><span style="color: #DD0000">'sitename'</span><span style="color: #007700">].</span><span style="color: #DD0000">'.getcss($xoopsConfig['theme_set']).'" />'.$xoopsLogger->dumpAll().'._CLOSE.'" type="button" onclick="javascript:window.close();" />
';


/html/header.php
$content '._LANGCODE.'" />'</span><span style="color: #007700">.</span><span style="color: #0000BB">$xoopsConfig</span><span style="color: #007700">[</span><span style="color: #DD0000">'sitename'</span><span style="color: #007700">].</span><span style="color: #DD0000">'.getcss($xoopsConfig['theme_set']).'" />'.$xoopsLogger->dumpAll().'._CLOSE.'" type="button" onclick="javascript:window.close();" />
';


/html/include/cp_functions.php
$content '._LANGCODE.'" />'</span><span style="color: #007700">.</span><span style="color: #0000BB">$xoopsConfig</span><span style="color: #007700">[</span><span style="color: #DD0000">'sitename'</span><span style="color: #007700">].</span><span style="color: #DD0000">'.getcss($xoopsConfig['theme_set']).'" />'.$xoopsLogger->dumpAll().'._CLOSE.'" type="button" onclick="javascript:window.close();" />
';


in case of XOOPS 2.1.0 dev
/html/class/logger.php
$content '
                    
                    ._LANGCODE.'" />
                    '</span><span style="color: #007700">.</span><span style="color: #0000BB">$xoopsConfig</span><span style="color: #007700">[</span><span style="color: #DD0000">'sitename'</span><span style="color: #007700">].</span><span style="color: #DD0000">'
                    .
xoops_getcss($xoopsConfig['theme_set']).'" />
                    
                    '
.$this->dumpAll().'
                    
                    ._CLOSE.'" type="button" onclick="javascript:window.close();" />
                    

                    
                    ';


------------------------
/html/pmlite.php
echo ".$jump."' />";


-------------------
/html/extras/login.php
<html>
  <
head>
    <
meta http-equiv="content-type" content="text/html; charset='._CHARSET.'" />
    <
meta http-equiv="content-language" content="'._LANGCODE.'" />
    <
title>'.$xoopsConfig['sitename'].'title>
    <
link rel="stylesheet" type="text/css" media="all" href="'.XOOPS_URL.'/xoops.css" />


---------------
/html/install/index.php
DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<
html>


--------------------
/html/install/install_tpl.php
DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<
html>


-------------------
/html/modules/system/admin/blocksadmin/main.php
$dummyhtml '._LANGCODE.'" />'</span><span style="color: #007700">.</span><span style="color: #0000BB">$xoopsConfig</span><span style="color: #007700">[</span><span style="color: #DD0000">'sitename'</span><span style="color: #007700">].</span><span style="color: #DD0000">'.getcss($xoopsConfig['theme_set']).'" />
'.$myblock->getVar('title').'
'.$myblock->getContent('S'$bctype).'
'
;


--------------
/html/modules/system/admin/tplsets/main.php
$dummylayout '._LANGCODE.'" />'</span><span style="color: #007700">.</span><span style="color: #0000BB">$xoopsConfig</span><span style="color: #007700">[</span><span style="color: #DD0000">'sitename'</span><span style="color: #007700">].</span><span style="color: #DD0000">'';


-------------------
/html/modules/system/admin/version/main.php
echo "nn";
echo 
"Content-Type" content="text/htmlcharset="._CHARSET."">n";
echo 
""</span><span style="color: #007700">.</span><span style="color: #0000BB">htmlspecialchars</span><span style="color: #007700">(</span><span style="color: #0000BB">$xoopsConfig</span><span style="color: #007700">[</span><span style="color: #DD0000">'sitename'</span><span style="color: #007700">]).</span><span style="color: #DD0000">"n";


-----------------
/html/modules/system/templates/system_redirect.html
<html>
<
head>
<
meta http-equiv="Content-Type" content="text/html; charset=<{$xoops_charset}>" />
<
meta http-equiv="Refresh" content="<{$time}>; url=<{$url}>" />
<
title><{$xoops_sitename}>title>

39
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/14 13:54

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


off the topic...
but...^^;;
Quote:

Herko Coomans wrote:
Step 1b:
CSS 2.0 compliant


Quote:

from:
http://www.w3.org/TR/CSS21

Cascading Style Sheets, level 2 revision 1 CSS 2.1 Specification

4 Syntax and basic data types
4.3 Values
4.3.2 Lengths
The format of a length value (denoted by in this specification) is a (with or without a decimal point) immediately followed by a unit identifier (e.g., px, em, etc.). After a zero length, the unit identifier is optional.

From:
http://www.w3.org/TR/CSS21/fonts.html
15.3 Font family: the 'font-family' property
Style sheet designers are encouraged to offer a generic font family as a last alternative. Generic font family names are keywords and must NOT be quoted.

In the example above, the last value is a generic family name. The following generic families are defined:
'serif' (e.g. Times)
'sans-serif' (e.g. Helvetica)
'cursive' (e.g. Zapf-Chancery)
'fantasy' (e.g. Western)
'monospace' (e.g. Courier)

-------------------------------------------------------
/html/themes/default/style.css
line3
table {width: 100%; margin: 5; padding: 5; font-size: small}
To:
table {width: 100%; margin: 5px; padding: 5px; font-size: small}

After this fix, it will be valid.
------------------------------------------------------------
/html/themes/phpkaox/style.css, styleMAC.css, styleNN.css
line1
table { width: 100%; margin: 5; padding: 5; font-size: small}
To:
table { width: 100%; margin: 5px; padding: 5px; font-size: small}

line6 ( I mean not ; but : )
body { font-family: Tahoma, taipei; color;#000000; font-size: 12px}
To:
body { font-family: Tahoma, taipei; color: #000000; font-size: 12px}

line6,7,8,9
body { font-family: Tahoma, taipei; color: #000000; font-size: 12px}
a { font-family: Tahoma, taipei; font-size: 12px; text-decoration: none; color: #666666; font-style: normal}
a:hover { text-decoration: underline overline; font-family: Tahoma, taipei; font-size: 12px; color: #FF9966; font-style: normal}
td { font-family: Tahoma, taipei; color: #000000; font-size: 12px;border-top-width : 1px; border-right-width : 1px; border-bottom-width : 1px; border-left-width : 1px;}

To:
body { font-family: Tahoma, taipei, Verdana, Arial, Helvetica, sans-serif; color: #000000; font-size: 12px}
a { font-family: Tahoma, taipei, Verdana, Arial, Helvetica, sans-serif; font-size: 12px; text-decoration: none; color: #666666; font-style: normal}
a:hover { text-decoration: underline overline; font-family: Tahoma, taipei, Verdana, Arial, Helvetica, sans-serif; font-size: 12px; color: #FF9966; font-style: normal}
td { font-family: Tahoma, taipei, Verdana, Arial, Helvetica, sans-serif; color: #000000; font-size: 12px;border-top-width : 1px; border-right-width : 1px; border-bottom-width : 1px; border-left-width : 1px;}

After this fix, it will be valid.
--------------------------------------------------------
/html/themes/x2t/style.css

/* Only IE that not affect the other Browsers */
* {scrollbar-face-color: #E9E9E9; scrollbar-highlight-color: #ffffff; scrollbar-shadow-color: #E0E0E0; scrollbar-3dlight-color: #000000; scrollbar-arrow-color: #000000; scrollbar-track-color: #ffffff; scrollbar-darkshadow-color: #000000;}
hr {height: 3px; border: 3px #D68000 solid; filter: Alpha(Opacity=100,FinishOpacity=10,Style=2); width: 95%;}

Yeah...
They are supported only in case of IE...
so...
If we want to make style.css valid, we have to remove them.
(I mean scrollbar-xxxx-xxxx and filter! )

/html/themes/x2t/styleNN.css
line 17
hr {height: 1px; #D68000 solid; width: 95%;}
To:
hr {height: 1px; border: 3px #D68000 solid; width: 95%;}

After this fix, it will be valid.
-------------------------------------------------------

40
chapi
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/14 14:34

  • chapi

  • Theme Designer

  • Posts: 611

  • Since: 2002/1/22


Quote:

/html/themes/x2t/style.css

/* Only IE that not affect the other Browsers */
* {scrollbar-face-color: #E9E9E9; scrollbar-highlight-color: #ffffff; scrollbar-shadow-color: #E0E0E0; scrollbar-3dlight-color: #000000; scrollbar-arrow-color: #000000; scrollbar-track-color: #ffffff; scrollbar-darkshadow-color: #000000;}
hr {height: 3px; border: 3px #D68000 solid; filter: Alpha(Opacity=100,FinishOpacity=10,Style=2); width: 95%;}

Yeah...
They are supported only in case of IE...
so...
If we want to make style.css valid, we have to remove them.
(I mean scrollbar-xxxx-xxxx and filter! )


Mozilla also supports the scrollbar styles, but they have to defined for the html tag and not for the body tag in the css. So the scrollbar styles don't have to be removed completely. They just have to be inside the correct tag!

Login

Who's Online

290 user(s) are online (170 user(s) are browsing Support Forums)


Members: 0


Guests: 290


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