W line - Federal Center vs Golden

[yamanote1138]

short version:
W line schedule doesn't indicate the difference between trains that stop at Federal Center station and ones that go to end of the line. Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to the end of the line. Due to budgetary reasons, there is only a single track between the Federal Center station and the Jefferson Government Center stations. In order to keep the rest of the system in sync, RTD has some trains turn around at the Federal Center station instead of going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red Rocks, which is the very next stop after Federal Center. SO... If I get on the 'wrong' W line, I have to get off at Federal Center and wait for the next train. Not a big deal unless the weather is particularly nasty.

When planning a trip that boards at any upstream station, it would be nice to know if the 'W Line' time you're looking at is one that will stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected schedule for more info.

ps - Thank you for open-sourcing the codebase, I have forked it... but am still at the grunting and poking it with a stick phase. If I can figure out a fix, I'll happily submit a PR.

[john970]

Chad,

We're actually in the midst of an update here internally (at Tack). This
is valuable info, I'll pass on to Kelvin who is working on this.

JKohn

On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains that
stop at Federal Center station and ones that go to end of the line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to the
end of the line. Due to budgetary reasons, there is only a single
track between the Federal Center station and the Jefferson Government
Center stations. In order to keep the rest of the system in sync, RTD
has some trains turn around at the Federal Center station instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red Rocks,
which is the very next stop after Federal Center. SO... If I get on
the 'wrong' W line, I have to get off at Federal Center and wait for
the next train. Not a big deal unless the weather is particularly
nasty.

When planning a trip that boards at any upstream station, it would be
nice to know if the 'W Line' time you're looking at is one that will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked it... but
am still at the grunting and poking it with a stick phase. If I can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:
#1

[yamanote1138]

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand what it is supposed to do, but couldn’t figure out the steps to reproduce.  I tried rotating my phone upside-down portrait mode and blew in the microphone.  All that happened is that my wife looked at me like I was insane.  (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at Tack). This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains that
stop at Federal Center station and ones that go to end of the line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to the
end of the line. Due to budgetary reasons, there is only a single
track between the Federal Center station and the Jefferson Government
Center stations. In order to keep the rest of the system in sync, RTD
has some trains turn around at the Federal Center station instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red Rocks,
which is the very next stop after Federal Center. SO... If I get on
the 'wrong' W line, I have to get off at Federal Center and wait for
the next train. Not a big deal unless the weather is particularly
nasty.

When planning a trip that boards at any upstream station, it would be
nice to know if the 'W Line' time you're looking at is one that will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked it... but
am still at the grunting and poking it with a stick phase. If I can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:
#1 (comment)

[john970]

I think we disabled the mic/audio because we couldn't get it to work- I
honestly don't remember. It also makes flippy-flippy noises when the
times update and I'm not sure if that's working or not in the currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand what
it is supposed to do, but couldn’t figure out the steps to
reproduce.  I tried rotating my phone upside-down portrait mode and
blew in the microphone.  All that happened is that my wife looked at
me like I was insane.  (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains that
stop at Federal Center station and ones that go to end of the line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to the
end of the line. Due to budgetary reasons, there is only a single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in sync,
RTD
has some trains turn around at the Federal Center station instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get on
the 'wrong' W line, I have to get off at Federal Center and wait for
the next train. Not a big deal unless the weather is particularly
nasty.

When planning a trip that boards at any upstream station, it would
be
nice to know if the 'W Line' time you're looking at is one that will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked it...
but
am still at the grunting and poking it with a stick phase. If I can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:
#1 (comment)

---

Reply to this email directly or view it on GitHub:
#1 (comment)

[yamanote1138]

yup, the flippy noises work in the current version. love that :)

On Mon, Jul 27, 2015 at 3:30 PM, John Myers notifications@github.com
wrote:

