From mark at novemberborn.net  Sun Feb  4 20:44:56 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Sun, 4 Feb 2007 21:44:56 +0100
Subject: [sIFR3-dev] Small update / Geneva
Message-ID: <DF79EC67-39AD-4E22-9324-591E8F694B0D@novemberborn.net>

Hey all,

Work on sIFR is as slow as work on meaningless university projects is  
high. One point of interest is that I fixed the issue where IE would  
mess up rendering the Flash movies if the innerHTML of an ancestor of  
a movie was edited. This fix is included in r213.

I'll be in Geneva from Tuesday - Sunday morning for LIFT. If you want  
to meet, let me know so we can make sure not to miss each other in  
the 400+ crowd.

Take care,

--
Mark


From amclin at kaadesigngroup.com  Sun Feb  4 21:56:00 2007
From: amclin at kaadesigngroup.com (amclin at kaadesigngroup.com)
Date: Sun, 4 Feb 2007 13:56:00 -0800
Subject: [sIFR3-dev] Possible solution to 'stuck' mouseovers
Message-ID: <20070204215617.E7553CA2BA9@kaadesigngroup.com>

While in the shower I had a brainstorm idea about solving the problem where mouseovers inside sIFR text gets "stuck".

Mark has said it seems like there isn't enough room around the text inside the Flash... Or that users are mousing off too quickly.

Here's my idea. What about increasing the framerate of the Flash file? I can't test right now, but if the file is set to the Flash default of 12fps, then 30 or 45 fps might do the trick.

If someone can test this I'd love to hear if it works.

- Anthony



From mark at novemberborn.net  Sun Feb  4 22:22:27 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Sun, 4 Feb 2007 23:22:27 +0100
Subject: [sIFR3-dev] Possible solution to 'stuck' mouseovers
In-Reply-To: <20070204215617.E7553CA2BA9@kaadesigngroup.com>
References: <20070204215617.E7553CA2BA9@kaadesigngroup.com>
Message-ID: <6092EEA0-43E5-474F-9FE1-095E5A7036A7@novemberborn.net>

On Feb 4, 2007, at 10:56 PM, <amclin at kaadesigngroup.com> wrote:
> While in the shower I had a brainstorm idea about solving the  
> problem where mouseovers inside sIFR text gets "stuck".

Ideas from the shower are always good.
> Here's my idea. What about increasing the framerate of the Flash  
> file? I can't test right now, but if the file is set to the Flash  
> default of 12fps, then 30 or 45 fps might do the trick.

That might work, though I'm worried it'll increase the CPU usage of  
the Flash movies. My plan was to catch the mouseout from the webpage  
itself, and tell the Flash movie to reset the text. Have yet to try  
it out, though. Thanks for the idea!

--
Mark


From mark at novemberborn.net  Mon Feb  5 13:10:29 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Mon, 5 Feb 2007 14:10:29 +0100
Subject: [sIFR3-dev] Possible solution to 'stuck' mouseovers
In-Reply-To: <6092EEA0-43E5-474F-9FE1-095E5A7036A7@novemberborn.net>
References: <20070204215617.E7553CA2BA9@kaadesigngroup.com>
	<6092EEA0-43E5-474F-9FE1-095E5A7036A7@novemberborn.net>
Message-ID: <6167DE39-2682-48D0-8069-F4F1B6311A87@novemberborn.net>

On Feb 4, 2007, at 11:22 PM, Mark Wubben wrote:
> That might work, though I'm worried it'll increase the CPU usage of
> the Flash movies. My plan was to catch the mouseout from the webpage
> itself, and tell the Flash movie to reset the text. Have yet to try
> it out, though.

I'm in the train right now, hacking away on sIFR. I implemented my  
workaround and it works great in Firefox and Safari. Opera isn't  
playing along, but that seems to be an issue with how Opera handles  
Flash. No MacBook for me yet, so haven't checked in IE.

This will go up as r215, should be today if I don't forget.

--
Mark


From branstrom at gmail.com  Mon Feb  5 16:48:02 2007
From: branstrom at gmail.com (=?ISO-8859-1?Q?Fredrik_Br=E4nstr=F6m?=)
Date: Mon, 5 Feb 2007 17:48:02 +0100
Subject: [sIFR3-dev] Possible solution to 'stuck' mouseovers
In-Reply-To: <6167DE39-2682-48D0-8069-F4F1B6311A87@novemberborn.net>
References: <20070204215617.E7553CA2BA9@kaadesigngroup.com>
	<6092EEA0-43E5-474F-9FE1-095E5A7036A7@novemberborn.net>
	<6167DE39-2682-48D0-8069-F4F1B6311A87@novemberborn.net>
Message-ID: <22410ce30702050848j44b4dadka4be59465529569b@mail.gmail.com>

Oh, those showers and train rides...

Good riddance. :)



On 2/5/07, Mark Wubben <mark at novemberborn.net> wrote:
>
> On Feb 4, 2007, at 11:22 PM, Mark Wubben wrote:
> > That might work, though I'm worried it'll increase the CPU usage of
> > the Flash movies. My plan was to catch the mouseout from the webpage
> > itself, and tell the Flash movie to reset the text. Have yet to try
> > it out, though.
>
> I'm in the train right now, hacking away on sIFR. I implemented my
> workaround and it works great in Firefox and Safari. Opera isn't
> playing along, but that seems to be an issue with how Opera handles
> Flash. No MacBook for me yet, so haven't checked in IE.
>
> This will go up as r215, should be today if I don't forget.
>
> --
> Mark
> _______________________________________________
> sifr3-dev mailing list
> sifr3-dev at lists.novemberborn.net
> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev
>



-- 
Fredrik Br?nstr?m
http://fredrik.branstrom.nu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.novemberborn.net/pipermail/sifr3-dev/attachments/20070205/9afe618d/attachment.html>

