Feature Request - Extensible TX2D Builder
by Christopher Perkins · in Torque X 2D · 07/23/2010 (10:22 pm) · 0 replies
It is very clear that you want the builders to be able to create any genre of game. You wan them to be powerful enough yet generic enough to speed up any games creation process. However in the idea that you are trying to be generic as possible, the builder easily loses a lot of functionality that could be used for focused issues. Since I believe it is still in ya'lls plans to upgrade the TX2D builder(at least it was on the last roadmap I saw), I suggest you think about making it extensible.
If you plan on building it on top of torque x and xna, I suggest you take a look at System.Addin to make it where we can build some addins for it. That way, the developers can add those little focused features for projects that need them and you won't need to spend the time developing them.
Things I'd like to be able to do:
Change out the collision framework(in code, that's doable now) and make it support AABB rectangles and circular collisions and make them visually editable in the editor(What the addin'd be for).
Create and Reference scripts made in the editor.
Make more things visible to editor and settable(materials and stuff like that).
The idea is you aren't going to be able to think of everything a developer is going to need and it's clear you are not going to give the builder source out to the normal devs, so making a extensible editor should be the solution to make this builder far more usable to the community. System.Addin is quite powerful and I've used it before, it'd be a pretty good choice if you choose it to be a WYSIWYG editor like TX3D built on Torque and XNA.
If you plan on building it on top of torque x and xna, I suggest you take a look at System.Addin to make it where we can build some addins for it. That way, the developers can add those little focused features for projects that need them and you won't need to spend the time developing them.
Things I'd like to be able to do:
Change out the collision framework(in code, that's doable now) and make it support AABB rectangles and circular collisions and make them visually editable in the editor(What the addin'd be for).
Create and Reference scripts made in the editor.
Make more things visible to editor and settable(materials and stuff like that).
The idea is you aren't going to be able to think of everything a developer is going to need and it's clear you are not going to give the builder source out to the normal devs, so making a extensible editor should be the solution to make this builder far more usable to the community. System.Addin is quite powerful and I've used it before, it'd be a pretty good choice if you choose it to be a WYSIWYG editor like TX3D built on Torque and XNA.