I think we disabled the mic/audio because we couldn't get it to work- I
honestly don't remember. It also makes flippy-flippy noises when the
times update and I'm not sure if that's working or not in the currently
deployed version.
John
On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand what
it is supposed to do, but couldn’t figure out the steps to
reproduce.  I tried rotating my phone upside-down portrait mode and
blew in the microphone.  All that happened is that my wife looked at
me like I was insane.  (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains that
stop at Federal Center station and ones that go to end of the line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to the
end of the line. Due to budgetary reasons, there is only a single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in sync,
RTD
has some trains turn around at the Federal Center station instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get on
the 'wrong' W line, I have to get off at Federal Center and wait for
the next train. Not a big deal unless the weather is particularly
nasty.

When planning a trip that boards at any upstream station, it would
be
nice to know if the 'W Line' time you're looking at is one that will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked it...
but
am still at the grunting and poking it with a stick phase. If I can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:
#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Reply to this email directly or view it on GitHub:
#1 (comment)

[PyroMonkey]

Flippy-flippy noises?

John I'm pretty sure I shouldn't be on this distribution list.

Hows everything going, anyway?

Jonathan Hartstein
jonhartstein@gmail.com
720-235-7209

On 7/27/15 3:30 PM, John Myers wrote:

I think we disabled the mic/audio because we couldn't get it to work- I
honestly don't remember. It also makes flippy-flippy noises when the
times update and I'm not sure if that's working or not in the currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode and
blew in the microphone. All that happened is that my wife looked at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains that
stop at Federal Center station and ones that go to end of the line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to the
end of the line. Due to budgetary reasons, there is only a single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in sync,
RTD
has some trains turn around at the Federal Center station instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get on
the 'wrong' W line, I have to get off at Federal Center and wait for
the next train. Not a big deal unless the weather is particularly
nasty.

When planning a trip that boards at any upstream station, it would
be
nice to know if the 'W Line' time you're looking at is one that will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out [the affected

schedule](http://www3.rtd-denver.com/schedules/getSchedule.action?runboardId=152&routeId=103&routeType=2&branch=W&lineName=W&direction=W-Bound&serviceType=4#day)
for more info.

ps - Thank you for open-sourcing the codebase, I have forked it...
but
am still at the grunting and poking it with a stick phase. If I can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

—
Reply to this email directly or view it on GitHub
#1 (comment).

[john970]

Hey Jon- it's a github list so I'm thinking you can add/remove yourself-
let me know if not. Will send you a message off-list.

On 27 Jul 2015, at 15:35, Jonathan Hartstein wrote:

Flippy-flippy noises?

John I'm pretty sure I shouldn't be on this distribution list.

Hows everything going, anyway?

Jonathan Hartstein
jonhartstein@gmail.com
720-235-7209

On 7/27/15 3:30 PM, John Myers wrote:

I think we disabled the mic/audio because we couldn't get it to work-
I
honestly don't remember. It also makes flippy-flippy noises when the
times update and I'm not sure if that's working or not in the
currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand
what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode and
blew in the microphone. All that happened is that my wife looked at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains
that
stop at Federal Center station and ones that go to end of the
line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to
the
end of the line. Due to budgetary reasons, there is only a single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in sync,
RTD
has some trains turn around at the Federal Center station instead
of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get
on
the 'wrong' W line, I have to get off at Federal Center and wait
for
the next train. Not a big deal unless the weather is particularly
nasty.

When planning a trip that boards at any upstream station, it would
be
nice to know if the 'W Line' time you're looking at is one that
will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out [the affected

schedule](http://www3.rtd-denver.com/schedules/getSchedule.action?runboardId=152&routeId=103&routeType=2&branch=W&lineName=W&direction=W-Bound&serviceType=4#day)
for more info.

ps - Thank you for open-sourcing the codebase, I have forked it...
but
am still at the grunting and poking it with a stick phase. If I
can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

—
Reply to this email directly or view it on GitHub
#1 (comment).

---

Reply to this email directly or view it on GitHub:
#1 (comment)

[john970]

Hey Chad,
I'm working on updating the app. The icons aren't dense enough to add an
asterisk but I put a red dot in the corner that should help distinguish the
differences between the routes. I'm still doing some digging myself to
figure out how to pull this off but I'll be in touch! Thanks!

On Mon, Jul 27, 2015 at 3:30 PM John Myers john@tackmobile.com wrote:

I think we disabled the mic/audio because we couldn't get it to work- I
honestly don't remember. It also makes flippy-flippy noises when the
times update and I'm not sure if that's working or not in the currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode and
blew in the microphone. All that happened is that my wife looked at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains that
stop at Federal Center station and ones that go to end of the line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to the
end of the line. Due to budgetary reasons, there is only a single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in sync,
RTD
has some trains turn around at the Federal Center station instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get on
the 'wrong' W line, I have to get off at Federal Center and wait for
the next train. Not a big deal unless the weather is particularly
nasty.

When planning a trip that boards at any upstream station, it would
be
nice to know if the 'W Line' time you're looking at is one that will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked it...
but
am still at the grunting and poking it with a stick phase. If I can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

[john970]

Hey Chad,

I just pushed up the fix for the W-line westward trains. Now when a train
will not continue all the way to the end of the line an asterisk will be
added to the cell.

On Mon, Jul 27, 2015 at 3:54 PM Kelvin Kosbab kelvin.kosbab@tackmobile.com
wrote:

Hey Chad,
I'm working on updating the app. The icons aren't dense enough to add an
asterisk but I put a red dot in the corner that should help distinguish the
differences between the routes. I'm still doing some digging myself to
figure out how to pull this off but I'll be in touch! Thanks!

On Mon, Jul 27, 2015 at 3:30 PM John Myers john@tackmobile.com wrote:

I think we disabled the mic/audio because we couldn't get it to work- I
honestly don't remember. It also makes flippy-flippy noises when the
times update and I'm not sure if that's working or not in the currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode and
blew in the microphone. All that happened is that my wife looked at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains that
stop at Federal Center station and ones that go to end of the line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to the
end of the line. Due to budgetary reasons, there is only a single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in sync,
RTD
has some trains turn around at the Federal Center station instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get on
the 'wrong' W line, I have to get off at Federal Center and wait for
the next train. Not a big deal unless the weather is particularly
nasty.

When planning a trip that boards at any upstream station, it would
be
nice to know if the 'W Line' time you're looking at is one that will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked it...
but
am still at the grunting and poking it with a stick phase. If I can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

[yamanote1138]

That is awesome! thanks so much :) I really appreciate it!

On Wed, Jul 29, 2015 at 9:59 AM, John Myers notifications@github.com
wrote:

Hey Chad,
I just pushed up the fix for the W-line westward trains. Now when a train
will not continue all the way to the end of the line an asterisk will be
added to the cell.
On Mon, Jul 27, 2015 at 3:54 PM Kelvin Kosbab kelvin.kosbab@tackmobile.com
wrote:

Hey Chad,
I'm working on updating the app. The icons aren't dense enough to add an
asterisk but I put a red dot in the corner that should help distinguish the
differences between the routes. I'm still doing some digging myself to
figure out how to pull this off but I'll be in touch! Thanks!

On Mon, Jul 27, 2015 at 3:30 PM John Myers john@tackmobile.com wrote:

I think we disabled the mic/audio because we couldn't get it to work- I
honestly don't remember. It also makes flippy-flippy noises when the
times update and I'm not sure if that's working or not in the currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode and
blew in the microphone. All that happened is that my wife looked at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains that
stop at Federal Center station and ones that go to end of the line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to the
end of the line. Due to budgetary reasons, there is only a single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in sync,
RTD
has some trains turn around at the Federal Center station instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get on
the 'wrong' W line, I have to get off at Federal Center and wait for
the next train. Not a big deal unless the weather is particularly
nasty.

When planning a trip that boards at any upstream station, it would
be
nice to know if the 'W Line' time you're looking at is one that will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked it...
but
am still at the grunting and poking it with a stick phase. If I can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

Kelvin Kosbab
Developer
719.310.5732

tackmobile.com

Reply to this email directly or view it on GitHub:
#1 (comment)

[john970]

Chad do you mind doing some testing before we submit?

Thanks,

John

On 29 Jul 2015, at 10:19, Chad Francis wrote:

That is awesome! thanks so much :) I really appreciate it!

