Demonstration Activities
#1
Posted 10 June 2019 - 11:27 PM
These activities will seek to fulfill the following purposes:
i) To demonstrate a particular feature or function within Open Rails and the correct configuration needed to implement it.
ii) To allow a user to test rolling stock configurations of their own. This can be done by replacing the existing consist with their own consist.
Currently it is recommended that the OR MG version is used to run these activities, as some of the features demonstrated are not available in the mainstream OR.
The first of this series of activities can be found on this page.
As stated elsewhere in the forum, I would like to add appropriate sounds to these activities, so if anybody can help in this area it would be appreciated.
#2
Posted 15 June 2019 - 03:18 AM
steamer_ctn, on 10 June 2019 - 11:27 PM, said:
Which features are these? Are they on the roadmap or in blueprints, do they have pull requests?
#3
Posted 15 June 2019 - 02:38 PM
James Ross, on 15 June 2019 - 03:18 AM, said:
The additional features are described in the latest feature release list for MG, as well as the associated forum topics, and the demonstration activity subject.
James Ross, on 15 June 2019 - 03:18 AM, said:
Blueprints have been raised.
James Ross, on 15 June 2019 - 03:18 AM, said:
No
#4
Posted 16 June 2019 - 11:50 AM
steamer_ctn, on 15 June 2019 - 02:38 PM, said:
I can see four separate features by you in that list; do you need them all? What, if anything, is preventing them being included in Open Rails? Have they been rejected, or not approved yet?
#5
Posted 16 June 2019 - 09:46 PM
James Ross, on 16 June 2019 - 11:50 AM, said:
James Ross, on 16 June 2019 - 11:50 AM, said:
James Ross, on 16 June 2019 - 11:50 AM, said:
The effort and timeliness to manage code commits into OR.
#6
Posted 29 June 2019 - 06:12 AM
steamer_ctn, on 16 June 2019 - 09:46 PM, said:
Would it help at all if I implemented the proposed unstable version includes trusted, open PRs (last quote and response)?
#7
Posted 29 June 2019 - 10:05 PM
James Ross, on 29 June 2019 - 06:12 AM, said:
Anything that reduces the time and effort required to develop and implement code will be a good step forward.
From my perspective, as a guide, the old commit process was around the right balance of developer effort vs the value for my time involvement in developing code, so if any additional effort is required, then it is likely to make it very difficult for me to find the extra time required to follow it.
#8
Posted 28 July 2019 - 10:04 AM
steamer_ctn, on 29 June 2019 - 10:05 PM, said:
Just to make sure you know - and everyone not part of the private forums:
The Unstable Version of Open Rails now has a new version numbering and new contents.
The versions are now dates prefixed with "U", such as "U2019.07.16-1959".
The contents now include all open GitHub pull requests from trusted developers (anyone in the world can open a pull request on GitHub so we're limiting this to only people we already know). This means that a new unstable version will be created when any of the following happens:
- Pull request created
- Pull request updated
- Pull request merged (although the output of this ought not to behave differently to the one before)
The change log and builds are in the same place as before.