You could use a database, but if you just want a low maintainance method
make a tab deliminated text file eg;
image1.jpgThis is the first image
image2.jpgThis is the second image
image3.jpgThis is the thrid image
Now of course the image names will reflect the images in your rotate
What you charge depends on a whole range of factors but these are the
main ones.
- The local going rate
- The type of clients you deal with
- How good you are at what you do
- Your overheads
Obviously a large agency with flash premises in the Middle of London
dealing with blue chip clients are
Narain said:
i am using a image rotator php script in the home page of the site. The problem will
image rotator scripts either in PHP or Javascript is that, they rotate the images
from a
particular folder randomly. But when you validate, the image will not have alt tag
or a
title tag to
I always code by hand and my editor of choice is NoteTab Pro
(www.notetab.com). As well as Find and Replace it has a neat function which
strips (X)HTML out of markup leaving just text and script excerpts etc.
Having redesigned a couple of sites in this way, I have yet to trip it up.
Bryan Davis
I'm rebuilding a gardening magazine site to web standards and
assessibility - and I've almost got it working as I wish ...
HTML is at: http://www.bluemountainsgardener.info/index-try.htm
CSS is at: http://www.bluemountainsgardener.info/style-accessible.css
No skip nav yet, but the layout
John Penlington wrote:
The text line in the footer lies just below the black footer, not within it.
There's a positioning problem with the horizontal menu in the header.
I'd like to know a way of reducing the gap below the headers in the infoboxes
On the #footer p, try margin : 0;
On the
Many thanks, Owen,
With your suggestions, all three problems fixed.
You'll see the results at
http://www.bluemountainsgardener.info/index-try.htm
Your prompt response will help me sleep tonight (in Australia).
Cheers,
John Penlington
- Original Message -
From: Owen Gregory [EMAIL
On 21/07/2004, at 4:10 PM, Bert Doorn wrote:
G'day
Looks distinctly like a case of totally unnecessary to me but we have
a difference of opinion in the office...
Even if it was written as VDS, it would be an abbr(eviation): abbr
title=Vent Door SystemsVDS/abbr
Actually, VDS is an acronym of Vent
Gah...not this discussion again...
Acronyms are a subset of abbreviations. All acronyms are
abbreviations, but not all abbreviations are acronyms.
Now, once it comes to defining what an acronym is, there's
cultural/regional differences as well: some argue that
acronyms need to be pronounceable,
Hi all,
I'm trying to decide on a nice semantic way to mark-up a short (usually
only a few words) block of help text in the context of a web form. I
currently use a label to label the input, and a paragraph or div to
mark-up the help text:
form...
div class='formitem'
label
Justin wrote:
I'm trying to decide on a nice semantic way to mark-up a short (usually
only a few words) block of help text in the context of a web form.
The label element can contain inline elements (like input /). So you can wrap it
around the input in your example and perhaps remove the p
Hi Justin
I asked about this a couple weeks ago.
You can put a title on the label.
label for=arrivaldate title=Enter the day you plan on arriving to our lovely
hotelArrival datelabel
When the person puts their cursor over the label, they will get a box that pops up
with your label. It's valid
Maybe a slight stretch, but how about wrapping these related elements
(label, input, etc) up in their own fieldset, and using the legend
for that text (thus associating it with the (input and label within).
form...
fieldset
legendThis is the title of your news post
(does not accept HTML
Both Patrick and Ted made good suggestions. However, I'd
prefer to see the page in question before making Patrick's
suggestion. If the form is like some of mine, that simply
won't work.
The title option always works, but the user must know the
title is there before it can help them.
Your best
XHTML 2 draft is out. see below.
--
Masayasu Ishikawa wrote:
Hello,
After long editorial work, finally the sixth public Working Draft of
XHTML 2.0 is now available at:
http://www.w3.org/TR/2004/WD-xhtml2-20040722
The HTML Working Group thanks
There are a number of things that need to be considered:
1. title attribute content is not accessible to users who cannot use a
mouse (as the tool tip only appears on mouseover not onfocus)
2. the title attribute content is only available to a subset of screen
reading software (latest versions of
Hi Ted, all
Title attributes don't have to pop up in a tooltip, that's up to the
user agent. I'd suggest you do something like this...
label for=arrivaldateYour arrival date at Hotel WSGlabel
Also, user of fieldsets allow to you to control the appearance of
different parts of a form:
fieldset
Another question for all you clever folk in Standardsland, and I can't help but
feel that the answer will probably be something really simple. I can't find it
though.
If you go to the link below, you will see that there is an odd space between
the rows of tabs and the start of the content.
Damn,
Just when I thought I had a cool solution for adding titles to the labels Steven comes
along and
shoots a hole the size of Africa and Taiwan in my plan.
I need some coffee...
Ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, July 22, 2004
Brian Cummiskey wrote:
XHTML 2 draft is out.
--
Sixth public Working Draft of XHTML 2.0 is now available at:
http://www.w3.org/TR/2004/WD-xhtml2-20040722
In many ways it is as if they went back to what HTML was meant to be,
and improved
- Original Message -
From: Mordechai Peller
[...]
The worst part of all this is it'll be years before we'll be able to use
the new toys in any meaningful way.
You could already use them server-side, then transform them to
xhtml1.0 or 1.1 before serving them to the client, but
- Original Message -
From: Mordechai Peller
[...]
While transforming from XHTML 1.0 or 1.1 is a trivial task, from XHTML 2
to even 1.1 is not so. In some cases there's no equivalent (di), in
others there's more than one choice depending on the CSS (l = span, br,
li, p).
Yes, I'm
Thanks to everyone for their input, especially Steven insight into the
world of screen readers. My summation of all this is that the elements
need to appear in this order:
Label Text
Extended help
Input or widgets
I really like the idea of wrapping the label tag around the whole lot,
so that
a couple of questions, somewhat off
topic
Iwould like to capture an image of the the
whole html pagei.e. what is not
visible in the scroll region,so the image would capture something
likean "800 x 3000" region to be printed in
abrochure.
I am lookingfor an elegantCMS tool
which will
I would like to capture an image of the the whole html page i.e. what
is not visible in the scroll region, so the image would capture
something like an 800 x 3000 region to be printed in a brochure.
SnagIt is very cool and worth the $40
http://www.techsmith.com/products/snagit/default.asp
Xstandard is worth a look for using with browser based CMS
http://xstandard.com/default.asp
with regards
Steven Faulkner
Web Accessibility Consultant
National Information Library Service (NILS)
454 Glenferrie Road
Kooyong Victoria 3144
Phone: (613) 9864 9281
Fax: (613) 9864 9210
Email: [EMAIL
On Friday, Jul 23, 2004, at 13:44 Australia/Sydney, Roly wrote:
a couple of questions, somewhat off topic
I would like to capture an image of the the whole html page i.e. what
is not visible in the scroll region, so the image would capture
something like an 800 x 3000 region to be printed in
First Labels should not wrap the input. The elements
within the Label tag become the label. By wrapping the
input with the Label you are stating the input is part of
its own Label. That's wrong.
Using heading tags for font declarations is poor form and
fails to meet the standards. DIV is a
28 matches
Mail list logo
