.:++ Me+MySelf & I ++:.

dari dalam diri seorang aku..

Editing RAW Files in Photoshop CS2 October 28, 2007

Filed under: Photography — asriey @ 2:18 am

Today I try to open .nef (Nikon Raw) files in Photoshop CS2, but I get an error “it’s not the right kind of document”. After googling around, I found out that I need to download Adobe Camera Raw plugin in order to open the files in Ps.

Here is the site where you can download (Windows) the files. After download, follow these instruction. (from adobe.com)

To install with Adobe Creative Suite 2 or Photoshop CS2:

1. Exit Photoshop CS2.

2. Open My Computer.

3. Double-click Local Disk (C:).

4. Navigate to: (Please read directory carefully)

Program Files/Common Files/Adobe/Plug-Ins/CS2/File Formats

5. Move the existing Camera Raw.8bi plug-in to another
location (for example, a new folder on your desktop). Ensure you keep
this version in case you need to revert back.

6. Copy the Camera Raw plug-in, Camera Raw.8bi, from the download into the same folder as Step 4.

7. Launch Photoshop CS2 or Adobe Bridge.

NOTE: If generic camera thumbnails appear in Adobe Bridge, please follow the these steps:

1. Check to make sure the plug-in was installed in the correct directory in Step 6 above.

2. Start Adobe Bridge.

3. Choose Tools > Cache > Purge Central Cache.

Important: Purging the Central Cache deletes cached
thumbnail information for all folders. It also deletes labels, ratings,
and rotation settings for read-only files (for example, files on a CD
or locked files) or file formats that don’t have XMP support.

Thats all, now you can open .NEF files easily.

Powered by ScribeFire.

Advertisements
 

Solving Exchange SMTP Problem October 18, 2007

Filed under: Windows — asriey @ 4:09 pm
Tags: , , ,

On a day I take a leave for Hari Raya, my boss ask me to solve an email problem. The problem was attended earlier where we(me and cikeasy) restart the ms exchange services(that suddenly down) at HQ. We thought the the problem already solved. But then, the user complaint that since two weeks ago they cannot receive incoming email.

It takes two days for us to find out and finally solve the problem. First, we think that it could be problem with the domain itself. when we do some checking with mynic, the domain account was expired since April 2007. When cikeasy make a phone call to mynic, the said, they never ever suspended .gov.my domain(for some reason maybe). Next

When running some dns test on the domain, we find out that it cannot using the SMTP port on the public IP to send email. So maybe problem with the port. Today we working together with the network engineer to check the problem. The first mistake, dns is not pointing to the right mail exchanger(MX). After changing the dns entry, it takes some times until it resolve the right IP.

Still, we have problem telnet to port 25 on the server to check whether SMTP port opened.  My silly mistakes was to (again) ping the wrong IP address. After a few adjustment to the switch, finally it was a success.

To make sure it works, I send an email from my yahoo account, to the .gov.my domain. It appears in bridgehead server que, and later on arrive at the mailbox. Finally, problem solved.

Thanks to cikeasy and our very helpful network engineer, Radzi. Kudos to both of you!

 

Fedora 7 Installation

Filed under: Linux & OpenSource — asriey @ 3:36 pm
Tags: , , , , , ,

Finally, after a half day troubleshooting, I can post something to share with you. The installation process take about 15 minutes to finish. Before this I’ve already installed Fedora Core 4 on my Dell Inspiron 6000 and it works perfectly. But this time, it gives me some headache.

Now, the problem that I’ve encounter is that, I can ping, resolve any domain or IP, but then, when I want to browse the Internet using Firefox, it will appear as connection timeout. I’ve recheck the IP address, routing, dns etc. But it’s the same with my windows configuration.

After searching for a solution, some people suggest that it’s a problem with IPv6. Below is what I’ve change on the system.

  1. edit /etc/modprobe.conf, insert these two lines to the end
    alias net-pf-10 0ff
    alias ipv6 off
  2. edit /etc/sysctl.conf, adding these two lines to the end
    net.ipv4.tcp_moderate_rcvbuf=0
    net.ipv4.tcp_default_win_scale=0
  3. Open Firefox, at the URL, type “about:config” (without quote), find for ipv6, u’ll get network.dns.disable.IPv6 and change default value to true by clicking on it.
  4. Restart

