search

alexyork / TrondheimDC-WebApp

TrondheimDC-WebApp
3 stars 1 forks source link

List speakers #1

Closed peirix closed 12 years ago

peirix commented 12 years ago

We need to list out all speakers

yornaath commented 12 years ago

Maybe the speakers should be tagged/cetagorized so the user can filter on subject he/she is interested in?

peirix commented 12 years ago

We can probably use the tags from the talks? If a speaker has multiple talks, then they will just get all the tags from all the talks?

hegerokenes commented 12 years ago

It will be more useful to tag sessions. We are going to do that in the printed program.

Suggestion for the data needed on each speaker: Name Twitter handle Bio Sessions

yornaath commented 12 years ago

Good point as the talks can vary in subject

alexyork commented 12 years ago

Yes, sessions are tagged, not speakers.

The mockups simply list the speaker name. However, below the speaker name we could show all of the tags for that speaker (the tags taken from all of the speakers sessions). Other info (like twitter handle, etc) should not be shown in the list, it should only be shown in the "drill-down" page.

For now, there is no need to allow filtering speaker by tags. We can add that as a "nice to have" if we have time. I think this will be fine:

Alex York (javascript, html5)

Hege Røkenes (html5, css3)

etc

peirix commented 12 years ago

I started looking at listing speakers today. But since the info was based on "sessions", I found it a bit hard, since there might be several sessions pr speaker. So I moved the speaker info out into a separate list, and merged them on id's.

It's my first attempt at using backbone, so if someone could just look over it and see if I'm sortof on target with it, that would be nice. (I got two green lights, so at least it's working :p)

I didn't get to actually listing out speakers, as I spent most of my time trying to merge the two lists. But I can work on that later today.

alexyork commented 12 years ago

Perhaps we don't even need a SpeakerID - maybe the speaker name on the Speaker and Session models are enough to link the two? :-)

Pål, if you have time tonight, perhaps we can do a remote "pair programming" session via Skype/GChat or something to work more on the Speaker list? You have gotten off to a great start, and I think it would be useful to finish it off together! There are some changes we should make that might be easier to explain without posting lots of github issues messages :-P

peirix commented 12 years ago

@alexyork Yeah, the reason I wanted to use id instead of name is simply to avoid typo's.

I have time set aside for progging tonight, so that would be good (: Just email me when you want to start. I'll probably be on around 6-7-ish.

alexyork commented 12 years ago

An int/guid ID is typically the right way to do ID's... however, I like to keep things simple, and since we only have 30 sessions/speakers, and we are in control of the data, I think we can get away with just speaker name! If there is a typo, we will just correct it ;-)

Tonight I will be home around 6-7 so I will tweet/email you and then we can begin :-)

peirix commented 12 years ago

Do we want to link from a speakers session and into a single session view? Should we even have single session views? By that I mean a page that displays only one session, and have the outline and such for that session.

alexyork commented 12 years ago

I am closing this issue because it works. Any tweaks or changes can be created as new issues.