From amclin at kaadesigngroup.com  Mon Feb  5 17:08:25 2007
From: amclin at kaadesigngroup.com (Anthony McLin)
Date: Mon, 05 Feb 2007 09:08:25 -0800
Subject: [sIFR3-dev] Possible solution to 'stuck' mouseovers
In-Reply-To: <6167DE39-2682-48D0-8069-F4F1B6311A87@novemberborn.net>
References: <20070204215617.E7553CA2BA9@kaadesigngroup.com>
	<6092EEA0-43E5-474F-9FE1-095E5A7036A7@novemberborn.net>
	<6167DE39-2682-48D0-8069-F4F1B6311A87@novemberborn.net>
Message-ID: <45C76489.1060404@kaadesigngroup.com>

Would the jscript workaround method work on hovers within the sIFR text? 
or only when the entire sIFR is a link?

-Anthony

Mark Wubben wrote:
> On Feb 4, 2007, at 11:22 PM, Mark Wubben wrote:
>> That might work, though I'm worried it'll increase the CPU usage of
>> the Flash movies. My plan was to catch the mouseout from the webpage
>> itself, and tell the Flash movie to reset the text. Have yet to try
>> it out, though.
>
> I'm in the train right now, hacking away on sIFR. I implemented my 
> workaround and it works great in Firefox and Safari. Opera isn't 
> playing along, but that seems to be an issue with how Opera handles 
> Flash. No MacBook for me yet, so haven't checked in IE.
>
> This will go up as r215, should be today if I don't forget.
>
> -- 
> Mark
>


-- 
Anthony McLin
Senior Web Developer
amclin at kaadesigngroup.com
T  310.821.1400 ext. 266
F  310.821.1440

KAA Design Group, Inc.
4201 Redwood Avenue
Los Angeles, CA 90066

ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
http://www.kaadesigngroup.com



From mark at novemberborn.net  Mon Feb  5 18:00:38 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Mon, 5 Feb 2007 19:00:38 +0100
Subject: [sIFR3-dev] Possible solution to 'stuck' mouseovers
In-Reply-To: <45C76489.1060404@kaadesigngroup.com>
References: <20070204215617.E7553CA2BA9@kaadesigngroup.com>
	<6092EEA0-43E5-474F-9FE1-095E5A7036A7@novemberborn.net>
	<6167DE39-2682-48D0-8069-F4F1B6311A87@novemberborn.net>
	<45C76489.1060404@kaadesigngroup.com>
Message-ID: <B7DA0AA1-24AC-4620-9217-3318BFCD54C0@novemberborn.net>

On Feb 5, 2007, at 6:08 PM, Anthony McLin wrote:

> Would the jscript workaround method work on hovers within the sIFR  
> text?
> or only when the entire sIFR is a link?

Whenever there's a link. It switches on when it finds a `:hover`  
string in the CSS.

--
Mark


From amclin at kaadesigngroup.com  Tue Feb 13 18:41:14 2007
From: amclin at kaadesigngroup.com (Anthony McLin)
Date: Tue, 13 Feb 2007 10:41:14 -0800
Subject: [sIFR3-dev] Possible solution to 'stuck' mouseovers
In-Reply-To: <6092EEA0-43E5-474F-9FE1-095E5A7036A7@novemberborn.net>
References: <20070204215617.E7553CA2BA9@kaadesigngroup.com>
	<6092EEA0-43E5-474F-9FE1-095E5A7036A7@novemberborn.net>
Message-ID: <45D2064A.8090600@kaadesigngroup.com>

Well, I finally got around to testing it, and it appears that simply 
increasing the Flash framerate doesn't help.... it was worth a try...

-Anthony

Mark Wubben wrote:
> On Feb 4, 2007, at 10:56 PM, <amclin at kaadesigngroup.com> wrote:
>> While in the shower I had a brainstorm idea about solving the problem 
>> where mouseovers inside sIFR text gets "stuck".
>
> Ideas from the shower are always good.
>> Here's my idea. What about increasing the framerate of the Flash 
>> file? I can't test right now, but if the file is set to the Flash 
>> default of 12fps, then 30 or 45 fps might do the trick.
>
> That might work, though I'm worried it'll increase the CPU usage of 
> the Flash movies. My plan was to catch the mouseout from the webpage 
> itself, and tell the Flash movie to reset the text. Have yet to try it 
> out, though. Thanks for the idea!
>
> -- 
> Mark
>


-- 
Anthony McLin
Senior Web Developer
amclin at kaadesigngroup.com
T  310.821.1400 ext. 266
F  310.821.1440

KAA Design Group, Inc.
4201 Redwood Avenue
Los Angeles, CA 90066

ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
http://www.kaadesigngroup.com



From amclin at kaadesigngroup.com  Tue Feb 13 18:44:08 2007
From: amclin at kaadesigngroup.com (Anthony McLin)
Date: Tue, 13 Feb 2007 10:44:08 -0800
Subject: [sIFR3-dev] Selectable text
Message-ID: <45D206F8.7070602@kaadesigngroup.com>

Is there a way to turn off the selectable attribute for sIFR text 
without doing it in the Flash file previous to publishing?

I ask because I'm working on a complex menu system and the only way I 
can use the sIFR is to replace at the anchor selector which means that 
my links end up getting the select text cursor instead of the hand cursor.

Perhaps this is something that can be achieved through the new 
Flash<->Javascript framework?

-Anthony

-- 
Anthony McLin
Senior Web Developer
amclin at kaadesigngroup.com
T  310.821.1400 ext. 266
F  310.821.1440

KAA Design Group, Inc.
4201 Redwood Avenue
Los Angeles, CA 90066

ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
http://www.kaadesigngroup.com



From mark at novemberborn.net  Tue Feb 13 19:05:27 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Tue, 13 Feb 2007 20:05:27 +0100
Subject: [sIFR3-dev] Selectable text
In-Reply-To: <45D206F8.7070602@kaadesigngroup.com>
References: <45D206F8.7070602@kaadesigngroup.com>
Message-ID: <7B265426-8C82-4A0D-BF50-DF9C88EAFC2A@novemberborn.net>

