I have more then 20 slave layers I want to show on a page. How does one go about a work around for this problem?I have simple roll overs that trigger these slaves.
I know this must be possible but can not figure this on out? Any guidance or wisdom is welcomed.
I have more then 20 slave layers I want to show on a page. How does one go about a work around for this problem?I have simple roll overs that trigger these slaves.
You have all the “color” group options, too. If you can structure your page so that you have groups of 20 images, then you can have 10 groups of 20, or 200 images total. Which is going to be The World’s Heaviest Page. So what I am really urging you to do is to embrace this limitation, and stick to 20 pictures on your page, and multiple pages to handle the overflow. Your users will thank you.
I would try to stay below 300K if you can. Even on a fast net
connection, that’s a long download and your user needs to be
sufficiently motivated to wait while it loads.
Making the additional page means that you provide the user with a way
to narrow down their selection. Think of it like folders in your hard
drive. As you choose a folder, you see a list of sub-folders that
(hopefully) are related to their parent. If you can arrange your
photos in a hierarchy of one kind or another, then you let someone
who is browsing your site have a clue about where they are going.
They make a choice, which narrows their options, then another choice,
which further narrows them, until they end up in a list that can’t be
divided any further (and hopefully contains 20 or fewer members).
Walter
On May 19, 2008, at 10:54 AM, shybuckstudio wrote:
thank you Walter…I’m not aware of what a heavy page might
be.Could you suggest a ball park range for a page that is too
combersum?
Also is making the additional page something that helps with
download time?