We closed this forum 18 June 2010. It has served us well since 2005 as the ALPHA forum did before it from 2002 to 2005. New discussions are ongoing at the new URL http://forum.processing.org. You'll need to sign up and get a new user account. We're sorry about that inconvenience, but we think it's better in the long run. The content on this forum will remain online.
IndexSuggestions & BugsSoftware,  Documentation,  Website Suggestions › standards-compliant "built with processing"
Page Index Toggle Pages: 1
standards-compliant "built with processing" (Read 2508 times)
standards-compliant "built with processing"
Dec 13th, 2006, 2:30pm
 
Howdy y'all.

I was cleaning up my website today (ugh!) and trying to remove a bunch of non-xHTML code (yikes!) when I ran into the non-standards-compliant problem of the default html that Processing generates.

I found this thread in the archives, (http://processing.org/discourse/yabb_beta/YaBB.cgi?board=Integrate;action=display;num=1119699148") which points to the following example (http://ww2.cs.fsu.edu/~steele/XHTML/appletObject.html), which is pretty good, although I suppose there is a cleaner solution out there.

The W3C validator (http://validator.w3.org) pointed me to a good article on A List Apart: http://alistapart.com/articles/flashsatay, which discusses this issue in relation to Flash.

Anyone have any suggestions on making the default "built with Processing" tag xHTML-Strict?
Re: standards-compliant "built with processin
Reply #1 - Dec 14th, 2006, 12:07am
 
We need someone to advise us on this because neither Ben or myself are in the business of building websites. Our most important consideration is not to be xHTML compliant, it's having the HTML work on as many browsers as possible, including older software.

Casey
Re: standards-compliant "built with processin
Reply #2 - Dec 15th, 2006, 8:46am
 
i'll be in the boston-office from saturday on. can work on it next week.

best,
F
Re: standards-compliant "built with processin
Reply #3 - Dec 15th, 2006, 1:41pm
 
I found the following code from the above site to work pretty well:

Code:
<!--[if !IE]>-->
<object classid="java:myFancySketch.class" type="application/x-java-applet" archive="myFancySketch.jar" height="300" width="400" >
<!-- Konqueror browser needs the following param -->
<param name="archive" value="myFancySketch.jar" />
<!--<![endif]-->
<object classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93" height="300" width="400" >
<param name="code" value="myFancySketch" />
<param name="archive" value="myFancySketch.jar" />
</object>
<!--[if !IE]>-->
</object>
<!--<![endif]-->


I don’t like the classid, frankly it’s an eyesore. There’s got to be better.

I tried it Mac/PC, Firefox/Safari/Explorer, worked fine. But those were all recent machines with recent iterations of those browsers. Someone should probably check further back.

I /absolutely/ agree with Casey : it’s important to have as many machines reading it as possible. And as such I agree with your priorities. But in the future, that’s also going to mean going standards-compliant. And someone here has got to be standards-savy, at least more than me, and apparently more than you. It’s a collective party, after all.
Re: standards-compliant "built with processin
Reply #4 - Jan 2nd, 2007, 4:18am
 
just quickly reporting back that i'm working on it.
have some notes and testpages here:
http://bezier.de/xhtml/

F
Re: standards-compliant "built with processin
Reply #5 - Jan 2nd, 2007, 4:55pm
 
The tableau looks great, but, uhhh, I didn't exactly understand the methodology, especially the first two collumns with Java disabled.
Re: standards-compliant "built with processin
Reply #6 - Jan 2nd, 2007, 4:58pm
 
first two columns check the behavior without java, so wether or not the fallback-text is displayed. fallback-text is the text inside the applet/object tag, which should be displayed if java's not there or not working.

next two columns are the results for the tags itself. wether or not the applet ran ok.

the last two columns are the results from testing wether or not the object tag fully supports javascript (mayscript-param) and wether the applet can read params from the tag.

F
Re: standards-compliant "built with processin
Reply #7 - Jan 2nd, 2007, 5:44pm
 
another thing i just have to add: i was impressed that, although everybody seems to hate the object-tag solution, in the end it was more predictable and reliable.

things i've not tested so far:
- different machines (but XP on virtualPC is almost as bad as it can get i guess)
- what happens if older versions (than 1.4.2) of java are installed
  (the object tag currently forces not specific version, maybe it should
  force at least 1.3.x which is the (current) Processing minimum)
- linux (just installing that)
- how the openGL tag behaves.
- DOM, for example if the object-tag-applet shows up in document.applets[]

F
Re: standards-compliant "built with processin
Reply #8 - Jan 2nd, 2007, 6:50pm
 
and to keep things tidy:

alpha discussions:
#2
Re: standards-compliant "built with processin
Reply #9 - Jan 4th, 2007, 2:38am
 
-- removed old links --

F
Re: standards-compliant "built with processin
Reply #10 - Jan 15th, 2007, 5:37pm
 
Continues here:
http://processing.org/discourse/yabb_beta/YaBB.cgi?board=Integrate;action=display;num=1168878870

F
Page Index Toggle Pages: 1