Adobe is passing by Montreal on Thursday December 6th, 2012 for the "Create the Web Tour". At this event you will get a chance to see the various Adobe Edge Tools in action and also how to create mobile apps using HTML, JavaScript and CSS using PhoneGap.
So all really cool stuff and if you want to attend follow this link to register, there is still places available.
Showing posts with label HTML. Show all posts
Showing posts with label HTML. Show all posts
2012-08-29
Firefox 15 is great for development
Firefox 15 was just released this week and I have been using it since the beta began and as far as I am concerned it is the best browser for development purposes. Let me highlight a couple of reasons why.
Working with CSS
A lot of times when developing a web site or web application, getting the "look" just right requires quite the effort. Up to now one of the best tools for working with CSS in Firefox was Firebug. However with the latest Firefox, you can just right-click on any element on a page and select "Inspect Element (Q)" and you get to see all the properties of the element and adjust them on the fly and see what effect your changes. Now this has been there for a while, but with version 15, in the bottom-right corner, you now get visual tool showing you the overall size of the element and the size of each of its properties (borders, padding and margins). Quite useful, here is a sample:
Testing for Mobile
As we go along in 2012 and beyond, a good portion of work will require us to make sure a site is mobile-ready. So if you are doing Responsive Design (using CSS Media Queries), you can now test your design in Firefox 15 without the need of having various physical devices. Simply navigate to the site and select from the Firefox menu, "Web Developer > Responsive Design View" and you will be able to see how your site looks based on some predefined screen resolutions that are available.
So happy developing using Firefox 15!
Working with CSS
A lot of times when developing a web site or web application, getting the "look" just right requires quite the effort. Up to now one of the best tools for working with CSS in Firefox was Firebug. However with the latest Firefox, you can just right-click on any element on a page and select "Inspect Element (Q)" and you get to see all the properties of the element and adjust them on the fly and see what effect your changes. Now this has been there for a while, but with version 15, in the bottom-right corner, you now get visual tool showing you the overall size of the element and the size of each of its properties (borders, padding and margins). Quite useful, here is a sample:
Testing for Mobile
As we go along in 2012 and beyond, a good portion of work will require us to make sure a site is mobile-ready. So if you are doing Responsive Design (using CSS Media Queries), you can now test your design in Firefox 15 without the need of having various physical devices. Simply navigate to the site and select from the Firefox menu, "Web Developer > Responsive Design View" and you will be able to see how your site looks based on some predefined screen resolutions that are available.
So happy developing using Firefox 15!
2012-08-21
Learn to build
There are a lot of technologies out there these days to work in: Flex, PHP, HTML, CSS, JavaScript, Ruby, the list goes on and on. And each one of them has their place in the grand scheme of things, each with its own strengths and weaknesses, each with its own particularities and each one has its appeal.
At some point in time, you will have to use one technology or another to get a job done, be it either by your own choice or because it is a requirement. And the technology of choice might not be one that you have used before. So what are you to do? Grab a book of course and starting reading. I've done that many times in the past. Another way is to read online tutorials and yes I've done this many times before as well. But honestly, the best way to learn is to ... build something! Ain't nothing like writing the lines of code yourself and seeing the results unfold right before your eyes. Really its the best way to learn, I can't stress that enough. It's the best way to learn the little hidden details of a language (or just a technology or framework for that matter) and to put what you have been reading into practice and really get a good grasp on things. You don't have to build anything complicated, just a simple contact manager will do, just enough so that you can really understand how something works.
So like my blog post title says, "Learn to build", or more like "build something" to "learn" :)
At some point in time, you will have to use one technology or another to get a job done, be it either by your own choice or because it is a requirement. And the technology of choice might not be one that you have used before. So what are you to do? Grab a book of course and starting reading. I've done that many times in the past. Another way is to read online tutorials and yes I've done this many times before as well. But honestly, the best way to learn is to ... build something! Ain't nothing like writing the lines of code yourself and seeing the results unfold right before your eyes. Really its the best way to learn, I can't stress that enough. It's the best way to learn the little hidden details of a language (or just a technology or framework for that matter) and to put what you have been reading into practice and really get a good grasp on things. You don't have to build anything complicated, just a simple contact manager will do, just enough so that you can really understand how something works.
So like my blog post title says, "Learn to build", or more like "build something" to "learn" :)
2012-06-28
Brakets, the code editor
I've been doing a lot of HTML/JS/CSS development in the last year and most of this work has been done in Eclipse. Now Eclipse is good for this type of development, but with many 3rd party JavaScript libraries out there, it is hard to find good support for these libraries in IDEs.
So I am always trying to find a better HTML/JS/CSS code editor, having used Dreamweaver, Sublime Text and WebStorm over the past year, and now we have Brackets.
Brackets is an HTML/JS/CSS code editor, developed, interestingly enough in HTML/JS/CSS :) And it's goal is to be an editor focused on HTML/JS/CSS development. Right now, the currently available download could be considered beta 1 (or perhaps not even that) and offers very little. It does have two interesting features however. First, it connects with your browser, so as you edit your file(s) and the browser will auto-refresh to show you what your changes look like. Secondly, if you highlight say a Javascript function call or a CSS class and hit CTRL+E, you will get what's called "Quick Editing". Quick Editing, allows the related piece of code from another file to appear in an overlay in the current file so you can make changes right away and save them. Saves you the hassle of having to go open a file and look for related piece of code.
Apart from that, Brackets doesn't offer much, for now. There is no code auto-completion of any kind, as this editor is still in its infancy. And hopefully at some point, it will have 3rd party library support as well. You can actually recommend features or vote for exiting ones here. But it will be growing from week to week, so I recommend, checking it out from time to time, or even contributing to the project if you can!
Labels:
Brackets,
CSS,
Editor,
HTML,
JavaScript
2012-02-10
Editing CSS on the fly in Firefox 11
As a developer, designing the look and feel of an HTML site using CSS can be a tedious task. Trying to get the dimensions of components or the colors of elements just right, can surely take its time. Thankfully over time, on-the-fly editing of CSS styles has been added to browsers and this is a great help. If you use Firefox or Chrome, you know what I am referring too, where you can right-click on an element on a page and then select "Inspect Element" using the context menu allows you to see all associated styles, make changes and see the effects of those changes directly on the page.
There is one complaint I have with this on-the-fly editing method and that is that the UI used to make the changes is too small and can be a pain to work with sometimes. However with the upcoming Firefox 11 release, there has been a new feature added, called the Style Editor. You can access the Style Editor by hitting SHIFT-F7. What it does is display a floating window (see below), that allows you to access all the CSS files associated with the currently displayed page and then make changes on the fly. So nothing new there, but it's more akin to working in your favorite editor and even allows you to save the CSS to a file. It also provides Import functionality, which allows you to quickly load different CSS files and see the effect they would have on how your page looks.
I believe this to be a great development tool going forward, so get the Firefox and give it a try!
2012-01-13
My mini-browser review
Being the first post of 2012 and seeing how I am currently brushing up on my JavaScript skills, I'd thought I'd post a mini-browser review.
Chrome
Over the last month, this has been my browser of choice at both home and work. Based on my perception, it is the fastest browser out there. It is also smooth (meaning initial start-up & opening app tabs) and when something goes wrong, you can just open up the Chrome Task Manager and kill the offending tab. I think its what most people think Firefox should be like. The only downside is that the developer tools are clunky to work with.
Firefox 4+
I have always love this browser from the start and it has been my main browser since then. But do I dare say, it seems bloated at times? The initial start-up can cause it to freeze for 30 secs (with only 2 app tabs mind you) and if a tab crashes, it takes a moment or two to recover. But for development purposes, its tools are unmatched.
Internet Explorer 9
I just can't use it. Its UI, while trying to catch up to Chrome and Firefox is still ugly. Some web sites still don't render properly and it is still behind its in implementation of HTML5/CSS3 web standards. Also how many releases have Chrome and Firefox have their been since IE9 came out? That's what I thought. Slow output from a company that needs to greatly pick up the pace. I'll wait till version 10 to see if my mind changes.
Opera 10+
I think Firefox stole its UI :) I use it from time-to-time to just see what it can offer and its pretty good. Pages load fast and it has interesting built-in development tools. How fonts look could use a little work however. It truly is the little browser that could.
Chrome
Over the last month, this has been my browser of choice at both home and work. Based on my perception, it is the fastest browser out there. It is also smooth (meaning initial start-up & opening app tabs) and when something goes wrong, you can just open up the Chrome Task Manager and kill the offending tab. I think its what most people think Firefox should be like. The only downside is that the developer tools are clunky to work with.
Firefox 4+
I have always love this browser from the start and it has been my main browser since then. But do I dare say, it seems bloated at times? The initial start-up can cause it to freeze for 30 secs (with only 2 app tabs mind you) and if a tab crashes, it takes a moment or two to recover. But for development purposes, its tools are unmatched.
Internet Explorer 9
I just can't use it. Its UI, while trying to catch up to Chrome and Firefox is still ugly. Some web sites still don't render properly and it is still behind its in implementation of HTML5/CSS3 web standards. Also how many releases have Chrome and Firefox have their been since IE9 came out? That's what I thought. Slow output from a company that needs to greatly pick up the pace. I'll wait till version 10 to see if my mind changes.
Opera 10+
I think Firefox stole its UI :) I use it from time-to-time to just see what it can offer and its pretty good. Pages load fast and it has interesting built-in development tools. How fonts look could use a little work however. It truly is the little browser that could.
Labels:
Browsers,
Flex,
HTML,
JavaScript
2010-11-19
Flex, HTML/JS Pros and Cons from a developers point-of-view
Having worked these last couple of months on a pure HTML/JS project at work, I'd thought I'd share a few pros and cons and random notes of working in both Flex and HTML/JS programming languages.
I'm not here to bash one or the other, enough people do that, just some thoughts for you guys to draw your own conclusions. Also this is from a developer stand-point, building web applications, not a web site with simple text and images...but an app, where you load, create and update data.
Note: Was using jQuery 1.4.2 for the javascript portion.
Flex
Pros
HTML/JS
Pros
I'm not here to bash one or the other, enough people do that, just some thoughts for you guys to draw your own conclusions. Also this is from a developer stand-point, building web applications, not a web site with simple text and images...but an app, where you load, create and update data.
Note: Was using jQuery 1.4.2 for the javascript portion.
Flex
Pros
- AS3 is very similar to the Java programming language
- Development, build and unit testing is almost exactly like in Java
- Great IDE (Flash Builder) provides an easy and fast way to code in MXML/AS3
- Online documentation is excellent and thus helps newbies learn the language
- SDK is open source, so a developer can learn and extend the base classes himself if need be
- In Flex, you manipulate the data directly and send it back to the server for processing, no need to worry about re-drawning the UI
- No cross-browser, cross-OS issues
- Object layout is flexible and easy to do
- With its a default theme, the app can look good and professional
- Can create re-usable controls/classes
- Takes time for new developers to realize that the app is one entity that just sends data to/from the server and not a collection of pages
- Compile times can be long
- Developer can get into the bad habit of loading lots of static data (countries, provinces, etc..) up-front, that will never be used, thus causing an unnecessary long load time for the app
- You application SWF can be de-compiled
- If end user can to copy data from multiple controls (or from DataGrid) to paste into another app (say an email), you pretty much have to code this, where its a default functionality with an HTML page since 1975
- Dealing with timezones can be a chore (Flex loves to deal with it on its own)
HTML/JS
Pros
- Faster load times
- The development cycle is quicker: update the page and reload in the browser
- In some cases you can have a single page and use Ajax calls to get the data you need, no need for a page refresh
- End users have been working with browsers for a long time now so the default copy'n'paste functionality is very useful to them and almost second nature
- Cross-browser issues still exist!
- IDE support not great for JS third-party frameworks like jQuery
- In my case, no documentation existing for how to built a jQuery widget, had to find an online tutorial after searching. So no real API doc.
- Object layout is a pain - tables still the way to go - and inconsistent across browsers sometimes
- As a developer you need some design skills to make the app look good.
- Handling the proper z-order of objects can be a chore
- Reading someone's jQuery plugin/widget can be interesting (enough braces and commas for you?)
- The browser BACK button can take your app out of proper state
2010-06-29
Firefox 4 is the new Opera
Downloaded Opera 10.54 just now and playing around with it and couldn't notice that the upcoming Firefox 4 is going to look very much like it.
And the reason why I am toying with Opera? Well we are going to be doing some heavy re-work of of one website at work and it will be all done in HTML (using JQuery for coolness). So yes that means I need to test the site as I go along in the most popular browsers: IE, Firefox and Chrome. So then I thought why not Opera as well. Heck I should also try Safari I guess. The worse is IE, cause so many still use version 6.0 (27% of internet users as of 2009). What a pain!
Oh wait, with Flex you just have test once :)
2009-02-05
Compiled code is bliss
In the past couple of days I've working on updating some functionality in one of our legacy apps at work. The app consists of many JSP pages and after making making one must considered minor changes, the Javascript on the page failed to function as it should. I keep getting an error stating that a hidden form field was no longer available. I was using Firebug in hopes of finding the issue and then resorted to looking thru all the HTML with my eyes and couldn't find any missing tags or anything of the sort. Also doing a "view source" was clearly showing me that the hidden form field was indeed there. So what was wrong?
After looking at the code I changed, I noticed that my IFRAME tag was not being closed with a corresponding IFRAME tag. And that is what cause the Javascript error. Of course nothing told me this was the case, so lost a couple hours of development trying to the root cause of my problem.
Needless to say in Flex this would have never happened. In Flex Builder, if I would have forgotten a closing tag in some MXML file the editor would have shown it to me right away and I would have corrected it immediately. And for those using only the command line Flex compiler, the same would have happened, the compilation would have failed and the appropriate error message displayed with the exact line number.
Needless to say compiled code is a bliss :)
Also, the amount of Java code written to populate HTML Comboboxes is crazy, long live Flex and its data-driven controls, where simple data-binding does wonders. Fewer lines of code, less error prone and thus better productivity.
After looking at the code I changed, I noticed that my IFRAME tag was not being closed with a corresponding IFRAME tag. And that is what cause the Javascript error. Of course nothing told me this was the case, so lost a couple hours of development trying to the root cause of my problem.
Needless to say in Flex this would have never happened. In Flex Builder, if I would have forgotten a closing tag in some MXML file the editor would have shown it to me right away and I would have corrected it immediately. And for those using only the command line Flex compiler, the same would have happened, the compilation would have failed and the appropriate error message displayed with the exact line number.
Needless to say compiled code is a bliss :)
Also, the amount of Java code written to populate HTML Comboboxes is crazy, long live Flex and its data-driven controls, where simple data-binding does wonders. Fewer lines of code, less error prone and thus better productivity.
Subscribe to:
Posts (Atom)