BVEStation Forums
BVE => General BVE/OpenBVE => Topic started by: Dj Hammers on May 07, 2012, 08:07:32 pm
-
OpenBVE development is not dead.
Yes! It is true.
A handful of BVEStation developers are going to continue OpenBVE development collaboratively with bveworldwide.
For now, this just entails a name change and some minor tweaks, but once we get our bearings, we hope to continue full development where michelle left off.
Also, if you can help in the development of OpenBVE in any way, PLEASE PM ME.
-
Thanks to our very own CT1660, the OpenBVE source code has been modified to point to the new website as a provision for hosting managed content.
The code will be compiled and uploaded as soon as possible as a standard OpenBVE download.
-
There will be strong supervision. If you have a strong grasp of the C++ Distributable coding, please contact DJ Hammers or myself. Lets work as a team and make this a BVEStation project of a life time.
We are also usually on the BVEStation Teamspeak. You can also visit us there.
-
This should be very interesting and only serious developers need apply. This will be a time consuming project and these guys don't need outside interference.
-
This should be very interesting and only serious developers need apply. This will be a time consuming project and these guys don't need outside interference.
Well said.
-
bveworldwide is considering working on continuing openbve development too: http://bveworldwide.unlimitedboard.com/t396p45-open-bve-discussion-board-closed#4703 (http://bveworldwide.unlimitedboard.com/t396p45-open-bve-discussion-board-closed#4703)
It has been suggested that BVEStation and bveworldwide could collaborate. We will see what shakes out of this.
-
Any plans to replace or retain the managed content?
-
I'll try to contribute as much as possible.
-
Much obliged.
In regards to the closing of the OpenBVE site, I hope this gives developers a chance to better their work. As Manny said, only serious developers need contribute to the source code of the program, as that we may be able to further development, especially in the object building and route building areas, where it is needed.
BStyles
-
Your basic minimum requirements is the knowledge of C++ to be able to modify the source code.
Recommended tools:
-Notepad++ (http://notepad-plus-plus.org/)
-SharpDevelop (http://www.icsharpcode.net/OpenSource/SD/Default.aspx)
Required:
-Microsoft Visual Studio (http://www.microsoft.com/visualstudio/en-us)
Please, only serious developers need apply.
-
Your basic minimum requirements is the knowledge of C++ to be able to modify the source code.
Recommended tools:
-Notepad++ (http://notepad-plus-plus.org/)
-SharpDevelop (http://www.icsharpcode.net/OpenSource/SD/Default.aspx)
Required:
-Microsoft Visual Studio (http://www.microsoft.com/visualstudio/en-us)
Please, only serious developers need apply.
well look at my pic of my computer
there is Microsoft Visual C++ 2008 Express Edition
(http://smhnoob2.webs.com/MyPCsVBs.png)
-
OpenBVE is written in C# not C++
-
OpenBVE is written in C# not C++
actually it's both...
-
First off I am wondering if any of you guys have captured the source file. Since trainsimframework.org is now offline, we need to put the files back online first.
Nevermind, see the homepage for the latest news.
-
CT1660 and I are in the process of putting up a website that could be used for hosting openbve development, since it was realized that it was very important to have development be hosted on a site that is independent of any one group of people, similar to the idea behind the United Nations.
CT1660 took a FULL online backup of trainsimframework.org right before it went down, and we hope to ideally put the entire website back up just like it was before on a domain that would be easier to find on search engines such as google and would not be as alienating to people who are not well versed in technology...
Trainsimframework" was not necessarily the most welcoming domain name to a person who has no idea what a software framework even is.
-
First off I am wondering if any of you guys have captured the source file. Since trainsimframework.org is now offline, we need to put the files back online first.
Nevermind, see the homepage for the latest news.
Pac, if you can send me a message on Facebook or give me a call. I have an idea to propose to you. But in the mean time. I wanna make a general statement that this is a wonderful oppurtunity and I want this thread to stay clean and at the same time we get some good input. I would like people interested to see us on the Teamspeak server where we will plan and start work. We may be a young site but lets see what we can do here in the US. You know other sites will not be holding back as they already have skilled developers. I am really stressing that if you guys are truly serious, that you provide an exuburant amount of input. Thanks and let's do this!!!!!
-
Thanks to the efforts of many, a new OpenBVE website has been put up, including nearly all of the features from the old site!
Link: www.openbve.org (http://www.openbve.org)
-
Thank you everyone who was involved in the making of this site, its VERY easy to navigate and looks amazing.
-
Excellent work, guys. OpenBVE will continue because of the enthusiasm of all involved, both past and present. It's business as usual in Ireland at www.celtictrainsim.com (http://www.celtictrainsim.com)
A new 50km addition to the Ballyfeckin routes will be released later this year. You can also follow celtictrainsim on Facebook http://www.facebook.com/pages/Celtictrainsim/219222831500959 (http://www.facebook.com/pages/Celtictrainsim/219222831500959)
-
A new downloads page has been implemented on OpenBVE.org, which includes an auto-installer for OpenBVE on the Mac thanks to the efforts of CT1660!
Link: http://www.openbve.org/Download (http://www.openbve.org/Download)
-
yay *JUMP* ;D
-
...at the very least, shouldn't there be a link to odakyufan.zxq.net/openbve on the openbve.org website??
-
We're still working on the links, which would also include odakyufan's page.
-
Yes a link will be created.
There needs to be a discussion over whether or not somebody "owns" OpenBVE, because the way that several people are acting is almost as if OpenBVE is really freeware instead of in the public domain.
-
Its a rather confusing issue, which can easily be solved using a repository like github. If OpenBVE was put on a repository before, it would be easy to distinguish the original version and a forked version of the project. Not to mention nothing would've been lost in the process, and there would've been no need to scramble around to try to buy up domains just to get the file hosted online again.
It would also be a million times easier to fork the project, and collaborate with other developers, who wish to work on the project, this is all through the source code versioning system allowing teams to easily create code changes and see what was done, but of course, at this stage, I'm still trying to convince people who will be willing to do this, as placing it on a source code versioning system like github, it will allow OpenBVE to retain its Open Source visions by providing a public location where everyone can view its source code, allow anyone and everyone to contribute or freely fork the project, and provide the security of a independent service (that is unlikely to go down) allowing anyone to download it.
As far as my opinions on OpenBVE.org (remember that BVEStation Administration DOES NOT own it), because it is not assumed to be the original version of OpenBVE, while at the same time it has the name of the official name of the site. The original developer should be the one holding the site, and I'm sure its frustrating for them to have to deal with it, even if the project is in public domain. That should be simply in respect of the original developer.
Also since the original developer michelle is now dead/gone putting her roadmap is something that nobody cares about at this point. I'm sure the community has different goals and requests. Rather the roadmap should be a collaborative effort of the community and it should be what the community wants and where everyone wants the project to move forward in. This really brings in the public domain and openness of the project. There's no need for a developer blog either, we have enough forums, and github's version control will force (kinda) you to comment on every change you make, this makes it easy to create change logs and all the other goodies you'd want from a blog, not to mention make it easy to download older versions of the project, track bugs, etc.
Ok, so to summarize, we need to get this project on some type of source code versioning system, github, source forge, etc. We should respect the original authors despite the project being in public domain and thats my 2 cents.
-
OpenBVE will be put on github pending POSSIBLE further development of the program if Odakyufan does not return to the community (which judging by an ongoing, more than 2 week absence from the community seems to be growing more likely)
-
Kevin I'll give you 5 cents if you make that whole thesis statement shorter so I can understand lol
-
My views on that sort've changed.
But what I said was to get OpenBVE on a source code versioning system and we should respect the original developer.
-
My views on that sort've changed.
But what I said was to get OpenBVE on a source code versioning system and we should respect the original developer.
Lol I'm joking but yeah I know what you mean.