And it works for me. Thanks to Fedora Support.


Screenshot of Fedora 7 installed on HP Compaq NX6320.

 

100 Things Martin Gommel Learned About Photography October 10, 2007

Filed under: Photography — asriey @ 3:40 am

Since I found photography two and a half years ago I have learned different things which I would like to share with you today. These lessons have made me richer and I hope that you will find them refreshing and inspiring on your journey with the camera, too.

1. Never do photography to become a rock-star.
2. Enjoy what you are shooting.
3. Prepare well for your shooting, realizing that your battery isn’t charge when you’re setting up for that sunrise shoot is too late!
4. Always take one warm garment more than you actually need with you
5. Pay attention to your thoughts and emotions while you are shooting
6. Set goals you can achieve
7. Write tips about photography, because writing is also learning
8. Never go shooting without a tripod
9. Be pleased with the little prosperities
10. Build relationships with potential photo buddies
11. Watch the place you want to shoot first with your heart then with the camera
12. Always stay calm
13. Know that you tend to overestimate yourself
14. Perspective is the killer
15. Dedicate yourself to photography, but never browbeat yourself too much
16. Take part in a photography community
17. Keep your camera clean
18. Never compare yourself to others in a better or worse context
19. Find your own style of photography
20. Try to compose more and to hit the shutter less
21. Seek out and learn to accept critique on your images
22. Do something different to recover creativity
23. Get inspiration from the work of other photographers
24. Criticize honestly but respectfully
25. Get feedback from your lady
26. Don’t copy other photographer’s style
27. Be bold
28. Take care of the golden ratio
29. 10mm rocks!
30. Take selfportraits
31. Read books about photography
32. To give a landscapephotograph the extra boost, integrate a person (maybe yourself)
33. Every shooting situation is different than you expect
34. Pay attention to s-curves and lines
35. Always shoot in RAW
36. Keep your sensor clean, so you can save some work cleaning your image in post production
37. Discover the things you think are beautiful
38. It takes time to become a good photographer
39. The best equipment is that what you have now
40. You can’t take photographs of everything
41. Break the rules of photography knowingly, but not your camera 😉
42. Pay attention to the different way that light falls on different parts of your scene
43. The eye moves to the point of contrast
44. Clouds increase the atmosphere of a landscape
45. Start a photoblog
46. Accept praise and say “thank you”
47. ‘Nice Shot’ is not a very useful comment to write
48. ‘Amazing!’ isn’t useful either. Try to describe specifically what you like or don’t like about an image.
49. You are not your camera
50. Ask a question at the end of your comment on a photo to get a ping-pong conversation with the photographer
51. Do a review of your archives on a regular basis, the longer you photograph – the more diamonds are hidden there
52. Always clarify what the eyecatcher (focal point) will be in your image
53. No image is better than a bad one
54. Everyone has to start little
55. Your opinion about photography is important!
56. Leave a funny but thoughtful comment
57. Speak about your experiences with your photo buddies
58. Limit your photograph to the substance
59. Participate in Photocontests
60. Post processing = Optimizing your image to the best result
61. Shoot exposure latitudes as often as possible
62. Use photomatix as seldom as possible, HDR’s always have a synthetic flavor
63. Always remember what brought you to photography
64. Never shoot a person who doensn’t want to be photographed
65. Always turn arround, sometimes the better image is behind you
66. It’s who’s behind the camera, not the camera
67. Mistakes are allowed! The more mistakes you make, the more you learn!
68. If you have an idea and immediately you think : No, this is not going to work – Do it anyway. When in doubt – always shoot.
69. Understand and look to your histogramm while shooting. It delivers very important information about your image
70. Know your camera, because searching the menu button in the night is time you don’t want to waste
71. Shoot as often as possible
72. Believe in yourself
73. Don’t be afraid of getting dirty
74. Pay attention to qualitiy in your image
75. Your photographs are a personal map of your psyche
76. Re-check your ISO-Settings. It’s aweful to detect the wrong settings on your screen.
77. Be thankful for long and thoughtful comments on your images
78. Never trust your LCD. Normally it is brighter and sharper as the original image.
79. Provide for enough disc space, because it’s cheap and you will need it.
80. Learn to enjoy beautful moments when you don’t have a camera with you.
81. Always arrive at least half an hour earlier before sunrise / sundown, composing in a hurry is a bad thing.
82. Try to amplify your mental and physical limits. Takes some extra shots when you think “it’s enough”
83. Pay attention to structures in the sky and wait until they fit into structures in the foreground
84. Visit the same place as often as possible. Light never shows the same mountain.
85. Print your images in big size. You will love it.
86. Calibrate your monitor. Working with a monitor that is not accurate is like being together with someone you can’t trust. It always ends badly.
87. Don’t think about what others may say about your image. If you like it, it’s worth publishing.
88. Never address reproaches to yourself. Learn from your mistakes and look forward, not backward.
89. Fight your laziness ! Creativitiy comes after discipline.
90. Ask yourself : What do you want to express in your images ?
91. Always try to think outside the box, collect new ideas about photographs you could do and ask yourself : Why not?
92. Search for a mentor.
93. Photography is never a waste of time.
94. Every community has it’s downsides. Don’t leave it out of an emotional response.
95. There will always be people who will not like what you are doing.
96. Henri Cartier-Bresson was right when he said that “Your first 10,000 photographs are your worst.”
97. A better camera doesn’t guarantee better images.
98. Always have printing in mind when you postprocess your images.
99. Photography is fair : You gain publicity with the quality of your images. Unless the images are stolen, there is no way of cheating yourself higher.
100. Write a 100 things list

