hi, anyone know how to create a page like this one Coda is now Nova but it doesnt need a carousel action, just click the tab and the information pops up from a trigger layer? I dont know how to have the initial tab showing visible. any help greatly apprectiated. I’ll try and upload a link later. cheers
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I’ve used that effect before, here’s where I learned how to make it happen:
http://jqueryfordesigners.com/coda-popup-bubbles/
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I have an example document here that can create this using Protaculous, and as soon as Verizon fixes my T1 line, I’ll post it. I kinda think it’s already on my scripty sever, but since that’s offline until the T1 is back up, you can’t see it and I can’t find it either.
Walter
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
thanks guys, its maybe something much simpler I’m trying to do!
http://www.vmobilehair.com/index2.html
I want to make the tabs rollover and stick when the coloured area is on. I found a freeway tutorial under tabs but it doesnt fully explain how to use slave triggers and image maps. I’ve downloaded the manual to try and figure it out. if you know of any simple how to’s or a better way I’d be glad to look at them. thanks for your help!
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
http://scripty.walterdavisstudio.com/tabs/
See if this does what you’re looking for. The Freeway icon in the upper right corner is a download link to the file that creates it. You will need the current versions of:
…both available from ActionsForge, in order to use this document.
Walter
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
One thing I forgot to mention. The way this document is constructed, the only element that is actually in the page when it loads is the content of the first tab. If you need all of the tabs’ content to be in the page (for SEO or JavaScript-disabled accessibility reasons, primarily), then there is another way to construct the page that does not rely on lazy-loading the content the way this page does. Let me know if you need to see what the difference is in the code.
There are distinct page size (and thus loading time) improvements to be had in this construction, though, so you should weigh one priority against the other when considering which way to go.
Walter
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Walter id like to see the other way if you could please, it would be a
lot easier for EE I think
thank you
Adam
On 16 Jul 2010, at 14:58, waltd wrote:
One thing I forgot to mention. The way this document is constructed,
the only element that is actually in the page when it loads is the
content of the first tab. If you need all of the tabs’ content to be
in the page (for SEO or JavaScript-disabled accessibility reasons,
primarily), then there is another way to construct the page that
does not rely on lazy-loading the content the way this page does.
Let me know if you need to see what the difference is in the code.There are distinct page size (and thus loading time) improvements to
be had in this construction, though, so you should weigh one
priority against the other when considering which way to go.Walter
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Okay, download the document again, and look at the page called All In.
If you want to preview it on the Web, it’s at All-In
It should look and behave identically to the original example page.
Walter
On Jul 16, 2010, at 10:12 AM, Adam Harras wrote:
Walter id like to see the other way if you could please, it would be
a lot easier for EE I thinkthank you
Adam
On 16 Jul 2010, at 14:58, waltd wrote:
One thing I forgot to mention. The way this document is
constructed, the only element that is actually in the page when
it loads is the content of the first tab. If you need all of the
tabs’ content to be in the page (for SEO or JavaScript-disabled
accessibility reasons, primarily), then there is another way to
construct the page that does not rely on lazy-loading the content
the way this page does. Let me know if you need to see what the
difference is in the code.There are distinct page size (and thus loading time) improvements
to be had in this construction, though, so you should weigh one
priority against the other when considering which way to go.Walter
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
thanks walter, the only other wish would be to make the tabs have a rollover as well please?! cheers
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Well, that would be easy in non IE browsers, just make a style called
#tabs h2:hover and add your desired background-color to it. But IE
won’t accept that the :hover pseudo-selector is valid for all
elements, not just A tags, and so it ignores that and your hover
effects won’t work in that browser.
The work-around would be to add the following lines to your Function
Body in Protaculous, at the very bottom:
$$('#tabs h2').each(function(elm){
elm.observe('mouseover',function(evt){
this['_bak'] = this.getStyle('background-color');
this.setStyle('background-color:#ff9');
});
elm.observe('mouseout', function(evt){
this.setStyle('background-color:' + this._bak);
});
});
Change #ff9 to your desired hover color. And don’t add the :hover
style if you do this, it will just confuse things (might cause the
element to memoize the wrong background-color).
Walter
On Jul 16, 2010, at 10:33 AM, richie hume wrote:
thanks walter, the only other wish would be to make the tabs have a
rollover as well please?! cheers
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi Walter
I have been playing with your examples and was confused when my ‘carrier’ corners weren’t radiused.
I removed the CSS3 corner action from ‘carrier’ published, reapplied and published again with the same settings as you had ie 0,9,9,9 - but no radiused corners.
However I found that if I applied the corner radius as 9,9,9,9 and published it worked with a radius on all corners. Then when I changed the first one back to 0 and republished it worked OK.
Bug?
David
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
No idea. I have never had a problem with that Action. If you had
installed it on your computer, and opened my document, you might have
hit a different version embedded in my document. Freeway can be odd
about that.
Walter
On Jul 17, 2010, at 8:27 PM, DeltaDave wrote:
Hi Walter
I have been playing with your examples and was confused when my
‘carrier’ corners weren’t radiused.
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
hi, I ended up doing it the old school way I think! which all works great, however as you’ll see I had to add an extra trigger show/hide layer so that about me was showing initially. the only problem is that I could only make it so that price list triggered it off not all 3 tabs. so if the user doesnt click that tab first but one of the other 2 then the text overlays until price list tab is clicked. is there any way to manipulate the code to say maybe if aqua 2,3 or 4 are clicked? any advice greatly appreciated. and thanks for the help with the carousel which works great I think.
http://www.vmobilehair.com/index2.html#
cheers
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
hi, connected to this I showed a friend who is a professional, he thought the code wasn’t good, as the CSS is better in its own doc. is this something I can do or are there any quick fixes which would make it better? cheers
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
In the Document Setup dialog, there is an option on the Output tab
that lets you shift the CSS to an external file. Note that this will
move all the text definitions used in your site into a common file. It
will not move the layout specs for individual page elements, so there
will still be some inline CSS in your page. But that big lump of code
at the very top of the page will be gone, which is nice.
Your friend is correct in once sense, but he’s definitely counting
angels on pinheads when he’s doing so. If you have a site that shares
an enormous amount of common layout code (a highly templated site,
say) then it makes a lot of sense to move as much of that into a
single file which can be cached by the browser, as this speeds up
subsequent page views.
Freeway is designed to make individual pages, each completely unique,
and so it uses inline CSS for the individual page elements. On a
highly-repetitive site, this does contribute to a very slight bloat on
those individual pages, but it’s a trade-off, like most things are.
In my experience, there are two types of “strict” Web developers.
There are those who are strict because it makes their work easier and
more predictable, and there are those who check it off a list as
something you MUST have, without thinking the whole thing through to
its logical conclusion. I’m not pointing fingers here, and I’m
definitely not changing the subject. If your goal is to complete the
checklist, then Freeway is the wrong tool for the job as it currently
stands.
You can point your friend to the W3C validator, where your page will
validate nicely. You can also point your friend to the Yslow plugin
for Firefox, which will knock the site for not having all of its CSS
and JavaScript externalized, but will give it good marks for overall
speed.
sidebar: Long ago, there was an early Web application called
WebGarage, which would slurp down whatever page you pointed it to, and
perform some performance evaluations on it (mostly based on file size
overall). In those days, it was common for a Freeway-generated site to
be in the very high 90th percentiles, like 97 or 98 for overall
efficiency. By contrast, hand-coded sites rarely climbed above 80, and
GoLive (remember that?) would be in the weeds around 60.
It’s really a matter of which goal you are aiming for – the technical
merit of having every checkbox filled on your chart, or the very human
merit of having an easier and more productive time of developing. In
the end, networks get faster and computers get more powerful every
single day. Try as we might, we are not going to choke the tubes of
the interweb anytime soon. Just as premature optimization is the root
of all evil, so too is optimizing the wrong thing. When Otto Daimler
and friends set out to make the car, they did not after all improve on
the horse.
Walter
On Jul 19, 2010, at 8:42 AM, richie hume wrote:
hi, connected to this I showed a friend who is a professional, he
thought the code wasn’t good, as the CSS is better in its own doc.
is this something I can do or are there any quick fixes which would
make it better? cheers
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Walter
Is the CSS-styles now outdated in FW5, do I just change my file in the
output tab if I wish to have a external CSS file or have I missed the
point. Three of my sites in FW 5 and using EE are using the CSS-styles
action and each time I make any changes or add a new style I have to
edit the CSS-Styles action after copying from my source the newly
created styles it would be nice if I didnt have to.
many thanks
Adam
On 19 Jul 2010, at 14:07, Walter Lee Davis wrote:
In the Document Setup dialog, there is an option on the Output tab
that lets you shift the CSS to an external file. Note that this will
move all the text definitions used in your site into a common file.
It will not move the layout specs for individual page elements, so
there will still be some inline CSS in your page. But that big lump
of code at the very top of the page will be gone, which is nice.Your friend is correct in once sense, but he’s definitely counting
angels on pinheads when he’s doing so. If you have a site that
shares an enormous amount of common layout code (a highly templated
site, say) then it makes a lot of sense to move as much of that into
a single file which can be cached by the browser, as this speeds up
subsequent page views.Freeway is designed to make individual pages, each completely
unique, and so it uses inline CSS for the individual page elements.
On a highly-repetitive site, this does contribute to a very slight
bloat on those individual pages, but it’s a trade-off, like most
things are.In my experience, there are two types of “strict” Web developers.
There are those who are strict because it makes their work easier
and more predictable, and there are those who check it off a list as
something you MUST have, without thinking the whole thing through to
its logical conclusion. I’m not pointing fingers here, and I’m
definitely not changing the subject. If your goal is to complete the
checklist, then Freeway is the wrong tool for the job as it
currently stands.You can point your friend to the W3C validator, where your page will
validate nicely. You can also point your friend to the Yslow plugin
for Firefox, which will knock the site for not having all of its CSS
and JavaScript externalized, but will give it good marks for overall
speed.sidebar: Long ago, there was an early Web application called
WebGarage, which would slurp down whatever page you pointed it to,
and perform some performance evaluations on it (mostly based on file
size overall). In those days, it was common for a Freeway-generated
site to be in the very high 90th percentiles, like 97 or 98 for
overall efficiency. By contrast, hand-coded sites rarely climbed
above 80, and GoLive (remember that?) would be in the weeds around 60.It’s really a matter of which goal you are aiming for – the
technical merit of having every checkbox filled on your chart, or
the very human merit of having an easier and more productive time of
developing. In the end, networks get faster and computers get more
powerful every single day. Try as we might, we are not going to
choke the tubes of the interweb anytime soon. Just as premature
optimization is the root of all evil, so too is optimizing the wrong
thing. When Otto Daimler and friends set out to make the car, they
did not after all improve on the horse.Walter
On Jul 19, 2010, at 8:42 AM, richie hume wrote:
hi, connected to this I showed a friend who is a professional, he
thought the code wasn’t good, as the CSS is better in its own doc.
is this something I can do or are there any quick fixes which would
make it better? cheers
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
thanks walter, quite a lot to take in there! I just put it into the W3C validator and it had 2 errors can this be fixed in freeway? also did you get a chance to read the post before that one about manipulating the code to make trigger the hide layer if any of the aqua 2,3 or 4 were clicked? thanks
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I’m not sure what your CSS Styles Action is doing, but let me spell
out what Freeway 5 currently does w/r/t CSS:
###Document Setup / Output / Use External Style sheets OFF:
All CSS relevant for the current page is embedded in the current page.
All positioned elements (usually DIVs) are styled with inline
(style=“foo:bar”) attributes within their code inside the body of the
page. All text styles are defined in the head of the page, inside a
style tag.
###Document Setup / Output/ Use External Style sheets ON:
Only positioning CSS code, and CSS added by Actions (which do not have
access to the external stylesheets) are placed within the page head in
a style tag. All text styles (and anything else created using the
Styles palette in Freeway’s Design view) are moved off to an external
stylesheet, which is linked to the head of the page.
###EE, or any other CMS:
Because you are using EE, your mileage will vary – a lot. Yours is a
highly templated environment, where you need to have absolute control
over which part of the page includes the style references or styles
themselves, because the inner elements cannot contain any style tags
themselves, or else the composite page rendered by EE will become
invalid. I haven’t used this particular combo myself, but I have
written the rough analogue of EE itself, many many times over. I’m
well aware of the traps that lie within building your templates in
Freeway and then consuming them inside a content management system. My
guess is that this CSS Action is needed to populate styles used on the
internal template elements into the parent page, so those styles will
be present and accounted for when they are asked for by name.
So for you, I am guessing that you might not need the CSS Action if
you are also using External Style sheets in Freeway. The default
behavior for Freeway is to put all text styles, no matter where they
are used, into the one and only stylesheet created for the site. So
you can get away with partials (fragments of HTML used within a larger
template system) by simply switching on the External option. But if
this Action is also moving the inline CSS into an external sheet, thus
cleaning up your generated code and making it more Buzzword-Compliant,
then you’re still in the same boat you were regardless how you change
that setting.
Walter
On Jul 19, 2010, at 9:32 AM, adam harras wrote:
Walter
Is the CSS-styles now outdated in FW5, do I just change my file in
the output tab if I wish to have a external CSS file or have I
missed the point. Three of my sites in FW 5 and using EE are using
the CSS-styles action and each time I make any changes or add a new
style I have to edit the CSS-Styles action after copying from my
source the newly created styles it would be nice if I didnt have to.many thanks
Adam
On 19 Jul 2010, at 14:07, Walter Lee Davis wrote:
In the Document Setup dialog, there is an option on the Output tab
that lets you shift the CSS to an external file. Note that this
will move all the text definitions used in your site into a common
file. It will not move the layout specs for individual page
elements, so there will still be some inline CSS in your page. But
that big lump of code at the very top of the page will be gone,
which is nice.Your friend is correct in once sense, but he’s definitely counting
angels on pinheads when he’s doing so. If you have a site that
shares an enormous amount of common layout code (a highly templated
site, say) then it makes a lot of sense to move as much of that
into a single file which can be cached by the browser, as this
speeds up subsequent page views.Freeway is designed to make individual pages, each completely
unique, and so it uses inline CSS for the individual page elements.
On a highly-repetitive site, this does contribute to a very slight
bloat on those individual pages, but it’s a trade-off, like most
things are.In my experience, there are two types of “strict” Web developers.
There are those who are strict because it makes their work easier
and more predictable, and there are those who check it off a list
as something you MUST have, without thinking the whole thing
through to its logical conclusion. I’m not pointing fingers here,
and I’m definitely not changing the subject. If your goal is to
complete the checklist, then Freeway is the wrong tool for the job
as it currently stands.You can point your friend to the W3C validator, where your page
will validate nicely. You can also point your friend to the Yslow
plugin for Firefox, which will knock the site for not having all of
its CSS and JavaScript externalized, but will give it good marks
for overall speed.sidebar: Long ago, there was an early Web application called
WebGarage, which would slurp down whatever page you pointed it to,
and perform some performance evaluations on it (mostly based on
file size overall). In those days, it was common for a Freeway-
generated site to be in the very high 90th percentiles, like 97 or
98 for overall efficiency. By contrast, hand-coded sites rarely
climbed above 80, and GoLive (remember that?) would be in the weeds
around 60.It’s really a matter of which goal you are aiming for – the
technical merit of having every checkbox filled on your chart, or
the very human merit of having an easier and more productive time
of developing. In the end, networks get faster and computers get
more powerful every single day. Try as we might, we are not going
to choke the tubes of the interweb anytime soon. Just as premature
optimization is the root of all evil, so too is optimizing the
wrong thing. When Otto Daimler and friends set out to make the car,
they did not after all improve on the horse.Walter
On Jul 19, 2010, at 8:42 AM, richie hume wrote:
hi, connected to this I showed a friend who is a professional, he
thought the code wasn’t good, as the CSS is better in its own doc.
is this something I can do or are there any quick fixes which
would make it better? cheers
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks Walter
The CSS action is only being used for Styles of text in these sites so
I think from you answer I can turn it off and use the built in Freeway
output option, I think this will then make it so much easier if Im
tweaking text styles
As usual thank you for such a thorough explanation Walter
kind regards
Adam
On 19 Jul 2010, at 14:59, Walter Lee Davis wrote:
I’m not sure what your CSS Styles Action is doing, but let me spell
out what Freeway 5 currently does w/r/t CSS:###Document Setup / Output / Use External Style sheets OFF:
All CSS relevant for the current page is embedded in the current
page. All positioned elements (usually DIVs) are styled with inline
(style=“foo:bar”) attributes within their code inside the body of
the page. All text styles are defined in the head of the page,
inside a style tag.###Document Setup / Output/ Use External Style sheets ON:
Only positioning CSS code, and CSS added by Actions (which do not
have access to the external stylesheets) are placed within the page
head in a style tag. All text styles (and anything else created
using the Styles palette in Freeway’s Design view) are moved off to
an external stylesheet, which is linked to the head of the page.###EE, or any other CMS:
Because you are using EE, your mileage will vary – a lot. Yours is
a highly templated environment, where you need to have absolute
control over which part of the page includes the style references or
styles themselves, because the inner elements cannot contain any
style tags themselves, or else the composite page rendered by EE
will become invalid. I haven’t used this particular combo myself,
but I have written the rough analogue of EE itself, many many times
over. I’m well aware of the traps that lie within building your
templates in Freeway and then consuming them inside a content
management system. My guess is that this CSS Action is needed to
populate styles used on the internal template elements into the
parent page, so those styles will be present and accounted for when
they are asked for by name.So for you, I am guessing that you might not need the CSS Action if
you are also using External Style sheets in Freeway. The default
behavior for Freeway is to put all text styles, no matter where they
are used, into the one and only stylesheet created for the site. So
you can get away with partials (fragments of HTML used within a
larger template system) by simply switching on the External option.
But if this Action is also moving the inline CSS into an external
sheet, thus cleaning up your generated code and making it more
Buzzword-Compliant, then you’re still in the same boat you were
regardless how you change that setting.Walter
On Jul 19, 2010, at 9:32 AM, adam harras wrote:
Walter
Is the CSS-styles now outdated in FW5, do I just change my file in
the output tab if I wish to have a external CSS file or have I
missed the point. Three of my sites in FW 5 and using EE are using
the CSS-styles action and each time I make any changes or add a new
style I have to edit the CSS-Styles action after copying from my
source the newly created styles it would be nice if I didnt have to.many thanks
Adam
On 19 Jul 2010, at 14:07, Walter Lee Davis wrote:
In the Document Setup dialog, there is an option on the Output tab
that lets you shift the CSS to an external file. Note that this
will move all the text definitions used in your site into a common
file. It will not move the layout specs for individual page
elements, so there will still be some inline CSS in your page. But
that big lump of code at the very top of the page will be gone,
which is nice.Your friend is correct in once sense, but he’s definitely counting
angels on pinheads when he’s doing so. If you have a site that
shares an enormous amount of common layout code (a highly
templated site, say) then it makes a lot of sense to move as much
of that into a single file which can be cached by the browser, as
this speeds up subsequent page views.Freeway is designed to make individual pages, each completely
unique, and so it uses inline CSS for the individual page
elements. On a highly-repetitive site, this does contribute to a
very slight bloat on those individual pages, but it’s a trade-off,
like most things are.In my experience, there are two types of “strict” Web developers.
There are those who are strict because it makes their work easier
and more predictable, and there are those who check it off a list
as something you MUST have, without thinking the whole thing
through to its logical conclusion. I’m not pointing fingers here,
and I’m definitely not changing the subject. If your goal is to
complete the checklist, then Freeway is the wrong tool for the job
as it currently stands.You can point your friend to the W3C validator, where your page
will validate nicely. You can also point your friend to the Yslow
plugin for Firefox, which will knock the site for not having all
of its CSS and JavaScript externalized, but will give it good
marks for overall speed.sidebar: Long ago, there was an early Web application called
WebGarage, which would slurp down whatever page you pointed it to,
and perform some performance evaluations on it (mostly based on
file size overall). In those days, it was common for a Freeway-
generated site to be in the very high 90th percentiles, like 97 or
98 for overall efficiency. By contrast, hand-coded sites rarely
climbed above 80, and GoLive (remember that?) would be in the
weeds around 60.It’s really a matter of which goal you are aiming for – the
technical merit of having every checkbox filled on your chart, or
the very human merit of having an easier and more productive time
of developing. In the end, networks get faster and computers get
more powerful every single day. Try as we might, we are not going
to choke the tubes of the interweb anytime soon. Just as premature
optimization is the root of all evil, so too is optimizing the
wrong thing. When Otto Daimler and friends set out to make the
car, they did not after all improve on the horse.Walter
On Jul 19, 2010, at 8:42 AM, richie hume wrote:
hi, connected to this I showed a friend who is a professional, he
thought the code wasn’t good, as the CSS is better in its own
doc. is this something I can do or are there any quick fixes
which would make it better? cheers
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Can you post a link to your page? Without seeing the particular error,
it’s impossible to say where it’s coming from or whether it’s fixable.
(Most things can be fixed.)
As far as using the Show Hide Actions to do these tabs, I’m not sure
that’s the best tool for the job. The tabs solution I posted does not
care which tab you click first, and always hides all but the first tab
when you load the page. I would encourage you to work through the
example document, adapt it to your layout, and use that instead of a
patchwork of duplicate content and individual Actions. The end result
will be both more accessible (to non-sighted visitors) and easier on
the browser, and easier on you to maintain and to lay out in the first
place.
Walter
On Jul 19, 2010, at 9:57 AM, richie hume wrote:
thanks walter, quite a lot to take in there! I just put it into the
W3C validator and it had 2 errors can this be fixed in freeway? also
did you get a chance to read the post before that one about
manipulating the code to make trigger the hide layer if any of the
aqua 2,3 or 4 were clicked? thanks
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options