User:Stuart/Scratchpad II: Difference between revisions
Jump to navigation
Jump to search
m Added link to story |
Added rail to exeter bits |
||
| Line 1: | Line 1: | ||
== Rail to Exeter == | |||
(from [http://www.traveline.info/ Traveline]) through there is [http://ojp.nationalrail.co.uk/service/timesandfares/LAN/HON/010717/0030/dep/070717/0830/dep?excludeslowertrains&via=Exeter this from nationalrail]: Less impressive, though - it has me sat around in Brum for an hour. | |||
(Lancaster) Train to Wolverhampton | |||
1 hour 37 minutes, Depart 07:56, Arrive 09:33 Virgin Trains | |||
(Wolverhampton) Train to Birmingham New Street | |||
17 minutes, Depart 09:41, Arrive 09:58 CrossCountry | |||
(Birmingham New Street) Train to Exeter St Davids | |||
2 hours 31 minutes, Depart 10:12, Arrive 12:43 CrossCountry | |||
== {{us|68}} - Stories for {{ep|10|Permissions Overhaul}} == | == {{us|68}} - Stories for {{ep|10|Permissions Overhaul}} == | ||
* Split compound methods into separate methods | * Split compound methods into separate methods | ||
Latest revision as of 22:54, 4 June 2017
Rail to Exeter
(from Traveline) through there is this from nationalrail: Less impressive, though - it has me sat around in Brum for an hour.
(Lancaster) Train to Wolverhampton 1 hour 37 minutes, Depart 07:56, Arrive 09:33 Virgin Trains
(Wolverhampton) Train to Birmingham New Street 17 minutes, Depart 09:41, Arrive 09:58 CrossCountry
(Birmingham New Street) Train to Exeter St Davids 2 hours 31 minutes, Depart 10:12, Arrive 12:43 CrossCountry
US-68 - Stories for EP-10: Permissions Overhaul
- Split compound methods into separate methods
- The archetypal example is changing a password, but there are others
- Tidy up existing methods
- There are some methods which are unused from the interface - either, they're only used from within
clsServeritself, or they're not used at all. These should be sorted out. - Equally, there are some which are just single line calls of another method - this is fine when it's just a class, but when we need to maintain > 1 file for each method, and apply behaviour to each individual method, it becomes somewhat wasteful. eg.
HasSchedulerDataUpdatedandHasFontDataUpdatedare just single line calls toHasDataUpdatedwith a first argument of"Schedule"or"Font", respectively.- Actually, that's as far as my examples went
- There are some methods which are unused from the interface - either, they're only used from within
- Enumerate the new permissions required
- Tie them into the current permissions, ie. for each current permission, detail the set of new permissions that a user with that permission would end up with
- Assign the new permissions to the IServer methods