Its right from UI design point of view to show user some kind of progress in case site or application is busy with some internal processing. Especially with AJAX requests, because they take time!
In jQuery its very easy to hook all AJAX requests into one start/stop functions, so there is no need to show and hide progress indicator on each $.ajax request.
CodeIgniter is great framework by its simplicity. But when I moved from CakePHP, I really missed layout pattern.
CodeIgniter documentations offers this way to include non-changing site header and footer
For sure it isn’t flexible and does not show page structure in a clear way. For many years I use layout pattern. Layout describes whole page as a template with blocks for header, menu, content, etc like on figure below. On page rendering these blocks are filled with data.
I found a small code snipped for CI and improved it. You are welcome to try!
Clustering markers on GoogleMap is a very useful think in case of thousands of markers displayed. It makes the map look nice and fancy, instead of marker mess. In my previous post I told how to use MarkerClusterer library.
Today I want to add some advanced techniq how to use different styles, in case there are several datasources available.
Quite often there is a need to parse HTML and extract some values from deep-deep nested tables or so. Most front solution is to use regular expressions but they sucks with nested tags. Other way is to use XPath, which performs much better here, but has not simple syntax to use.
Nowadays almost all PHP developers knows jQuery, which became like a standard in front-end development. Why not to use it for HTML parsing using familiar syntax.
Nowadays quite lots of sites are AJAXy, especially their back-end part. This introduces one interesting issue with sessions and password protected areas.
Typical scenario is: password protected URL initiates a server-side check for valid user is logged in or in other case redirects to login page.
What happen when session is expired by timeout? Session data is wiped from the server, so already logged user becomes like a just comer. Next request to the server will eventually redirect him back to login dialog.
But not in case of AJAX. Usually AJAX requests are written in the way not to support sudden session break and this situation can lead to a very unpredictable behavior. How to fix it quick?
Quite often I was in need a function to scale an image to the size right to fit into bounding box.
For example, displaying images of real estate or product image in the shop site. Images can be different sizes, less or bigger of target size, portrait or landscape, etc..
I wrote little helper function in PHP that does that tasks using two modes: FIT and FILL. It uses standard PHP-GD extension.
If you used Google Maps in your projects as a developer, probably you faced with a problem to display huge amount of markers on the map. Problem seems more User Interface related, than technical. On small zoom it does not look good. I solved it using a very nice marker clustering library available from Google.
If you did not face with .live() handler before, this post is probably for you! It makes event handling code much cleaner and easier to use on heavily dynamic pages.
Nowadays jQuery become a very standard library used in in 90% of all projects. Simplicity of DOM manipulation with cross browser capability attracts all developers, from newbies to profs.
While developing AJAX UI with many forms nested in each other I faced a problem of not well written code, what was a real pain to modify.
I am going to tell how jQuery events saved my ass.
Nowadays many sites uses embedded map from Google for purposes like showing object location, drive-in way or more complex stuff. Recent Google Maps Version3 (V3) API becomes very powerful, but remained very clear and easy to use.
While developing site for real estate company I faced with necessity to display fancy, complex overlays on top of the map when user clicks on the marker.
There are some standard ways of showing so called info-windows. The problem is that it is not possible put complex formatting there or catch mouse clicks events.
To solve it I have to to dig into API internals and recent version V3 has some surprises here.