Expand current home page to link to team/year pages

[eigenhombre]

Currently, "/team/:team/:year/" and "/" are available but not connected.

I want to see a list of available teams and years on the home page. Clicking on one of those gives me a list of years or teams available for that team or year, respectively. Clicking on that final link should send me to "/team/:team/:year/". This will make our site immediately navigable and arguably minimally useful.

[mrocklin]

This list would be very large.

Rather, I suggest putting a list of possible teams as an auto-complete list for the team form. Can you suggest a javascript widget to do this?

Also /team/:team/:year/ is just an api address. ajaxtest.html is really the user visible page. I'll change the name of this.

[eigenhombre]

On Aug 10, 2013, at 10:22 AM, Matthew Rocklin notifications@github.com wrote:

This list would be very large.

Rather, I suggest putting a list of possible teams as an auto-complete list for the team form. Can you suggest a javascript widget to do this?

Autocompletion is great, but it's more complex to implement. In general, I propose to start with simple HTML (it could be a subset of teams/years initially) and then add widgets/features once something is working.

Another way of looking at this is thinking about site usability from the beginning. Right now the user sees "Welcome to Fantasy Baseball" and that's all there is. What small changes can we make to make the data explorable? Remember that this is a prototype, so fancy widgets are less important than getting a feel for what links should lead where.

Also /team/:team/:year/ is just an api address. ajaxtest.html is really the user visible page. I'll change the name of this.

I don't follow you. ajaxtest.html is the template, right? The user browses to something like /team/NYN/2013.... You want to change the name of the template, that's obviously fine, and a good idea.

— Reply to this email directly or view it on GitHub.

[mrocklin]

ajaxtest.html is fully runnable. It accesses /team/NYN/2013, 2012 etc. through ajax calls. Ideally users will be able to switch between teams and years without a page reload.

When I navigate google maps the url changes without page reloads. How is this done? I'd like to make the year and team form values part of the url.

Is this a reasonable direction?

Also happy to chat if lower-latency communication is desirable.

On Sat, Aug 10, 2013 at 10:34 AM, John Jacobsen notifications@github.comwrote:

On Aug 10, 2013, at 10:22 AM, Matthew Rocklin notifications@github.com wrote:

This list would be very large.

Rather, I suggest putting a list of possible teams as an auto-complete list for the team form. Can you suggest a javascript widget to do this?

Autocompletion is great, but it's more complex to implement. In general, I propose to start with simple HTML (it could be a subset of teams/years initially) and then add widgets/features once something is working.

Another way of looking at this is thinking about site usability from the beginning. Right now the user sees "Welcome to Fantasy Baseball" and that's all there is. What small changes can we make to make the data explorable? Remember that this is a prototype, so fancy widgets are less important than getting a feel for what links should lead where.

Also /team/:team/:year/ is just an api address. ajaxtest.html is really the user visible page. I'll change the name of this.

I don't follow you. ajaxtest.html is the template, right? The user browses to something like /team/NYN/2013.... You want to change the name of the template, that's obviously fine, and a good idea.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/mrocklin/ball/issues/15#issuecomment-22441751 .

[eigenhombre]

On Aug 10, 2013, at 10:38 AM, Matthew Rocklin notifications@github.com wrote:

ajaxtest.html is fully runnable. It accesses /team/NYN/2013, 2012 etc. through ajax calls. Ideally users will be able to switch between teams and years without a page reload.

Got it.

When I navigate google maps the url changes without page reloads. How is this done? I'd like to make the year and team form values part of the url.

Is this a reasonable direction?

Also happy to chat if lower-latency communication is desirable.

We should chat - but again, I strongly favor getting information out as simply as possible first and worrying about fancy navigation features after. Many Web sites start as pure HTML prototypes with no JavaScript at all.

The reason for this is that fiddling with JavaScript tends to be very time consuming and one can easily waste time fiddling with the wrong things.

Unfortunately I am on the run now until late tonight, but hope to have more time tomorrow.

On Sat, Aug 10, 2013 at 10:34 AM, John Jacobsen notifications@github.comwrote:

On Aug 10, 2013, at 10:22 AM, Matthew Rocklin notifications@github.com wrote:

This list would be very large.

Rather, I suggest putting a list of possible teams as an auto-complete list for the team form. Can you suggest a javascript widget to do this?

Autocompletion is great, but it's more complex to implement. In general, I propose to start with simple HTML (it could be a subset of teams/years initially) and then add widgets/features once something is working.

Another way of looking at this is thinking about site usability from the beginning. Right now the user sees "Welcome to Fantasy Baseball" and that's all there is. What small changes can we make to make the data explorable? Remember that this is a prototype, so fancy widgets are less important than getting a feel for what links should lead where.

Also /team/:team/:year/ is just an api address. ajaxtest.html is really the user visible page. I'll change the name of this.

I don't follow you. ajaxtest.html is the template, right? The user browses to something like /team/NYN/2013.... You want to change the name of the template, that's obviously fine, and a good idea.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/mrocklin/ball/issues/15#issuecomment-22441751 .

— Reply to this email directly or view it on GitHub.

[mrocklin]

I'm interested in learning the JS game a bit. Doing the ajax call wasn't too bad and resulted in, I think a substantially better solution. It's fairly slick as is.

[eigenhombre]

One last thought/question - you know Datomic better than I and can already produce queries/results quickly. If you were limited to any number of pure HTML pages, what potentially interesting views could you display for users? That may help flesh out a minimally-interesting high-level experience for initial users.

BTW, Eden says there are 30 MLB teams. That's not too many to put on one page.

At the JS level, since you're interested in that: if you want to prototype autocompletion, there is a jQuery plugin -- I'd start there and see if you can get anywhere until tomorrow.

At some point we will also want to start thinking of an overall look-and-feel - styling (colors, typefaces, button styling etc.) and possibly logo(s). That stuff can yield early returns in terms of overall fun, and can be applied to very simple HTML as well as complex JS widgets.