how to create a horizontal dropdown menu with html css

CSS tutorial, Here in this article we explained, how to create a horizontal dropdown menu with html css. We given CSS code with screenshots.

This tutorial explains how to build horizontal lists using “display: inline”.

There are many methods that can be used to making a horizontal list. The main ingredient is “display: inline”, applied to the “LI” element.

Step 1: Make a basic list

Start with a basic unordered list. The list items are all active (wrapped in <a href=”#”> </a>) which is essential for this list to work. Some CSS rules are written exclusively for the “a” element within the list items. For this example a “#” is used as a dummy link.

HTML CODE
<div id="
topnav">
<ul>
<li><a href="#">Home</a></li>
<li><a href="#">Product</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">Contact</a></li>
<li><a href="#">About</a></li>
</ul>
</div>

Step 2: Remove the bullets

To remove the HTML list bullets, set the “list-style-type” to “none”.

how to create a horizontal dropdown menu with html css
how to create a horizontal dropdown menu with html css

CSS CODE
#topnav ul

{

list-style-type: none;

}

HTML CODE
<div id=”topnav">
<ul>
<li><a href="#">Home</a></li>
<li><a href="#">Product</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">
Contact</a></li>
<li><a href="#">About</a></li>
</ul>
</div>

Step 3: Remove padding and margins

Standard HTML lists have a certain amount of left-indentation. The amount varies on each browser. Some browsers use padding (Mozilla, Netscape, Safari) and others use margins (Internet Explorer, Opera) to set the amount of indentation.

To remove this left-indentation consistently across all browsers, set both padding and margins to “0” for the “UL”.

CSS CODE
#topnav ul

{

margin: 0px;

padding: 0px;

list-style-type: none;

}

HTML CODE
<div id=”topnav">
<ul>
<li><a href="#">Home</a></li>
<li><a href="#">Product</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">
Contact</a></li>
<li><a href="#">About</a></li>
</ul>
</div>

Step 4: Display inline

To force the list into one line, apply “display: inline;” to the “LI”.

CSS CODE

#topnav ul
{
margin: 0px;
padding: 0px;
list-style-type: none;
}
#topnav ul li
{
display: inline;
}

HTML CODE
<div id=”topnav">
<ul>
<li><a href="#">Home</a></li>
<li><a href="#">Product</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">
Contact</a></li>
<li><a href="#">About</a></li>
</ul>
</div>

Step 5: Removing text decoration

At this point you may wish to remove the text underline. It is a common practice for navigation not to have underlines as their placement and other feedback mechanisms make them more obviously links. However, you should be aware that modifying standard hyperlink behaviour (such as underlines) can be confusing for some users, who may not realise that the item is a link.

CSS CODE

#topnav ul
{
margin: 0px;
padding: 0px;
list-style-type: none;
}
#topnav ul li
{
display: inline;
}
#topnav ul li a
{
text-decoration:none;
}

HTML CODE
<div id=”topnav">
<ul>
<li><a href="#">Home</a></li>
<li><a href="#">Product</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">
Contact</a></li>
<li><a href="#">About</a></li>
</ul>
</div>

Step 6: Padding around list items

To make each list item into a box, we need to add padding to the “a” element.

CSS CODE

#topnav ul
{
margin: 0px;
padding: 0px;
list-style-type: none;
}
#topnav ul li
{
display: inline;
}
#topnav ul li a
{
text-decoration:none;
padding: 1em 1em;
}

HTML CODE
<div id=”topnav">
<ul>
<li><a href="#">Home</a></li>
<li><a href="#">Product</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">
Contact</a></li>
<li><a href="#">About</a></li>
</ul>
</div>

Step 7: Adding background color

At this point a background color and border can be applied. There are many combinations of border and background colors that can be used.

create horizontal rollover list with css
create horizontal rollover list with css

CSS CODE

#topnav ul
{
margin: 0px;
padding: 0px;
list-style-type: none;
}
#topnav ul li
{
display: inline;
}
#topnav ul li a
{
text-decoration:none;
padding:1em 1em;
color:#fff;
background-color:#808000;

}

HTML CODE
<div id=”topnav">
<ul>
<li><a href="#">Home</a></li>
<li><a href="#">Product</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">
Contact</a></li>
<li><a href="#">About</a></li>
</ul>
</div>

Step 8: Add a rollover color

Use “a:hover” to set a second background color, as a rollover. Roll over the list now you will see how it works.

CSS CODE

#topnav ul
{
margin: 0px;
padding: 0px;
list-style-type: none;
}
#topnav ul li
{
display: inline;
}
#topnav ul li a
{
text-decoration:none;
padding:1em 1em;
color:#fff;
background-color:#808000;
}
#topnav ul li a:hover
{
color: #fff;
background-color:#000000;
}

HTML CODE
<div id=”topnav">
<ul>
<li><a href="#">Home</a></li>
<li><a href="#">Product</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">
Contact</a></li>
<li><a href="#">About</a></li>
</ul>
</div>

Step 9: Center the list

To center the list, add “text-align: center;” to the “UL”.

CSS CODE

#topnav ul
{
margin: 0px;
padding: 0px;
list-style-type: none;
text-align: center;
}
#topnav ul li
{
display: inline;
}
#topnav ul li a
{
text-decoration:none;
padding:1em 1em;
color:#fff;
background-color:#808000;
}
#topnav ul li a:hover
{
color: #fff;
background-color:#000000;
}

HTML CODE
<div id=”topnav">
<ul>
<li><a href="#">Home</a></li>
<li><a href="#">Product</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">
Contact</a></li>
<li><a href="#">About</a></li>
</ul>
</div>

And you done it.

Thank you!

create a web photo gallery in 5 minutes using photoshop

Photoshop Tutorial, create a web photo gallery in 5 minutes using photoshop, Photoshop makes it easy to share your pictures with friends and family using the automated Web Photo Gallery command. This command generates an index page of thumbnail images with hyperlinks to all your pictures. Adobe Photoshop CS3 allow someone with little or no web design experience to make stunning photo galleries.

create a web photo gallery in 5 minutes using photoshop

These instructions were written for Photoshop version 5.5. Later versions introduced more templates and options, but these instructions should be enough to get you started. :~

*************************************************************************************************

  1. Prepare your photos for the Web by rotating, cropping, resizing, and color correcting, if necessary. Refer to the related information in the links below for tips on prepping your pictures.
  2. Places the photos you want to include in the gallery in a folder on your hard drive.
  3. Choose an empty folder or create a new one to use as a destination folder for the files created by the Photo Gallery command.

************************************************************************************************
Step 1: Open Photoshop & Go to File > Automate > Web Photo Gallery to open the photo gallery dialog box.

 

Step 2: At the very top of the window, take some time to choose the template you like best under the Styles drop down menu. Keep in mind that the Flash Template will take more bandwidth, require more time to load, and must be supported by a flash plugin (which most web browsers have anyway). With this in mind, the Flash-based styles do look very modern and attractive. You can see below in this image:

Step 3: Below that, insert your email address if you want it to be published on your site. If not, then just leave this segment blank.

Step 4: Now you have a photo gallery dialog box on your computer screen, click the “choose” button and select the folder containing your images. If thefolder contains sub-folders with images you want to include, check the box to include subdirectories.

Step 5: Next to Destination, click the “choose” button and select the empty folder. (I created it on my desktop)

Step 6: In the Site Name field, type a title that will appear on all the pages of your gallery. This is the text that also appears in the title bar when the page is viewed in a Web browser.

Step 7: If desired, fill in the Phototographer and Date fields. This information will also appear on the Web pages if it’s filled in.

Step 7: Click OK in the photo gallery dialog box.

And you’re done it!

Your Photo Gallery should automatically launch in your Web browser.

Here’s my Web Photo Gallery:

~: Thank you! :~

Use smilies/smileys in wordpress posts

By default, WordPress automatically converts text smileys to graphic images. In this post I showed how to Use smilies/smileys in wordpress posts

Use smilies/smileys in wordpress posts

Use smilies/smileys in wordpress posts
Use smilies/smileys in wordpress posts

Smileys, also known as “emoticons,” are glyphs used to convey emotions in your writing. They are a great way to brighten up posts. smile emoticon

By default, WordPress automatically converts text smileys to graphic images. When you type 😉 in your post you see smile emoticon when you preview or publish your post.

If you turn off graphic smileys, whatever you type in plain text will remain, and be displayed, as plain text.

  1. Go to your Admin Panel
  2. Select Settings -> Writing
  3. In the Formatting section, uncheck the box for “Convert emoticons like 🙂 and 😛 to graphics on display

Turning off emoticons means that when you type 😉 in a post you will see 😉 when you preview or publish your post. So it doesn’t stop you from using emoticons as plain text. wink emoticon

What Text Do I Type to Make Smileys?

Smiley images and the text used to produce them*:

icon text text full text icon full text
smile 🙂 🙂 🙂 lol 😆
biggrin 😀 😀 😀 redface 😳
sad 🙁 🙁 🙁 cry 😥
surprised 😮 😮 😮 evil 👿
eek 😯 😯 😯 twisted 😈
confused 😕 😕 😕 rolleyes 🙄
cool 8) 😎 😎 exclaim
mad 😡 😡 😡 question
razz 😛 😛 😛 idea 💡
neutral 😐 😐 😐 arrow
wink 😉 😉 😉 mrgreen :mrgreen:

* In some instances, multiple text options are available to display the same smiley.

Note: The smiley or emoticon image graphics are found in the /wp-includes/images/smilies directory.


How to install siege on Linux box

In this article I given step by step information about How to install siege on Linux box. I given the full commands and there output with full description.

How to install siege on Linux box

ABOUT SIEGE – Background
Siege is an http load testing and benchmarking utility. It was designed to let web developers measure their code under duress, to see how it will stand up to load on the internet. Siege supports basic authentication, cookies, HTTP and HTTPS protocols. It lets its user hit a web server with a configurable number of simulated web browsers. Those browsers place the server “under siege.”

How to install siege on Linux box
How to install siege on Linux box

PLATFORM SUPPORT
Siege was written on GNU/Linux and has been successfully ported to AIX, BSD, HP-UX and Solaris. It should compile on most System V UNIX variants and on most newer BSD systems. Because Siege relies on POSIX.1b features not supported by Microsoft, it will not run on Windows. Of course you can use Siege to test a Windows HTTP server.

Download siege from following URL or Using following command
[kapil@kapil-pc ~]$ wget ftp://ftp.joedog.org/pub/siege/siege-latest.tar.gz
[kapil@kapil-pc ~]$ tar xzf siege-latest.tar.gz
[kapil@kapil-pc ~]$ mv siege-2.69 siege
[kapil@kapil-pc ~]$ cd siege
[kapil@kapil-pc siege ~]$ su
[root@kapil-pc siege ~]$ ROOT_PASSWORD

