Elvas Tower: Proposal to introduce 'pool' concept in timetable mode - Elvas Tower

Jump to content

Posting Rules

All new threads will be started by members of the Open Rails team, Staff, and/or Admins. Existing threads started in other forums may get moved here when it makes sense to do so.

Once a thread is started any member may post replies to it.
  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

Proposal to introduce 'pool' concept in timetable mode Rate Topic: -----

#1 User is offline   roeter 

  • Vice President
  • Group: Status: Elite Member
  • Posts: 2,325
  • Joined: 25-October 11
  • Gender:Male
  • Country:

Posted 07 March 2017 - 01:56 AM

This blueprint proposes to introduce the concept of 'train pools' in timetable mode :
Timetable pools

Example of a pool definition (two storage tracks) :

Attached Image: CochemPool.jpg

Example of paths definitions - storage path, access path and train path for train to exit from pool :

Attached Image: CochemPaths.jpg

Regards,
Rob Roeterdink

#2 User is online   James Ross 

  • Open Rails Developer
  • Group: Status: Elite Member
  • Posts: 5,399
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 19 March 2017 - 07:32 AM

View Postroeter, on 07 March 2017 - 01:56 AM, said:

This blueprint proposes to introduce the concept of 'train pools' in timetable mode :
Timetable pools