I'm a bit reluctant to do this, as it's yet another way to harm  
usability. On the other hand, making the selections in Flash isn't  
the greatest thing anyway. I'm just worried about people who'll use  
it without seeing the bigger picture.

Wouldn't disabling the selection result in showing the pointer,  
instead of the hand cursor? And are you sure you want to use sIFR for  
menus? ;-)

On Feb 13, 2007, at 7:44 PM, Anthony McLin wrote:

> Is there a way to turn off the selectable attribute for sIFR text
> without doing it in the Flash file previous to publishing?
>
> I ask because I'm working on a complex menu system and the only way I
> can use the sIFR is to replace at the anchor selector which means that
> my links end up getting the select text cursor instead of the hand  
> cursor.
>
> Perhaps this is something that can be achieved through the new
> Flash<->Javascript framework?
>
> -Anthony
>
> -- 
> Anthony McLin
> Senior Web Developer
> amclin at kaadesigngroup.com
> T  310.821.1400 ext. 266
> F  310.821.1440
>
> KAA Design Group, Inc.
> 4201 Redwood Avenue
> Los Angeles, CA 90066
>
> ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
> http://www.kaadesigngroup.com
>
> _______________________________________________
> sifr3-dev mailing list
> sifr3-dev at lists.novemberborn.net
> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev



From mark at novemberborn.net  Tue Feb 13 20:11:55 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Tue, 13 Feb 2007 21:11:55 +0100
Subject: [sIFR3-dev] Selectable text
In-Reply-To: <45D20DD6.4020405@kaadesigngroup.com>
References: <45D206F8.7070602@kaadesigngroup.com>
	<7B265426-8C82-4A0D-BF50-DF9C88EAFC2A@novemberborn.net>
	<45D20DD6.4020405@kaadesigngroup.com>
Message-ID: <C0140338-FF23-408E-B5C7-2953442184F8@novemberborn.net>

On Feb 13, 2007, at 8:13 PM, Anthony McLin wrote:
> Hmmm... didn't think it would do the pointer, but that's something  
> I guess I can test. And no I don't really want to use sIFR for  
> menus, but the alternative is image-based text and the designer is  
> not flexible on the font choice. Image-based menu items isn't the  
> greatest idea for a CMS.
>
> I understand the useability issues, and I agree that in most cases  
> this kind of functionality would be a bad thing. That's why I was  
> wondering if it could be accessed through the javascript  
> interaction rather than it be a sIFR property.

It's probably better to do it through sIFR itself. I'll see what I  
can do.

--
Mark


From amclin at kaadesigngroup.com  Tue Feb 13 20:24:13 2007
From: amclin at kaadesigngroup.com (Anthony McLin)
Date: Tue, 13 Feb 2007 12:24:13 -0800
Subject: [sIFR3-dev] Selectable text
In-Reply-To: <C0140338-FF23-408E-B5C7-2953442184F8@novemberborn.net>
References: <45D206F8.7070602@kaadesigngroup.com>
	<7B265426-8C82-4A0D-BF50-DF9C88EAFC2A@novemberborn.net>
	<45D20DD6.4020405@kaadesigngroup.com>
	<C0140338-FF23-408E-B5C7-2953442184F8@novemberborn.net>
Message-ID: <45D21E6D.7040509@kaadesigngroup.com>

Sorry to keep asking for difficult weird things.... but thank you very 
very much.

Mark Wubben wrote:
> On Feb 13, 2007, at 8:13 PM, Anthony McLin wrote:
>> Hmmm... didn't think it would do the pointer, but that's something I 
>> guess I can test. And no I don't really want to use sIFR for menus, 
>> but the alternative is image-based text and the designer is not 
>> flexible on the font choice. Image-based menu items isn't the 
>> greatest idea for a CMS.
>>
>> I understand the useability issues, and I agree that in most cases 
>> this kind of functionality would be a bad thing. That's why I was 
>> wondering if it could be accessed through the javascript interaction 
>> rather than it be a sIFR property.
>
> It's probably better to do it through sIFR itself. I'll see what I can 
> do.
>
> -- 
> Mark
>


-- 
Anthony McLin
Senior Web Developer
amclin at kaadesigngroup.com
T  310.821.1400 ext. 266
F  310.821.1440

KAA Design Group, Inc.
4201 Redwood Avenue
Los Angeles, CA 90066

ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
http://www.kaadesigngroup.com



From amclin at kaadesigngroup.com  Tue Feb 13 22:52:46 2007
From: amclin at kaadesigngroup.com (Anthony McLin)
Date: Tue, 13 Feb 2007 14:52:46 -0800
Subject: [sIFR3-dev] Selectable text
In-Reply-To: <7B265426-8C82-4A0D-BF50-DF9C88EAFC2A@novemberborn.net>
References: <45D206F8.7070602@kaadesigngroup.com>
	<7B265426-8C82-4A0D-BF50-DF9C88EAFC2A@novemberborn.net>
Message-ID: <45D2413E.5000807@kaadesigngroup.com>

You're right... setting the text block to non-selectable means it gets 
the pointer mouse cursors, not the action mouse cursor... which isn't 
really any better for my problem... I'll have to do more digging.

Mark Wubben wrote:
> I'm a bit reluctant to do this, as it's yet another way to harm 
> usability. On the other hand, making the selections in Flash isn't the 
> greatest thing anyway. I'm just worried about people who'll use it 
> without seeing the bigger picture.
>
> Wouldn't disabling the selection result in showing the pointer, 
> instead of the hand cursor? And are you sure you want to use sIFR for 
> menus? ;-)
>
> On Feb 13, 2007, at 7:44 PM, Anthony McLin wrote:
>
>> Is there a way to turn off the selectable attribute for sIFR text
>> without doing it in the Flash file previous to publishing?
>>
>> I ask because I'm working on a complex menu system and the only way I
>> can use the sIFR is to replace at the anchor selector which means that
>> my links end up getting the select text cursor instead of the hand 
>> cursor.
>>
>> Perhaps this is something that can be achieved through the new
>> Flash<->Javascript framework?
>>
>> -Anthony
>>
>> --Anthony McLin
>> Senior Web Developer
>> amclin at kaadesigngroup.com
>> T 310.821.1400 ext. 266
>> F 310.821.1440
>>
>> KAA Design Group, Inc.
>> 4201 Redwood Avenue
>> Los Angeles, CA 90066
>>
>> ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
>> http://www.kaadesigngroup.com
>>
>> _______________________________________________
>> sifr3-dev mailing list
>> sifr3-dev at lists.novemberborn.net
>> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev
>
>