On Wed, Jul 29, 2015 at 9:59 AM, John Myers notifications@github.com
wrote:

Hey Chad,
I just pushed up the fix for the W-line westward trains. Now when a
train
will not continue all the way to the end of the line an asterisk will
be
added to the cell.
On Mon, Jul 27, 2015 at 3:54 PM Kelvin Kosbab
kelvin.kosbab@tackmobile.com
wrote:

Hey Chad,
I'm working on updating the app. The icons aren't dense enough to
add an
asterisk but I put a red dot in the corner that should help
distinguish the
differences between the routes. I'm still doing some digging myself
to
figure out how to pull this off but I'll be in touch! Thanks!

On Mon, Jul 27, 2015 at 3:30 PM John Myers john@tackmobile.com
wrote:

I think we disabled the mic/audio because we couldn't get it to
work- I
honestly don't remember. It also makes flippy-flippy noises when
the
times update and I'm not sure if that's working or not in the
currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand
what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode
and
blew in the microphone. All that happened is that my wife looked
at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at
Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains
that
stop at Federal Center station and ones that go to end of the
line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to
the
end of the line. Due to budgetary reasons, there is only a
single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in
sync,
RTD
has some trains turn around at the Federal Center station
instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get
on
the 'wrong' W line, I have to get off at Federal Center and wait
for
the next train. Not a big deal unless the weather is
particularly
nasty.

