glaubinix / conference-schedule Goto Github PK

Using px can break the layout, e.g. if the default font size is different on different devices (desktop browser vs. mobile), the schedule tabs and refresh have different heights. That's why we should use a relative unit (em) for this.

@robin-drexler just noticed this:

It would be super awesome if people could click on a location (let's say in the description of the talk, as I don't know a better concept for it) and then a view with all talks for a specific location would be rendered.

Currently events are (almost) always triggered twice, because they were added twice: 1st time when schedule is initialized from localstorage and a 2nd time after successful sync via XHR.

This leads to performance issues on frequently triggered events like "touchmove" and on the other hand it's just bad.

it was mentioned that it is really annoying that it is impossible to select description text or interact with the box at all without triggering the hide/show action.

Should include travis build status
How to setup and run the test files on the command line / browser

Currently data is only loaded after page load. We need a refresh button or "pull down to refresh" functionality.

I was just thinking that it might be useful to display some sort of alert if the schedule changes. I remember that at jsconfeu there was a talk not yet announced in the beginning (or at least not added to the spreadsheet) and I only saw it later by accident.

Implementation: We could simply diff the data from the local storage to the data fetched from the server. Some things should be fairly easy to diff like "Talk was moved to room X" or "Talk X was cancelled".

This could be done with a simple box at the bottom of the page.

If you star a talk, reload -> star is gone

This issue has probably a lot in common with the schedule change plugin - we need a way to identify the talk. Once we are able to do that this should be really easy.

We should add a config file where you can specify a couple of things. Like:
-json or spreadsheet (or even something else)
-json name, spreadsheet id

Maybe even add stylesheet, title, ...

@kiltec mentioned that he might be interested in writing some tests (because we do have non so far). Question now what library / framework would be want?

My suggestion would be Jasmine.

Since a couple of days Code Climate also supports JS, it looks pretty useful and it's free for OSS projects:
http://blog.codeclimate.com/blog/2013/10/24/code-climate-for-javascript/

What do you think?

The lib should be added to the package.json

It would be nice to have a toggle for each talk, that highlights it in a certain way (e.g. by showing an icon or changing the background color).

We should bind the events to the most outer element of a talk in order to support "click anywhere" within a talk section.

Roadmap

Just because I need a place to dump my ideas

v0.2

• Remove custom code with npm packages #phaseOne
• Introduce browserify
• Introduce build step

v0.3

• Remove custom code with npm packages #phaseTwo

v0.4

• Introduce templating and avoid html strings (Preparation for plugin system)

v0.5

• Plugin system not necessary support for all existing plugins
• Reintroduce tests for custom code (Preference on tap)

v1.0

• Plugin system full support for current plugins
• Extract plugins into modules
• Move project to org

Future (no specific order)

• iOS like Menu support (Button on the top, menu slides in from the left)
• Filters/Search
• Location Maps probably GoogleMaps integration for the location(s)
• Venue maps: not really sure what is possible but for some conferences this would be really helpful
• ConfS as a Service
• Allow multiple events in one App and allow certain events to be hidden (for instance for something like jsfest)

@BattleRattle can you please tell me if you are still interested in being actively involved in the project or as an alternative as an advisor?

If yes, please have a look at my proposal and check if you agree. Idea is to prepare for a v1.0 with full plugin support and actually usable/extendable structure.

We were talking already a couple of times about a build script
* merge js, css
* maybe build custom html with data from the config file and replace stuff like title
* maybe even merge everything into one single html file
* have different tasks for the different formats

A start would be actually figure out what sort of build script we want:
* grunt
* custom js file
* other option?