-- 
Anthony McLin
Senior Web Developer
amclin at kaadesigngroup.com
T  310.821.1400 ext. 266
F  310.821.1440

KAA Design Group, Inc.
4201 Redwood Avenue
Los Angeles, CA 90066

ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
http://www.kaadesigngroup.com



From davebytes at comcast.net  Wed Feb 14 20:29:08 2007
From: davebytes at comcast.net (David Chait)
Date: Wed, 14 Feb 2007 15:29:08 -0500
Subject: [sIFR3-dev] Any wordpress users?
In-Reply-To: <mailman.23.1171454457.65253.sifr3-dev@lists.novemberborn.net>
References: <mailman.23.1171454457.65253.sifr3-dev@lists.novemberborn.net>
Message-ID: <45D37114.9040008@comcast.net>

I've got an alpha version (v3.0a2) of my upgraded CG-FlashyTitles plugin 
that uses sIFR 3, if anyone out there is a wordpress user and would like 
to test it out and make suggestions of "what would an average blogger 
need for better interface to hide the complexity of sIFR, but deliver 
the stunning visual results".

Regards,

David Chait



From mark at novemberborn.net  Wed Feb 14 21:21:58 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Wed, 14 Feb 2007 22:21:58 +0100
Subject: [sIFR3-dev] Any wordpress users?
In-Reply-To: <45D37114.9040008@comcast.net>
References: <mailman.23.1171454457.65253.sifr3-dev@lists.novemberborn.net>
	<45D37114.9040008@comcast.net>
Message-ID: <3F85D0EE-3A18-446D-BFDC-737A45C3EEEE@novemberborn.net>

I'm a TextPattern user, but this is awesome news! :)

On Feb 14, 2007, at 9:29 PM, David Chait wrote:

> I've got an alpha version (v3.0a2) of my upgraded CG-FlashyTitles  
> plugin
> that uses sIFR 3, if anyone out there is a wordpress user and would  
> like
> to test it out and make suggestions of "what would an average blogger
> need for better interface to hide the complexity of sIFR, but deliver
> the stunning visual results".
>
> Regards,
>
> David Chait
>
> _______________________________________________
> sifr3-dev mailing list
> sifr3-dev at lists.novemberborn.net
> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev



From mark at novemberborn.net  Sat Feb 17 22:49:27 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Sat, 17 Feb 2007 23:49:27 +0100
Subject: [sIFR3-dev] Selectable text
In-Reply-To: <45D2413E.5000807@kaadesigngroup.com>
References: <45D206F8.7070602@kaadesigngroup.com>
	<7B265426-8C82-4A0D-BF50-DF9C88EAFC2A@novemberborn.net>
	<45D2413E.5000807@kaadesigngroup.com>
Message-ID: <8E49D7CC-B50A-42C8-889B-8A5B44E86372@novemberborn.net>

Disabling the text cursor is now in (r220). Use selectable: false as  
a keyword argument.

On Feb 13, 2007, at 11:52 PM, Anthony McLin wrote:

> You're right... setting the text block to non-selectable means it  
> gets the pointer mouse cursors, not the action mouse cursor...  
> which isn't really any better for my problem... I'll have to do  
> more digging.
>
> Mark Wubben wrote:
>> I'm a bit reluctant to do this, as it's yet another way to harm  
>> usability. On the other hand, making the selections in Flash isn't  
>> the greatest thing anyway. I'm just worried about people who'll  
>> use it without seeing the bigger picture.
>>
>> Wouldn't disabling the selection result in showing the pointer,  
>> instead of the hand cursor? And are you sure you want to use sIFR  
>> for menus? ;-)
>>
>> On Feb 13, 2007, at 7:44 PM, Anthony McLin wrote:
>>
>>> Is there a way to turn off the selectable attribute for sIFR text
>>> without doing it in the Flash file previous to publishing?
>>>
>>> I ask because I'm working on a complex menu system and the only  
>>> way I
>>> can use the sIFR is to replace at the anchor selector which means  
>>> that
>>> my links end up getting the select text cursor instead of the  
>>> hand cursor.
>>>
>>> Perhaps this is something that can be achieved through the new
>>> Flash<->Javascript framework?
>>>
>>> -Anthony
>>>
>>> --Anthony McLin
>>> Senior Web Developer
>>> amclin at kaadesigngroup.com
>>> T 310.821.1400 ext. 266
>>> F 310.821.1440
>>>
>>> KAA Design Group, Inc.
>>> 4201 Redwood Avenue
>>> Los Angeles, CA 90066
>>>
>>> ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
>>> http://www.kaadesigngroup.com
>>>
>>> _______________________________________________
>>> sifr3-dev mailing list
>>> sifr3-dev at lists.novemberborn.net
>>> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev
>>
>>
>
>
> -- 
> Anthony McLin
> Senior Web Developer
> amclin at kaadesigngroup.com
> T  310.821.1400 ext. 266
> F  310.821.1440
>
> KAA Design Group, Inc.
> 4201 Redwood Avenue
> Los Angeles, CA 90066
>
> ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
> http://www.kaadesigngroup.com
>