When planning a trip that boards at any upstream station, it
would
be
nice to know if the 'W Line' time you're looking at is one that
will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked
it...
but
am still at the grunting and poking it with a stick phase. If I
can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

Kelvin Kosbab
Developer
719.310.5732

tackmobile.com

Reply to this email directly or view it on GitHub:
#1 (comment)

---

Reply to this email directly or view it on GitHub:
#1 (comment)

[PyroMonkey]

Now I'm just being CC'd on these :)

Jonathan Hartstein
jonhartstein@gmail.com
720-235-7209

On 7/29/15 10:21 AM, John Myers wrote:

Chad do you mind doing some testing before we submit?

Thanks,

John

On 29 Jul 2015, at 10:19, Chad Francis wrote:

That is awesome! thanks so much :) I really appreciate it!

On Wed, Jul 29, 2015 at 9:59 AM, John Myers notifications@github.com
wrote:

Hey Chad,
I just pushed up the fix for the W-line westward trains. Now when a
train
will not continue all the way to the end of the line an asterisk will
be
added to the cell.
On Mon, Jul 27, 2015 at 3:54 PM Kelvin Kosbab
kelvin.kosbab@tackmobile.com
wrote:

Hey Chad,
I'm working on updating the app. The icons aren't dense enough to
add an
asterisk but I put a red dot in the corner that should help
distinguish the
differences between the routes. I'm still doing some digging myself
to
figure out how to pull this off but I'll be in touch! Thanks!

On Mon, Jul 27, 2015 at 3:30 PM John Myers john@tackmobile.com
wrote:

I think we disabled the mic/audio because we couldn't get it to
work- I
honestly don't remember. It also makes flippy-flippy noises when
the
times update and I'm not sure if that's working or not in the
currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand
what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode
and
blew in the microphone. All that happened is that my wife looked
at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at
Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains
that
stop at Federal Center station and ones that go to end of the
line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to
the
end of the line. Due to budgetary reasons, there is only a
single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in
sync,
RTD
has some trains turn around at the Federal Center station
instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get
on
the 'wrong' W line, I have to get off at Federal Center and wait
for
the next train. Not a big deal unless the weather is
particularly
nasty.

When planning a trip that boards at any upstream station, it
would
be
nice to know if the 'W Line' time you're looking at is one that
will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out [the affected
schedule](

http://www3.rtd-denver.com/schedules/getSchedule.action?runboardId=152&routeId=103&routeType=2&branch=W&lineName=W&direction=W-Bound&serviceType=4#day
)

for more info.

ps - Thank you for open-sourcing the codebase, I have forked
it...
but
am still at the grunting and poking it with a stick phase. If I
can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

Kelvin Kosbab
Developer
719.310.5732

tackmobile.com

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

—
Reply to this email directly or view it on GitHub
#1 (comment).

[yamanote1138]

I’d be happy to!  what mechanism are you using to distribute beta releases?