original text with photos can be found here. Look at the bold. I bold it myself.

Powered by ScribeFire.

 

Learn 10 good UNIX usage habits October 9, 2007

Filed under: Solaris/Unix — asriey @ 7:25 am

Introduction

When you use a system often, you tend to fall into set usage patterns. Sometimes, you do not start the habit of doing things in the best possible way. Sometimes, you even pick up bad practices that lead to clutter and clumsiness. One of the best ways to correct such inadequacies is to conscientiously pick up good habits that counteract them. This article suggests 10 UNIX command-line habits worth picking up — good habits that help you break many common usage foibles and make you more productive at the command line in the process. Each habit is described in more detail following the list of good habits.

Adopt 10 good habits

Ten good habits to adopt are:

  1. Make directory trees in a single swipe.
  2. Change the path; do not move the archive.
  3. Combine your commands with control operators.
  4. Quote variables with caution.
  5. Use escape sequences to manage long input.
  6. Group your commands together in a list.
  7. Use xargs outside of find.
  8. Know when grep should do the counting — and when it should step aside.
  9. Match certain fields in output, not just lines.
  10. Stop piping cats.

Make directory trees in a single swipe

Listing 1 illustrates one of the most common bad UNIX habits around: defining directory trees one at a time.

Listing 1. Example of bad habit #1: Defining directory trees individually

~ $ mkdir tmp
~ $ cd tmp
~/tmp $ mkdir a
~/tmp $ cd a
~/tmp/a $ mkdir b
~/tmp/a $ cd b
~/tmp/a/b/ $ mkdir c
~/tmp/a/b/ $ cd c
~/tmp/a/b/c $

It is so much quicker to use the -p option to mkdir and make all parent directories along with their children in a single command. But even administrators who know about this option are still caught stepping through the subdirectories as they make them on the command line. It is worth your time to conscientiously pick up the good habit:

Listing 2. Example of good habit #1: Defining directory trees with one command

~ $ mkdir -p tmp/a/b/c

You can use this option to make entire complex directory trees, which are great to use inside scripts; not just simple hierarchies. For example:

Listing 3. Another example of good habit #1: Defining complex directory trees with one command

~ $ mkdir -p project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

In the past, the only excuse to define directories individually was that your mkdir implementation did not support this option, but this is no longer true on most systems. IBM, AIX®, mkdir, GNU mkdir, and others that conform to the Single UNIX Specification now have this option.

For the few systems that still lack the capability, use the mkdirhier script (see Resources), which is a wrapper for mkdir that does the same function:

~ $ mkdirhier project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

Change the path; do not move the archive

Another bad usage pattern is moving a .tar archive file to a certain directory because it happens to be the directory you want to extract it in. You never need to do this. You can unpack any .tar archive file into any directory you like — that is what the -C option is for. Use the -C option when unpacking an archive file to specify the directory to unpack it in:

Listing 4. Example of good habit #2: Using option -C to unpack a .tar archive file

~ $ tar xvf -C tmp/a/b/c newarc.tar.gz

Making a habit of using -C is preferable to moving the archive file to where you want to unpack it, changing to that directory, and only then extracting its contents — especially if the archive file belongs somewhere else.

Back to top

Combine your commands with control operators

You probably already know that in most shells, you can combine commands on a single command line by placing a semicolon (;) between them. The semicolon is a shell control operator, and while it is useful for stringing together multiple discrete commands on a single command line, it does not work for everything. For example, suppose you use a semicolon to combine two commands in which the proper execution of the second command depends entirely upon the successful completion of the first. If the first command does not exit as you expected, the second command still runs — and fails. Instead, use more appropriate control operators (some are described in this article). As long as your shell supports them, they are worth getting into the habit of using them.

Run a command only if another command returns a zero exit status

Use the && control operator to combine two commands so that the second is run only if the first command returns a zero exit status. In other words, if the first command runs successfully, the second command runs. If the first command fails, the second command does not run at all. For example:

Listing 5. Example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c && tar xvf ~/archive.tar

In this example, the contents of the archive are extracted into the ~/tmp/a/b/c directory unless that directory does not exist. If the directory does not exist, the tar command does not run, so nothing is extracted.

Run a command only if another command returns a non-zero exit status

Similarly, the || control operator separates two commands and runs the second command only if the first command returns a non-zero exit status. In other words, if the first command is successful, the second command does not run. If the first command fails, the second command does run. This operator is often used when testing for whether a given directory exists and, if not, it creates one:

Listing 6. Another example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c

You can also combine the control operators described in this section. Each works on the last command run:

Listing 7. A combined example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c && tar xvf -C tmp/a/b/c ~/archive.tar
Back to top

Quote variables with caution

Always be careful with shell expansion and variable names. It is generally a good idea to enclose variable calls in double quotation marks, unless you have a good reason not to. Similarly, if you are directly following a variable name with alphanumeric text, be sure also to enclose the variable name in curly braces ({}) to distinguish it from the surrounding text. Otherwise, the shell interprets the trailing text as part of your variable name — and most likely returns a null value. Listing 8 provides examples of various quotation and non-quotation of variables and their effects.

Listing 8. Example of good habit #4: Quoting (and not quoting) a variable