From amclin at kaadesigngroup.com  Tue Feb 20 19:52:46 2007
From: amclin at kaadesigngroup.com (Anthony McLin)
Date: Tue, 20 Feb 2007 11:52:46 -0800
Subject: [sIFR3-dev] Selectable text
In-Reply-To: <8E49D7CC-B50A-42C8-889B-8A5B44E86372@novemberborn.net>
References: <45D206F8.7070602@kaadesigngroup.com>
	<7B265426-8C82-4A0D-BF50-DF9C88EAFC2A@novemberborn.net>
	<45D2413E.5000807@kaadesigngroup.com>
	<8E49D7CC-B50A-42C8-889B-8A5B44E86372@novemberborn.net>
Message-ID: <45DB518E.7090700@kaadesigngroup.com>

I just tested this out and it seems to work great, thanks! This appears 
to be a 'global' setting for the font correct? Meaning if I set it for 
one of the sIFR.replace() statements for a font, then I have to set all 
the others to selectable: true ?

-Anthony

Mark Wubben wrote:
> Disabling the text cursor is now in (r220). Use selectable: false as a 
> keyword argument.
> 
> On Feb 13, 2007, at 11:52 PM, Anthony McLin wrote:
> 
>> You're right... setting the text block to non-selectable means it gets 
>> the pointer mouse cursors, not the action mouse cursor... which isn't 
>> really any better for my problem... I'll have to do more digging.
>>
>> Mark Wubben wrote:
>>> I'm a bit reluctant to do this, as it's yet another way to harm 
>>> usability. On the other hand, making the selections in Flash isn't 
>>> the greatest thing anyway. I'm just worried about people who'll use 
>>> it without seeing the bigger picture.
>>>
>>> Wouldn't disabling the selection result in showing the pointer, 
>>> instead of the hand cursor? And are you sure you want to use sIFR for 
>>> menus? ;-)
>>>
>>> On Feb 13, 2007, at 7:44 PM, Anthony McLin wrote:
>>>
>>>> Is there a way to turn off the selectable attribute for sIFR text
>>>> without doing it in the Flash file previous to publishing?
>>>>
>>>> I ask because I'm working on a complex menu system and the only way I
>>>> can use the sIFR is to replace at the anchor selector which means that
>>>> my links end up getting the select text cursor instead of the hand 
>>>> cursor.
>>>>
>>>> Perhaps this is something that can be achieved through the new
>>>> Flash<->Javascript framework?
>>>>
>>>> -Anthony
>>>>
>>>> --Anthony McLin
>>>> Senior Web Developer
>>>> amclin at kaadesigngroup.com
>>>> T 310.821.1400 ext. 266
>>>> F 310.821.1440
>>>>
>>>> KAA Design Group, Inc.
>>>> 4201 Redwood Avenue
>>>> Los Angeles, CA 90066
>>>>
>>>> ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
>>>> http://www.kaadesigngroup.com
>>>>
>>>> _______________________________________________
>>>> sifr3-dev mailing list
>>>> sifr3-dev at lists.novemberborn.net
>>>> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev
>>>
>>>
>>
>>
>> --Anthony McLin
>> Senior Web Developer
>> amclin at kaadesigngroup.com
>> T  310.821.1400 ext. 266
>> F  310.821.1440
>>
>> KAA Design Group, Inc.
>> 4201 Redwood Avenue
>> Los Angeles, CA 90066
>>
>> ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
>> http://www.kaadesigngroup.com
>>
> 
> 


-- 
Anthony McLin
Senior Web Developer
amclin at kaadesigngroup.com
T  310.821.1400 ext. 266
F  310.821.1440

KAA Design Group, Inc.
4201 Redwood Avenue
Los Angeles, CA 90066

ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
http://www.kaadesigngroup.com


From amclin at kaadesigngroup.com  Tue Feb 20 19:59:00 2007
From: amclin at kaadesigngroup.com (Anthony McLin)
Date: Tue, 20 Feb 2007 11:59:00 -0800
Subject: [sIFR3-dev] Selectable text
In-Reply-To: <45DB518E.7090700@kaadesigngroup.com>
References: <45D206F8.7070602@kaadesigngroup.com>	<7B265426-8C82-4A0D-BF50-DF9C88EAFC2A@novemberborn.net>	<45D2413E.5000807@kaadesigngroup.com>	<8E49D7CC-B50A-42C8-889B-8A5B44E86372@novemberborn.net>
	<45DB518E.7090700@kaadesigngroup.com>
Message-ID: <45DB5304.7050108@kaadesigngroup.com>

Nevermind, I just figured out the answer to my own question. For 
everyone else's edification, the new parameter is specific to the 
sIFR.replace() statement.

-Anthony

Anthony McLin wrote:
> I just tested this out and it seems to work great, thanks! This appears 
> to be a 'global' setting for the font correct? Meaning if I set it for 
> one of the sIFR.replace() statements for a font, then I have to set all 
> the others to selectable: true ?
>
> -Anthony
>
> Mark Wubben wrote:
>   
>> Disabling the text cursor is now in (r220). Use selectable: false as a 
>> keyword argument.
>>
>> On Feb 13, 2007, at 11:52 PM, Anthony McLin wrote:
>>
>>     
>>> You're right... setting the text block to non-selectable means it gets 
>>> the pointer mouse cursors, not the action mouse cursor... which isn't 
>>> really any better for my problem... I'll have to do more digging.
>>>
>>> Mark Wubben wrote:
>>>       
>>>> I'm a bit reluctant to do this, as it's yet another way to harm 
>>>> usability. On the other hand, making the selections in Flash isn't 
>>>> the greatest thing anyway. I'm just worried about people who'll use 
>>>> it without seeing the bigger picture.
>>>>
>>>> Wouldn't disabling the selection result in showing the pointer, 
>>>> instead of the hand cursor? And are you sure you want to use sIFR for 
>>>> menus? ;-)
>>>>
>>>> On Feb 13, 2007, at 7:44 PM, Anthony McLin wrote:
>>>>
>>>>         
>>>>> Is there a way to turn off the selectable attribute for sIFR text
>>>>> without doing it in the Flash file previous to publishing?
>>>>>
>>>>> I ask because I'm working on a complex menu system and the only way I
>>>>> can use the sIFR is to replace at the anchor selector which means that
>>>>> my links end up getting the select text cursor instead of the hand 
>>>>> cursor.
>>>>>
>>>>> Perhaps this is something that can be achieved through the new
>>>>> Flash<->Javascript framework?
>>>>>
>>>>> -Anthony
>>>>>
>>>>> --Anthony McLin
>>>>> Senior Web Developer
>>>>> amclin at kaadesigngroup.com
>>>>> T 310.821.1400 ext. 266
>>>>> F 310.821.1440
>>>>>
>>>>> KAA Design Group, Inc.
>>>>> 4201 Redwood Avenue
>>>>> Los Angeles, CA 90066
>>>>>
>>>>> ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
>>>>> http://www.kaadesigngroup.com
>>>>>
>>>>> _______________________________________________
>>>>> sifr3-dev mailing list
>>>>> sifr3-dev at lists.novemberborn.net
>>>>> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev
>>>>>           
>>>>         
>>> --Anthony McLin
>>> Senior Web Developer
>>> amclin at kaadesigngroup.com
>>> T  310.821.1400 ext. 266
>>> F  310.821.1440
>>>
>>> KAA Design Group, Inc.
>>> 4201 Redwood Avenue
>>> Los Angeles, CA 90066
>>>
>>> ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
>>> http://www.kaadesigngroup.com
>>>
>>>       
>>     
>
>
>   


