Mike Kienenberger schrieb:
Ok. I've went through the Tomahawk issue tracker and looked at all
Blocker and Critical issues. I find three that appear to be
regressions (no patches), and one that appears to affect other
frameworks (includes a patch).
Everything else I changed to major priority.
But this did bring up another consideration. If we are going to make
wide, sweeping changes to Tomahawk, we need to commit all outstanding
patches first. Otherwise these patches are going to become obsolete.
Just to clear things up, my move of dojo is not a wide sweeping
change of tomahawk, it is more an additional codebase
which is moved from the sandbox down to the core
(if you think that the pure addition of code is a wide sweeping change
then it is)
I tried to take care that no core tomahawk code was touched from
my side when I was working on the dojo stuff.
I added my own tools class for dojo only so that I did not have
to add it to the existing tools classes
the rest is a lot of javascript resources and one component.
I dont know what was done by the others, but that is mostly
it of what I would start to migrate down.
So no existing Tomahawk code will be altered only
the example links will be touched, but a lot of code
will be moved down from the sandbox to Tomahawk.
(mostly with svn move)
Expect a handful of java classes one component and several hundred
javascript files being moved into Tom...
