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. :~
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.
Places the photos you want to include in the gallery in a folder on your hard drive.
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.
Twitter is routing links within Direct Messages through our link service to detect, intercept, and prevent the spread of malware, phishing, and other dangers. Any link shared in a Direct Message has been wrapped with a twt.tl URL.
Twitter is scanning all shortened URLs befor being posted
Links reported to us as malicious are blacklisted, and we present users with a page that warns them of potentially malicious content if they click blacklisted links. Twitter wants users to have this benefit on all tweets.
Twitter is scanning all shortened URLs befor being posted
Raffi Krikorian, a technical lead on the Twitter Platform Team, explained in a Google Groups posting that the t.co system will always format links to 20 characters.
Additionally, as we mentioned at our Chirp developer conference in April, if you want to share a link through Twitter, there currently isn’t a way to automatically shorten it and we want to fix this. It should be easy for people to share shortened links from the Tweet box on Twitter.com.
To meet both of these goals, we’re taking small steps to expand the link service currently available in Direct Messages to links shared through all Tweets. We’re testing this link service now with a few Twitter employee accounts.
This change will is specially made for mobile users. In addition to a better user experience and increased safety, routing links through this service will eventually contribute to the metrics behind our Promoted Tweets platform and provide an important quality signal for our Resonance algorithm—the way we determine if a Tweet is relevant and interesting to users. We are also looking to provide services that make use of this data, an example would be analytics within our eventual commercial accounts service.
If you want to use smiley images in wordpress posts then you can use our tricks. Here in this article, we given sample and trick for using smiley in posts.
Follow our steps.
Find your smiley image files in the /wp-includes/images/smilies directory and back them up to another directory
Note the names of each smiley file. Your files must match these names and should be in the same ‘gif’ image format.
For predictable behavior, the image sizes should be similar.
Upload your new files to the /wp-includes/images/smilies directory with an FTP program.
How to use smiley images in wordpress posts
How to use smiley images in wordpress posts
If you want to changes the names of smiley and you need to edit wp-includes/functions.php file.
In that file you will find the “smilies_init” function.
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
Smileys, also known as “emoticons,” are glyphs used to convey emotions in your writing. They are a great way to brighten up posts.
By default, WordPress automatically converts text smileys to graphic images. When you type 😉 in your post you see 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.
Go to your Admin Panel
Select Settings -> Writing
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.
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
🙂
🙂
🙂
😆
😀
😀
😀
😳
🙁
🙁
🙁
😥
😮
😮
😮
👿
😯
😯
😯
😈
😕
😕
😕
🙄
8)
😎
😎
❗
😡
😡
😡
❓
😛
😛
😛
💡
😐
😐
😐
➡
😉
😉
😉
* 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.
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
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
——————————————————–
[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 ~]#
Most of wordpress plugin writer choose the new table for saving data for plugin setting and any setting in wordpress plugin. In this article we will show, how to use update option in wordpress plugin. I recommend to use the update option for saving data in wordpress database.
how to use update option in wordpress plugin
how to use update option in wordpress plugin
There is ready made option is provided by wordpress to save custom data in there table.
Here with very simple code I will show how use save the data in wordpress database.
< ?php
$variable = array(‘var1′ => $_POST['var1'], ‘var2′ => $_POST['var2']);
update_option(‘myPlugin_var1′, serialize($variable));
get_option(‘myPlugin_var1′) == “” ? “” : $new = unserialize(get_option(‘myPlugin_var1′));
?>
You should save data in simple variable format or I suggest always save data in array format.
For more reference you can check the following URL
http://phpxref.com/xref/wordpress/wp-admin/options.php.source.html
Yahoo users can now view their Facebook News Feed via their Yahoo home page, Yahoo Mail, and other Yahoo sites, the company said. Additionally, content created on Yahoo sites, including Yahoo News, Sports, Movies and the photo-site Flickr, can be shared with friends on Facebook.
Yahoo and Facebook Users now exchange content and data
Yahoo and Facebook Users now exchange content and data
Ethan Beard, director of Facebook Developer Network, was quoted in the Yahoo statement saying that, “by integrating with Facebook on a global scale, Yahoo is building upon an already valuable brand to give people easy ways to share the content they enjoy on Yahoo! with their friends on Facebook.”
Yahoo offered more details of the way people can connect with Facebook sites on its blog, but Facebook remained mum on the issue early Monday, without any details in its press center, blog or twitter feed. The most recent communications on these pages largely addressed privacy concerns.
Yahoo and Facebook first announced a plan to integrate services much more closely last December. At the time, Yahoo users in the U.S. were able to call up their Facebook activity streams and post status updates from the Yahoo home page, as well as use buttons to share certain Yahoo content. The companies promised much more this year via the use of Facebook’s Connect technology across Yahoo sites.
Here in this article we will show, how to upload videos to wordpress blog using wordpress plugin called videopress. Videopress is best worpdress plugin for videos.
VideoPress is a strong supporter of free software, including video formats and codecs. All videos uploaded to VideoPress are available for download in Ogg video format with Theora video and Vorbis audio. If you blog on WordPress.com you now have the ability to restrict VideoPress embed to only free video formats unrestricted by known patent claims or intellectual property licensing hurdles.
how to upload videos to wordpress blog
how to upload videos to wordpress blog
Publishers concerned about the freedom restrictions of the default VideoPress player’s use of Adobe Flash, MP4, H.264/AVC High profile video, and AAC–LC can override the default behavior through their WordPress.com blog’s Media Settings page (yourblog.wordpress.com/wp-admin/options-media.php). Your free software formats choice applies to all VideoPress videos embedded on your blog, including videos from other VideoPress publishers.
Videos included in your posts and pages will be output using HTML5 for playback using default video controls in supporting web browsers such as Mozilla Firefox 3.5+, Google Chrome 3.0+, and Opera 10.5+.
The free formats setting may be expanded in the future to include additional formats free of known patent claims. The newly supported WebM file container with VP8 video and Vorbis audio is an early example of what could become a video format without known intellectual property claims prohibiting open distribution. We plan to add support for freedom preference for self-hosted WordPress blogs through our VideoPress plugin once we have tested this new feature with the millions of active blogs on WordPress.com.
Photoshop has been a part of every web designer’s life since they picked up their first mouse. Here we given brief History of Adobe Photoshop with screenshots.
History of Adobe Photoshop
History of Adobe Photoshop
On February 10th, 2010, Photoshop turns twenty. To mark this anniversary, we’ve come up with an article that takes you through the evolution of Photoshop from its modest beginnings as a bundled program sold with scanners to its current version.
For each version and major feature listed, we couldn’t help but think “did Photoshop ever exist without that feature?”.
Some of the minor details are fun too, such as the one-liner Easter Eggs that Photoshop developers hid in some versions and the fact that the most current versions of Adobe Photoshop CS are equipped with anti-counterfeiting measures for multiple world currencies.
Please join us in thanking the Knolls and Adobe for making all of our lives more awesome, every day.
One of the most impressive things about the company is the fact that one gifted family, consisting of an engineering prof, a PHD engineering student, and a talented special effects whiz working at Industrial Light and Magic came up with the core idea of Photoshop.
Thomas Knoll, the PHD student, is still heavily involved with Photoshop years later.
Glen Knoll was a college professor with two sons and two hobbies; computers and photography.
He had a darkroom in his basement, and an Apple II Plus that he was allowed to bring home from work.
Thomas Knoll adopted his father’s photography habit throughout high school, while his brother, John Knoll, purchased one of the first Macs available to the public.
Fast forward to 1987: Thomas Knoll was a PHD student studying Engineering at the University of Michigan. His brother was working at Industrial Light and Magic.
Thomas Knoll wrote a subroutine for a program to translate monochrome images on his monitor to grayscale.
The successful subroutine led Knoll to create more and very soon he had a number of processes for achieving photographic effects on digital images.
After his brother John saw what Thomas was doing, he recommended that Thomas turn what he was doing into a full-featured image editor.
History of Adobe Photoshop
The combination of Thomas’ programming abilities with John’s pragmatic design background led to a collaboration between the two brothers to develop more processes and improve on the initial application.
Even though the process led to interruption in Thomas’ thesis work, the brothers released “Image Pro” in 1988.
John suggested that they begin to sell Image Pro as an application.
Within six months, the brothers had a partnership with a company that manufactured scanners, Barneyscan.
They purchased 200 copies of the program to ship with their scanners.
They called on Supermac and Aldus, but were turned away at both, a move that Aldus would come to seriously regret.
Shortly after, the Knoll brothers struck gold when they won over Adobe management with their product, and formed a licensing partnership with Adobe that was to launch their software and Adobe into the stratosphere.
We’ve included major changes within each version and some minor ones. This is meant to be a fun stroll down memory lane rather than a complete version catalogue.
If you have a particular version change that got your hackles up or a feature that you’d to mention, feel free to add it to the comments section.
1990 – Photoshop 1.0
John Knoll, Thomas’ brother, wrote “special effects” for the program which were frowned upon by Adobe staff as being too “gimmicky”. Thomas and John found a way to sneak them into Photoshop as plugins, giving rise to what is now a huge cottage industry in add-ons to the popular program.
John and Adobe staff constantly pushed Thomas to make improvements until the final product shipped.
The first version of the Photoshop splash screen features just four Photoshop programmers. In subsequent versions, more and more names are added to the list. In more recent versions, a limited number of Adobe VIP’s appear in the splash screen.
Photoshop 2.0 included the Path feature, which allowed users to trim around an object easily and to save that path for future use. This feature was added by a second engineer, Mark Hamburg, that Adobe hired to work on the application.
Up until 2.0, Thomas Knoll was the only engineer working on it. Adobe called Mark the “Path Man”. 2.0 also featured rasterizing for Illustrator files, support for CMYK colour which led to widespread Photoshop adoption by the printing industry, and the Pen.
Photoshop 2.0 also required 4 megabytes of RAM to run rather than 2, which really helped program stability.
Photoshop 2.5, released in 1992, was notable for being the first release for the Windows operating systems.The code had to be completely changed in order to accomplish this goal which meant that the first effort was slow going.
16-bit file support and palettes were added to this version as well. The initial Windows release had a “memory bug”, a bug which actually saw Mark Hamburg offer to make house calls. The patched version was released as 2.5.1. Filters got their own menu in 2.5 as well. The workspace shot below is of Photoshop 2.5 for the Mac.
The big story for Adobe Photoshop 3.0 was layers. Layers were and are a lifesaver for any marginally complex design.
Prior to their introduction, designers would save different versions of designs so that they could go back and grab them if needed; layers made this practice redundant.
Layers are individual slices of the image that go together to make the final “sandwich” of the image. Different images, such as those used in the image above in the 3.0 splash screen, are assigned their own layers, making it easy to work on those images without tampering with other areas of the image.
Thomas Knoll, the original creator of the program, was responsible for their development. Other engineers made improvements in the program’s performance with Power Mac chips and bringing the Windows version up to the same level as the Mac version. Tabbed palettes also had their debut in 3.0.
Adobe engineers included Adobe Transient Witticisms (ATW) with this version. They were little Easter Egg funny one-liners that would appear only when you pressed obscure combinations of keys.
Adjustment layers and macros were the two most notable features of Photoshop 4.0.
Adjustment layers allow the designer to apply one effect to a group of layers. Macros, or actions in Photoshop speak, allow you to map a series of commands to one command. This allows you to perform the same operation in much less time if you have a bunch of images to work on.
The most important change to 4.0 was the unification of the user interface with other Adobe products, a feature which Adobe has stayed consistent with right up to present-day incarnations of the program. This meant a less steep learning curve for Adobe products, a blessing for those who got their start with Photoshop 4.0.
Loyal users of Photoshop were not amused with the redesign, the common question from the community being “Why did you break Photoshop?”.
The two most important features released with 5.0 were editable type and the ability to undo actions multiple times in the “History” palette.
Previous versions of Photoshop allowed text to be added, but the fuzzy rasterized type didn’t make for pretty magazine mastheads or decent web menus. This was a huge step forward. Multiple undos via the History palette were very helpful, especially since designers were starting to use the new Adobe tools for increasingly complex designs.
Color Management made its debut with 5.0. Like other major changes to Photoshop, it was greeted with equal parts of praise and condemnation. It allowed colors to be managed natively within the application rather than relying on third-party tools that had been used, a huge improvement.
However, it also automatically converted the colors when opening files, a “feature” that engineers quickly eliminated after multiple user complaints. The magnetic lasso tool debuted in 5.0, making selecting areas of an image to work on much easier.
Photoshop 5.5 featured the huge time saver, “Save For Web”. This feature allows those who choose it to save the image in a preset specifically designed for web use which allows the user to adjust image quality to achieve a smaller image.
Version 5.0 had failed to take the Web into account with all of its other major feature changes on the table. It was also bundled with ImageReady, a standalone program that was purpose-built to edit web graphics.
Most of the features of ImageReady were later incorporated into the full version of Photoshop and the idea of a simpler program was reborn eventually in the form of Photoshop Elements.
The layer styles panel made working with layers even easier in Photoshop 6. Vector shapes were also added in this release; the ability to draw vector shapes such as arrows into a bitmap was lauded by users.
There was also a new custom shapes palette that allowed the user to draw using vector shapes rather than just using lines. Text could also now be typed directly onto a picture, rather than being typed first into a text box.
Multi-layer functions made their first appearance with version 6.0. The Blending Options dialogue was also introduced which made blending various elements of an image much easier. 6.0 separated the crop tool from the marquee tool, making it that much easier to get to this commonly used command.
With the increasing complexity of the tools available to users, Photoshop was risking losing a significant market share that didn’t understand or need some of its more advanced tools.
In order to combat this, they released Photoshop Elements in 2001. The new product was a success, and designers continue to recommend it to clients for simple image resizing and other non-design tasks.
While its current interface, shown below, isn’t intuitive for those trained in traditional Photoshop, it is highly usable and labeled clearly for the average user. If there are any problems with it in terms of functionality, the simple answer is to upgrade to the full-featured Photoshop.
Version 7.0 introduced the healing brush and text that was fully vector-based. More importantly to veteran users, it introduced a new file browser that let designers easily pore through folders to find the graphics that they wanted.
Files within a folder could be renamed using Batch Rename, plus a bunch of other helpful commands that made working with a high volume of files much easier.
Workspaces could also be created and saved, allowing you to save your file locations and groups for future use.
The brush palette also featured a number of changes, including the new healing brush tool, patch tool, and the ability to create custom brushes. Spell check and a find/replace feature rounded out the updates to the text tool.
A number of enhancements were also included for web use, including the addition of rollover effects for images and a web gallery feature.
One of the most important upgrades was under the hood; 7.0 was optimized for use with Mac OS X, virtually eliminating crashes in the middle of working on large files. The tool presets palette let users program presets for commonly performed tasks, increasing efficiency.
Photoshop CS was the first to employ the CDS (counterfeit deterrence system) which recognized and refused to allow duplication of paper currency.
Scripting support for various web languages, including JavaScript, was also new to this release.
Layer groups were introduced with this version, which allowed various layers to be grouped together for effects to be applied to some and not others.
Improvements to the File Browser made images easier to work with, and the 16-bit and better large file support made CS much easier to work with for designers who constantly worked with larger images and photographers.
The red eye removal tool, previously exclusive to Elements, was popular enough to make an appearance in the core version of Photoshop. Smudging options and the ability to select multiple layers also added to the functionality of Photoshop.
The Vanishing Point tool allowed users to edit images in perspective. The largest moment of panic when upgrading to PS2 came for most when they tried to find the Paint Bucket tool, which had been classified under the Gradient tool. There were other significant changes to the UI that prompted one writer to put out this “Where’s My Stuff?” column.
Layers and the layers palette were other areas of note. The “links” column was removed because CS2 included a link button rather than the small chains beside each layer. The “Smart Object” feature was introduced, which allows the user to scale a layer up without significant loss of quality.
A faster load was probably the most noticeable feature of this 2007 release. It included fine tuning to a number of its existing tools rather than focusing on new ones.
The most notable new feature was graphic optimization for mobile devices, a feature which many web designers focusing on mobile design were thankful for. This version also saw significant feature updates to Adobe Camera RAW, a Quick Select tool, alterations to core commands like Brightness and Contrast and Black and White conversion.
CS3 shipped in Standard and Extended editions. The Extended version was intended for high end video and scientific users. Improved performance for Intel-based Macs significantly improved the speed of Photoshop, while Windows users also enjoyed performance upgrades. The new Quick Selection tool put the rest of the selection tools in Photoshop to shame with easy object selection with one or two strokes.
Cloning became easier in CS3 with the birth of the Clone Source palette which increased the options available to the Clone Stamp tool in an easily accessible palette.
The smoother pan and zoom allowed for fast drill down on the areas of an image that you wanted to look at. Prior to this, there was a lag time of a few seconds (depending on your system) if you wanted to zoom in or out on an image.
The Masks and Adjustments panel was added, making working with masks easier. CS 4 also dealt with edges on masks more effectively. Colour correction took a huge step forward with this release.
The user interface was significantly simplified in CS4. The support of tabbed documents made it much easier to use and the main tools were added to the title bar for easier access. Quick access for common actions was made available in the panel area.
Thomas Knoll
Thomas was the lead developer of Photoshop right up until CS 4. He now leads up the Camera Raw plugin for Photoshop, which allows Photoshop to develop a smooth handshake between different models of camera raw image formats.
History of Adobe Photoshop
John Knoll
John is still employed by Industrial Light and Magic as a Visual Effects Supervisor. He was the Visual Effects Supervisors for the recent efforts on the first three Star Wars prequel films. He also supervised work on two Star Trek movies, Star Trek episodes, and the Pirates of the Caribbean movies.
Glenn Knoll
Their father is a teacher at the University of Michigan in the Engineering Department.
In this article, we will tell you very nice resources for contact form in wordpress plugins. We collected unique Best contact form wordpress plugins.
best contact form wordpress plugins
1. Contact Form 7
Best contact form wordpress plugins
WordPress plugin for contact form is Contact Form 7.
Contact Form 7 can manage multiple contact forms, plus you can customize the form and the mail contents flexibly with simple markup. The form supports Ajax-powered submitting, CAPTCHA, Akismet spam filtering and so on.
You can download this plugin from following url. http://ideasilo.wordpress.com/2007/04/30/contact-form-7/
This plugin is good to use but there no advanced options like customize css and look of contact form.
Clean-contact hides itself from spam-bots by, and optionally will filter messages using Akismet — Capctha and skill testing questions not required.
You can download this plugin from following url. http://www.checkfront.com/dev/extras/wp-clean-contact
Cforms is a great plugin but it hardcode some datas in PHP and JS files. It also save on WP options the URL of the blog, it’s cause some problem when you want moving your blog.
This plugin allow edit this parameter from WordPress without open your FTP client or use phpMyAdmin.
You can download this plugin from following url. http://www.deliciousdays.com/cforms-plugin/
6. Fast and Secure Contact Form
Fast and Secure Contact Form for WordPress. This contact form lets your visitors send you a quick E-mail message. Blocks all common spammer tactics. Spam is no longer a problem. Includes a CAPTCHA and Akismet support. Additionally, the plugin has a multi-form feature, optional extra fields, and an option to redirect visitors to any URL after the message is sent. Does not require JavaScript.
You can download this plugin from following url. http://wordpress.org/extend/plugins/si-contact-form/