-- 
Anthony McLin
Senior Web Developer
amclin at kaadesigngroup.com
T  310.821.1400 ext. 266
F  310.821.1440

KAA Design Group, Inc.
4201 Redwood Avenue
Los Angeles, CA 90066

ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
http://www.kaadesigngroup.com



From mark at novemberborn.net  Tue Feb 20 20:07:02 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Tue, 20 Feb 2007 21:07:02 +0100
Subject: [sIFR3-dev] Selectable text
In-Reply-To: <45DB5304.7050108@kaadesigngroup.com>
References: <45D206F8.7070602@kaadesigngroup.com>	<7B265426-8C82-4A0D-BF50-DF9C88EAFC2A@novemberborn.net>	<45D2413E.5000807@kaadesigngroup.com>	<8E49D7CC-B50A-42C8-889B-8A5B44E86372@novemberborn.net>
	<45DB518E.7090700@kaadesigngroup.com>
	<45DB5304.7050108@kaadesigngroup.com>
Message-ID: <74AFC7DB-8E1B-4EE0-A853-70264343C70F@novemberborn.net>

On Feb 20, 2007, at 8:59 PM, Anthony McLin wrote:

> Nevermind, I just figured out the answer to my own question. For
> everyone else's edification, the new parameter is specific to the
> sIFR.replace() statement.

Yep. Although, if you want it to be general, and you have something  
like this:

var font = { src: 'font.swf' };
sIFR.replace(font, {selector:'h1',selectable:false})

You could also do:

var font = { src: 'font.swf', selectable: false };
sIFR.replace(font, {selector:'h1'})

--
Mark


From mark at novemberborn.net  Mon Feb 26 10:47:42 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Mon, 26 Feb 2007 11:47:42 +0100
Subject: [sIFR3-dev] r229, and Wikipedia!
Message-ID: <C6785617-CACA-4F6A-975C-B0036F3DBDDA@novemberborn.net>

Hey all, I posted an update about revision 229 yesterday, you can  
find it at <http://novemberborn.net/sifr3/r229>. And I just noticed  
that there's a Wikipedia page for sIFR! <http://en.wikipedia.org/wiki/ 
SIFR>

--
Mark


From amclin at kaadesigngroup.com  Mon Feb 26 17:11:17 2007
From: amclin at kaadesigngroup.com (Anthony McLin)
Date: Mon, 26 Feb 2007 09:11:17 -0800
Subject: [sIFR3-dev] r229, and Wikipedia!
In-Reply-To: <C6785617-CACA-4F6A-975C-B0036F3DBDDA@novemberborn.net>
References: <C6785617-CACA-4F6A-975C-B0036F3DBDDA@novemberborn.net>
Message-ID: <45E314B5.8010905@kaadesigngroup.com>

Great news! Thanks for letting us know. I can't wait to try out the 
mouseover fix.

I love how the release comment for r229 includes an additional feature 
in r230.... now that's fast development.


-Anthony

Mark Wubben wrote:
> Hey all, I posted an update about revision 229 yesterday, you can  
> find it at <http://novemberborn.net/sifr3/r229>. And I just noticed  
> that there's a Wikipedia page for sIFR! <http://en.wikipedia.org/wiki/ 
> SIFR>
>
> --
> Mark
> _______________________________________________
> sifr3-dev mailing list
> sifr3-dev at lists.novemberborn.net
> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev
>
>   


-- 
Anthony McLin
Senior Web Developer
amclin at kaadesigngroup.com
T  310.821.1400 ext. 266
F  310.821.1440

KAA Design Group, Inc.
4201 Redwood Avenue
Los Angeles, CA 90066

ARCHITECTURE | LANDSCAPE | GRAPHICS | INTERIORS
http://www.kaadesigngroup.com



From mark at novemberborn.net  Mon Feb 26 17:18:49 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Mon, 26 Feb 2007 18:18:49 +0100
Subject: [sIFR3-dev] r229, and Wikipedia!
In-Reply-To: <45E314B5.8010905@kaadesigngroup.com>
References: <C6785617-CACA-4F6A-975C-B0036F3DBDDA@novemberborn.net>
	<45E314B5.8010905@kaadesigngroup.com>
Message-ID: <2B8FB8AC-888F-4607-8659-BF0FFB247706@novemberborn.net>

On Feb 26, 2007, at 6:11 PM, Anthony McLin wrote:
> I love how the release comment for r229 includes an additional  
> feature in r230.... now that's fast development.

Well, turns out I got the revision number wrong :)

--
Mark


