Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:

shortcuts: hit alt+s to submit/post or alt+p to preview

Please read the rules before you post!


Topic Summary

Posted by: waresky
« on: December 24, 2012, 07:14:07 AM »

Steve.

Concentrate over Aurora II and CLOSE old Aurora,bug or not..

Aurora II r ur child..NEW Child..

Am waitin for those.

1 year or 2..NP..but please go ahead : step forward.

happy New Project.
Posted by: Steve Walmsley
« on: September 30, 2011, 02:18:15 PM »

Hey Steve,

I just got to thinking about all the new code you're likely already writing, and the additional that you'll need to write, for the Newtonian reboot of Aurora I, and how once it all works you're likely going to want to port that over to Aurora II.   I wondered if you've considered doing all your greenfield development for BOTH revs of your software in modern VB or C# libraries? Interop between VB6 and .  NET assemblies is tricky but not impossible, and if it meant you could leverage new stuff like better installer code and newer interfaces/abstractions maybe it'd be worth the challenge to consider this approach. 

hxxp: msdn.  microsoft.  com/en-us/vbasic/ms788241
hxxp: www.  vbrad.  com/article.  aspx?id=46

If you refactor your code for, say, movement and intercept and fuel consumption calculations, or your basic system- and galaxy-generation algorithms so that certain pieces of it are implemented in . NET libraries, you could possibly wrap and invoke them from your VB6 environment and from the newer Aurora II CLR runtime.

Anyway I'm just wondering if you've given any thought to a sort of gradual movement away from VB6 for new development work, since I'm really intrigued by all the new work you're doing for the Newtonian mechanics but part of me is thinking "it's a shame this is going to have to be redone all over again for A-II. "

I think some form of developing new functionality in libraries of a more modern language will be the eventual route to Aurora II. The reason for developing Newtonian Aurora in VB6 is that I am trying out some complex funcitonality at the moment and I don't want to have to think about the language I am writing in :)

Steve
Posted by: skeolan
« on: September 24, 2011, 02:56:12 PM »

Oh and I just saw this reply on the older A-II thread that posits an interesting notion too:

hxxp: aurora2. pentarch. org/index. php/topic,4103. msg40097. html#msg40097

Quote from: Antagonist
I am reminded what ToadyOne of Dwarf Fortress did with the OpenGL code.   He basically posted source of a MUCH older unrelated game which uses the same drawing engine as DF.   The community stepped in and OpenGL'fied the code, fixing it and improving its performance considerably, after which he took the resulting product and merged it with DF source, in the end keeping DF closed but still getting help from the community.

I wonder if that is possible with the Aurora and Aurora II UI?  If there isn't too much game logic in there is it possible to post it and have the community help and pretty it up, while keeping the backend (the interesting stuff) closed?  Particularly, I am thinking of the system and galaxy views.   This is a decisively non-artist game, but those two can still do with some love.

This.  Totally this! If there were closed assemblies maintained by the original designer but with published interfaces, they could be consumed by enthusiastic contributors to help build out new UI parts for Aurora II's frontend.
Posted by: skeolan
« on: September 24, 2011, 02:46:58 PM »

Hey Steve,

I just got to thinking about all the new code you're likely already writing, and the additional that you'll need to write, for the Newtonian reboot of Aurora I, and how once it all works you're likely going to want to port that over to Aurora II.   I wondered if you've considered doing all your greenfield development for BOTH revs of your software in modern VB or C# libraries? Interop between VB6 and .  NET assemblies is tricky but not impossible, and if it meant you could leverage new stuff like better installer code and newer interfaces/abstractions maybe it'd be worth the challenge to consider this approach. 

hxxp: msdn.  microsoft.  com/en-us/vbasic/ms788241
hxxp: www.  vbrad.  com/article.  aspx?id=46

If you refactor your code for, say, movement and intercept and fuel consumption calculations, or your basic system- and galaxy-generation algorithms so that certain pieces of it are implemented in . NET libraries, you could possibly wrap and invoke them from your VB6 environment and from the newer Aurora II CLR runtime.

Anyway I'm just wondering if you've given any thought to a sort of gradual movement away from VB6 for new development work, since I'm really intrigued by all the new work you're doing for the Newtonian mechanics but part of me is thinking "it's a shame this is going to have to be redone all over again for A-II. "