General > News and Announcements
The Beginning
Gob:
--- Quote from: Lexx on June 30, 2013, 01:39:57 am ---You remember wrong then, because I never said something like that. The only thing I did was the more pretty interface.
--- End quote ---
Oh yeah sorry. Nvm then :P.
wladimiiir:
--- Quote from: AHS-9 on June 28, 2013, 07:53:13 am ---...we have decided to focus on something slightly different than a game - creating a new FOnline development kit with improved scripts and tools. Our aim is to create a better starting point for new projects...
--- End quote ---
Do you think you could give us some more info about the process of what you plan to do? For example:
* Do you plan to implement everything from scratch?
* If so do you plan to implement it in AS or C#?
* Do you plan to do some changes in hardcoded part of the engine? And do you even plan to use CVET's engine or create a new one?
* Can we help?Thanks. :)
Bartosz:
--- Quote from: wladimiiir on July 01, 2013, 10:55:19 am ---Do you think you could give us some more info about the process of what you plan to do? For example:
* Do you plan to implement everything from scratch?
* If so do you plan to implement it in AS or C#?
* Do you plan to do some changes in hardcoded part of the engine? And do you even plan to use CVET's engine or create a new one?
* Can we help?Thanks. :)
--- End quote ---
* No, it's always good to reuse, depends how far we want to go.
* I'm now pushing C# exclusive, as it gives more possibilities and frees of interop burden. (If we choose C# only, it would even differ from what's currently in Server/mono, because many things could've been done differently if AS hadn't been taken into consideration.
* Starting new engine would be too much of a task. We definitely would want customized one, however, we're struggling currently whether to decide that backward compatibility is worth it, or not.
* I suppose so, but that damned process of early decisions is somewhat blocking such initiative.
wladimiiir:
--- Quote from: Bartosz on July 01, 2013, 11:00:04 am ---
* No, it's always good to reuse, depends how far we want to go.
* I'm now pushing C# exclusive, as it gives more possibilities and frees of interop burden. (If we choose C# only, it would even differ from what's currently in Server/mono, because many things could've been done differently if AS hadn't been taken into consideration.
* Starting new engine would be too much of a task. We definitely would want customized one, however, we're struggling currently whether to decide that backward compatibility is worth it, or not.
* I suppose so, but that damned process of early decisions is somewhat blocking such initiative.
--- End quote ---
1. That's what I am asking - how far do you want to go? :)
2. Thumbs up for that.
3. From my point of view backward compatibility is not worth, if you would be forced not to introduce features that could be really helpful and better or pay for bad decisions made in the past. If you are trying to do better improved version of SDK, that should serve as a base for new projects, than screw backward compatibility and do it better. :)
4. I guess, it is not some decisioning that community could help you with. Or is it?
Bartosz:
--- Quote from: wladimiiir on July 01, 2013, 11:22:59 am ---1. That's what I am asking - how far do you want to go? :)
2. Thumbs up for that.
3. From my point of view backward compatibility is not worth, if you would be forced not to introduce features that could be really helpful and better or pay for bad decisions made in the past. If you are trying to do better improved version of SDK, that should serve as a base for new projects, than screw backward compatibility and do it better. :)
4. I guess, it is not some decisioning that community could help you with. Or is it?
--- End quote ---
1. Depends on 4:)
4. I guess community could state their needs for better SDK, but we're aware of many needs and limitations ourselves, we just need to somehow fit it into 'roadmap' picture, so we are deciding about "how", and not necesarily "what".
I guess lots of it should be exposed outside, to give people a chance to contribute, but also some things cannot be, due to the "closed" nature of engine. And things like choosing scripting runtime is definitely an engine thing, but once it's chosen, things like utility classes, frameworks are definitely open things.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version