From mark at novemberborn.net  Tue Feb 27 10:30:26 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Tue, 27 Feb 2007 11:30:26 +0100
Subject: [sIFR3-dev] A dilemma
Message-ID: <86DCA1E0-116C-428D-B9E6-A326C456A856@novemberborn.net>

Hey,

There are / will be a couple of things in sIFR which rely heavily on  
current browser implementations. This means that when the  
implementation changes, we're in trouble. I can think of two ways of  
handling these situations:

Scenario 1: Have it active by default, then have users upgrade to a  
fixed version when new browser versions break stuff. Any issues are  
sIFR's (my) fault.

Scenario 2: Let the user enable the "risky" features manually.  
Provide fixed versions when needed. Still sIFR's fault, but at least  
the user took the responsibility for turning on a risky feature.

Scenario 2 is safer (for me), but I wonder how much people will  
really think about it. Font resizing is one of the features, and  
virtually everybody will switch it on. It's a bit like these "Are you  
sure you want to.... YES!" dialogs where nobody pays attention.

What do you think?

(And yes, this basically is about escaping blame. And communicating  
that certain stuff may brake in the future.)

--
Mark


From design at violetsky.net  Tue Feb 27 15:13:07 2007
From: design at violetsky.net (Stephanie Sullivan)
Date: Tue, 27 Feb 2007 10:13:07 -0500
Subject: [sIFR3-dev] A dilemma
In-Reply-To: <86DCA1E0-116C-428D-B9E6-A326C456A856@novemberborn.net>
Message-ID: <C209B4B3.26B3E%design@violetsky.net>

On 2/27/07 5:30 AM, "Mark Wubben" <mark at novemberborn.net> wrote:

> Scenario 2: Let the user enable the "risky" features manually.
> Provide fixed versions when needed. Still sIFR's fault, but at least
> the user took the responsibility for turning on a risky feature.
> 
> Scenario 2 is safer (for me), but I wonder how much people will
> really think about it. Font resizing is one of the features, and
> virtually everybody will switch it on. It's a bit like these "Are you
> sure you want to.... YES!" dialogs where nobody pays attention.
> 
> What do you think?

My vote would be to make yourself as safe as possible... Doesn't matter if
they think about it or not -- as long as the documentation is there... At
least then, you can say -- I told you that might happen. :)  Scenario one
means they really WON'T look at it (for the most part) -- if it just works
by default.

My two cents...
Stef.

Stephanie Sullivan
Community MX Partner :: http://www.communitymx.com/author.cfm?cid=1008
Adobe Community Expert :: http://tinyurl.com/6huw3
Co-Author .: "Macromedia Dreamweaver MX 2004 Magic" :. New Riders
Dreamweaver Task Force for WaSP

?We forfeit three-fourths of ourselves to be like other people." - Arthur
Schopenhauer 





From branstrom at gmail.com  Tue Feb 27 17:00:08 2007
From: branstrom at gmail.com (=?ISO-8859-1?Q?Fredrik_Br=E4nstr=F6m?=)
Date: Tue, 27 Feb 2007 18:00:08 +0100
Subject: [sIFR3-dev] A dilemma
In-Reply-To: <C209B4B3.26B3E%design@violetsky.net>
References: <86DCA1E0-116C-428D-B9E6-A326C456A856@novemberborn.net>
	<C209B4B3.26B3E%design@violetsky.net>
Message-ID: <22410ce30702270900j6b0ed4dnbee74b986a737f8f@mail.gmail.com>

That's my vote too.

The only way to make them really think about it is too summarize the
reasoning in one or two sentences, choose a really big font and shove that
in their faces. Kind of.

On 2/27/07, Stephanie Sullivan <design at violetsky.net> wrote:
>
> On 2/27/07 5:30 AM, "Mark Wubben" <mark at novemberborn.net> wrote:
>
> > Scenario 2: Let the user enable the "risky" features manually.
> > Provide fixed versions when needed. Still sIFR's fault, but at least
> > the user took the responsibility for turning on a risky feature.
> >
> > Scenario 2 is safer (for me), but I wonder how much people will
> > really think about it. Font resizing is one of the features, and
> > virtually everybody will switch it on. It's a bit like these "Are you
> > sure you want to.... YES!" dialogs where nobody pays attention.
> >
> > What do you think?
>
> My vote would be to make yourself as safe as possible... Doesn't matter if
> they think about it or not -- as long as the documentation is there... At
> least then, you can say -- I told you that might happen. :)  Scenario one
> means they really WON'T look at it (for the most part) -- if it just works
> by default.
>
> My two cents...
> Stef.
>
> Stephanie Sullivan
> Community MX Partner :: http://www.communitymx.com/author.cfm?cid=1008
> Adobe Community Expert :: http://tinyurl.com/6huw3
> Co-Author .: "Macromedia Dreamweaver MX 2004 Magic" :. New Riders
> Dreamweaver Task Force for WaSP
>
> ?We forfeit three-fourths of ourselves to be like other people." - Arthur
> Schopenhauer
>
>
>
> _______________________________________________
> sifr3-dev mailing list
> sifr3-dev at lists.novemberborn.net
> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev
>



-- 
Fredrik Br?nstr?m
http://fredrik.branstrom.nu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.novemberborn.net/pipermail/sifr3-dev/attachments/20070227/b61df46c/attachment.html>

From mark at novemberborn.net  Tue Feb 27 21:36:15 2007
From: mark at novemberborn.net (Mark Wubben)
Date: Tue, 27 Feb 2007 22:36:15 +0100
Subject: [sIFR3-dev] A dilemma
In-Reply-To: <22410ce30702270900j6b0ed4dnbee74b986a737f8f@mail.gmail.com>
References: <86DCA1E0-116C-428D-B9E6-A326C456A856@novemberborn.net>
	<C209B4B3.26B3E%design@violetsky.net>
	<22410ce30702270900j6b0ed4dnbee74b986a737f8f@mail.gmail.com>
