guuz / anwb-mobile Goto Github PK

The list can be hard coded for now.
It should be filterable.

See the jq mobile docs about list filtering.

Create a welkom page to inform users about the (new) mobile website.

For every route there are lines like this:
req.locals = req.locals || {};
req.locals.title = 'ANWB Mobiel';
req.locals.apps = {apps:{}};
req.locals.apptags = null;

This doesn't scale and maintain very well. We need to find a more elegant solution.

As described in the title, the traffic jam information should be dynamic.

Anwb.nl currently does not support a json feed for this, but we can work with the html-file that is publicly available.

We probably want to be able to show the visitor the apps for his/her device. If so; do we want to do server- or client-side detection and what are we gonna use for that?

Can we seperate the stdout log file and stderr log file?

We should show the effects of a responsive and adaptive design.
Just like the jQuery mobile docs we could shift some collums around.
It would be nice to be able to see the platform selection on the left on a tablet. Instead of a pup up.

Cheerio should be a more simple alternative to jsdom.
https://github.com/MatthewMueller/cheerio
It doesnt have the contextify/python/visual studio dependencies.

We are using a reverse proxy infront of our application. For logging purposes we need the "real" ip address.

If you look at the verkeer and wegenwacht page you see that on the verkeer page the related apps accordion has rounded corners and on the wegenwacht page they do not. I think it should be rounded corners on both page. HTML seems to be the same... (same Jade template)

There are no apps shown on the Android or iOS apps pages.

user a src folder for the sources, etc.

The related apps feature breaks some features on other pages. Integrate it correctly.

The wegenwacht page does not exist yet. Create it and fill it with some content.

In the client-side JavaScript file we use:

$(document).bind('pagebeforeshow', toonGerelateerdeApps);

This seems to fire twice for every page that is shown.

We want to cache the verkeersinformatie page for a short while. Like 1 minute. Therefore we need to set the cache headers and make sure jQuery Mobile doesnt cache the page in the DOM. So far this was unsuccessful. This might work by adding dom-cache=false on the page div. (see jQuery mobile docs.)

There seems to be a memory leak of some sort. After a few hours the memory and CPU usage grows and grows.
I suspect this has something to do with the scraping of traffic jams. (issues seems to be introduced since that time.)