On Wed, Jul 29, 2015 at 10:21 AM, John Myers notifications@github.com
wrote:

Chad do you mind doing some testing before we submit?
Thanks,
John
On 29 Jul 2015, at 10:19, Chad Francis wrote:

That is awesome! thanks so much :) I really appreciate it!

On Wed, Jul 29, 2015 at 9:59 AM, John Myers notifications@github.com
wrote:

Hey Chad,
I just pushed up the fix for the W-line westward trains. Now when a
train
will not continue all the way to the end of the line an asterisk will
be
added to the cell.
On Mon, Jul 27, 2015 at 3:54 PM Kelvin Kosbab
kelvin.kosbab@tackmobile.com
wrote:

Hey Chad,
I'm working on updating the app. The icons aren't dense enough to
add an
asterisk but I put a red dot in the corner that should help
distinguish the
differences between the routes. I'm still doing some digging myself
to
figure out how to pull this off but I'll be in touch! Thanks!

On Mon, Jul 27, 2015 at 3:30 PM John Myers john@tackmobile.com
wrote:

I think we disabled the mic/audio because we couldn't get it to
work- I
honestly don't remember. It also makes flippy-flippy noises when
the
times update and I'm not sure if that's working or not in the
currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand
what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode
and
blew in the microphone. All that happened is that my wife looked
at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at
Tack).
This
is valuable info, I'll pass on to Kelvin who is working on this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains
that
stop at Federal Center station and ones that go to end of the
line.
Suggest adding an asterisk to the icon or something like that...

long version:
On weekday evenings, the westbound W line does not always go to
the
end of the line. Due to budgetary reasons, there is only a
single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in
sync,
RTD
has some trains turn around at the Federal Center station
instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I get
on
the 'wrong' W line, I have to get off at Federal Center and wait
for
the next train. Not a big deal unless the weather is
particularly
nasty.

When planning a trip that boards at any upstream station, it
would
be
nice to know if the 'W Line' time you're looking at is one that
will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked
it...
but
am still at the grunting and poking it with a stick phase. If I
can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

Kelvin Kosbab
Developer
719.310.5732

tackmobile.com

Reply to this email directly or view it on GitHub:
#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Reply to this email directly or view it on GitHub:
#1 (comment)

[john970]

Hmm, they are all github.com domains I can see. Are you sure you're
unsubscribed from all of the lists? I don't see you as a collaborator on
github.

On 29 Jul 2015, at 10:21, Jonathan Hartstein wrote:

Now I'm just being CC'd on these :)

Jonathan Hartstein
jonhartstein@gmail.com
720-235-7209

On 7/29/15 10:21 AM, John Myers wrote:

Chad do you mind doing some testing before we submit?

Thanks,

John

On 29 Jul 2015, at 10:19, Chad Francis wrote:

That is awesome! thanks so much :) I really appreciate it!

On Wed, Jul 29, 2015 at 9:59 AM, John Myers
notifications@github.com
wrote:

Hey Chad,
I just pushed up the fix for the W-line westward trains. Now when a
train
will not continue all the way to the end of the line an asterisk
will
be
added to the cell.
On Mon, Jul 27, 2015 at 3:54 PM Kelvin Kosbab
kelvin.kosbab@tackmobile.com
wrote:

Hey Chad,
I'm working on updating the app. The icons aren't dense enough to
add an
asterisk but I put a red dot in the corner that should help
distinguish the
differences between the routes. I'm still doing some digging
myself
to
figure out how to pull this off but I'll be in touch! Thanks!

On Mon, Jul 27, 2015 at 3:30 PM John Myers john@tackmobile.com
wrote:

I think we disabled the mic/audio because we couldn't get it to
work- I
honestly don't remember. It also makes flippy-flippy noises when
the
times update and I'm not sure if that's working or not in the
currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand
what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode
and
blew in the microphone. All that happened is that my wife looked
at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at
Tack).
This
is valuable info, I'll pass on to Kelvin who is working on
this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains
that
stop at Federal Center station and ones that go to end of the
line.
Suggest adding an asterisk to the icon or something like
that...