[root@kapil-pc siege ~]$ ./configure
checking for a BSD-compatible install… /usr/bin/install -c
checking whether build environment is sane… yes
checking for gawk… gawk
checking for gcc… no
checking for cc… no
checking for cc… no
checking for cl… no
configure: error: no acceptable cc found in $PATH

If you got above error Please Use following command.

[root@kapil-pc siege ~]$ yum install gcc*

Than run following command again

[root@kapil-pc siege ~]$ ./configure
checking for a BSD-compatible install… /usr/bin/install -c
checking whether build environment is sane… yes
checking for gawk… gawk
checking whether make sets $(MAKE)… yes
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking for style of include used by make… GNU
checking for gcc… gcc
checking for C compiler default output file name… a.out
checking whether the C compiler works… yes
checking whether we are cross compiling… no
checking for suffix of executables…
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ANSI C… none needed
checking dependency style of gcc… none
checking how to run the C preprocessor… gcc -E
checking for egrep… grep -E
checking for AIX… no
checking for gcc… (cached) gcc
checking whether we are using the GNU C compiler… (cached) yes
checking whether gcc accepts -g… (cached) yes
checking for gcc option to accept ANSI C… (cached) none needed
checking dependency style of gcc… (cached) none
checking for a sed that does not truncate output… /bin/sed
checking for ld used by gcc… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking for /usr/bin/ld option to reload object files… -r
checking for BSD-compatible nm… /usr/bin/nm -B
checking whether ln -s works… yes
checking how to recognise dependent libraries… pass_all
checking for ANSI C header files… yes
checking for sys/types.h… yes
checking for sys/stat.h… yes
checking for stdlib.h… yes
checking for string.h… yes
checking for memory.h… yes
checking for strings.h… yes
checking for inttypes.h… yes
checking for stdint.h… yes
checking for unistd.h… yes
checking dlfcn.h usability… yes
checking dlfcn.h presence… yes
checking for dlfcn.h… yes
checking for g++… g++
checking whether we are using the GNU C++ compiler… yes
checking whether g++ accepts -g… yes
checking dependency style of g++… none
checking how to run the C++ preprocessor… g++ -E
checking for g77… no
checking for f77… no
checking for xlf… no
checking for frt… no
checking for pgf77… no
checking for fort77… no
checking for fl32… no
checking for af77… no
checking for f90… no
checking for xlf90… no
checking for pgf90… no
checking for epcf90… no
checking for f95… f95
checking whether we are using the GNU Fortran 77 compiler… yes
checking whether f95 accepts -g… yes
checking the maximum length of command line arguments… 32768
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for objdir… .libs
checking for ar… ar
checking for ranlib… ranlib
checking for strip… strip
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC
checking if gcc PIC flag -fPIC works… yes
checking if gcc static flag -static works… yes
checking if gcc supports -c -o file.o… yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries… yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… yes
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
configure: creating libtool
appending configuration tag “CXX” to libtool
checking for ld used by g++… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking for g++ option to produce PIC… -fPIC
checking if g++ PIC flag -fPIC works… yes
checking if g++ static flag -static works… yes
checking if g++ supports -c -o file.o… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
appending configuration tag “F77” to libtool
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
checking for f95 option to produce PIC… -fPIC
checking if f95 PIC flag -fPIC works… yes
checking if f95 static flag -static works… yes
checking if f95 supports -c -o file.o… yes
checking whether the f95 linker (/usr/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking for perl… /usr/bin/perl
checking for a POSIX-compliant shell… /bin/sh
checking whether make sets $(MAKE)… (cached) yes
checking for a BSD-compatible install… /usr/bin/install -c
checking for buggy pthread mutex initializers… no
checking for dlopen() in -ldld… no
checking for dlopen() in -ldl… yes
checking for ssl support… yes
checking off/include/openssl/opensslv.h usability… no
checking off/include/openssl/opensslv.h presence… no
checking for off/include/openssl/opensslv.h… no
checking /usr/include/openssl/opensslv.h usability… yes
checking /usr/include/openssl/opensslv.h presence… yes
checking for /usr/include/openssl/opensslv.h… yes
checking for OpenSSL version… >= 0.9.8 (appropriate flag set)
checking for ANSI C header files… (cached) yes
checking for sys/wait.h that is POSIX.1 compatible… yes
checking fcntl.h usability… yes
checking fcntl.h presence… yes
checking for fcntl.h… yes
checking for unistd.h… (cached) yes
checking signal.h usability… yes
checking signal.h presence… yes
checking for signal.h… yes
checking sys/socket.h usability… yes
checking sys/socket.h presence… yes
checking for sys/socket.h… yes
checking sys/select.h usability… yes
checking sys/select.h presence… yes
checking for sys/select.h… yes
checking sys/time.h usability… yes
checking sys/time.h presence… yes
checking for sys/time.h… yes
checking sys/times.h usability… yes
checking sys/times.h presence… yes
checking for sys/times.h… yes
checking sys/resource.h usability… yes
checking sys/resource.h presence… yes
checking for sys/resource.h… yes
checking errno.h usability… yes
checking errno.h presence… yes
checking for errno.h… yes
checking arpa/inet.h usability… yes
checking arpa/inet.h presence… yes
checking for arpa/inet.h… yes
checking netinet/in.h usability… yes
checking netinet/in.h presence… yes
checking for netinet/in.h… yes
checking netdb.h usability… yes
checking netdb.h presence… yes
checking for netdb.h… yes
checking pthread.h usability… yes
checking pthread.h presence… yes
checking for pthread.h… yes
checking for string.h… (cached) yes
checking for strings.h… (cached) yes
checking sched.h usability… yes
checking sched.h presence… yes
checking for sched.h… yes
checking openssl/e_os.h usability… no
checking openssl/e_os.h presence… no
checking for openssl/e_os.h… no
checking openssl/e_os2.h usability… yes
checking openssl/e_os2.h presence… yes
checking for openssl/e_os2.h… yes
checking for an ANSI C-conforming const… yes
checking for size_t… yes
checking whether time.h and sys/time.h may both be included… yes
checking return type of signal handlers… void
checking for working alloca.h… yes
checking for alloca… yes
checking for strchr… yes
checking for memcpy… yes
checking for strncpy… yes
checking for strstr… yes
checking for strlen… yes
checking for strncasecmp… yes
checking for strncmp… yes
checking for socket… yes
checking for gethostbyname… yes
checking for snprintf… yes
checking for strdup… yes
checking for rand_r… yes
checking for localtime_r… yes
checking for getipnodebyname… no
checking for freehostent… no
checking for getopt_long… yes
checking for socket in -lsocket… no
checking for pthread_attr_init in -lpthread… yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating doc/Makefile
config.status: creating html/Makefile
config.status: creating lib/Makefile
config.status: creating lib/joedog/Makefile
config.status: creating include/Makefile
config.status: creating include/joedog/Makefile
config.status: creating utils/Makefile
config.status: creating include/config.h
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: executing default-2 commands
config.status: executing default-3 commands
config.status: executing default-4 commands
config.status: executing default-5 commands
config.status: executing default-6 commands

——————————————————–
Configuration is complete

Run the following commands to complete the installation:
make
make install

To upgrade an old siegerc file (optional):
mv ~/.siegerc.new ~/.siegerc

For complete documentation: http://www.joedog.org
——————————————————–

Than Use following command

[root@kapil-pc siege ~]# make
Making all in .
make[1]: Entering directory `/home/kapil/testing/siege’
make[1]: Nothing to be done for `all-am’.
make[1]: Leaving directory `/home/kapil/testing/siege’
Making all in include
make[1]: Entering directory `/home/kapil/testing/siege/include’
make all-recursive
make[2]: Entering directory `/home/kapil/testing/siege/include’
Making all in joedog
make[3]: Entering directory `/home/kapil/testing/siege/include/joedog’
make[3]: Nothing to be done for `all’.
make[3]: Leaving directory `/home/kapil/testing/siege/include/joedog’
make[3]: Entering directory `/home/kapil/testing/siege/include’
make[3]: Nothing to be done for `all-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/include’
make[2]: Leaving directory `/home/kapil/testing/siege/include’
make[1]: Leaving directory `/home/kapil/testing/siege/include’
Making all in lib
make[1]: Entering directory `/home/kapil/testing/siege/lib’
Making all in joedog
make[2]: Entering directory `/home/kapil/testing/siege/lib/joedog’
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o memory.lo memory.c
mkdir .libs
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c memory.c -fPIC -DPIC -o .libs/memory.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c memory.c -o memory.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o notify.lo notify.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c notify.c -fPIC -DPIC -o .libs/notify.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c notify.c -o notify.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o perl.lo perl.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c perl.c -fPIC -DPIC -o .libs/perl.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c perl.c -o perl.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o util.lo util.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c util.c -fPIC -DPIC -o .libs/util.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c util.c -o util.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o snprintf.lo snprintf.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c snprintf.c -fPIC -DPIC -o .libs/snprintf.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c snprintf.c -o snprintf.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o stralloc.lo stralloc.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c stralloc.c -fPIC -DPIC -o .libs/stralloc.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c stralloc.c -o stralloc.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=link gcc -W -Wall -g -O2 -o libjoedog.la -version-info 1:0:1 memory.lo notify.lo perl.lo util.lo snprintf.lo stralloc.lo
libtool: link: warning: `-version-info/-version-number’ is ignored for convenience libraries
ar cru .libs/libjoedog.a .libs/memory.o .libs/notify.o .libs/perl.o .libs/util.o .libs/snprintf.o .libs/stralloc.o
ranlib .libs/libjoedog.a
creating libjoedog.la
(cd .libs && rm -f libjoedog.la && ln -s ../libjoedog.la libjoedog.la)
make[2]: Leaving directory `/home/kapil/testing/siege/lib/joedog’
make[2]: Entering directory `/home/kapil/testing/siege/lib’
make[2]: Nothing to be done for `all-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/lib’
make[1]: Leaving directory `/home/kapil/testing/siege/lib’
Making all in src
make[1]: Entering directory `/home/kapil/testing/siege/src’
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c auth.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c base64.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c client.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c cookie.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c cfg.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c crew.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c data.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c date.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c eval.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c getopt.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c getopt1.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c handler.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c hash.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c http.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c init.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c load.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c log.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c main.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c md5.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c sock.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c ssl.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c timer.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c url.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c util.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c version.c
/bin/sh ../libtool –tag=CC –mode=link gcc -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -L/usr/lib -lpthread -o siege auth.o base64.o client.o cookie.o cfg.o crew.o data.o date.o eval.o getopt.o getopt1.o handler.o hash.o http.o init.o load.o log.o main.o md5.o sock.o ssl.o timer.o url.o util.o version.o ../lib/joedog/libjoedog.la -ldl -lssl -lcrypto
mkdir .libs
gcc -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -o siege auth.o base64.o client.o cookie.o cfg.o crew.o data.o date.o eval.o getopt.o getopt1.o handler.o hash.o http.o init.o load.o log.o main.o md5.o sock.o ssl.o timer.o url.o util.o version.o -L/usr/lib -lpthread ../lib/joedog/.libs/libjoedog.a -ldl -lssl -lcrypto
make[1]: Leaving directory `/home/kapil/testing/siege/src’
Making all in utils
make[1]: Entering directory `/home/kapil/testing/siege/utils’
make[1]: Nothing to be done for `all’.
make[1]: Leaving directory `/home/kapil/testing/siege/utils’
Making all in doc
make[1]: Entering directory `/home/kapil/testing/siege/doc’
make[1]: Nothing to be done for `all’.
make[1]: Leaving directory `/home/kapil/testing/siege/doc’
Making all in html
make[1]: Entering directory `/home/kapil/testing/siege/html’
make[1]: Nothing to be done for `all’.
make[1]: Leaving directory `/home/kapil/testing/siege/html’

Now you can use following command.

[root@kapil-pc siege ~]# make install
Making install in .
make[1]: Entering directory `/home/kapil/testing/siege’
make[2]: Entering directory `/home/kapil/testing/siege’
make[2]: Nothing to be done for `install-exec-am’.
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege’
make[1]: Leaving directory `/home/kapil/testing/siege’
Making install in include
make[1]: Entering directory `/home/kapil/testing/siege/include’
Making install in joedog
make[2]: Entering directory `/home/kapil/testing/siege/include/joedog’
make[3]: Entering directory `/home/kapil/testing/siege/include/joedog’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/include/joedog’
make[2]: Leaving directory `/home/kapil/testing/siege/include/joedog’
make[2]: Entering directory `/home/kapil/testing/siege/include’
make[3]: Entering directory `/home/kapil/testing/siege/include’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/include’
make[2]: Leaving directory `/home/kapil/testing/siege/include’
make[1]: Leaving directory `/home/kapil/testing/siege/include’
Making install in lib
make[1]: Entering directory `/home/kapil/testing/siege/lib’
Making install in joedog
make[2]: Entering directory `/home/kapil/testing/siege/lib/joedog’
make[3]: Entering directory `/home/kapil/testing/siege/lib/joedog’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/lib/joedog’
make[2]: Leaving directory `/home/kapil/testing/siege/lib/joedog’
make[2]: Entering directory `/home/kapil/testing/siege/lib’
make[3]: Entering directory `/home/kapil/testing/siege/lib’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/lib’
make[2]: Leaving directory `/home/kapil/testing/siege/lib’
make[1]: Leaving directory `/home/kapil/testing/siege/lib’
Making install in src
make[1]: Entering directory `/home/kapil/testing/siege/src’
make[2]: Entering directory `/home/kapil/testing/siege/src’
test -z “/usr/local/bin” || mkdir -p — “/usr/local/bin”
/bin/sh ../libtool –mode=install /usr/bin/install -c ‘siege’ ‘/usr/local/bin/siege’
/usr/bin/install -c siege /usr/local/bin/siege
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/src’
make[1]: Leaving directory `/home/kapil/testing/siege/src’
Making install in utils
make[1]: Entering directory `/home/kapil/testing/siege/utils’
make[2]: Entering directory `/home/kapil/testing/siege/utils’
make install-exec-hook
make[3]: Entering directory `/home/kapil/testing/siege/utils’
/bin/sh ../utils/mkinstalldirs /usr/local/bin
/bin/sh ../libtool –mode=install /usr/bin/install -c bombardment /usr/local/bin/bombardment
/usr/bin/install -c bombardment /usr/local/bin/bombardment
/bin/sh ../libtool –mode=install /usr/bin/install -c siege2csv.pl /usr/local/bin/siege2csv.pl
/usr/bin/install -c siege2csv.pl /usr/local/bin/siege2csv.pl
/bin/sh ../libtool –mode=install /usr/bin/install -c siege.config /usr/local/bin/siege.config
/usr/bin/install -c siege.config /usr/local/bin/siege.config
make[3]: Leaving directory `/home/kapil/testing/siege/utils’
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/utils’
make[1]: Leaving directory `/home/kapil/testing/siege/utils’
Making install in doc
make[1]: Entering directory `/home/kapil/testing/siege/doc’
make[2]: Entering directory `/home/kapil/testing/siege/doc’
make install-exec-hook
make[3]: Entering directory `/home/kapil/testing/siege/doc’
make[3]: Leaving directory `/home/kapil/testing/siege/doc’
test -z “/usr/local/man/man1” || mkdir -p — “/usr/local/man/man1”
/usr/bin/install -c -m 644 ‘./siege.1’ ‘/usr/local/man/man1/siege.1’
/usr/bin/install -c -m 644 ‘./siege.config.1’ ‘/usr/local/man/man1/siege.config.1’
/usr/bin/install -c -m 644 ‘./bombardment.1’ ‘/usr/local/man/man1/bombardment.1’
/usr/bin/install -c -m 644 ‘./siege2csv.1’ ‘/usr/local/man/man1/siege2csv.1’
test -z “/usr/local/man/man5” || mkdir -p — “/usr/local/man/man5”
/usr/bin/install -c -m 644 ‘./urls_txt.5’ ‘/usr/local/man/man5/urls_txt.5’
test -z “/usr/local/man/man7” || mkdir -p — “/usr/local/man/man7″
/usr/bin/install -c -m 644 ‘./layingsiege.7’ ‘/usr/local/man/man7/layingsiege.7′
make[2]: Leaving directory `/home/kapil/testing/siege/doc’
make[1]: Leaving directory `/home/kapil/testing/siege/doc’
Making install in html
make[1]: Entering directory `/home/kapil/testing/siege/html’
make[2]: Entering directory `/home/kapil/testing/siege/html’
make install-exec-hook
make[3]: Entering directory `/home/kapil/testing/siege/html’
HTML pages not installed
make[3]: Leaving directory `/home/kapil/testing/siege/html’
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/html’
make[1]: Leaving directory `/home/kapil/testing/siege/html’

Now siege installation is done. Than Use following command for using the siege for testing.

[root@kapil-pc siege ~]# siege
SIEGE 2.69
Usage: siege [options]
siege [options] URL
siege -g URL
Options:
-V, –version VERSION, prints version number to screen.
-h, –help HELP, prints this section.
-C, –config CONFIGURATION, show the current configuration.
-v, –verbose VERBOSE, prints notification to screen.
-g, –get GET, pull down headers from the server and display HTTP
transaction. Great for web application debugging.
-c, –concurrent=NUM CONCURRENT users, default is 10
-u, –url=”URL” Deprecated. Set URL as the last argument.
-i, –internet INTERNET user simulation, hits the URLs randomly.
-b, –benchmark BENCHMARK, signifies no delay for time testing.
-t, –time=NUMm TIME based testing where “m” is the modifier S, M, or H
no space between NUM and “m”, ex: –time=1H, one hour test.
-r, –reps=NUM REPS, number of times to run the test, default is 25
-f, –file=FILE FILE, change the configuration file to file.
-R, –rc=FILE RC, change the siegerc file to file. Overrides
the SIEGERC environmental variable.
-l, –log LOG, logs the transaction to PREFIX/var/siege.log
-m, –mark=”text” MARK, mark the log file with a string separator.
-d, –delay=NUM Time DELAY, random delay between 1 and num designed
to simulate human activity. Default value is 3
-H, –header=”text” Add a header to request (can be many)
-A, –user-agent=”text” Sets User-Agent in request
[root@kapil-pc siege ~]#

how to remove freckles of face using photoshop

In this tutorial we’re going to show you how you can remove freckles easily and quickly using Photoshop. In very simple steps you will be able to create the freckles face effect with photoshop.

how to remove freckles of face using photoshop

Step 1: Once your image in Photoshop, duplicate your background layer by choosing ‘layer>duplicate layer’ or simply drag your background layer to ‘create new layer’ button in the layer pallete.

how to remove freckles of face using photoshop
how to remove freckles of face using photoshop

Step 2: Now apply gaussian blur (Filter > Blur > Gaussian Blur) to your background copy. Try to drag the slider slowly to the right until you see the freckles are no longer visible.

Step 3: If you can’t find your history pallete on the screen, go to window > history to bring up the history pallete

Step 4: Now click on the duplicate layer state to return your photo to what it looked like when you haven’t applied the gaussian blur. Also click in the first column next to gaussian blur state.

Step 5: Choose the ‘History Brush’ from your tool pallete. Change the History Brush’s Mode to ‘lighten’ to keep from simply painting in a blurry version of our photo.

Step 6: Start to paint your photo to remove the freckles. If you find that the person looks ‘too clean’ you can always undo your step, and lower the opacity of the brush and try again.

Here’s the original image to comparison:

And here’s my final image:

Thank You!

how to create realistic clouds image with photoshop

Photoshop tutorial, explained you about create realistic clouds image with photoshop. We given step by step information with screen shots and short cut keys.

how to create realistic clouds image with photoshop

This tutorial will show you how to use photoshop’s cloud filter to create realistic looking clouds .

Step 1: Start a new document of any size you want in Photoshop.

how to create realistic clouds image with photoshop
how to create realistic clouds image with photoshop

Step 2: Create a new layer by pressing Ctrl+J, and fill it with a Linear gradient of dark blue to lighter blue.

Darker blue: #395D9E
Lighter blue: #6A9BC9


Step 3: Create a new layer. & Press D to reset your color pallete.

Step 4: Go to Filter » Render » Clouds.

Step 5: Then again Filter » Render » Difference Clouds.

Step 6: Press CTRL+F twice. & set the clouds layer blending mode to: “Screen”

Step 7: Go to image » Adjustments » Levels.
And set the input values to: 20, 1.00, and 120

Step 8: Duplicate the cloud layer (Press CTRL+J).

Step 9: Go to Filter » Stylize » Extrude & apply the settings given below:

Step 10: Reduce to Opacity of the original cloud layer to 70%, and the extrude layer to 50%

Step 11: Now finally select the extruded cloud layer and apply a gaussian blur with 5.0 px setting. (Filter » Blur-Gaussian Blur)

And you done it!

Here’s my final image of the clouds:

Now I will show you how to use it in an image.

I got this image below which I removed the sky in the background.

Now this image, I create the clouds and put it behind the mountain, but it looks rather fake because its too flat.

Now we need to distort the clouds a little, so merge the Gradient layer,  extruded clouds layer and the original clouds layer together.

Then finally go to Edit » Transform » Perspective.

and drag the clouds image outward like I’ve done here:

Now our image is looking more realistic clouds.

Here’s the final result:

Thank You!

How to use memcached with php

Using this tutorial you will know, How to use memcached with php. We given code for using memcache with php. we shown you to configure memcache with php.

How to use memcached with php

 

How to use memcached with php
How to use memcached with php

If you try to install memcached with Linux server then use following commands

# yum install libevent
# yum install libmemcached libmemcached-devel
# yum install memcached

For Starting the memcached server
# memcached -d -m 512 -l 127.0.0.1 -p 11211 -u nobody

11211 port is default port for memcached server.

For using the memecached with php client you need to install following package

# pecl install memcache

After installing all packages restart the apache server.

# /etc/sbin/service httpd restart

<!--?php
/* OO API */
$memcache_obj = new Memcache;
$memcache_obj--->connect('memcache_host', 11211);
$memcache_obj->set('any_key', 'some value', MEMCACHE_COMPRESSED, 50);
echo $memcache_obj->get('any_key');
?>

Important Note: Memcached key has limitations of 250 charactors, So key value should be with in 250 charactors.

how to create glossy buttons for website using photoshop

In this tutorial we are going to re-create those fancy buttons that are used on Mac OSX.

how to create glossy buttons for website using photoshop

Step 1: Create a new document of any size in Photoshop.

In this tutorial we are going to re-create those fancy buttons that are used on Mac OSX. how to create glossy buttons for website using photoshop
In this tutorial we are going to re-create those fancy buttons that are used on Mac OSX. how to create glossy buttons for website using photoshop

Step 2: Create a new layer by pressing Ctrl+J. Name this layer ‘Layer 1’. Select Rectangular Marquee Tool and make a square selection as I’ve done here:

Step 3: Go to Select->Modify->Smooth with a setting of 30 pixels:

Step 4: Set your foreground color to: #373fa4 and your background color to: #8dddf8

Step 5: Now select a Gradient Tool(G), and set it up with a foreground, to background gradient as I’ve done here:

Now fill in your selection with a dark to light gradient as I’ve done here:

Do not deselect the selection.

Step  6: Double click this layer, and apply the following blending options:

Do not deselect the selection.

Step 7: Create a new layer, by pressing CTRL+ SHIFT + N on your keyboard.

Your selection should still be active, if not hold down the CTRL Key on your keyboard, and click the layer named “Layer 1”.

Select Rectangular Marquee Tool. Now while holding down the ALT key on your keyboard deselect the bottom half of our selection as l’ve done here:

Step 8: Set your foreground color to white (#FFFFFF), select Gradient Tool(G) and set your gradient style to “foreground to transparent”:

Step 9: Now fill in this selection with our gradient, with a white to transparent, like I’ve done here:

Press CTRL + D on your keyboard to deselect the selection.

Step 10: Next press CTRL + T on your keyboard to get out the free transform tool.
Here’s how your screen should look:

Step 11: Now hold down the SHIFT + CTRL + ALT keys on your keyboard, place your cursor near the node (small square) in the bottom left corner of the box and drag it slightly inward as l’ve done here:

Press ENTER on your keyboard to finalize the transformation, result:

Step 12: Now press the V key on your keyboard to get out the move tool. and tap the DOWN ARROW on your keyboard once, to nudge the gloss down one pixel, result:

Step 13: Drop the opacity of this layer down to 80 percent as I’ve done here:

This should lighten it up, just a little bit.

Step 14: The only thing left to do is add some text. I select the 36pt Verdana, with the SHARP setting:

Here’s my final result:

Thank You!

create water drops using photoshop cs3

we created the detailed article for create water drops using photoshop cs3. We given the full steps with there proper steps and screenshots in this article.

create water drops using photoshop cs3

Get yourself a close up pic of a leaf or something like that..
I chose this one:

create water drops using photoshop cs3
create water drops using photoshop cs3

Step 1: Create a new document of Default Photoshop Size.

Create a new layer and paste the leaf picture into it.

Step 2: Now get your Elliptical Marque Tool hold shift and drag so that you get a circle like this.

Step 3: Now go to Filter -> Distort -> Spherize.
You’ll get a popup window and then apply the settings given below:

Step 4: Get your marque tool and rightclick on the “marking” and press “select inverse”.

Step 4: This will mark everything else but your current “circle” or “sphere”, now press delete.

Now you should have something like this:

Step 5: Lets set some blending options to the layer.

Rightclick the layer you’ve got the sphere in and press “Blending Options” or just double click the layer and set the following settings.

Step 6: Now duplicate the layer so that you have 2 sphere layers. Create yet another layer between the two.

 

Step 7: Now press the newest sphere layer and merge it down to the empty layer by pressing ctrl+E

Step 8: Then get your Elliptical Marque Tool once more, but this time just make a marque that covers about 40 percent of the sphere like this. Use the gradiant tool to create a nice gradiant that goes from white to transparent.

Step 9: Go to Filter->Blur->Gaussian Blur and set the Radius to 3.9 pixels.

Now your sphere should look something like this:

Step 10: Now use the Dodge tool to lighten up some parts of the original “Sphere-layer”.

Step 11: When you’ve done this you’ll have to create a new layer that will be beneath all the other layers except the background layer. Here you will paste your original leaf picture.

Here’s my image after pest original leaf picture in a new layer:

Step 12: Now merge both sphere-layers by pressing Ctrl+E.

Step 13: Go to Edit in the menu then -> Transform ->Warp. Press+hold and drag your mouse down to the right, you can change the shape of water drop.


Step 14: Copy the water drop layer and change the shape by applying step 13

Here’s my final result:

Thank You!

convert photo into realistic fog effect using photoshop

Photoshop tutorial, how to convert photo into realistic fog effect using photoshop. we given step by step guide and screenshots of every step.

convert photo into realistic fog effect using photoshop

To create a fog effect I will be using the basic brush, gaussian blur and a layer mask with a gradient in it. First of we need a good picture where fog will look naturall, I have chosen a picture with water in it since it is the most common place for fog.

Step 1: Open an image you want to add fog in Photoshop.

convert photo into realistic fog effect using photoshop
convert photo into realistic fog effect using photoshop

Step 2: Create a New Layer by pressing Shift+Ctrl+N.

Select the Brush Tool and set the Diameter to 150px, Hardness to 0%, Mode to Dissolve, Opacity to 15% and Flow to 30%. Set the Foreground Colour to a light grey color, I used #d6d6d6.

Step 3: Use the brush to draw horizontal lines over the image. This will create even and not very realistic fog so we need to make it thicker in some places. Set the Opacity of the brush to something like 70% and make areas with more grey. Your image should now look something like the one bellow.

Step 4: Now go to Filter > Blur > Gaussian Blur and set the Radius to 14px or something similar that you think looks good. Your image should now look like the image bellow. The next step is optional but will make the fog look more realistic.

Now your image looking like this:

Step 5: We are now going to use a layer mask to make the fog behave more realistic. Start by pressing the Add Layer Mask button at the bottom of the Layers Window. Click the Layer Mask Preview which now is visible next to the Layer Preview to make sure it’s selected. Use the Gradient tool to make a gradient going from white to black starting at the top of the layer and going straight down. Now your fog should look in the image bellow where you can compare before and after picture.

The result compared ot the original photo:

Here’s my final result:

Thank You!