The aim was to have a more up to date navigation bar which is fully responsive across all platforms. We took the Behaviour Driven Development (BDD) approach which involved us writing tests & defining the behaviour of our nav first. Before doing that we needed to come up with a way this nav would work.
Architecture & Idea
The radionav was broken down into separate modules (using RequireJS) which gave us a Model, View, Controller structure. The View would manipulate the DOM, our Models would gather data (for our Programmes panel) and the Controller would handle everything inbetween such as user actions.
Building in a BDD fashion
We then moved to the visual behaviour of the radio nav itself; including animation, colours changing, links working properly and content showing on certain screen sizes. Each of these scenarios were written in a language known as Gherkin. Gherkin can be understood by cucumber which in turn talks to Capybara, a tool which simulates real world interaction. These tests are then ran in a browser automatically and therefore becomes very useful when building anything that’s responsive as we can resize the browser, check what appears, resize again, repeat..
The advantage became clear when we changed how we wanted certain modules to work before writing up any code, had we changed our minds later the process would have taken longer. You are also clarifying your requirements from the beginning with everyone, this should mean less confusion across the board when features (and their usability) are brought to light. Stakeholders being able to read and understand the requirements (scenarios) you wrote down for each feature provides an advantage too.
The BDD process certainly takes more time, you need to think about investing time to write tests, to consult with others when sketching out scenarios on how your product will work and learning new frameworks/languages. There’s no denying this adds more overhead and its certainly not something which will run smoothly amongst the team overnight.
Libraries and Techniques
We have our models which asynchronously go of an get data for search results in the programme panel. Instead of using typical JS callbacks we use promises. Promises are very powerful and represent the eventual outcome of an asynchronous action, they’re also chainable. You can read more about the Promises/A+ spec here
EventEmitter & RequireJS
By calling events rather than functions directly means we can hook multiple functions to a particular event. Our section of code that handles the view fires off events when actions happen by the user (I.E clicking on the search box, typing in a query etc). The event fires and the view sits and waits for data to come back. By separating logic into modules we can swap out how our implementation but keep the view the same. These modules are put together with RequireJS.
Well it seems we’ve reached a point where we can do CSS transition and have them degrade gracefully; browsers not supporting these just open and close. The opening and closing of the drawer is a CSS transition. This brings us a nice advantage of having the animations being handled directly by the browser; It should give us a much smoother transition. Our JS code can listen on the transtionEnd event to know when the drawer has finished opening/closing.
So here it is.. We finally have an updated version of Mixcloud's widget for Joomla users (1.6+). As you can see I have included it here on this page on the left. Although this widget is quite simple to implement by hand many users can simply install, add their URL and wallah!
But there is also another reason why this module would suite some users. It validates!.. Yes thats right, it passes W3C validation correctly on most used HTML doctypes, thats HTML4.0, XHTML1.0 and HTML5. I often find it annoying installing flash modules/widget and then my webpage not validate so I have cleaned the code up (mixcloud tut tut) to make sure this validates and works on all browsers down to IE 6.
You can set the Height, Width, the link from which cloudset it uses and finally the style colour for the font, button and loading bar colour.
W3schools holds too much inaccurate information which many readers take at face value without even challenging. This causes issues which usually ends up with users coming back to us asking why something isn't working, when in reality none of which would have happened if they chose the right place to begin with! Another issue is transparency, we don't know the people updating this site, how often they're updating and what they plan to add/remove. It makes the source quite untrustworthy.
W3schools also holds outdated information: Lets take a look at PHP for example, here it still advocates the use of mysql_connect(). Something developers would warn you against using! Lets also remember that W3Schools.com is not affiliated with the W3C in any way. Members of the W3C have asked W3Schools to explicitly disavow any connection in the past, and they have refused to do so. More info: W3Fools
Mozilla Development Network (or MDN)
We are an open community of developers building resources for a better web, regardless of brand, browser or platform. Anyone can contribute and each person who does makes us stronger. Together we can continue to drive innovation on the Web to serve the greater good. It starts here, with you.
Using it effectively
MDN doesn't come up in search results very well, its usually overshadowed by someone's blog or W3Schools (argggh!). I find the best way to bring up the MDN reference is to prefix your query with mdn. So in google your search would be like this; 'mdn canvas'.
Lets make this faster
Ok sounds like some effort? Lets make this easier. If you're using chrome click 'the spanner' -> settings -> then click 'manage search engines':
In Search Engine Name - enter 'MDN' (without quotes)
In Keyword - enter 'mdn' (without quotes)
in Link - enter 'https://developer.mozilla.org/en-US/search?q=%s' without quotes.
Now we have our own MDN search. Lets give it a try: Typing in 'mdn' (followed by spacebar) now triggers our search engine for the Mozilla Development Network (awesome!). Now we just need to type in our keyword. I want more information on the article element so im going to search for that.
Let's make this EVEN faster!
So that was too much work right? How can we make this even faster? What if we completely bypass MDN's search results and go directly to the page we're after? That way we type article and we're there!. Lets take advantage of Google's "I'm feeling lucky!" search link to give us a helping hand.
Go back into Chrome settings
Manage search engines
in 'Add new search engine' type in 'MDN Instant' (without quotes)
in keyword type in 'mdni' (without quotes)
in link add 'http://google.com/search?btnI=1&q=mdn+%s' without quotes
Notice how we're still prefixing 'mdn' to our search? We're adding a space (+) then our query after. Assuming its something web relative, we can go directly to pages we want! Let's try this again:
in the omnibox we'll type in 'mdni' (followed by Space to trigger search engine)
we then add the 'article' after. (no image for this but you know what you're doing!)
The all new Blu Saphir website was launched on the 30th of April this year. Its about time Blu Saphir website had a change considering its predeccessor was outdated, had little content and was entirely based on flash.
The site's built on the open source CMS Joomla, which in turn, is built on PHP. This is one of the most dynamic websites I have ever put together. For example: The radio page feeds directly from Mixcloud's servers using JSON. So once Jay has finished his radio show and uploaded it to his mixcloud account, the radio page will change completely, including tracklistings. This saves Jay from having to do any work to manually change the radio page. The releases page uses redSHOP which is a carting system for Joomla, this enables Jay to manage his own releases and sales without having to dive into the code! Changes such as price, description, new releases and images can be altered with a click.
Thats right, I've used the HTML5 buzzword. Infact this site is HTML5 and uses some of its features...such as the audio player (yes I know it could look better) uses the Jplayer script which enables audio to be played on all (well most) browsers and even your iPhone or android! This actually falls back to flash for browser which don't support the <audio> tag yet. Other features soon to be implemented are localstorage and canvas for the ads at the top.