Closed GoogleCodeExporter closed 9 years ago
For some reason I can't find where I can change the type to "Type-Enhancement"
sorry for the inconvenience I didn't mean to make this "Type-Defect".
Original comment by bober...@gmail.com
on 22 Jun 2010 at 5:37
no worries, the lack of option to change Label into 'Type-Enhancement'
afterwards is a google code limitation, that should be fixed. If you like file
an issue with google code?
With respect to Horde3D, we are already too busy with Ogre, and hardly time to
update Irrlicht, so adding another graphics engine is beyond our resources.
Of course you are welcome to provide a patch, but would you be willing to
maintain it?
Original comment by erwin.coumans
on 29 Jun 2010 at 4:58
Horde is very nice, in my humble opinion it could replace Ogre IF it is made
opengl ES 2 compatible, in order to render to embedded devices, like Ogre is
able to.
Original comment by smog...@gmail.com
on 30 Jun 2010 at 10:17
Horde seems nice I agree (from the feature list, I didn't test it). On the
portability side, Ogre also works with openGL 1.2 and OpenGL ES 1, lot of
embedded devices doest not have openGL ES 2 capabilities yet.
Original comment by xavier.thomas.1980@gmail.com
on 30 Jun 2010 at 3:51
I don't debate that Horde is nice or even that it "could" replace Ogre. However
the practicality of such is important here. OgreKit is getting the lion's share
of development effort and, given how advanced it is against the other
back-ends, it would take something considerable to change that focus.
Right now there are a few of us already using OgreKit in projects. What is
there in Horde to make it worth the time to drop Ogre and get the Horde
back-end up to the same level? Given the use of Ogre in existing published
titles, the extra features that can be plugged in, and the time it would take
to get Horde just to the current level of functionality - it needs to be a
compelling reason.
This is not to say that you cannot develop and contribute a Horde back-end
yourself, I'd certainly take a look at the finished product to see how it
performs in comparison. I'm just trying to point out why it will be hard to
convince others with a working & promising back-end to drop it's development
for something else.
Original comment by BenT.Sol...@gmail.com
on 30 Jun 2010 at 10:07
Original comment by erwin.coumans
on 14 Jul 2010 at 11:51
Original issue reported on code.google.com by
bober...@gmail.com
on 22 Jun 2010 at 5:36