The file name in this blueprint of ".pool_or" should be ".pool-or" (or ".timetable-pool-or" to be really good) as hyphens are preferred in file extensions (the timetable extension is similarly "bad" but it's too late to fix that unless we support two extensions).

#3 User is offline   roeter 

  • Vice President
  • Group: Status: Elite Member
  • Posts: 2,325
  • Joined: 25-October 11
  • Gender:Male
  • Country:

Posted 20 March 2017 - 02:40 PM

It's hard to change a habit of a lifetime - I've been using underscores as 'separators' for over 30 years, never used hyphens.
It wouldn't be too difficult to handle both timetable-or and timetable_or definitions, I will look into that.

Regards,
Rob Roeterdink

#4 User is offline   Jovet 

  • Open Rails Developer
  • Group: Status: Elite Member
  • Posts: 2,136
  • Joined: 14-January 08
  • Gender:Male
  • Location:Omaha, Nebraska.
  • Simulator:MSTS/Open Rails
  • Country:

Posted 21 March 2017 - 03:21 AM

View PostJames Ross, on 19 March 2017 - 07:32 AM, said:

...as hyphens are preferred in file extensions...

Why?

#5 User is online   James Ross 

  • Open Rails Developer
  • Group: Status: Elite Member
  • Posts: 5,399
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 21 March 2017 - 10:00 AM

View PostJovet, on 21 March 2017 - 03:21 AM, said:

Why?

I seem to remember seeing it in one of the MSDN guidelines documents, but I haven't been able to find that since; in any case, the examples on e.g. https://msdn.microso...esktop/cc144148 and the ones registered on my computer all point to hyphens:

  • .accountpicture-ms
  • .appcontent-ms
  • .appref-ms
  • .bash_login
  • .bash_logout
  • .bash_profile
  • .devicemanifest-ms
  • .devicemetadata-ms
  • .dl_
  • .dtcp-ip
  • .dvr-ms
  • .ex_
  • .in_
  • .library-ms
  • .mfcribbon-ms
  • .ms-one-stub
  • .ms-windows-store-license
  • .oc_
  • .search-ms
  • .searchConnector-ms
  • .settingcontent-ms
  • .sr_
  • .sy_
  • .vbox-extpack
  • .xrm-ms
  • ._bsln140
  • ._bsln150
  • ._sln
  • ._sln100
  • ._sln110
  • ._sln120
  • ._sln140
  • ._sln150
  • ._sln60
  • ._sln70
  • ._sln71
  • ._sln80
  • ._sln90
  • ._vbxsln100
  • ._vbxsln110
  • ._vbxsln80
  • ._vbxsln90
  • ._vcppxsln100
  • ._vcppxsln110
  • ._vcppxsln80
  • ._vcppxsln90
  • ._vcsxsln100
  • ._vcsxsln110
  • ._vcsxsln80
  • ._vcsxsln90
  • ._vjsxsln80
  • ._vpdxsln100
  • ._vpdxsln110
  • ._vpdxsln120
  • ._vstasln80
  • ._vw8xsln110
  • ._vwdxsln100
  • ._vwdxsln110
  • ._vwdxsln120
  • ._vwdxsln140
  • ._vwdxsln150
  • ._vwdxsln80
  • ._vwdxsln90
  • ._vwinxsln120
  • ._vwinxsln140
  • ._vwinxsln150
  • ._wdxsln110
  • ._wdxsln120
  • ._wdxsln140
  • ._wdxsln150

The ones with underscores are either: Linux files (.bash_*) or compressed/backup versions of normal types (.xx_ and ._xxx).

The ones with hyphens are all normal (non-backup, etc.) files, like ".accountpicture-ms" and ".library-ms".

#6 User is offline   engmod 

  • Open Rails Developer
  • Group: Status: First Class
  • Posts: 1,489
  • Joined: 26-February 08
  • Gender:Male
  • Location:Eltham, Victoria, Australia
  • Simulator:OR
  • Country:

Posted 21 March 2017 - 11:47 AM

I too have been using _ for 30 years.

We will not be using Microsoft crap in the long term.

The hyphen is for English punctuation.

#7 User is offline   Jovet 

  • Open Rails Developer
  • Group: Status: Elite Member
  • Posts: 2,136
  • Joined: 14-January 08
  • Gender:Male
  • Location:Omaha, Nebraska.
  • Simulator:MSTS/Open Rails
  • Country:

Posted 21 March 2017 - 01:42 PM

View PostJames Ross, on 21 March 2017 - 10:00 AM, said:

I seem to remember seeing it in one of the MSDN guidelines documents, but I haven't been able to find that since;

That's utterly ridiculous. It's not Microsoft's business whether someone chooses to use underscores or hyphens in a file extension. Just more example of their inanity. I would hope you would not take such a "recommendation" seriously.

Personally, I do not like either in a file extension. I think file extensions should be short and sweet.

#8 User is online   James Ross 

  • Open Rails Developer
  • Group: Status: Elite Member
  • Posts: 5,399
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 21 March 2017 - 02:10 PM

View PostJovet, on 21 March 2017 - 01:42 PM, said:

That's utterly ridiculous. It's not Microsoft's business whether someone chooses to use underscores or hyphens in a file extension. Just more example of their inanity. I would hope you would not take such a "recommendation" seriously.

I do not understand your position at all; it's their OS, why would you not expect them to issue some guidance on how to use it? The most prominent stuff is UI/UX (which is backed by years of research and development, and user testing) but I don't see why it shouldn't extend to development stuff - in fact, it can be critically important for apps to stay compatible and not interfere with each other (although not so important in this case).

IIRC their recommendation was to use "type-company" so that the file extension was effectively namespaced to your company, preventing unexpected collisions - which is a real problem when people insist on creating new 3-letter extensions.

I don't know why they chose hyphens. I happen to think hyphens read better than underscores in this case, but above all else it is still just a recommendation. We can follow it or ignore it. My recommendation is to follow their recommendation, though. :)

#9 User is offline   Jovet 

  • Open Rails Developer
  • Group: Status: Elite Member
  • Posts: 2,136
  • Joined: 14-January 08
  • Gender:Male
  • Location:Omaha, Nebraska.
  • Simulator:MSTS/Open Rails
  • Country:

Posted 22 March 2017 - 04:19 AM

View PostJames Ross, on 21 March 2017 - 02:10 PM, said:

I do not understand your position at all; it's their OS, why would you not expect them to issue some guidance on how to use it?

Because it's micro-managing. Pun not intended.

Next it will be "recommended" Hungarian notation be used for data filenames, or something like that. It's pretty easy to make a fairly unique file extension (which, of course, do not have to be 3 chars long) without all that overthink. It's a solution for a non-problem. Just like a lot of stuff coming out of Redmond these days.

#10 User is offline   cjakeman 

  • Vice President
  • PipPipPipPipPipPipPipPip
  • Group: ET Admin
  • Posts: 2,626
  • Joined: 03-May 11
  • Gender:Male
  • Location:Peterborough, UK
  • Simulator:Open Rails
  • Country:

Posted 22 March 2017 - 09:05 AM

View PostJovet, on 22 March 2017 - 04:19 AM, said:

Because it's micro-managing.

I don't agree. When we're working together on something complex, we all benefit from things which are tidy and predictable - it saves a lot of time and frustration.

Overall, I think we developers are given a great deal of freedom, but some things are best done "the Open Rails way".

  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users