- What is traceur?
- ES6 -> ES5
- What are the required node_modules to makes traceur working properly
$ npm install traceur $ npm install traceur-runtime
- Why do you need traceur-runtime?
- What is the node command to compile ES6 to ES5?
I am having some spare time. So I am taking the liberty to compile Semantic Snippets.
I’m using few handpicked resources to ensure everything is consistent. So all the code will be mash up of
- BBC Future Media Standards & Guidelines
- Google webmaster academy
- HTML 5 Doctor
- Dive in to HTML5
- Twitter Bootstrap
- Baseline Grid
At this stage I do not intend provide comprehensive guide to how html5 should be used as above resources are more than enough. Just compilation of snippets inline with best practice for different use cases with references to additional reading materials.
Some of this issues may be subjected to debate. I certainly welcome that
You can view the progress here:
It’s been a very long time since my last post. Last year been busy with uni, work working on couple of very exciting projects and alot of travelling.
I am quite excited about new year. New plans, priorities and focus. To start with there are few personal projects that been put on hold for various reasons which I decided to take up on.
One of them is my website. I am sure all the designers agree that designing for yourself is the hardest thing (possibly only second to designing for someone close :p). But I am quite excited by this because this allows me a chance to explore and try some bleeding edge web development techonologies and do things my way.
So in the coming weeks I will be sharing my progress.
Last few weeks I’ve been looking deep in to various issues related to web. One specific area which I am militant about is semantic markup. I strongly believe that documents should be laid out in proper manner in a way that machines can understand and interpret it. Even though for the layman may not realise this.
With HTML5 designers/developers are really spoilt with markup (there are 104 HTML5 compatible tags). But that’s just the easy part! Throw in Global attributes and values then it becomes more interesting. Then add other markups like schema, WAI-ARIA spec etc… then things can drive you insane.
I am pretty sure those who actually care sometimes struggle to determine how this new markup should be used. Easier option for us it to ignore the markup and go back to the basics. However this does not help the progress. So this mean we spending time to understand the content as well as deciphering HTML5 spec in order to find best fit markup.
There are plenty of boilerplates out there which we can use readily. Danger is it’s very easy to take this for granted and be lazy and build a website/app and ignore the website use cases also miss out on rich experiences we create because we are not aware of it since it’s not in boilerplate.
Truly understanding the HTML5 spec (and browser capabilities) allow designers/developers to implement well thought site architecture.
For example how to design layout of an article with headings content and pictures. Like we do with a print design to put in to perspective. Then use appropriate tags to mark sections like <time> so that machines and robots (SEO, Screen readers etc) can understand and in turn allow us to build better rich user experience for users.
So I’ve decided to spend time building/compiling an extensive snippet library and concentrate on Semantic markup to explore all the possibilities of HTML5 and how it can be used in different contexts/user case without bloating the code.
Issue I personally have with these kind of posts is they can be sometimes too long to read. So idea here is compile list of markups which can be mixed and matched.
I will be doing these snippets as modules which can be interchanged without upsetting semantic markup and allowing the code to be adopted to rapidly to work with overall unique user cases that may arise.
A word of Caution
I like to iterate a point regards to this. That these snippets can be subjective and depend on how you perceive the content and may not work out.
Before writing a JAVA program first need to download JDK which allows write JAVA and compile the code.
- Download appropriate JAVA SE Development Kit (JDK) for your operating system
- Run the Installation
- Navigate to C:\Program Files\Java\jdk1.7.0\bin (this location may change in any instance you want to navigate to bin in JDK installation) make sure you have the .exe files there.
- copy the location of the bin C:\Program Files\Java\jdk1.7.0\bin
- Right click on computer and select properties > Advanced System settings > Environment variables
- Click on New and Variable name as Path and variable value as location of the bin so in my case it would be C:\Program Files\Java\jdk1.7.0\bin
- Click OK OK
- To make sure compiler is working and ready for JAVA programming open cmd and run JavaC and if Java Compliler is working should get some random code as below