You may not be away of bookmarklets which are an underused tool in web designer or developer’s toolbox. A bookmarklet is a a term that merges bookmark and applet to add functionality to a web browser. They can be stored in the bookmark bar of any browser and used from there to perform useful tasks and consist primarily of Javascript code.
As Javascript is synonymous with web development, some clever developers have created some extremely helpful bookmarklets that can improve your day to day work. Here are ten of the best available.
All web designers and developers should be familiar with Firebug (if for some reason you’re not then go now) and Firebug Lite is a striped down version that works on all browsers. Especially useful for fixing IE issues.
Very simple, click on the following links to resize your browser window to these common resolutions. Only works in Firefox but that’s most of you who read Inspect Element.
One of the most useful bookmarklets for development is ReCSS. It reloads the CSS file independent of the HTML which speeds up work considerably when you’re only writing CSS code.
Delicious is one of, if not the most, popular way of saving articles especially in the web design and development community. This bookmarlet provides a quick way to save the current page to Delicious. Give it a go and save this article to Delicious!
Sure, you can preview edits of HTML text using Firebug or WebKit’s Web Inspector but this bookmarklet turns the whole page into a WYSIWYG editor. Of course these changes aren’t permanent and are only local to your machine but gives you a good idea of what changing content does to the page.
Having trouble lining up elements on a page? Andy Budd’s layout grid bookmarklet will come in handy as it overlays a transparent image of a grid, complete with pixel rulers along the X and Y axis.
Google and it's record breaking industrial complex within the search engine world, has broken many barriers by creating interesting new products which fans go mad about. They first exploded with the search engine in 1998, and since then have not only become a giant worldwide in just indexing, but a well oiled machine in the software world as well.
Google has broken walls and created a foundation with it's innovations, allowing itself to not only become number one in the search category, but one of the best email services available, with Gmail. They since developed "Gears", which is an "active" production wheel of services that keep Google products adapting to your operating system.
Some knew this was a prequel to the future, and their beliefs were proven true when Google unveiled the mighty Google Chrome browser, which has become a powerhouse in competing with the number one ranked Mozilla Firefox, and the original Internet Explorer from Microsoft.
Google did not stop there. Google for the last year, have been implementing "Android" Google based "mobile operating systems" into cell phones, and have claimed a huge amount of market share in the ever growing handheld/mobile industry. Google had claimed it's throne as the "king of kings" in the online and multimedia categories.
Google though, had been planning something greater, the highly anticipated Google operating system for personal computers, which has still yet to reach the markets. It promised a linux-based engine, which would of course slaughter Microsoft Windows in performance. That day of reckoning is near, where as next week the Google OS will finally be revealed. Google busts out yet again, with a new force, but none are sure of how compatible it will be.
None the less, this new OS, will be another breakthrough for the powerhouse ran by Eric Schmidt, which many expect to be a huge success. Although there are doubters, many claim that drivers necessary for a smooth running platform OS will not be available immediately. Only time will tell.
The code-named "Chrome OS" is slated for the first public release next week, even though some analysts claim it will be pushed back. The future succession of the OS is yet to be seen, as Linux based operating systems and open source platforms have been available for a very long time, free of charge, and have yet to hold a firm grip upon the market.
Microsoft dominates, clearly in the world of operating systems, but, another brand of competition, let alone a financial giant such as Google, could prove to be a challenge for Microsoft. We shall all see soon.
This guide will let you run jboss as a daemon, that means you'll have a jboss instance that starts a computer boot. When you download jboss you get some example init scripts for different distributions but none for ubuntu. I did however get it to work with minor changes to the red hat init script. This is how I did it, there might be some better way and if you find better solutions than the ones in this guide please let me now and I'll post them here.
At the end of this tutorial you will have (if everything goes as planned) a jboss instance running that starts at computer boot with the help of a daemon script in /etc/init.d/. To keep things tidy jboss will have a separate user called jboss as process owner.
Ubuntu versions tested
Ubuntu 7.10 32 bit Server Version
Ubuntu 7.10 32 bit Desktop Version
Step 1: Install suns jdk
There have been problems reported with jboss and java 6 in the past. I don't know if there still is compatibility issues but to be safe I use java 5.
Code:
sudo apt-get install sun-java5-jdk
Step 2: create the jboss user
The reason to use a separate user account for jboss is to control the permissions of the jboss instance. You don't want jboss running as root with unlimited access to the whole system. There is no password created for the jboss user, and you probably don't need one either (unless you actually want to login as the jboss user).
Code:
sudo mkdir /home/jboss
sudo useradd -s /bin/bash -d /home/jboss jboss
sudo chown jboss:jboss /home/jboss/
Step 3: Download jboss
Go to http://labs.jboss.com/jbossas/downloads/ and get the latest stable version of jboss (4.2.2.GA when this guide was written). Download it to your home directory.
Now you have a file in ~/jboss-4.2.2.GA.zip
I used unzip to extract the archive, to install it run
Code:
sudo apt-get install unzip
but feel free to extract it with what ever program you feel fit.
sidenote:
When I installed jboss on my server I installed it in the /opt/folder instead of /home/jboss/. Where ever you decide to put jboss make sure the jboss user has read and write permission to the jboss folder and it's subfiles/-folders.
Move it to jboss home and extract it. To make a future upgrade of jboss a little easier a symlinc to jboss home is created. When you decide to upgrade jboss you'll just have to edit the symlinc to point to the new version.
All the changes to the red hat init script is in the setup section in the beginning of the script. If you followed my guide to the letter you can download my version of the script thats attached to this post. If you installed java or jboss in other directories it's probably easier to edit the script your self.
Option 1: download my script
Download the scriptattached to this post to your home folder then run this to move it to the correct folder.
Code:
sudo mv ~/jboss/jboss_init.sh /etc/init.d/jboss
End option 1
Option 2: edit the original red hat script yourself.
Copy the red hat init script to the init.d directory and rename it.
Make your script owned by root and executable.
Create run level shortcuts for the script.
Code:
sudo chown root:root /etc/init.d/jboss
sudo chmod ug+x /etc/init.d/jboss
sudo update-rc.d jboss defaults
To start jboss you type
Code:
sudo /etc/init.d/jboss start
If everything has gone as planned you should now have a functional installation of jboss that will start itself on computer boot.
Step 7: Redirecting traffic from port 80 to jboss port 8080 (Optional)
The default port for jboss is 8080 but the standard port for http traffic is 80. Port 80 is however a restricted port and can only be bound by root. To get around this little pickle you can redirect the incoming traffic on port 80 to 8080, the same goes for the https traffic on port 443 to jboss 8443. Here's a way to do that.
);void(myBody=document.getElementsByTagName('body')%5B0%5D);if(myDiv!=null){void(myBody.removeChild(myDiv));}else{void(myDiv=document.createElement%20('div'));void(myDiv.id='_grid_div_mrb');void(myDiv.style.background='url(http://www.andybudd.com/images/layoutgrid.png)');void(myDiv.style.position='absolute');void(myDiv.style.width=myBody.offsetWidth+%20'px');void(myDiv.style.height=myBody.offsetHeight+'px');void(myDiv.style.top='0');void(myDiv.style.left='0');void(myBody.appendChild(myDiv));}){kind=link}