OGEd is now open-source :)
OGEd stands for Open Game Editor but at this stage it is more an Ogre Resource Editor and will evolve into an OGE Editor before becoming a true versatile Open Game Editor :D
You can get it on the OGE sourceforge as code or binary.
Of course there are still lots to do and any help would be great.
If you are interested you can look on the oge wiki for more information like todo list, planned features, how to compile, etc.
http://www.opengameengine.org/wiki
Originally I took inspiration from the Ogre project name "Material Editor" and 5 files that allowed Ogre script edition were really interesting.
So I proposed to the Ogre owner -Sinbad- that we exchange some code so that both could benefit - I thought it was a win-win proposal. I was wrong.
His answer disappointed me. As I want to be able to distribute OGEd under our OGE unlimited license -which I can't if I must keep Ogre license and copyright- I was obliged to remove ANY code that could be interpreted as being originally from the Material Editor :(
This attitude is bit to near to the "SCO versus Linux" for my taste. This is not how I idealise the open source movement. For me if someone is willing to exchange worthwhile code I am more than happy to give mine. Saving time is the most important thing in live! I am not immortal! In my opinion copyrights and licenses are primarily a way to protect my work from people patenting it and then trying to stop me using my code or even making me pay for the work I did! I use them to protect me against crooks and felons.
This lead me to read some legal texts about using existing code without infringing copyright & license. And I found this legal review from the ReactOS project: http://www.reactos.org/en/dev_legalreview.html (ReactOS is a nice project btw I hope it will reach the stage where VC runs on it).
This point is fairly obvious but IMO hard to achieve as C++ programmers are increasingly using the same coding style:
Developers are encouraged to NOT attempt to copy the coding style of non-free code. While coding style may not covered by copyright, a similar or identical coding style to a piece of non-free code casts suspicion on the new code.
This experience made me realise that the "Tainted Developers" theory is nearly unavoidable and I was not able to explain my position to Sinbad. So to avoid again a "SCO versus linux" issue I will avoid reading
ANY copyrighted code from now on.
"Tainted Developers". There is a legal theory that is occasionally cited in the context of producing a work-alike implementation of a published copyrighted work. There is concern that, if the creators of the new work have seen the original work, they will be unable to create a similar work without infringing the copyright of the original. It is the position of the Project that this theory is invalid for a number of reasons. As a general rule, there is no reason that a developer who has seen non-free code cannot write logically similar code for ReactOS.
What a lose of time and effort - I hate to reinvent the wheel.
"This was an appeals court decision. The appeals court doesn't decide all those things. The legal issue was whether the license was enforceable under copyright law, or whether it was a "mere covenant," meaning that Jacobsen would get nothing because he was not making money off the software. The lower court had ruled that it was a mere covenant. On appeal, the Federal Circuit vacated that ruling, which means it now goes back to the trial court to apply the "correct" law as announced by the Fed. Cir.
Two takeaway lessons, one for Big Business, and one for developers. For Big Business, you can't infringe on the copyrights of open source developers with impunity. For developers, even if you are doing open source software, REGISTER YOUR COPYRIGHT. If you register your copyright up front, you can get statutory damages and attorney fees if some idiot from Big Business decides to try this kind of stunt. Those damages are almost always more than the "actual" damages you'll get for software that you give away for free (as in beer). If you wait until after somebody infringes before you file your copyright, it's too late. And registering is cheap and easy [copyright.gov]. In many cases, you don't even need to get an attorney involved (although if you need a patent or trademark or help with a copyright, I know this really great IP attorney who also posts on Slashdot and is clued in on open source. [jw.com]
And despite the stuff above that may look like 'advice" to the untrained eye, this post absolutely, positively is NOT legal advice."