raising bugs for SVG animation features

--===============6413651495012566953==
Content-Type: multipart/alternative; boundary="00000000000018038905a5bb9d79"

--00000000000018038905a5bb9d79
Content-Type: text/plain; charset="UTF-8"

I emailed a roadmap and high level break down of features that need to be
implemented or adapted to implement SVG animation, I'm fairly sure there's
a whole host of features I've missed off.

I'm going to be handing around rocketchat on freenode for as much of the
day as possible and I hope to bump into some people for a discussion about
the breakdown I have emailed hopefully resulting in a little more fleshing
out of the roadmap and feature break down and sanitizing it to the level
that a list of bugs can be raised that need to be implemented for a robust
implementation of SVG animation. it would be nice to break down the road
map into key stages forinstance. Javascript engine implemented. javascript
markup implemented. GUI integration implemented. keyframes and timeline
implemented

once we get a better more complete grasp of what needs to be implemented
for each stage it would be nice to come up with some timeframe estimates
so I can track my progress against them..

quite a lot of the work I expect to be quite repetitive and boring, but I
actually quite like that kind of work, that still doesn't stop me wanting
to turn it into a script.


I have nothing coming up in the foreseeable future also I expect very much
that I will be able to work on svg animation until such times as it's
completely implemented. I'm not working at the moment so I should be able
to put quite a reasonable number of hours in so hopefully the project
won't drag on and it can be completed in a reasonable time frame. I don't
mind working with other people if other people want to join in so long as
we have things reasonably well defined so there isn't a mixture of styles
and implementation methodologies and we're not stepping on each other's
toes. I also don't want to be responsible for tidying up another developers
code when it is found to be unpalatable buggy.

that's about all I can think of for the time being and hope to catch you on
IEC. I  think I'm off to bed.

--00000000000018038905a5bb9d79
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I emailed a roadmap and high level break down of features =
that need to be implemented=C2=A0or adapted to implement SVG animation, I&#=
39;m fairly sure there&#39;s a whole host of features I&#39;ve missed off.<=
br><br>I&#39;m going to be handing around rocketchat on freenode for as muc=
h of the day as possible and I hope to bump=C2=A0into some people=C2=A0for =
a discussion about the breakdown I have emailed hopefully resulting in a li=
ttle more fleshing out of the roadmap and feature break=C2=A0down and sanit=
izing=C2=A0it to the level that a list of bugs can be raised that=C2=A0need=
 to be implemented for a robust implementation of SVG animation. it would b=
e nice to break down the road map into key stages forinstance. Javascript=
=C2=A0engine implemented. javascript markup implemented. GUI integration im=
plemented. keyframes and timeline implemented<br><br>once we get=C2=A0a=C2=
=A0better=C2=A0more complete grasp of what needs=C2=A0to=C2=A0be implemente=
d for each stage it=C2=A0would be=C2=A0nice to come up with some timeframe =
estimates so=C2=A0I can track my progress against=C2=A0them..=C2=A0=C2=A0<b=
r><br>quite a lot of the work I expect to be quite repetitive and boring, b=
ut I actually quite=C2=A0like that kind of work, that still doesn&#39;t sto=
p me wanting to turn it into a script.<br><br><br>I have nothing coming up =
in the foreseeable future also I expect very much that I will be able to wo=
rk on svg animation until such times as it&#39;s completely implemented. I&=
#39;m not working at the moment so I should be able to put quite a reasonab=
le number of hours in so hopefully the project won&#39;t=C2=A0drag on and i=
t can be completed in a reasonable time frame. I don&#39;t mind working wit=
h other people if other people want to join in so long as we have things re=
asonably well defined so there isn&#39;t a mixture of styles and implementa=
tion methodologies and we&#39;re not stepping on each other&#39;s toes. I a=
lso don&#39;t want to be responsible for tidying up another developers code=
 when it is found to be unpalatable buggy.<div><div><br>that&#39;s about al=
l I can think of for the time being and hope to catch you on IEC. I=C2=A0 t=
hink I&#39;m off to bed.<br><br><br><br><br></div></div></div>

--00000000000018038905a5bb9d79--


--===============6413651495012566953==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============6413651495012566953==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Inkscape-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

--===============6413651495012566953==--