Message-ID: <14AC13F5-56D6-4986-A292-2A1B98BC5659@novemberborn.net>

Thanks Stephanie and Frederik (and Danilo too, who replied just to  
me?). I'll go for option two, with big fat warnings :)

--
Mark

On Feb 27, 2007, at 6:00 PM, Fredrik Br?nstr?m wrote:

> That's my vote too.
>
> The only way to make them really think about it is too summarize the
> reasoning in one or two sentences, choose a really big font and  
> shove that
> in their faces. Kind of.
>
> On 2/27/07, Stephanie Sullivan <design at violetsky.net> wrote:
>>
>> On 2/27/07 5:30 AM, "Mark Wubben" <mark at novemberborn.net> wrote:
>>
>> > Scenario 2: Let the user enable the "risky" features manually.
>> > Provide fixed versions when needed. Still sIFR's fault, but at  
>> least
>> > the user took the responsibility for turning on a risky feature.
>> >
>> > Scenario 2 is safer (for me), but I wonder how much people will
>> > really think about it. Font resizing is one of the features, and
>> > virtually everybody will switch it on. It's a bit like these  
>> "Are you
>> > sure you want to.... YES!" dialogs where nobody pays attention.
>> >
>> > What do you think?
>>
>> My vote would be to make yourself as safe as possible... Doesn't  
>> matter if
>> they think about it or not -- as long as the documentation is  
>> there... At
>> least then, you can say -- I told you that might happen. :)   
>> Scenario one
>> means they really WON'T look at it (for the most part) -- if it  
>> just works
>> by default.
>>
>> My two cents...
>> Stef.
>>
>> Stephanie Sullivan
>> Community MX Partner :: http://www.communitymx.com/author.cfm? 
>> cid=1008
>> Adobe Community Expert :: http://tinyurl.com/6huw3
>> Co-Author .: "Macromedia Dreamweaver MX 2004 Magic" :. New Riders
>> Dreamweaver Task Force for WaSP
>>
>> ?We forfeit three-fourths of ourselves to be like other people." -  
>> Arthur
>> Schopenhauer
>>
>>
>>
>> _______________________________________________
>> sifr3-dev mailing list
>> sifr3-dev at lists.novemberborn.net
>> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev
>>
>
>
>
> -- 
> Fredrik Br?nstr?m
> http://fredrik.branstrom.nu



From branstrom at gmail.com  Tue Feb 27 21:44:29 2007
From: branstrom at gmail.com (=?ISO-8859-1?Q?Fredrik_Br=E4nstr=F6m?=)
Date: Tue, 27 Feb 2007 22:44:29 +0100
Subject: [sIFR3-dev] A dilemma
In-Reply-To: <14AC13F5-56D6-4986-A292-2A1B98BC5659@novemberborn.net>
References: <86DCA1E0-116C-428D-B9E6-A326C456A856@novemberborn.net>
	<C209B4B3.26B3E%design@violetsky.net>
	<22410ce30702270900j6b0ed4dnbee74b986a737f8f@mail.gmail.com>
	<14AC13F5-56D6-4986-A292-2A1B98BC5659@novemberborn.net>
Message-ID: <22410ce30702271344y7b4e1ac6g755b3acbd9927f84@mail.gmail.com>

Sounds good. Don't overdo it though, so you scare some people off or
something.

On 2/27/07, Mark Wubben <mark at novemberborn.net> wrote:
>
> Thanks Stephanie and Frederik (and Danilo too, who replied just to
> me?). I'll go for option two, with big fat warnings :)
>
> --
> Mark
>
> On Feb 27, 2007, at 6:00 PM, Fredrik Br?nstr?m wrote:
>
> > That's my vote too.
> >
> > The only way to make them really think about it is too summarize the
> > reasoning in one or two sentences, choose a really big font and
> > shove that
> > in their faces. Kind of.
> >
> > On 2/27/07, Stephanie Sullivan <design at violetsky.net> wrote:
> >>
> >> On 2/27/07 5:30 AM, "Mark Wubben" <mark at novemberborn.net> wrote:
> >>
> >> > Scenario 2: Let the user enable the "risky" features manually.
> >> > Provide fixed versions when needed. Still sIFR's fault, but at
> >> least
> >> > the user took the responsibility for turning on a risky feature.
> >> >
> >> > Scenario 2 is safer (for me), but I wonder how much people will
> >> > really think about it. Font resizing is one of the features, and
> >> > virtually everybody will switch it on. It's a bit like these
> >> "Are you
> >> > sure you want to.... YES!" dialogs where nobody pays attention.
> >> >
> >> > What do you think?
> >>
> >> My vote would be to make yourself as safe as possible... Doesn't
> >> matter if
> >> they think about it or not -- as long as the documentation is
> >> there... At
> >> least then, you can say -- I told you that might happen. :)
> >> Scenario one
> >> means they really WON'T look at it (for the most part) -- if it
> >> just works
> >> by default.
> >>
> >> My two cents...
> >> Stef.
> >>
> >> Stephanie Sullivan
> >> Community MX Partner :: http://www.communitymx.com/author.cfm?
> >> cid=1008
> >> Adobe Community Expert :: http://tinyurl.com/6huw3
> >> Co-Author .: "Macromedia Dreamweaver MX 2004 Magic" :. New Riders
> >> Dreamweaver Task Force for WaSP
> >>
> >> ?We forfeit three-fourths of ourselves to be like other people." -
> >> Arthur
> >> Schopenhauer
> >>
> >>
> >>
> >> _______________________________________________
> >> sifr3-dev mailing list
> >> sifr3-dev at lists.novemberborn.net
> >> http://lists.novemberborn.net/mailman/listinfo/sifr3-dev
> >>
> >
> >
> >
> > --
> > Fredrik Br?nstr?m
> > http://fredrik.branstrom.nu
>
>


-- 
Fredrik Br?nstr?m
http://fredrik.branstrom.nu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.novemberborn.net/pipermail/sifr3-dev/attachments/20070227/fef3e491/attachment.html>