Recently I have been toying with the idea of re-coding StarForge in C#. Why, you ask? Because the current version is riddled with bugs that I don't really feel like tracking down. It also was designed very poorly, since it was the first program I had ever written on this scale. I'm also thinking about making it open-source.
I am a firm believer in Open Source myself, and so have voted that way. Will the rewritten form have an previous connections, such as use of Starforge-made Library files or not? Or is everything being redone.
Im voteing on making the new one. You have learned so much since you started work on the current version sometimes starting over is the best way to go. You had mentioned that you realized compatability takes higher priority than the features it has, it would be good to start a editor with that opinion. You know where to contact me for my opinions.
I think open source is a good idea. Alot of people have there own ideas for SF and a few might actually have the know how and determination to do it. I would suggest having your email on it and request that people inform you if there working on it. (I don't really know much about this sort of thing so i might sound like an idiot now)
PS. Do you intend on realeasing what you have for 2.1 before starting the C version? Did you finish the overlap previewer?
im going for new version open source
you should realky make another editor of starforge
or atleast an expansion for it
I think that starting anew is the way to go.
QUOTE(Heimdal @ Oct 29 2004, 09:46 AM)
Recently I have been toying with the idea of re-coding StarForge in C#. Why, you ask? Because the current version is riddled with bugs that I don't really feel like tracking down. It also was designed very poorly, since it was the first program I had ever written on this scale. I'm also thinking about making it open-source.
[right][snapback]91556[/snapback][/right]
that would be cool, old starforge is pretty complex, and can i have one suggestion (jokingly) can it have an undo button?
well im not sure it was a bug or something, but the undo button didnt work on old starforge
I definitely think you should make a new one, and open source too.
ops. i acedently clicked on make the new one, i meant to click on make the new one open scource. any way you could change that???
i think you should do the new open scource because mostly what they said, so people can add new things if they figure out how to do it.
Make Strforge perfect, then we will never need another editor. Welcome back Heim.
Well Heimdal did promise all those features... hm? Yes, this editor will definitely be the best if Starforge 2.1 is already the best. I'd be looking forward to that mapping online or whatever it was. :/
Towards what Bolt was talking about, maybe you could enable the ability to create add-on patches which can be applied to StarForge, in many aspects, therefore enabling you not to give out full, open-source which may be tampered with, while not just giving it to friends, which isn't good for a Community as a whole.
Thats difficult i know, because likely it will lead to huge bugs with these Add-Ons. But sometimes they add good things.
wait... is the new version of SF out?
I vote yes. My reasons can be found in Bolt's post.
and another thing, i's not easy finding each and every bug and fixing it in 2.1
QUOTE(Heimdal @ Oct 29 2004, 09:46 AM)
I'm also thinking about making it open-source.
[right][snapback]91556[/snapback][/right]
yes,yes,yes,...and yes. please
I don't think you would do such a thing...but....here's a suggestion, learn python and make it in there
What in the world? Why on earth Python?
A new version with undo would be super nice! Maybe make it a bit easier for newbies to jump in and not be confused as hell? Like i was when i first got it lol
QUOTE(NeoNightmareX @ Oct 29 2004, 03:17 PM)
that would be cool, old starforge is pretty complex, and can i have one suggestion (jokingly) can it have an undo button?
well im not sure it was a bug or something, but the undo button didnt work on old starforge
[right][snapback]91613[/snapback][/right]
Nah it was just incompleat, I remember heimdal telling me he had figured out how to do it and he might of even done it after he released the current version. Well better that he reply to this himself (i know your watching lol).
Perhaps you could team up with Suicidal Insanity or something, combine the best of SCMDraft2 and SCXE and Starforge and SCMIE and all those other things into one editor. It really makes no sense for you both to be competing, when you could be working together and achieving the ultimate editor.
QUOTE(illusion(SS) @ Oct 29 2004, 08:02 PM)
wait... is the new version of SF out?
[right][snapback]91778[/snapback][/right]
no hes thinking about making it but needs a kind like open source
QUOTE(Paella @ Oct 30 2004, 09:33 AM)
Perhaps you could team up with Suicidal Insanity or something, combine the best of SCMDraft2 and SCXE and Starforge and SCMIE and all those other things into one editor. It really makes no sense for you both to be competing, when you could be working together and achieving the ultimate editor.
[right][snapback]91980[/snapback][/right]
I agree, that would be purely awsome... SCMDraft with a choice bewteen drop-down or text triggers, with custom terrain or something.
QUOTE
Perhaps you could team up with Suicidal Insanity or something, combine the best of SCMDraft2 and SCXE and Starforge and SCMIE and all those other things into one editor. It really makes no sense for you both to be competing, when you could be working together and achieving the ultimate editor.
I doubt that would happen... SI probably wouldn't want to. Clokr_ already said he may be working on his own editor source, he also said that he isn't continuing ProEdit. What's that? SCXE? You can't combine a
modification of Staredit.exe with that of
real homebrew editors.
QUOTE(DT_Battlekruser @ Oct 29 2004, 11:11 PM)
What in the world? Why on earth Python?
[right][snapback]91856[/snapback][/right]
because we have to get rid of all the outdated[crappy] languages like C
Python is hard to make applications in..
I would work on a new one and release the code for the old one, so others could improve upon it. Or maybe fix easy-to-fix bugs on the old one as you work on the new one.
fast fix big bugs and open source the old one.
then work on the new one