Now that Zend Server has had its public beta release I thought it was finally worth a installation to see what its all about. One of the main differences between this and xampp that jumped out at me was there was a Mac version to download along side Linux (rpm and dem) and Windows. There will be two version of the product to be called the ‘Community Edition’ and the standard commercial version. The commercial version comes with monitoring capabilities and additional Zend modules (page cache and data cache).
After the initial download of around 50mb for windows with comes with a nice installer to take care of everything. It then I realised I hadn’t downloaded everything yet and more modules need to be added before installing such as MySQL. There was also other option like a Java Bridge, Zend Framework (with or without dojo) and various other database adaptors.
After a 5 minutes everything was done. The apache web service monitor appeared which confirmed it was running. Icons now appeared in my program folder so I went ahead and click on ‘Zend Service’. Also worth noting that it also had Links to apache, MySQL service programs and to the htdocs.
Up loaded a web page taking me to the control panel. Everything looked a bit more flashy and provided similar links as xampp to phpmyadmin, a phpinfo file and the status of various services. You are reminded in various places that you only have the free version which is a little irritating. With the links provided you have easy access to the root folder and setting up passwords on MySQL.
Its really done exactly what it said it would do and i encountered no problems installing it. Less experienced users may bit a little confused when it comes choosing which components to install. It does however lack some features that xampp comes with such as SQLite and perl. There is also no centralised management tool like the xammp control panel to easily start and stop apache and MySQL. This is a real shame as this just makes xampp so easy to use.
Related links
http://www.zend.com/en/products/server/downloads
http://devzone.zend.com/article/4272-Zend-announces-public-beta-of-a-new-product-Zend-Server
http://www.apachefriends.org/en/xampp.html
With the release of the jQuery 1.3 on the 24th Janurary 2009 see’s the new feature called ‘Live Events’. This goes some way to solve the jQuery problem of creating dom elements on the fly which then have no events bound. Then your normally required to rebind any event handlers to them, resulting another potential large layer of complexity to your code.
Well with Live Events this is no longer required (well for some events anyway). By creating a event handler through a via Live Event it bounds all current and future elements. This gives you the advantage of not having to repeat the events handlers. Some events are excluded: blur, focus, mouseenter, mouseleave, change, submit. Fortunately the most common ones are supported and no doubt all will be supported in the future.
jQuery Live Events Doc
popmenu is a jQuery plugin that allows you to create simple ‘pop-up’ menu’s like which appear on web sites like play.com. It is currently being used at ikonsports.com.
It has similar functionality jQuery’s hover(over, out) but with a few more options specifically geared towards pop up menus. Most importantly it will continue to match an element that you want to appear when you move off the mouse original element and on to any new element, where ever its located in the DOM.
Parameters
target (DOMElement): This is the element that is to ‘appear’ when the hover event is called.
addStyle (string): Optional. Adds a class to the matched element on hover (of matched element and target). Removed on hover off.
time (int): Optional. Time in milliseconds after a hover off when target element is invisible.
speed (String|Number): Optional. A string representing one of the three predefined speeds (”slow”, “normal”, or “fast”) or the number of milliseconds to run the animation displaying the target (e.g. 1000).
autooff (boolean): Optional. Default is true. If turned on will automatically hide any target elements if visible when a different popmenu is triggered. For example if you pop up menu’s would overlap if they were both visable at the same time it will hide it first.
Example
$('#mybutton').popupmenu({
target: "#mybutton_menu",
time: 300 });Download
Production (944 bytes, packed) v1.0
Development (1.75 Kb) v1.0
