24
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/6 7:13

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


Quote:

artigas wrote:
Hope That Helps.

Thanks a lot!!
Quote:

Gambero wrote:
Why isn't wanikoo in XOOPS Core development Team ?
......
And like you said he just need to ask. So, wanikoo: ASK!

Gambero, you are so generous!
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^^;;

23
artigas
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/5 21:11

  • artigas

  • Quite a regular

  • Posts: 208

  • Since: 2004/12/21


Greetings -

I actually answered my own question. Here is what I found goes through the validator.

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

<
html><head><title>Go Back</title>
<
meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<
script type="text/javascript">history.go(-1);</script>
</
head><body><!-- ... body of document ... --></body></html>

Hope That Helps.

22
artigas
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/5 20:34

  • artigas

  • Quite a regular

  • Posts: 208

  • Since: 2004/12/21


Greetings -

Would that mean that the index.html that is used as a place holder in directories would be changed

from
<script>history.go(-1);</script>

to
<script type='text/javascript'>history.go(-1);</script>

or would there be some additional changes needed to make it fully compliant to strict?

Thanks In Advance.

21
Herko
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/5 17:04

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


Wanikoo has indeed shown a lot of initiative and skills in helping Mithrandir (and others) out, his PM hack is one of the things that is on the list to be added to XOOPS 2.1/2.2.

Again, not disqualifying Wanikoo but giving more information on our policy, one of the citeria we have for the Core Development Team is the ability to work as part of a team. I suggest Wanikoo joins as a virtual member so we can examine his team player qualities as well as his programming skills Then who knows, if Wanikoo still wants to work with us loonies he might become a core developer.

Herko

20
Gambero[removed]
Re: Let's make XOOPS valid xhtml1.0 transitional!

Quote:
...and because he can help as much by submitting these items to the trackers on sf.net, making him a 'virtual core development team member' Wanikoo is but a 'young' member, core developers most often are people a bit more 'ripened' in the community DOn't get me wrong, this is not to disqualify Wanikoo, but part of our policy on adding people to our core development team.


This is a little offtopic but I would just like to say this.

Wanikoo looks a very good programmer (in PHP) and he helps saving bugs everytime. I think he likes XOOPS and would be a great member in core development team. He deserves to be a part of you ... Mithrandir just remember how many times he helped you out ... and if I can see this, then probably you too. And like you said he just need to ask. So, wanikoo: ASK!

19
Herko
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/5 16:50

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


Quote:

Gambero wrote:
Why isn't wanikoo in XOOPS Core development Team ?


...and because he can help as much by submitting these items to the trackers on sf.net, making him a 'virtual core development team member' Wanikoo is but a 'young' member, core developers most often are people a bit more 'ripened' in the community DOn't get me wrong, this is not to disqualify Wanikoo, but part of our policy on adding people to our core development team.

As for WarDick's comment on trackers being a black box, you're absolutely right there. That is one of the things we're addressing in the new development roadmap, starting already with the development of XOOPS 2.1/2.2, as you can see by Mithrandir's recent posts on sf.net and these forums The most apparent reason of it having been a black box for so long is that XOOPS 2.0.x has been a bugfix/security patches branch (as it should have been). This means that there has been a feature freeze on the core, at least where database changes are concerned (you will find that there have been no changes to any core database tables since 2.0.1). Now, with the development of XOOPS 2.1 starting, this feature freeze has been selectively lifted. With the coming roadmap for X2.1/2.2 you will get a good view of what is going to happen, and tracker status fits in that roadmap strategy.

Herko

18
Mithrandir
Re: Let's make XOOPS valid xhtml1.0 transitional!

because he hasn't asked

17
Gambero[removed]
Re: Let's make XOOPS valid xhtml1.0 transitional!

Why isn't wanikoo in XOOPS Core development Team ?

16
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/5 14:52

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


------------------------------------
pages with javascript
------------------------------------
ex)

/html/misc.php
line 71
<script language='javascript'>
line 238
<script language='javascript'>
--------------
error message:
required attribute "type" not specified

<script language="javascript">

The attribute given above is required for an element that you've used, but you have omitted it.
For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>
--------------

From:
<script language='javascript'>
To:
<script type='text/javascript'>

------------------------------
After this modification,
we can get this message, "This Page(ex: misc.php case:friend) Is Valid XHTML 1.0 Transitional!" from W3 validator.


-------to be continued----------

ps: some bug in misc.php

/html/misc.php
-----------------
line 102
echo '</tr></table></form></div>';
no open tag<div> for end tag</div>
so...just remove </div>

line 172
case 'online':
there are no end tag</head> and no start tag <body>
so this is neccessary
case 'online':
echo '</head><body>';

15
wanikoo
Re: Let's make XOOPS valid xhtml1.0 transitional!
  • 2005/4/5 10:45

  • wanikoo

  • Not too shy to talk

  • Posts: 129

  • Since: 2003/12/27


------------------------
etc.... for some modules&blocks
-------------------------
Quote:

Fromhttp://www.w3.org/TR/xhtml1/

4.2. Element and attribute names must be in lower case
XHTML documents must use lower case for all HTML element and attribute names. This difference is necessary because XML is case-sensitive e.g. <li> and <LI> are different tags.

ex)
<TD id="headerbar" colspan="2"></td>
->it gives us some error messages
element "TD" undefined
there is no attribute "colspan"
there is no attribute "id"
end tag for element "td" which is not open
end tag for "TD" omitted
etc...
Quote:

4.4. Attribute values must always be quoted
All attribute values must be quoted, even those which appear to be numeric.

ex)
<th colspan=2>
->error message
an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
Quote:

4.5. Attribute Minimization
XML does not support attribute minimization. Attribute-value pairs must be written in full. Attribute names such as compact and checked cannot occur in elements without their value being specified.

ex}
<input type='text' name='fname' value />
->error message
"value" is not a member of a group specified for any attribute

Login

Who's Online

141 user(s) are online (90 user(s) are browsing Support Forums)


Members: 0


Guests: 141


more...

Donat-O-Meter

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

Latest GitHub Commits