ManiacTwister wrote:But wouldn't it be better if you and the one who are working on the SMAseco port using a svn-system (maybe git or so) to keep everything updated. I think there should be no problem if SMAseco and XAseco2 keep one tool, shouldn't it?
My having no cycles for XAseco on SM extends to having no cycles for changing the way I develop/release versions, or even setting up svn/github. These are real life constraints.
And I expect there to be quite a few differences even in the core and basic plugins (like the local database) between XAseco2 versions for TM2C and SM, because [X]Aseco's architecture dates back to Flo's original work in 2006. I've had plenty of complaints about it over the years, but choose to stick to it because so many plugins already existed for Aseco/Rasp when I took over development, plus at that time I lacked the skills and experience to rewrite the system to a modern, modular, real object-oriented structure anyway. I'm not even sure I could do it nowadays, but then I'm not going to try either.
Flo and others' work in ManiaLive demonstrates how this should be done with a modern architecture, and is one of the technical reasons I don't even want to try combining ShootMania support with TM2C in XAseco2, let alone QuestMania further down the road. Deriving XAseco2 from XAseco was a ton of work already, last Summer.
So someone else can carry the torch regarding a XAseco variant for SM, if they choose, but if it doesn't happen I won't be disappointed either. It might actually be the right thing in the long run.
I totally understand people wishing to stick to something they're familiar with, something that seems simpler and more accessible. And perhaps it demonstrates my approach to create as much documentation as I could, and support XAseco1 & 2 via a few thousand posts on tm-forum.com, helped to get them as widely adopted as they are. But then this lesson may also motivate the ManiaLive/MLEPP and FoxControl developers (and others still in development) to try even harder at making adoption of their respective controllers just as easy.