- From: Rik Cabanier <cabanier@gmail.com>
- Date: Fri, 7 Dec 2012 14:43:06 -0800
- To: Alexandre Prokoudine <alexandre.prokoudine@gmail.com>
- Cc: www-svg <www-svg@w3.org>
- Message-ID: <CAGN7qDApJdpTz3zSaEiFXiZrudzxDg9Jqbyh5pzW4d_7Udt1_A@mail.gmail.com>
On Fri, Dec 7, 2012 at 10:42 AM, Alexandre Prokoudine < alexandre.prokoudine@gmail.com> wrote: > On Fri, Dec 7, 2012 at 10:25 PM, Rik Cabanier wrote: > > >> Just a quick note from end-user dept. LPEs are limiting in a way that > >> they impose single style for the output path. That's not too bad for > >> the PAP effect (contrary to e.g. Interpolation). However, for real, > >> usable brushes you would want to read input device characteristics > >> such as pen pressure and velocity, and affect color, opacity etc. In > >> terms of SVG markup that would mean storing style for each copy of a > >> brush primitive > > > > ah, true bristle brushes. > > Oh, not really. What I'm talking about is a fairly generic brush > engine. AFAIK, what's typically referred to as bristle brushes > involves physical modeling and other kinds of heavy calculations. > yes, they're harder to implement but their markup is probably similar. I think we can start with something basic and make sure that it is a good foundation. > > > Those are certainly very useful, but HARD to implement! The markup for > those > > will also be tough since as you mention you'd have to store all that > extra > > information alongside the path. > > Saving style settings would suffice. OTOH, a convergence with > http://www.w3.org/TR/InkML/ could be interesting. > > Did anyone implement InkML?
Received on Friday, 7 December 2012 22:43:35 UTC