long version:
On weekday evenings, the westbound W line does not always go
to
the
end of the line. Due to budgetary reasons, there is only a
single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in
sync,
RTD
has some trains turn around at the Federal Center station
instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I
get
on
the 'wrong' W line, I have to get off at Federal Center and
wait
for
the next train. Not a big deal unless the weather is
particularly
nasty.

When planning a trip that boards at any upstream station, it
would
be
nice to know if the 'W Line' time you're looking at is one
that
will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out [the affected
schedule](

http://www3.rtd-denver.com/schedules/getSchedule.action?runboardId=152&routeId=103&routeType=2&branch=W&lineName=W&direction=W-Bound&serviceType=4#day
)

for more info.

ps - Thank you for open-sourcing the codebase, I have forked
it...
but
am still at the grunting and poking it with a stick phase. If
I
can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

Kelvin Kosbab
Developer
719.310.5732

tackmobile.com

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

—
Reply to this email directly or view it on GitHub
#1 (comment).

---

Reply to this email directly or view it on GitHub:
#1 (comment)

[john970]

We don't have anything formal setup for this project, but I believe
Kelvin pushed the changes up, so you should be able to pull and build on
your device.

John

On 29 Jul 2015, at 10:23, Chad Francis wrote:

I’d be happy to!  what mechanism are you using to distribute beta
releases?

On Wed, Jul 29, 2015 at 10:21 AM, John Myers
notifications@github.com
wrote:

Chad do you mind doing some testing before we submit?
Thanks,
John
On 29 Jul 2015, at 10:19, Chad Francis wrote:

That is awesome! thanks so much :) I really appreciate it!

On Wed, Jul 29, 2015 at 9:59 AM, John Myers
notifications@github.com
wrote:

Hey Chad,
I just pushed up the fix for the W-line westward trains. Now when a
train
will not continue all the way to the end of the line an asterisk
will
be
added to the cell.
On Mon, Jul 27, 2015 at 3:54 PM Kelvin Kosbab
kelvin.kosbab@tackmobile.com
wrote:

Hey Chad,
I'm working on updating the app. The icons aren't dense enough to
add an
asterisk but I put a red dot in the corner that should help
distinguish the
differences between the routes. I'm still doing some digging
myself
to
figure out how to pull this off but I'll be in touch! Thanks!

On Mon, Jul 27, 2015 at 3:30 PM John Myers john@tackmobile.com
wrote:

I think we disabled the mic/audio because we couldn't get it to
work- I
honestly don't remember. It also makes flippy-flippy noises when
the
times update and I'm not sure if that's working or not in the
currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand
what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode
and
blew in the microphone. All that happened is that my wife
looked
at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at
Tack).
This
is valuable info, I'll pass on to Kelvin who is working on
this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains
that
stop at Federal Center station and ones that go to end of the
line.
Suggest adding an asterisk to the icon or something like
that...

long version:
On weekday evenings, the westbound W line does not always go
to
the
end of the line. Due to budgetary reasons, there is only a
single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in
sync,
RTD
has some trains turn around at the Federal Center station
instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I
get
on
the 'wrong' W line, I have to get off at Federal Center and
wait
for
the next train. Not a big deal unless the weather is
particularly
nasty.

When planning a trip that boards at any upstream station, it
would
be
nice to know if the 'W Line' time you're looking at is one
that
will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out the affected
schedule
for more info.

ps - Thank you for open-sourcing the codebase, I have forked
it...
but
am still at the grunting and poking it with a stick phase. If
I
can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

Kelvin Kosbab
Developer
719.310.5732

tackmobile.com

Reply to this email directly or view it on GitHub:
#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Reply to this email directly or view it on GitHub:
#1 (comment)

---

Reply to this email directly or view it on GitHub:
#1 (comment)

[PyroMonkey]

Check the CC list on the sent messages.

Also, it looks like I somehow had a fork of the repo on GitHub, so even
though I wasn't "Watching" the main one, I was still getting the
messages. I just deleted my fork, so hopefully that'll help.

Jonathan Hartstein
jonhartstein@gmail.com
720-235-7209

On 7/29/15 10:24 AM, John Myers wrote:

Hmm, they are all github.com domains I can see. Are you sure you're
unsubscribed from all of the lists? I don't see you as a collaborator on
github.

On 29 Jul 2015, at 10:21, Jonathan Hartstein wrote:

Now I'm just being CC'd on these :)

Jonathan Hartstein
jonhartstein@gmail.com
720-235-7209

On 7/29/15 10:21 AM, John Myers wrote:

Chad do you mind doing some testing before we submit?

Thanks,

John

On 29 Jul 2015, at 10:19, Chad Francis wrote:

That is awesome! thanks so much :) I really appreciate it!

On Wed, Jul 29, 2015 at 9:59 AM, John Myers
notifications@github.com
wrote:

Hey Chad,
I just pushed up the fix for the W-line westward trains. Now when a
train
will not continue all the way to the end of the line an asterisk
will
be
added to the cell.
On Mon, Jul 27, 2015 at 3:54 PM Kelvin Kosbab
kelvin.kosbab@tackmobile.com
wrote:

Hey Chad,
I'm working on updating the app. The icons aren't dense enough to
add an
asterisk but I put a red dot in the corner that should help
distinguish the
differences between the routes. I'm still doing some digging
myself
to
figure out how to pull this off but I'll be in touch! Thanks!

On Mon, Jul 27, 2015 at 3:30 PM John Myers john@tackmobile.com
wrote:

I think we disabled the mic/audio because we couldn't get it to
work- I
honestly don't remember. It also makes flippy-flippy noises when
the
times update and I'm not sure if that's working or not in the
currently
deployed version.

John

On 27 Jul 2015, at 12:59, Chad Francis wrote:

very cool, thanks for the info!

also, i noticed a folder labelled ‘easter egg’. i understand
what
it is supposed to do, but couldn’t figure out the steps to
reproduce. I tried rotating my phone upside-down portrait mode
and
blew in the microphone. All that happened is that my wife looked
at
me like I was insane. (but that’s nothing new)

On Mon, Jul 27, 2015 at 11:59 AM, John Myers
notifications@github.com
wrote:

Chad,
We're actually in the midst of an update here internally (at
Tack).
This
is valuable info, I'll pass on to Kelvin who is working on
this.
JKohn
On 27 Jul 2015, at 0:13, Chad Francis wrote:

short version:
W line schedule doesn't indicate the difference between trains
that
stop at Federal Center station and ones that go to end of the
line.
Suggest adding an asterisk to the icon or something like
that...

long version:
On weekday evenings, the westbound W line does not always go
to
the
end of the line. Due to budgetary reasons, there is only a
single
track between the Federal Center station and the Jefferson
Government
Center stations. In order to keep the rest of the system in
sync,
RTD
has some trains turn around at the Federal Center station
instead of
going to the end of the line.

Most folks don't even notice. Unfortunately, I get off at Red
Rocks,
which is the very next stop after Federal Center. SO... If I
get
on
the 'wrong' W line, I have to get off at Federal Center and
wait
for
the next train. Not a big deal unless the weather is
particularly
nasty.

When planning a trip that boards at any upstream station, it
would
be
nice to know if the 'W Line' time you're looking at is one
that
will
stop at Federal Center or go all the way to the end.

This only affects the W Line. You can check out [the affected
schedule](

http://www3.rtd-denver.com/schedules/getSchedule.action?runboardId=152&routeId=103&routeType=2&branch=W&lineName=W&direction=W-Bound&serviceType=4#day

)

for more info.

ps - Thank you for open-sourcing the codebase, I have forked
it...
but
am still at the grunting and poking it with a stick phase. If
I
can
figure out a fix, I'll happily submit a PR.

---

Reply to this email directly or view it on GitHub:

#1

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

Kelvin Kosbab
Developer
719.310.5732
tackmobile.com

Kelvin Kosbab
Developer
719.310.5732

tackmobile.com

Reply to this email directly or view it on GitHub:

#1 (comment)

---

Reply to this email directly or view it on GitHub:

#1 (comment)

—
Reply to this email directly or view it on GitHub

#1 (comment).

---

Reply to this email directly or view it on GitHub:

#1 (comment)

—
Reply to this email directly or view it on GitHub
#1 (comment).