Re: [WSG] My Favorite XHTML/CSS/JavaScript/PHP Editor - NO WYSIWYG
I use TSWARE Its AWESOME! www.tsware.net built in PHP/CSS/XHTML/JAVASCRIPT syntax hightligher. it can tell when a PHP doc has PHP and HTML so they are higlighted with their own type. also HTML with embedded Javascript - it does that too. built in FTP. tabbed windows. project manager - with todo list etc... validates your pages on the fly... its great! *- Chris Stratford* Leslie Riggs wrote: I'm currently test driving a free editor, PSPad Editor, which has Top Style 3.10 (trial edition) built-in - you can also get Top Style Lite which is a free version, instead. I'm fast falling in love with Top Style. So far, I'm finding it a pleasure to work with PSPad/Top Style. The best thing about it: it doesn't take up a huge amount of space on your computer, it's fast, and it's feature-packed. Yes, you can write Javascript and PHP files in PSPad Editor, as well as C++, COBOL, Python, etc. It doesn't slow down my machine or crash. It's not WYSIWYG, but you can click to see what your code produces in IE and Mozilla. No more fighting with the program just to get what I want out of it - at last, a tool that lets me concentrate on what I'm trying to accomplish. Just a delight to use. Leslie Riggs jEdit: http://www.jedit.org/ ...and be sure to check out the recommended plugins in the jEdit Wiki: http://community.jedit.org/cgi-bin/TWiki/view/Main/PluginsOverview Nick Greetings Every One! After 1st Page 2000, I'm using AceHTML 5 Pro to build websites (info: http://www.visicommedia.com/). It is great for HTML and CSS developer, but not for a programmer who uses JavaScript and PHP. ... I'm getting tired of it :-( What is your favorite XHTML Editor? (Please note that I'm not looking for WYSIWYG Editors) -- Thanks in advance, Behzad P.S. If you have no time, just mention the program's name :-) ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
CLOSED Re: [WSG] My Favorite XHTML/CSS/JavaScript/PHP Editor - NO WYSIWYG
Hi all This has been discussed ad nauseam previously on the list. Their is a resource category on the site created just for this topic so that all members can have quick access to available editors and add new ones. http://webstandardsgroup.org/resources/#cat30 Please feel free to log in at the site and add the editor you have discussed here. No more replies to this topic on the list - and please avoid starting new ones on the same topic. Cheers James ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Longdesc?
I noticed this attribute as part of an img element in Mark Stanton's presentation at the Sydney meeting last Thursday... he didn't make reference to it, though, and I've been struggling to see the application of it ever since. Does longdesc really have to comprise a link to an external page, or can it simply be an extended version of the alt attribute? Regardless, what are the practical applications of this, anyway? Can any user agents read it? Do screen readers use it? Does ANYTHING use it? Right clicking on an image which uses longdesc, then clicking Properties in Firefox reveals the URI which longdesc points to... and the benefits of this make sense, but still... inline display through fetching the longdesc URI if the image is not available would seem to make more sense, at least to me. It's not an urgent matter for resolution, at least, not for me, but I've been musing over it ever since... Joshua Street base10solutions Website: http://www.base10solutions.com/ Phone: (02) 9898-0060 Fax: (02) 8572-6021 Mobile: 0425 808 469 E-mails and any attachments sent from base10solutions are to be regarded as confidential. Please do not distribute or publish any of the contents of this e-mail without the senders consent. If you have received this e-mail in error, please notify the sender by replying to the e-mail, and then delete the message without making copies or using it in any way. Although base10solutions takes precautions to ensure that e-mail sent from our accounts are free of viruses, we encourage recipients to undertake their own virus scan on each e-mail before opening, as base10solutions accepts no responsibility for loss or damage caused by the contents of this e-mail. ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Longdesc?
Ahh, I didn't even think about the possibility of using anchors! Thanks for the informative response. :) Josh On Sun, 2004-09-19 at 21:29, Patrick H. Lauke wrote: Joshua Street wrote: Does longdesc really have to comprise a link to an external page, or can it simply be an extended version of the alt attribute? as per http://www.w3.org/TR/html4/struct/objects.html#h-13.2 it *has to be* a URI by the way: it doesn't need to be a link to an external page...you can also have longdesc pointing at an anchor or fragment identifier on the same page (e.g. longdesc=#imagedescription) or you can have one single external page for all descriptions, and then link to the specific one for the particular image, again with anchor or fragment identifier (e.g. longdesc=alldescriptions.html#bookcover1) Regardless, what are the practical applications of this, anyway? Can any user agents read it? Do screen readers use it? Does ANYTHING use it? if by use it you mean expose it to the user then in most cases the answer seems to be no. can't vouch for it, as i haven't got any installed here at home, but i do seem to recall that some screenreaders to present the option to jump to the longdesc when they encounter it. incidentally, i've just written an extension for firefox to offer a View Image Longdesc: ... in the image context menu, whenever an image actually has a longdesc attribute set. http://www.splintered.co.uk/experiments/55/ i'm hoping that this sort of thing will make it into the browser(s) as standard. inline display through fetching the longdesc URI if the image is not available would seem to make more sense, at least to me. no, that's what ALT is for. imagine if the image is a book cover. the ALT would say book cover: title of book and the document referenced by the londesc would go into the details of what the cover looks like, e.g. a man and a woman, kissing in front of a nuclear explosion while debris flies all around the scene or something. now imagine your screenreader is reading out the page...having the longdesc plonked right there in the middle of the original document would be very disruptive to the flow of the document, and in most cases unnecessary and distracting if the ALT already adequately conveys what the image is for. Patrick _ redux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] IE border dotted
On 20/09/2004, at 2:02 AM, Cameron Muir wrote: Does IE support 'border-style: dotted' ? In my IE it renders as dashed. Mozilla/Firefox are fine, of course. I've certainly never seen it work -- definitely not in a standards-compliant way. However, before you start bashing IE, consider this quote from the w3 spec http://www.w3.org/TR/CSS2/box.html#propdef-border-style: Conforming HTML user agents may interpret 'dotted', 'dashed', 'double', 'groove', 'ridge', 'inset', and 'outset' to be 'solid'. So, IE isn't exactly compliant (it should render dotted as solid), but I guess they figured dashed is closer than solid. --- Justin French http://indent.com.au ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] IE border dotted
Thanks Justin. I really like dotted - oh well. regards, cameron. Justin French wrote: On 20/09/2004, at 2:02 AM, Cameron Muir wrote: Does IE support 'border-style: dotted' ? In my IE it renders as dashed. Mozilla/Firefox are fine, of course. I've certainly never seen it work -- definitely not in a standards-compliant way. However, before you start bashing IE, consider this quote from the w3 spec http://www.w3.org/TR/CSS2/box.html#propdef-border-style: Conforming HTML user agents may interpret 'dotted', 'dashed', 'double', 'groove', 'ridge', 'inset', and 'outset' to be 'solid'. So, IE isn't exactly compliant (it should render dotted as solid), but I guess they figured dashed is closer than solid. --- Justin French http://indent.com.au ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] css validation error
Hello,
I can't work out why this is producing an error. I'm sure there must be
a simple solution that I've missed.
body {
font: small Trebuchet MS, sans-serif;
color: #66;
}
The error:
URI : http://design.quagma.net/themes/quagma/style.css
* Line: 0 Context : sans-serif
Parse Error - : Trebuchet MS
* Line: 0 Context : sans-serif
Parse Error - sans-serif;
* Line: 0 Context : sans-serif
Parse error - Unrecognized : { }
The site:
http://design.quagma.net
**
The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] css validation error
Hi Cameron,
You have this
.paymate {
position: relative:
top: 20px;
right: 10px;
}
the position:relative needs a semi colon and you should be on your way
Regards,
John,
Cameron Muir wrote:
Hello,
I can't work out why this is producing an error. I'm sure there must be
a simple solution that I've missed.
body {
font: small Trebuchet MS, sans-serif;
color: #66;
}
The error:
URI : http://design.quagma.net/themes/quagma/style.css
* Line: 0 Context : sans-serif
Parse Error - : Trebuchet MS
* Line: 0 Context : sans-serif
Parse Error - sans-serif;
* Line: 0 Context : sans-serif
Parse error - Unrecognized : { }
The site:
http://design.quagma.net
**
The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
**
The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] Image work around
Hmmm, I'm sorry I must have inadverdently left out some text. At www.guildinstitute.org, I have placed an image on the left and text on the right. Currently the text and image are in a 2-column table to keep each in a separate column. How can I achieve the same thing using CSS? The style sheet I used comes from a Dreamweaver template and has the images float left. http://www.guildinstitute.org/css/emx_nav_leftrev.css Also, the image I understand is too large for those who come to the website using a 600 by 800 display. I will have to reduce the size as well. Is there an ideal width for images these days? Thank you, Nancy Johnson --- Lea de Groot [EMAIL PROTECTED] wrote: On Sat, 18 Sep 2004 08:40:01 -0700 (PDT), Nancy Johnson wrote: What is the best way to have in css to have an image on the left with on the right without using , but keeping each in it's own column. I'm sorry, could you try phrasing that again? I don't seem to be able to validate your syntax. bg Lea -- Lea de Groot Elysian Systems - http://elysiansystems.com/ Brisbane, Australia ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** __ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] IE border dotted
IE 6 supports the dotted style - so long as the border width is above 2px. ...which totally sucks, because 1px dotted is nice ;) http://leftjustified.net/ ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Testing render speed
** EDIT from above: It would seem that as of August 11th they have altered it to include images from CSS... This is one of those times I'm really glad I'm wrong :o As for home testing... Could you include some form of timestamp using php and then a javascvript onload function to work out the time difference? That's a wild guess, but it might just work. Andrew. http://leftjustified.net/ ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Testing render speed
Logically, yes, but you'd need to be hosting on loopback, otherwise the timestamps would most probably be out of sync (not a problem for most). The initial question specified from initial request through to completion, which means that we've got to take into account transport time, for the leaner nature of CSS-based markup to become apparent. Obviously, network conditions from loopback aren't an accurate representation of the wider Internet... How well synchronised can computers get with time servers? I've never really thought about it too hard... but in this case, the margin for error would be in milliseconds, so it matters. On Mon, 2004-09-20 at 10:14, Andrew Krespanis wrote: ** EDIT from above: It would seem that as of August 11th they have altered it to include images from CSS... This is one of those times I'm really glad I'm wrong :o As for home testing... Could you include some form of timestamp using php and then a javascvript onload function to work out the time difference? That's a wild guess, but it might just work. Andrew. http://leftjustified.net/ ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** Joshua Street base10solutions Website: http://www.base10solutions.com/ Phone: (02) 9898-0060 Fax: (02) 8572-6021 Mobile: 0425 808 469 E-mails and any attachments sent from base10solutions are to be regarded as confidential. Please do not distribute or publish any of the contents of this e-mail without the senders consent. If you have received this e-mail in error, please notify the sender by replying to the e-mail, and then delete the message without making copies or using it in any way. Although base10solutions takes precautions to ensure that e-mail sent from our accounts are free of viruses, we encourage recipients to undertake their own virus scan on each e-mail before opening, as base10solutions accepts no responsibility for loss or damage caused by the contents of this e-mail. ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Footer stuff
Apologies if this has been discussed before. What is better in terms of semantics and accessibility? div id=footer pstuff | more stuffbr / stuff too | more stuff again/p /div or div id=footer ullistuff/li | limore stuff/li listuff too/li | limore stuff again/li/ul /div Obviously the first one uses a br / to differentiate 2 lines, which I am sure can be done many other ways too. The second method in my opinion has more control over the information as it uses lis instead of p, would it be right to say ps need be used more in the content area instead of footers. Would appreciate your feedback on this. Regards, Amit Karmakar http://karmakars.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Footer stuff
Adding | between links in footer is good practice for screenreaders because it breaks up the reading of the links. But in the second example, you already do this with the list items, so in terms of accessibility I doubt you would need to add | to them. Also those | are outside the li/li so I'm not sure if that would validate? I couldn't say whether one option is better or not in terms of semantics though sorry. Might find a similar topic of discussion on the simple quiz site: http://www.simplebits.com/bits/simplequiz/ Tim Hill Computer Associates Graphic Artist tel: +612 9937 0792 fax: +612 9937 0546 [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Amit Karmakar Sent: Monday, 20 September 2004 11:22 AM To: [EMAIL PROTECTED] Subject: [WSG] Footer stuff Apologies if this has been discussed before. What is better in terms of semantics and accessibility? div id=footer pstuff | more stuffbr / stuff too | more stuff again/p /div or div id=footer ullistuff/li | limore stuff/li listuff too/li | limore stuff again/li/ul /div Obviously the first one uses a br / to differentiate 2 lines, which I am sure can be done many other ways too. The second method in my opinion has more control over the information as it uses lis instead of p, would it be right to say ps need be used more in the content area instead of footers. Would appreciate your feedback on this. Regards, Amit Karmakar http://karmakars.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Footer stuff
Hi Amit,
Ben Bishop's presentation at the sydney WSG meeting outlined that he
used a list for his footer:
http://www.nzsteel.co.nz/nz/
He also used css for the divider, instead of pipes:
#footermenu li a {
height:1em;
padding:0 0.75em;
border-left:1px solid #999;
font-weight:bold;
}
#footermenu li.first a {
border:none;
}
in regards to your situation, i would go for a list, or two, depending
on the information.
div id=footer
ullistuff/li | limore stuff/li/ul
ullistuff too/li | limore stuff again/li/ul
/div
two lists, in the footer, that both behave in the same way. Seems
semantically sound from my viewpoint.
Best of luck!
Adam
**
The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] Footer stuff
The semantics obviously depend on what stuff | more stuff and stuff too | more stuff again actually are... Patrick Amit Karmakar wrote: Apologies if this has been discussed before. What is better in terms of semantics and accessibility? div id=footer pstuff | more stuffbr / stuff too | more stuff again/p /div or div id=footer ullistuff/li | limore stuff/li listuff too/li | limore stuff again/li/ul /div Obviously the first one uses a br / to differentiate 2 lines, which I am sure can be done many other ways too. The second method in my opinion has more control over the information as it uses lis instead of p, would it be right to say ps need be used more in the content area instead of footers. Would appreciate your feedback on this. Regards, Amit Karmakar http://karmakars.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** -- _ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Footer stuff
If you were going to use the second example, I'd recommend using border:whatever; instead of pipe characters... My $AU0.03 On Mon, 2004-09-20 at 11:22, Amit Karmakar wrote: Apologies if this has been discussed before. What is better in terms of semantics and accessibility? div id=footer pstuff | more stuffbr / stuff too | more stuff again/p /div or div id=footer ullistuff/li | limore stuff/li listuff too/li | limore stuff again/li/ul /div Obviously the first one uses a br / to differentiate 2 lines, which I am sure can be done many other ways too. The second method in my opinion has more control over the information as it uses lis instead of p, would it be right to say ps need be used more in the content area instead of footers. Would appreciate your feedback on this. Regards, Amit Karmakar http://karmakars.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** Joshua Street base10solutions Website: http://www.base10solutions.com/ Phone: (02) 9898-0060 Fax: (02) 8572-6021 Mobile: 0425 808 469 E-mails and any attachments sent from base10solutions are to be regarded as confidential. Please do not distribute or publish any of the contents of this e-mail without the senders consent. If you have received this e-mail in error, please notify the sender by replying to the e-mail, and then delete the message without making copies or using it in any way. Although base10solutions takes precautions to ensure that e-mail sent from our accounts are free of viruses, we encourage recipients to undertake their own virus scan on each e-mail before opening, as base10solutions accepts no responsibility for loss or damage caused by the contents of this e-mail. ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Footer stuff
adam reitsma wrote: div id=footer ullistuff/li | limore stuff/li/ul ullistuff too/li | limore stuff again/li/ul /div Drop those | in between list items, as it's not valid markup (probably just an oversight, but it's best to clarify nonetheless) Patrick _ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Footer stuff
Amit It's a list of information for the user. You can use floats to turn on/off horizontal/vertical display of the list. You'll have much more control over the list display than with a br Also, you should move the pipes within an li tag or use the li or a border to act as the delimiter so a screen reader won't pick it up and say pipe or whatever (I think that's right?) . As an aside it's a good idea to watch that the characters # and | in that order :D You never know what the screen reader might say.. Also Also watch the in footer. Cheers James Amit Karmakar wrote: Apologies if this has been discussed before. What is better in terms of semantics and accessibility? div id=footer pstuff | more stuffbr / stuff too | more stuff again/p /div or div id=footer ullistuff/li | limore stuff/li listuff too/li | limore stuff again/li/ul /div Obviously the first one uses a br / to differentiate 2 lines, which I am sure can be done many other ways too. The second method in my opinion has more control over the information as it uses lis instead of p, would it be right to say ps need be used more in the content area instead of footers. Would appreciate your feedback on this. Regards, Amit Karmakar http://karmakars.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] css validation error
Thanks for pointing that out John - serves me right for not cleaning out
disused styles.
However, I'm still getting the same error.
John Oxton wrote:
Hi Cameron,
You have this
.paymate {
position: relative:
top: 20px;
right: 10px;
}
the position:relative needs a semi colon and you should be on your way
Regards,
John,
Cameron Muir wrote:
Hello,
I can't work out why this is producing an error. I'm sure there must
be a simple solution that I've missed.
body {
font: small Trebuchet MS, sans-serif;
color: #66;
}
The error:
URI : http://design.quagma.net/themes/quagma/style.css
* Line: 0 Context : sans-serif
Parse Error - : Trebuchet MS
* Line: 0 Context : sans-serif
Parse Error - sans-serif;
* Line: 0 Context : sans-serif
Parse error - Unrecognized : { }
The site:
http://design.quagma.net
**
The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
**
The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
**
The discussion list for http://webstandardsgroup.org/
Proud presenters of Web Essentials 04 http://we04.com/
Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
Re: [WSG] Footer stuff
Thanks All, I think lists is the way to go in this case, a paragraph is more appropriate(some would say only ever appropriate) where it is truly a paragraph of text/content Well, time to rework my own footers :) On Mon, 20 Sep 2004 01:50:21 +, James Ellis [EMAIL PROTECTED] wrote: Amit It's a list of information for the user. You can use floats to turn on/off horizontal/vertical display of the list. You'll have much more control over the list display than with a br Also, you should move the pipes within an li tag or use the li or a border to act as the delimiter so a screen reader won't pick it up and say pipe or whatever (I think that's right?) . As an aside it's a good idea to watch that the characters # and | in that order :D You never know what the screen reader might say.. Also Also watch the in footer. Cheers James Amit Karmakar wrote: Apologies if this has been discussed before. What is better in terms of semantics and accessibility? div id=footer pstuff | more stuffbr / stuff too | more stuff again/p /div or div id=footer ullistuff/li | limore stuff/li listuff too/li | limore stuff again/li/ul /div Obviously the first one uses a br / to differentiate 2 lines, which I am sure can be done many other ways too. The second method in my opinion has more control over the information as it uses lis instead of p, would it be right to say ps need be used more in the content area instead of footers. Would appreciate your feedback on this. Regards, Amit Karmakar http://karmakars.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** -- Regards, Amit Karmakar http://karmakars.com ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] New website launch
Hi Ian, I had a similar problem with my site - I had some tables that refused to display in the proper(desired) placement - they insisted on appearing below the absolutely positioned element - way down the page. I created a floating div and stuck them in that - seems to work, but I'm not sure it's the proper way to go! Kay Murphey Web Manager Dept of Community Services -Original Message- From: Ian Fenn [mailto:[EMAIL PROTECTED] Sent: Monday, 20 September 2004 09:20 To: [EMAIL PROTECTED] Subject: [WSG] New website launch Hi, I've launched my first website using web standards for a client: http://www.housedoctor.co.uk/ Checking the website in browsercam: http://www.browsercam.com/public.aspx?proj_id=98657 ...it doesn't seem to be rendering quite right in IE5 or IE5.5 in Windows 2000. It's also a bit screwy in Opera 6.0 on the Mac. I'd be most grateful for any possible fixes... All the best, -- Ian Fenn http://www.chopstixmedia.com/ ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the named addressee(s) only. It may be confidential. If you receive this message in error please notify us immediately by return mail and delete the message (and any attachments). Neither the NSW Department of Community Services nor the NSW Department of Ageing, Disability Home Care are responsible for any changes to this message, or the consequences of any changes to this message. ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Testing render speed
Try http://www.xat.com/wo/index.html We've been using it and find it very helpful. I think you could set it to unlimited speed to get just render times... I want to test the render speed (from initial request through to completion, and just the render once all files are cached) of some pages, specifically to see if a non-table based approach is speeding things up at all. Anyone know what the best way of doing this is? ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