~ $ ls tmp/a b~ $ VAR="tmp/*"~ $ echo $VARtmp/a tmp/b~ $ echo "$VAR"tmp/*~ $ echo $VARa

~ $ echo "$VARa"

~ $ echo "${VAR}a"tmp/*a~ $ echo ${VAR}atmp/a~ $
Back to top

Use escape sequences to manage long input

You have probably seen code examples in which a backslash (\) continues a long line over to the next line, and you know that most shells treat what you type over successive lines joined by a backslash as one long line. However, you might not take advantage of this function on the command line as often as you can. The backslash is especially handy if your terminal does not handle multi-line wrapping properly or when your command line is smaller than usual (such as when you have a long path on the prompt). The backslash is also useful for making sense of long input lines as you type them, as in the following example:

Listing 9. Example of good habit #5: Using a backslash for long input

~ $ cd tmp/a/b/c || \> mkdir -p tmp/a/b/c && \> tar xvf -C tmp/a/b/c ~/archive.tar

Alternatively, the following configuration also works:

Listing 10. Alternative example of good habit #5: Using a backslash for long input

~ $ cd tmp/a/b/c \
>|| \> mkdir -p tmp/a/b/c \
>&& \> tar xvf -C tmp/a/b/c ~/archive.tar

However you divide an input line over multiple lines, the shell always treats it as one continuous line, because it always strips out all the backslashes and extra spaces.

Note: In most shells, when you press the up arrow key, the entire multi-line entry is redrawn on a single, long input line.

Back to top

Group your commands together in a list

Most shells have ways to group a set of commands together in a list so that you can pass their sum-total output down a pipeline or otherwise redirect any or all of its streams to the same place. You can generally do this by running a list of commands in a subshell or by running a list of commands in the current shell.

Run a list of commands in a subshell

Use parentheses to enclose a list of commands in a single group. Doing so runs the commands in a new subshell and allows you to redirect or otherwise collect the output of the whole, as in the following example:

Listing 11. Example of good habit #6: Running a list of commands in a subshell

~ $ ( cd tmp/a/b/c/ || mkdir -p tmp/a/b/c && \
> VAR=$PWD; cd ~; tar xvf -C $VAR archive.tar ) \
> | mailx admin -S "Archive contents"

In this example, the content of the archive is extracted in the tmp/a/b/c/ directory while the output of the grouped commands, including a list of extracted files, is mailed to the admin address.

The use of a subshell is preferable in cases when you are redefining environment variables in your list of commands and you do not want those definitions to apply to your current shell.

Run a list of commands in the current shell

Use curly braces ({}) to enclose a list of commands to run in the current shell. Make sure you include spaces between the braces and the actual commands, or the shell might not interpret the braces correctly. Also, make sure that the final command in your list ends with a semicolon, as in the following example:

Listing 12. Another example of good habit #6: Running a list of commands in the current shell

~ $ { cp ${VAR}a . && chown -R guest.guest a && \
> tar cvf newarchive.tar a; } | mailx admin -S "New archive"
Back to top

Use xargs outside of find

Use the xargs tool as a filter for making good use of output culled from the find command. The general precept is that a find run provides a list of files that match some criteria. This list is passed on to xargs, which then runs some other useful command with that list of files as arguments, as in the following example:

Listing 13. Example of the classic use of the xargs tool

~ $ find some-file-criteria some-file-path | \
> xargs some-great-command-that-needs-filename-arguments

However, do not think of xargs as just a helper for find; it is one of those underutilized tools that, when you get into the habit of using it, you want to try on everything, including the following uses.

Passing a space-delimited list

In its simplest invocation, xargs is like a filter that takes as input a list (with each member on a single line). The tool puts those members on a single space-delimited line:

Listing 14. Example of output from the xargs tool

~ $ xargsabcControl-Da b c~ $

You can send the output of any tool that outputs file names through xargs to get a list of arguments for some other tool that takes file names as an argument, as in the following example:

Listing 15. Example of using of the xargs tool

~/tmp $ ls -1 | xargs
December_Report.pdf README a archive.tar mkdirhier.sh
~/tmp $ ls -1 | xargs 
fileDecember_Report.pdf: PDF document, version 1.3
README: ASCII text
a: directoryarchive.tar: POSIX tar archive
mkdirhier.sh: Bourne shell script text executable
~/tmp $

The xargs command is useful for more than passing file names. Use it any time you need to filter text into a single line:

Listing 16. Example of good habit #7: Using the xargs tool to filter text into a single line

~/tmp $ ls -l | xargs
-rw-r--r-- 7 joe joe 12043 Jan 27 20:36 December_Report.pdf -rw-r--r-- 1 \
root root 238 Dec 03 08:19 README drwxr-xr-x 38 joe joe 354082 Nov 02 \
16:07 a -rw-r--r-- 3 joe joe 5096 Dec 14 14:26 archive.tar -rwxr-xr-x 1 \
joe joe 3239 Sep 30 12:40 mkdirhier.sh
~/tmp $

Be cautious using xargs

Technically, a rare situation occurs in which you could get into trouble using xargs. By default, the end-of-file string is an underscore (_); if that character is sent as a single input argument, everything after it is ignored. As a precaution against this, use the -e flag, which, without arguments, turns off the end-of-file string completely.

Back to top

Know when grep should do the counting — and when it should step aside

Avoid piping a grep to wc -l in order to count the number of lines of output. The -c option to grep gives a count of lines that match the specified pattern and is generally faster than a pipe to wc, as in the following example:

Listing 17. Example of good habit #8: Counting lines with and without grep

~ $ time grep and tmp/a/longfile.txt | wc -l2811

real    0m0.097suser    0m0.006ssys     0m0.032s~ $ time grep -c and tmp/a/longfile.txt2811

real    0m0.013suser    0m0.006ssys     0m0.005s~ $

An addition to the speed factor, the -c option is also a better way to do the counting. With multiple files, grep with the -c option returns a separate count for each file, one on each line, whereas a pipe to wc gives a total count for all files combined.

However, regardless of speed considerations, this example showcases another common error to avoid. These counting methods only give counts of the number of lines containing matched patterns — and if that is what you are looking for, that is great. But in cases where lines can have multiple instances of a particular pattern, these methods do not give you a true count of the actual number of instances matched. To count the number of instances, use wc to count, after all. First, run a grep command with the -o option, if your version supports it. This option outputs only the matched pattern, one on each line, and not the line itself. But you cannot use it in conjunction with the -c option, so use wc -l to count the lines, as in the following example:

Listing 18. Example of good habit #8: Counting pattern instances with grep

~ $ grep -o and tmp/a/longfile.txt | wc -l3402~ $

In this case, a call to wc is slightly faster than a second call to grep with a dummy pattern put in to match and count each line (such as grep -c).

Back to top

Match certain fields in output, not just lines

A tool like awk is preferable to grep when you want to match the pattern in only a specific field in the lines of output and not just anywhere in the lines.

The following simplified example shows how to list only those files modified in December:

Listing 19. Example of bad habit #9: Using grep to find patterns in specific fields

~/tmp $ ls -l /tmp/a/b/c | grep Dec
-rw-r--r--  7 joe joe  12043 Jan 27 20:36 December_Report.pdf
-rw-r--r--  1 root root  238 Dec 03 08:19 README
-rw-r--r--  3 joe joe   5096 Dec 14 14:26 archive.tar
~/tmp $

In this example, grep filters the lines, outputting all files with Dec in their modification dates as well as in their names. Therefore, a file such as December_Report.pdf is matched, even if it has not been modified since January. This probably is not what you want. To match a pattern in a particular field, it is better to use awk, where a relational operator matches the exact field, as in the following example:

Listing 20. Example of good habit #9: Using awk to find patterns in specific fields

~/tmp $ ls -l | awk '$6 == "Dec"'
-rw-r--r--  3 joe joe   5096 Dec 14 14:26 archive.tar
-rw-r--r--  1 root root  238 Dec 03 08:19 README
~/tmp $

See Resources for more details about how to use awk.

Back to top

Stop piping cats

A basic-but-common grep usage error involves piping the output of cat to grep to search the contents of a single file. This is absolutely unnecessary and a waste of time, because tools such as grep take file names as arguments. You simply do not need to use cat in this situation at all, as in the following example:

Listing 21. Example of good and bad habit #10: Using grep with and without cat

~ $ time cat tmp/a/longfile.txt | grep and2811

real    0m0.015suser    0m0.003ssys     0m0.013s~ $ time grep and tmp/a/longfile.txt2811

real    0m0.010suser    0m0.006ssys     0m0.004s~ $

This mistake applies to many tools. Because most tools take standard input as an argument using a hyphen (-), even the argument for using cat to intersperse multiple files with stdin is often not valid. It is really only necessary to concatenate first before a pipe when you use cat with one of its several filtering options.

Back to top

Conclusion: Embrace good habits

It is good to examine your command-line habits for any bad usage patterns. Bad habits slow you down and often lead to unexpected errors. This article presents 10 new habits that can help you break away from many of the most common usage errors. Picking up these good habits is a positive step toward sharpening your UNIX command-line skills.

copied from http://www-128.ibm.com/developerworks/aix/library/au-badunixhabits.html

Powered by ScribeFire.

 

Selamat Hari Raya Aildilfitri 1428H October 8, 2007

Filed under: Personal — asriey @ 1:22 pm

Di kesempatan ini, saya ingin mengucapkan selamat hari raya aidilfitri kepada semua. tak kira siapa juga anda. Maaf Zahir & Batin andai ada salah dan silap dalam saya mencoret dalam blog ini.

Powered by ScribeFire.

 

Configure ScribeFire

Filed under: Tutorial — asriey @ 1:13 pm

First of all you need to have Firefox installed on your pc/notebook. Then go to https://addons.mozilla.org/en-US/firefox/addon/1730. Download and install the addon. restart firefox. The addon will appear at the bottom right of your browser. click on it will open the menu.

On the Blogs tab, click Add. Type in your blog address and choose the blogging service to add. If you are using blogspot, you need to custom it a lil bit. the tricky part when to set API URL for the blog. after that just fill in the username and password. It will connect to your blog and you can start posting from the browser without need to open and login through the web.

Thanks to ScribeFire.

Powered by ScribeFire.