Hi.
This news will be very terrible for you and will result in all you puking, shouting "NO WAY!!!" in all your might, warning or banning me on every BVE/openBVE forum permanently and by IP, writing an internet meme that will depict me and force all to hate me. And this is not only reason. Read "My Story" topic on BVEStation and you will hate me since I am against this stupid COPPA law and if I will know any 10-12 years old train enthusiasts, I will support them, help them, chat with them and teach them openBVE manual route coding commands, programming in different environments for helping me and developing together. Also I am a communist/socialist, and you will hate me since so. Also besides BVE, I have many other interests that aren't railway-oriented. It's like drawing anime/manga, composing music and stuff, web designing, learning Japanese, playing guitar/synth, freestyling, chatting with children, sciences - high tech, UFOlogy (You will hate me since you all don't believe in UFOs) etc. I am like emo guy, and I hate when everyone hates me. Since I am very nice, like kiddos which are chatting with me, I won't harrass you. I will just remind you about so.
Stories are stories, but here are NEWS. I recently got a RouteBuilder source code from Uwe Post, and I am trying to develop it in future. I am searching for programmers that can help me with the visual editor interface of this new route editor. My project is not a route coding helper, not a 1st April joke, not a stunning one-click route generator. It is a visual track segment-based railway editor that can make openBVE routes. Each segment is 25 meters long and has something attached to it (background, form, wall etc - in one word, all openBVE commands). There will be no point-and-click interface like in Uwe Post's version, as I said, there will be segment-based interface, like you work in RouteBuilder with grids. I have seen similar interfaces in model railroad layout planning softwares like WinRail, RailEdit etc. The whole code of the two connected segments in BVE route will look like this:
0, .railtype 0, .ground 0, form 0;L;0;0, .limit 0
25, .railtype 0, .curve 1000
(the commands are entered just for example)
For building the route skeleton, the route definitions (as in Uwe Post's version) will be used. While developing, EVERY CSV command will be considered. Nothing except freeobj will be treated as freeobj. There will be some addons like in Uwe Post's version. There will be route packager like in Uwe Post's version. There will be both b3d, csv, x and animated object support. In one word, there will be all enough to create a powerful BVE route. And no blackjack and chicks!
If you are with me to develop the software with me, if you are fluent with C# or Delphi, if you respect my insights, we'll develop it! Who is not with me is against me!
For checking source codes (Uwe's and my), you need a Google account and TortoiseSVN to check out sources from the
subversion.