Hai speedy64,
speedy64 wrote:I would be happy to do it for myself - but atm i would say - i easily are not able to do it for myself

i have done only a few small things in C before - never more than 100lines... far away from saying i could do something like that...
The only thing you really need is enough will power to make it happen.
Anything else can be learned.
Learning takes time, but hey, it is a hobby, it does not need to be finished any time soon, does it?
speedy64 wrote:but i think u know how long it takes to come far enough to build something in such a big (and very nice) project.
yes I do

(I spent 1.5 years designing and implementing new widgets)
Be patient, make a master plan with steps so you understand where you want to go (and what is part and what is not part of the plan), then start at step one. You also will need to start again from scratch a few times. It is all part of the learning process.
Realizing that you did something wrong, and that all your hard work is for nothing, really ruins your day. However, in hind sight, trying it again always brought new insights, and resulted in an even better project result in the end.
speedy64 wrote:i really dont know how it does that autoreplace atm... but when its possible to say "replace car x with car y", why shouldnt it be possible to say "if option sampletrain is set, replace waggons x with waggons y"... but ok maybe its much more complicate

for shure there are a lot more options like fright-types and so on to look at. but that was why i meaned a sampletrain - a kind of "dont care about the old frights, settings and soon, easily take anything from that one" - and only for a single shared timetable to be shure they all go same way...
Like you, I have no clue how it works, and neither how it should work in the new enhanced way. (I may be a dev, but I have seen about 20% of the code, 10-15% or so I really understand, so the remaining 90-85% is still to discover for me!)
speedy64 wrote: there i saw: there is very much movement in the code

new widgets (what the hell are this?

)
Code ages rapidly indeed, I think it is a good sign.
speedy64 wrote: and so on... it took a few days to find anything. at least i could do it for trunk, my later try to update also for cargodist failed as i couldnt find any old cargodist-version to look the differences.
My standard approach when I have to find out something, is to document it using doxygen comments. That way, the information is preserved, and others (and myself too in the future) don't have to dig again.
Good luck with plotting your plan.