The beta for NetBeans 7.3 is out and with it comes Project Easel.
Whilst this is not too much of an inconvenience; forgetting to refresh can cause some confusion when editing files, not to mention the constant switching can slow your work flow when changing simple things like some CSS style rules. NetBeans does away with these problems!
To get started with Easel, download NetBeans 7.3 Beta (making sure to either get the Full version or JavaEE version as I don’t believe Easel is in the standard JSE version), install it and create a new project:
After creating a new project from scratch or from an existing source (this is the one I use the most for debugging results from our PDF2HTML5 converter), you can then run the project or a file within it and it will attempt to open Google Chrome with the NetBeans plugin running on the tab. If you don’t have the plugin it will prompt you to install it.
So how does the plugin help your work? Well to start with it pipes all the console outputs and error messages back to NetBeans with click-able links that will take you to the problem files and lines within those files.
And any changes you make in the IDE are instantly reflected in the browser window! So no need to manually refresh the page. This works great if you have a large enough resolution to have NetBeans and Chrome side by side or a dual monitor set-up.
It also comes with this nifty menu that allows you to preview what your pages will look like at different resolutions, along with a select tool! You can even add resolutions to the list and edit the existing ones.
Feel free to share what you have learnt using NetBeans 7.3 and Project Easel!
This post is part of our “HTML5 Article index” in these articles, we aim to help you understand the world of HTML5.
Latest posts by Lyndon Armitage (see all)
- It’s as Easy as Pi to make MagPi into HTML5 on your Pi - October 9, 2013
- Making a jQuery PDF Viewer - August 20, 2013
- Check if a PDF is valid using the HTML5 File API - July 11, 2013
- Save time, Test your Code Part 2 - June 26, 2013
- Save time, Test your Code Part 1 - June 18, 2013