W3C home > Mailing lists > Public > www-svg@w3.org > November 2003

Re: [SVG 1.2] Other notes.

From: Antoine Quint <ml@graougraou.com>
Date: Sat, 15 Nov 2003 17:33:48 +0100
Message-Id: <7D1A692B-1789-11D8-BD45-000393D124C4@graougraou.com>
Cc: www-svg@w3.org
To: "Jim Ley" <jim@jibbering.com>

Hey Jim,

> "Antoine Quint" <ml@graougraou.com> wrote in message
> news:80654DAD-1784-11D8-BD45-000393D124C4@graougraou.com...
>
>> and someone would have to do it RCC.
>
> That's what we have you for...

It seems that it's everyone's assumption these days, but where the damn 
RCC contracts???

>> Current extended links is basically simple instructions to have
>> native UI pop-up with a bunch of associated links show up.
>
> I don't know of a native UI that behaves that way for my OS,

I meant that it would pop-up a native UI menu  la ASV contextMenu.

> and if it can't
> be styled, I'm not sure how many people would really use it, when they 
> could
> just over-ride it by RCC to get a proper styled reference.

The guys who don't care so much about beautiful graphics and want a 
profile without RCC, like the guys I hinted at previously who were the 
first motivation for this feature.

> However by
> including it within SVG, we can no longer RCC it (as currently 
> defined) so
> we're stuck with either the default rendering or a proprietary syntax.

Indeed, that needs to be solved.

> I would like a method to disable the default handling, and have it
> rendered - being able to RCC any SVG element though would probably be 
> more
> useful - certainly SVG elements which have no visual rendering should 
> be
> easy to specify, and very useful to me.

Spot on.

Antoine
-- 
Antoine Quint <aq@fuchsia-design.com>
W3C SVG Working Group Invited Expert
SVG Consulting, Teaching and Outsourcing
Fuchsia Design <http://www.fuchsia-design.com/>
Received on Saturday, 15 November 2003 11:34:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 November 2012 23:52:55 GMT