Friday, February 27, 2009

The Decline of Handwriting Skills: A Tragedy, or a Sign of Progress?


I just found an article about the slow death of handwriting while surfing the web. It really caught my attention because, while not mentioned or even hinted in that article, it would seem that technology could be one of the major causes of the declining relevance of handwriting today, and I am fond of both technology and writing—of which, handwriting is a natural part, whether by history or convention. In fact, I recursively use technology to write and publish stuff about technology and publishing (blogging).

Learning the art of handwriting is a demanding undertaking. It takes a lot of patience and practice to be proficient in it. Technology, on the other hand, promises desktop publishing even to hunt and peck typists.

In less than half a day, the average adult can be taught how to turn on the computer and fire up notepad. After that, she can type (even with both index fingers only) and print a simple letter to her boss. But if she does it by hand and her handwriting is indistinguishable from hieroglyphics, it’s going to take a lot longer than half of a day if she does not want her boss to take the letter as a death threat from a mummy.

Since learning the art of handwriting is tedious and rendered unnecessary due to the ease with which technology can duplicate the results, there is less motivation to undergo the torture—specially if it involves one’s hand being slapped with a long ruler. In addition, time spent learning the intricacies of holding the pen in just the right angle is time lost for learning more employable and relevant skills—like typing and how to use OpenOffice.org. So, most schools would rather focus on the latter.

Clearly, technology is one of the many culprits—if not the master-mind—of handwriting’s fall from grace. The question is: Is this a good thing, or not? Also, should technology be punished for the fate of handwriting, or applauded for the productivity it offers in exchange? Finally, should handwriting still occupy the same status in our schools as it did in the past, considering the amount of new materials to cover and the limited time? This is for each individual to consider. For me, the answer is clear.

Personally, I really like to write. Not just the writing one does when creating content but the physical act of writing itself, regardless of the product or result. There is so much to be said about the feeling you get when a good pen slides and glides on a piece of paper. It's like some kind of moving meditation by which you are disconnected from the whole world for a moment and you, the pen and the paper become one. This I do all the time when the need to relax or to clear my mind arises. I write random words, small loops, big loops, diagonals, and curls. What I write does not matter; only the act of writing does. It is a wonderful exercise that helps me feel better, improve my handwriting and reuse some paper which should have been due for the recycle bin.

There is another benefit of writing by hand. With it, you can draft the most personal message you can send somebody. Sending a handwritten message sends a message of its own—that of sincerity and importance.

The significance of a handwritten document is also not lost in the legal world. In some jurisdictions, a handwritten document takes precedence over typewritten or printed ones. In testamentary succession, some jurisdictions do not require a will to be notarized if it is in the handwriting of the testator (a holographic will). This speaks a lot about the weight given to handwritten documents and instruments.

However, while the importance and benefits of writing by hand is certainly acknowledged, the increased productivity you get with the aid of technology cannot be simply ignored. There are just a lot of things you can do better with a keyboard and a text editor than with a pen and paper.

When time is of the essence, a fast writer will find it very hard to match the speed of an average typist hammering on a Dvorak-layout keyboard. Finding mistakes in a word processor or text editor and correcting them is also a little less messy than with the pen and paper counterpart. In this Internet age, it becomes easier to integrate research and writing if you do it with a text editor. And when we add spell checking, search and replace, copy and paste functionalities, etc., it becomes a no contest.

Another thing is, and I think this is the real reason for the impending demise of handwriting as people knew it in the pre-60's, you need an inordinate amount of time to learn to write something as presentable as a computer generated document—time better spent learning to touch-type. For this reason, most people will not bother to spend more time with their handwriting above what is required to be reasonably legible. They can be more productive in a much shorter amount of time with a keyboard. Sure, people will still write by hand and it will still be taught in schools—but not in the same manner and emphasis as in the past.

I already confessed that I love to write by hand. But since it is not practical for the tasks that I commonly face in this day and age, I became a keyboard warrior, practiced mouse-fu for my daily tasks, and wielded the pen only for leisure, a short note and the oft-cited example: to-do or grocery lists. Luckily (or perhaps, unluckily) for me, I have already developed a reasonable level of handwriting skill to be able to use it without requiring the reader to have an advanced degree in cryptography. But for those still in school, I am not surprised and do not blame them if they de-emphasize handwriting in favor of typing skills. After all, nobody ever shed a tear when the slide rule was replaced by the calculator, or when travelling by foot was replaced by speedy and convenient transportation, or when the telegram was replaced by text messaging then by twitter, or when...

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Wednesday, February 25, 2009

Does Writing and Programming Mix?


Since I sometimes write and also do some programming, I began to wonder if there really are any significant differences between the two activities.

On the surface, it would seem that the two are very different. Programming is usually associated with logic and hence, with the left hemisphere of the brain. Writing, on the other hand, is normally viewed as a creative endeavor which taps on the right hemisphere just like other things creative.

Studies show that creative people have a dominant right hemisphere and logical people have a dominant left. Since one side is dominant than the other in both types, does that mean that writers can only write and not program well, or that programmers can only program and not write well?

I think both are really just different sides of the same coin just as Slackware and Debian are different packages of the same Linux kernel and GNU components.

Writing is not purely creative. You need a dash of logic to put structure in what you write. Programming is not pure logic either. Most of the brilliant hackers (think Dennis Ritchie, Ken Thompson, Richard Stallman, Linus Torvalds, Bill Gates, Steve Jobs, Eric Raymond, etc.—not network intruders or system crackers) are known to be very creative people. And in programming, sometimes only creativity can get you out of a situation where logic and reason deem hopeless.

Both of them even have the same elements. Communication is the raison d'ĂȘtre of both. In the case of writing, you are communicating with another person—your readers. In programming, you communicate with the machine. Both also use language to communicate. This could be English or Spanish for writing, and Lisp or Smalltalk for programming. And just like any other languages, programming languages also have grammar; they just call it syntax. They even have their own elements of style.

I like to think of programming as “writing” a program and do it just like I would do any writing project. There’s still that planning phase before any writing gets done, of course. The only differences are the language and references I use and my target audience. Instead of a dictionary, I reach for the language’s class or function reference—I even use a text editor for both.

I believe that writing a program is like writing a book (programs also have publishers, right?). A small program equals a small book and a large program equals a large book—or a series of books. I could be wrong, of course, considering that I haven’t written any significant program (or book) worthy of SourceForge or Google Code. But then again, maybe the next hottest programming methodology will be called Persuasive Programming wherein you aim to persuade the computer to refrain from giving you headaches and to just do whatever it is that it should do.

What do you think? Could it be that we got it wrong when we correlated programming, which deals more about the abstract and conceptual, to building construction which is more about real and concrete materials? Should programmers, then, be called Software Writers rather than the current and more macho title of Software Engineer and Software Architect? Or shouldn’t writing and programming mix?

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Monday, February 23, 2009

How The Web Was (or Will Be) Won


In a previous post, I talked about how non-compliant browsers are hindering Web development progress. I urged everyone to upgrade their browsers to more standards compliant ones. If a lot of users do so, they will be helping the Web reach its true potential. In the end, all users will benefit.

The problem is that most users mistakenly follow the if-it-ain’t-broke-don’t-fix-it mentality when it comes to their Web browsers. They use the browser that comes with their windows pre-loaded computer and, as long as this browser continues to let them to view Web pages, do not bother to upgrade it.

There are a lot of problems to this. First, it does not mean that if a browser continues to render pages then it isn't broken and that you shouldn’t fix it. The older a browser becomes, the more time there is for malicious crackers and coders to find out and exploit the browser’s weak spots. If a security weakness is found, the browser is, from that time on, considered broken in terms of security. And if you don’t  fix it, you are opening your system up to be hijacked by a lot of malwares like rootkits, spyware, adware, and viruses. If you do not believe me, try searching the Web for information on the Vundo or Virtumonde virus. You will find out how users who got infected with this nasty piece of malware are having a very difficult time removing it.

Aside from being a security concern, older browsers also hinder the progress of the Web. Web developers normally design for a broad variety of browsers for the sake of cross-platform compatibility. The presence of these aging browsers skew the lowest common denominator down. As a result, a lot of these developers cannot implement newer techniques and technologies for fear that some of their visitors might not have a capable modern browser and therefore might not be able to view the site properly or at all.

The sad part is that this problem does not have to be. Downloading modern standards-compliant browsers like Firefox, Opera, and Chrome, and installing them is so easy and free (They’re even linked here so that you wouldn’t have to search for them). It’s not like users are urged to upgrade to a newer version of Windows with which they must pay a substantial amount to do the upgrade.

But since some users just won’t take notice until something is apparently broken, some brave souls like Finn.no and digi.no are declaring war against older browsers. If users find it hard to use the sites they want to use, they might, hopefully, consider upgrading their browsers. This is for their own good and that of the Web. About time.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Friday, February 20, 2009

A Mac OS X Trial Version for the PC


The Mac is a wonderful system. It is an icon of both form and function which only a few in the hardware and software domain have ever achieved. Not only is the computer itself a real stunner, the operating system is an ideal convergence of rock-solid Unix reliability and modern-day user interface design. The seamless integration of both hardware and software is unmatched in the PC world

But for most businesses and a lot of people, crossing the bridge to Macland is a costly and uncertain venture. Long-time PC users have established habits and ways of doing things which they are not sure if doable on the new platform. This uncertainty and doubt is multiplied for businesses where there are more than one user to consider and where interoperability with the existing system is not to be taken lightly. Also, businesses typically have more established ways of doing things.

However, there is no easy way to find out what can be done on the other side of the bridge. The only way to know is to buy the Mac OS X operating system so that you can see how things are done there and how your favorite program or its Mac equivalent behaves in that environment. But the problem is, you cannot just install it on the PC that you are currently using. You need to shell out some serious cash for a Mac.

The hindrance is not a technical matter but a legal one. Macs now use the same hardware architecture and components as a PC; so, it is technically possible to run OS X on your average garden variety computer as long as it meets the minimum system requirements. But thanks to Apple’s End User License Agreement (EULA), you can only install OS X on Mac branded computers and nothing else. And they enforce this with some kind of a chip in their Macs and a team of lawyers on their payroll. You could bypass the former, but if you do, you’ll be messing up with the latter which is the last thing you’d want to do.

As a consequence, those entertaining the thought of switching to the Mac are required to take a considerable leap of faith. A lot of users are unwilling to undertake this leap blindly—and for good reason. Instead, Apple should make the transition easier by relaxing their EULA to allow users to try out even a time-limited version of OS X on their regular PCs. Users could then sample OS X’s goodies without having to spend a fortune before deciding if the Mac is really for them.

If Apple is listening, I believe that this is a great idea—an opportunity for them, even: offer a trial version of OS X so that users can see for themselves the wonders of this operating system and what it can do for their productivity before they purchase a real Mac. Apple could convert more users this way and make some headway into homes and businesses.

This technique has been successfully used by shareware programs for years and commercial programs nowadays are catching up by offering downloadable trial versions of their products. If this system benefits those selling software, then it will work all the more for Apple because they themselves said that they are in the hardware business, not in the software business. So, offering a trial version of the software should be no sweat specially if it could boost their hardware sales where the real money is made.

If Apple acts on this, the next computer on your officemate’s desk might be a Mac.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Wednesday, February 18, 2009

HTML Editors and so-called WYSIWYG HTML Editors


I have been surfing the Net since last week sampling tools which could help me create Web pages. There are quite a lot of them: some are open source, others are not but are still free, some are shareware, yet others are trial versions of their commercial siblings. These tools can be broadly categorized as either text editors, HTML editors, or WYSIWYG Page Designers.

Text Editors

Web pages happen to be plain text which just includes some markup along with the content in order for a browser to know how to display or present that content. This means that even a simple text editor can create and edit web pages.

This lowers the barrier of entry considerably—you do not need any special IDE or compiler like you would when programming. To make Web pages, you only need a text editor and a browser—both are already on your system. You can also download better alternatives at no cost other than your internet connection.

If you are still learning, this is the best way to start. You do not have to make any investment in cost and time (in learning a more powerful and hence, complicated software). Also, you get to focus on how to cut the grass rather than how to operate your XD2000+ lawnmower.

A few sample of text editors are:

HTML Editors

These are more specialized text editors. They are still technically text editors but have functions that make creating Web pages faster and easier. Some of these HTML editors are souped up text editors while others are designed to be HTML editors from the start.

These tools are better suited to those who already know their code and need something to up their productivity. They already know the doctype declaration like the back of their hand and could type in the xmlns attribute and other meta elements even while asleep. So, they’d rather let the software automate those mundane task. These tools are like calculators which should not be used while still learning your arithmetic but should be resorted to later when you need to focus on the finer points of differential equations.

Here are some advanced text editors which can double-duty as HTML editors:

And here are some of the more dedicated ones:

WYSIWYG Page Designers

You will have better luck searching the Web if you search for WYSIWYG HTML Editors rather than WYSIWYG Page Designers. But I believe that the latter is the more accurate term.

WYSIWYG Page Designers let you compose using colors, layouts, fonts, and graphics. It then generates the CSS and HTML or XHTML code for you. This makes complex designs and layouts a little easier.

However, there is a downside to this. Since the software generates the code instead of you, and since we already know that computers are crappy most of the time when it comes to making complex decisions, some generated code leaves much to be desired. This is more so when the complex decision is creative in nature.

This resulted in a division among the Web design and development community. The designer/ artistic types mostly prefer WYSIWYG Page Designers while the development/ programmer types mostly prefer HTML editors. The battle cry of the former is productivity and efficiency while that of the latter is elegance and correctness.

In my side of the fence, I do not think that you should be one or the other. Why not have the best of both worlds? You can always start designing things visually with a WYSIWYG Page Designer and then tidy things up with an HTML editor. Or, if your page can be neatly divided into more visual and less visual parts, you can design the former with a WYSIWYG Page Designer and the latter with an HTML editor.

The big players in this category are Adobe and Microsoft with their Dreamweaver and Expression Web applications. But there are also simpler and cheaper ones:

A Word About WYSIWYG HTML Editors

A WYSIWYG HTML Editor is somewhat of a misnomer. It can even be considered an oxymoron or a contradiction of terminology. Technically, there is no WYSIWYG HTML editor. What an HTML editor does is edit HTML code in the same manner that a text editor edits text. The HTML code you write in an HTML Editor is composed of text and markup (and that’s what you see); what you get in the browser are images and nicely formatted text with different colors and a layout so different from that of the source document. What you see, therefore, will not be what you will get.

So, if there are no WYSIWYG HTML editors or HTML editors that are WYSIWYG, what do we call those software being referred to as such? First, let us see what they do. They let you design the look and layout of the page visually, add some graphics and then generate the HTML or XHTML code and the stylesheet. Based on that, it would be more fitting to call them WYSIWYG Page Designers because (hopefully) the design and layout you made will be the same as that displayed in the viewer’s browser.

Creating Web pages has become more involved nowadays compared to how it has been in the past. Fortunately, the tools we use to develop them have also improved and have become more available. We only need to choose the right one in these embarrassment of riches.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Monday, February 16, 2009

Offline Post Editors / Blog Clients: The Final Showdown


I made individual reviews of Deepest Sender and ScribeFire as these post editors are of a different breed—they are application extensions. Semagic is also different because while it can post to a variety of blog platforms, it leans more toward LiveJournal journals rather than blogs.

Bleezer and the other editors I looked at, though, have a larger set of common features. So here, we will tackle them together and will be looking only at their differences and their unique features. Common editing functions such as bold, italics and underline, and html functions such as adding lists and quotes, are presumed available unless otherwise specified.

For the sake of completeness, previously reviewed post editors will also be given some space here.

Deepest Sender

Deepest Sender is a lightweight Firefox extension which might be enough for most bloggers using LiveJournal or Wordpress. I can’t make it connect to Blogger, though. So if you are using Blogger, you might want to pass this up until the issue is resolved or you know some arcane connection settings for this post editor.

But if it can connect to your blog platform, then Deepest Sender is worth a try. It has a small footprint and allows you to blog about a page you happen land while surfing. Spell checking is provided via Firefox 3 or Firefox extension. It also allows you to enter CSS Statements which you can use to mimic the look of your blog and thereby achieve some degree of WYSIWYG capability.

ScribeFire

This one has surprising WYSIWYG capability for a small application which runs on Firefox. When you click on preview, it asks you if you’d like it to download your blog’s theme. If you click yes, it would make a temporary post just to download your blog’s theme and immediately delete the post after the download. The downloaded theme is then used when you preview again. As this is the same theme used in your blog, it achieves a high degree of WYSIWYG functionality.

With ScribeFire, you can easily promote your blog. It allows you to notify about nine social bookmarking sites right from the post editor.

It is also possible to insert ads in your posts using ScribeFire’s own ads system. To use this, you first have to register to ScribeFire Quick Ads. Quick Ads is like an ads middleman. Using Quick Ads, you can serve ads from networks like AdSense, Kontera, IntelliTXT and others without having to deal with each one of them.

Semagic

Unlike the previous two, Semagic is a stand-alone offline blog client which does not need Firefox in order for it to run. But instead of automatically downloading your blog’s template like what ScribeFire does, it only allows you to specify a local template file. This file may be one of those included with the application or one you make on your own. The former, obviously, won’t be similar to your blog’s template; so, you won’t be achieving WYSIWYG functionality using them. You have to make your own which mimics your blog’s template.

This editor, however, has a distinctive LiveJournal flavor to it. That may or may not be a problem depending on whether you post to LiveJournal or not. If you do, then it’s a feature; if you don’t, then it’s a distraction.

Bleezer

I still haven’t figured out how to make it connect to Blogger; but if you use other platforms, then that may not be a problem at all. If you want a simple and easy to use post editor and do not use Firefox or don’t care about Firefox extensions, then Bleezer would seem to be a good match. Just remember that it does not allow you to specify templates. So, WYSIWYG functionality is not one of its strong points.

However, it can be argued that when it comes to the Web in general and to blogging in particular, there is no true WYSIWYG editors. Your readers could easily resize and shrink their browser windows or change their browser’s background color, font style, font face and font color, among other things. If they do, your efforts at WYSIWYG goes down the drain. This is not even counting the fact that some readers might be using old or non-compliant browsers which would probably display your page incorrectly, if at all. And if they use Lynx, good luck with that.

BlogDesk

BlogDesk is also a clean and simple offline blog client/post editor which currently does not support Blogger. It also has the usual spelling, editing and HTML features. Like Bleezer, you don’t need a manual to use this editor. The buttons and menu options are easily recognizable. Nothing gets in the way between you and your first post with this editor—unless you use Blogger.

Post2Blog

Post2Blog has features and buttons galore! In addition to the usual spell checker, it has the ability to look words up in a thesaurus. It can also clean MS Word HTML if you happen to use word formatted documents. It is also possible to export posts to pdf.

If you are the kind who likes to add smiles to your post, then you’re going to have fun with this editor. Uploading photos to your Flickr account can also be done as with ScribeFire.

For those interested in HTML source editing, Post2Blog has a decent HTML editor and allows more HTML tags to be added with a click of a button. You can instantly add snippets and insert HTML from a file or in a dialog box. These are handy if you frequently use the same blocks of HTML code. The editor can be set to generate either XHTML or HTML code.

The problem I have with this editor is that it does not show the titles of my posts when I try to retrieve them. Instead of the title, “<no subject>” appears. But it displays the body ok. I also cannot find the option to add templates for WYSIWYG preview. But if you are not bothered by this and want a feature rich editor, then this is a nice candidate.

w.bloggar

w.bloggar, like Post2Blog, is a very nice post editor (for those like me who like to tweak html). In fact, w.bloggar only lets you compose in HTML view unlike other editors which let you compose in Compose view and tweak in HTML view. However, w.bloggar makes HTML editing easy. You can easily insert tags with a click of a button. It is also possible to define your own tags and named entities.

HTML Editing seems to be the strength of this post editor. You can design web pages with this post editor better than with text editors without HTML extensions. It would even seem like w.bloggar is an HTML editor with the added feature of being able to post to your blog.

But like Post2Blog, it does not display post titles properly. It displays a string of numbers for a post’s title. Its download template function won’t work if your Blogger blog uses layouts. So if your blog uses Blogger layouts, you won’t have WYSIWYG.

Qumana

I actually do not know why but the user interface of Qumana is quite refreshing. It is as clean and elegant as BlogDesk and Bleezer but works with my Blogger blog. It may not be as feature rich as Post2Blog or w.bloggar but it displays my post titles properly.

Qumana also has its own Ad Network called QAds. After registering with QAds, you can easily add ads to your posts using Qumana.

Unfortunately, I don’t see any support for templates so those interested in WYSIWYG might not be pleased.

Zoundry Raven

Zoundry Raven is one of the best offline post editor / blog client for me. For direct html editing, it is the best. End of story. If it could only save in HTML, I could use this as an HTML editor. For general posting, it comes second only to Windows Live Writer. But since it has just been released as Open Source, it could improve rapidly in the near future.

Raven has the HTML editing power of w.bloggar and the simplicity of Qumana. Like Qumana, its interface is clean and unobtrusive but has more power under the hood. Like w.bloggar, it edits HTML like there’s no tomorrow complete with tag and attribute completion (Ctrl+Spacebar)! In addition, it reads my post titles properly.

As to WYSIWYG functionality, it supports downloading of your Blogger template if you tell it to. So, your preview would look just like what it would on your blog.

Windows Live Writer

Windows Live Writer is what I am currently using right now. It has one feature I really, really like—word count. No other post editor that I have tried included this feature. Also, I do not have to do anything to display the word count—its already there in the status bar. All I have to do is look down a little bit and the number is there (you have to set it in Options|Editing first).

Another plus for Windows Live Writer is plug-ins. This makes it easy to extend Writer. You can find all sorts of plug-ins in Writer’s plug-ins page which you can then plug in Writer. But one plug-in that I find hard to be without is the Dynamic Template plug-in by Joe Cheng. It lets me add HTML tags not provided by Writer such as cite, quote, and keyboard tags. You can also use C# statements. With this capability, you can make your own plug-in in a plug-in.

Like Raven, it has good WYSIWYG functionality. It downloads your blog’s template and uses it for previewing. Its image handling and manipulation is superb. You can do a lot of things to images which you normally need an external image editor for.

A Word About Images

If you insert images in your post from the internet, almost all post editors will have no problems with that. If the image resides locally in your computer, however, the ride starts to get a little bumpy.

If you use Blogger’s online post editor and insert an image residing in your hard disk, Blogger uploads the image to their servers and inserts it to your post. If you use an offline post editor, it won’t get uploaded to Blogger’s servers so it has to be hosted somewhere else for you to be able to link to it.

I did not discuss this in the individual post editor reviews as this is not a post editor problem. Blogger simply does not allow it. For a lot of post editors, the only solution would be to upload the images first to an image hosting service provider like Picasa or Flickr then to link to it.

Raven and Writer have a way around this though. You can configure both to automatically upload the image somewhere else like in Flickr, Picasa, or ImageShack.us and then link to it.

While using offline post editors would require additional steps when it comes to inserting images to your posts, it still beats using Blogger’s online post editor. Editing and formatting text with offline post editors are still more flexible and convenient that I am willing to take the additional steps to insert the occasional image. Moreover, it is really not that difficult after you have tried it even just once.

Conclusion

Since I use Blogger, three of the post editors mentioned here are automatically off the list for being unable to connect to my blog. Semagic is too LiveJournal for my taste while w.bloggar and Post2Blog have problems with post titles. That leaves me with ScribeFire, Qumana, Zoundry Raven and Windows Live Writer. Since I need something more than what the first two can provide such as good HTML editing support and image uploading, I settled with Writer and Raven and use one or the other depending on the mood.

Others might want something simpler so the first two might be a better choice. ScribeFire also has good blog template support and WYSIWYG capability while Qumana is simple, clean and elegant.

Those using Wordpress have a wider array of choices. For example, w.bloggar and Post2Blog might not have problems with titles in their particular platform. But I still think that they should consider the four that work well with Blogger for maximum flexibility and compatibility.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Friday, February 13, 2009

A Quick Look at Bleezer


If you are using Blogger like I do, then we’re out of luck. I cannot make Bleezer work with my Blogger blog. Unfortunately, the latest entry in its website was made last July 1, 2007. This could mean that Bleezer is not being actively developed at the moment and that we cannot expect a fix any time soon.

But I read reports while surfing the Web that this post editor works with Wordpress.com and, presumably, with Wordpress.org. If you use one of those platforms, read on; I’ll share to you what little I could with this software.

You can do the usual formatting commands using the toolbar buttons such as bold, italics, underline and strikethrough. For most, this is all they’ll ever need. The markup code that is generated by the editor are mostly presentational and not structural. Instead of of marking up text with the <strong> tag, for example, it uses <b> which is less than ideal. But if you are not a stickler with standards, that shouldn’t be a problem.

In addition to the common formatting commands, you can also add blockquotes, lists, links and images. Image handling, however, is simple. For blogs, where you really don’t need extensive image editing, this is not a show stopper. Most images that you insert are already edited, anyway. Adding headings is a manual affair. You have to go to html view and add heading tags there yourself because the compose view does not provide automatic formatting of headings. Alternatively, you can just select the heading and format it as a different font and increase its size. That should also do the trick.

It has a built in spell checker which is nice. I really believe that this functionality should be present in all offline post editors or blog clients anyway. I’d rather have an editor which does not have common formatting functionality rather than one without a spell check capability. It is better to memorize the markups used for common formatting and add them manually than to memorize all the commonly (and the not-so-commonly) misspelled words and manually hunt for them in a 600-word post. If you encounter one without a spell checker, dump it immediately. There are better editors out there.

The WYSIWYG functionality would have been better if it lets you specify a style which would allow you to mimic your blog’s template just like what Deepest Sender does. This post editor is not WYSIWYG in a way that the word is commonly understood. However, WYSIWYG is all relative. It could display faithfully to one browser but not to another. So in a strict sense, there really is no true WYSIWYG post editor as there are always different browsers which always displays things differently.

In sum, if you use Wordpress and want a simple and uncluttered offline post editor, Bleezer could serve you well. It is also a good option if you want a simple editor but don’t want Deepest Sender or ScribeFire because you don’t (or won’t) use Firefox for one reason or another (like if you use Opera or Chrome). Finally, with Bleezer, you do not need to wade through pages of a manual in order to publish your first post. The user interface is your manual.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Wednesday, February 11, 2009

A Quick Look at Semagic


Semagic 1.7.3.3U is the first stand-alone client I have reviewed so far. Unlike Deepest Sender and ScribeFire, this is not a Firefox extension. But similar to Deepest Sender, though in a much greater degree, Semagic has a LiveJournal flavor to it. It leans more towards posting to a journal than to a blog.

But if you can get over the fact that your blog is called a journal and your post title, a subject, then Semagic could work for you. I was able to post to my blogger blog and then edit that post using Semagic. Deepest Sender did not even allow me to post.

Looking at the toolbar tells us that the usual suspects are there. You can do common formatting tasks and add links and images. It also has a built-in spell checker called MySpell though you have the option of using MS Word’s spell checker instead. A nice thing about its WYSIWYG formatting is that it generates structural markups like emphasis tags instead of the presentational markups like italics and bold tags.

In addition, it has LiveJournal specific features like the ability to view your friends list and detect the music you are currently playing. I really do not know much about these features as I don’t have a LiveJournal account but for those of you who are interested, you can give this a try.

As to its WYSIWYG capability, it does allow you to specify a separate file as your template which will then be the presentational basis of your post when you preview it. Since it does not automatically download the blog’s template, I tried downloading it myself and specified the local file as my template in Semagic’s setting. Semagic, however, cannot read it.

So, you either have to make your own template or modify the one provided by default. If you just want to set your blog’s width in Semagic so that images and text wrap in the editor just like they would in your blog, then you could just use the width CSS property with a value of 400px and enclose the whole thing in a body selector like so:

body {width:400px;}

If you remember, this was the work-around we used with Deepest Sender. But this will not make the font style, size and color similar to that in your blog. You still have to add those properties.

Is Semagic WYSIWYG? It certainly is, but only with respect to the current template it is using. Most current WYSIWYG editors work in a similar way—using local templates. Some just download the template transparently in the background while others let you do the downloading or the creation of the templates. Without templates, no post editor could determine how your blog is set to display your posts.

If you don’t mind the slight emphasis on LiveJournal, then Semagic is worth a try. However, you have to work a little harder to make its preview look as close to your blog as possible. This would be a good software for someone who posts in both LiveJournal and Blogger.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Monday, February 9, 2009

A Quick Look at ScribeFire


Like Deepest Sender, which I reviewed in a previous post, ScribeFire is also an offline post editor or a desktop blog client which is installed as a Firefox extension. This means that you must have Firefox to run it. That should not be a problem because you should be using Firefox anyway.

You can start ScribeFire by:

  • Pressing F8
  • Clicking on the ScribeFire icon in the status bar
  • Selecting ScribeFire from the Firefox Tools menu
  • Right-clicking on any web page you want to blog about and selecting "Blog this page" from the ScribeFire submenu
  • Adding a ScribeFire button to your toolbar and clicking it.

A quick glance at the array of buttons on the toolbar would show you the main editing features of ScribeFire. You can, for instance, bold, italicize, and underline text by selecting it and clicking on the appropriate button. You can also apply strikethrough effects and emphasis, increase or decrease text sizes, and add links, images and video. It also has lists, justification, and blockquote tags.

The second row of toolbar contains special characters. This scrolls horizontally if you hover your cursor over the right and left arrows. Once you find the symbol you wish to insert, just click on it and it gets inserted in your document on the current cursor location.

What I like about ScribeFire’s editing features is that you can tell it to use CSS for content style in the options or settings mode. What this does is make the WYSIWYG editor generate more standards compliant code. For example, if you select text and click the italics button, it italicizes the text using CSS instead of using the presentational italics element (<i>).

Misspellings will be brought to your attention by red-dotted lines underneath the offending words. I do not know if this spell checking capability is provided by ScribeFire or by Firefox 3 but it doesn’t matter because if it is not provided by ScribeFire and you have an earlier version of Firefox, you can always download a spell checker extension.

On the right pane of the program’s interface, you will find more options for your blog or post.

The first tab is labeled Blogs. Here, you can see a list of your blogs ScribeFire can publish to, and options for adding, editing and deleting blogs. The next tab contains a list of the titles of the posts in the currently selected blog. The Categories tab contains all the labels or categories you have used in your blog. This makes it easier to add labels to new posts and to add new labels. The last tag is where you can set the time and date stamp of your post and include Technorati and Delicious tags if you so desire.

Now to the fun part. This post editor has good WYSIWYG functionality. If you click the preview button at the bottom or select the preview tab on top of the editing area, it downloads the template from your blog and uses it. As a result, you would see how your post, including images, would look on your blog.

While the dialog box above informs you that it is going to make a temporary post to your blog, it will only do so to enable it to download your template. It immediately deletes the temporary post after the template has been downloaded and even before you leave preview. It does not preview your post by posting it to your blog and viewing it there. I tried this and went to my blog; the previewed post is not there. So no need to worry that your unfinished post will be public when you preview it using ScribeFire.

A nice addition, though I have not tried it yet, is the ability to insert ads to your posts using ScribeFire’s own ads system. To use this, you first have to register to ScribeFire Quick Ads. Quick Ads is like an ads middleman. Using Quick Ads, you can serve ads from networks like AdSense, Kontera, IntelliTXT and others without having to deal with each one of them.

You can also promote your blog easily with ScribeFire. Click on any or all of the buttons in the Share This Page mode and you’re good to go.

What I don’t like with this editor is that it does not automatically generate paragraph tags when you press the Enter key. It also does not have buttons or commands to let you add them yourself. The same goes with headings. While there is a provision for adding custom HTML tags, it does not let you save what you just added so you have to do it all over again every time you need to insert another heading or a paragraph tag. It is easier just going into code view and placing the tags yourself with copy and paste. However, this is not a problem if you do not care what code is generated as long as the final layout looks right.

At the time of this post’s writing, Deepest Sender and ScribeFire are the only offline post editors that I know of which runs as extensions of Firefox. And between the two, ScribeFire wins hands-down. It is more feature rich than Deepest Sender and can actually connect to my Blogger blog. It also has a better interface. With the “blog this” functionality, it is so easy to blog about pages you read as you surf the web. The very small file size and quick download makes this a must-try post editor.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Friday, February 6, 2009

Making the World Wide Web a Gigantic Database of Useful Information


Sir Isaac Newton once said: If I have seen farther than others, it is because I was standing on the shoulder of giants.

With all the information now available in the Internet particularly in the World Wide Web, imagine how much farther we can see if we can stand on its shoulders. It contains every conceivable topic in the world. There is probably no subject which is not published somewhere in the vast cloud that is the Web. If we could only access all of those information, progress in every avenue and endeavor is not far. The Web is truly a giant of an information source.

The user’s desire to retrieve information from the Web can be shown in Google’s rise to fame. When it first started, Google provided nothing much other than the ability to search the Web for pure information unadulterated with advertising which the users were not getting from the search engines of that time. The fact that Google not only survived but thrived is a sure indicator of the user’s need to access information.

But even Google could not search and index all of the pages of information in the Web. The unstructured nature of documents make information retrieval difficult. If the the World Wide Web were a database, it is one where a lot of data cannot be accessed. Those inaccessible data are a waste. Unlike discrete data like names and dates which can easily be stored in a data field, pages of posts and articles do not lend themselves to be stored and retrieved as easily. The answer to this is structural markup like XML.

Modern web standards have been developed to address this situation. HTML 4.01, for example, is a W3C recommendation which is based on SGML. XHTML 1.1, based on XML, is also another step in the right direction. These standards, particularly the XML based XHTML 1.1 and the soon to come XHTML 2, would greatly aid in making the Web an easily searchable index of information.

The problem is that these standards are just that—standards. Browsers and web designers can and do ignore them. Even with these modern standards which has the potential of organizing the information on the Web, designers still cling to the old ways.

One of the reasons why this is so is Internet Explorer. Quite a lot of users use it; not by choice, but because it comes with their Microsoft Windows installation. The problem is that this browser does not recognize proper XHTML. This leaves web designers no choice but to serve XHTML in a way it was not designed to be thereby negating a lot of the benefits XHTML has to offer. If they did not do so, a lot of their IE equipped viewers might not be able to view their pages properly or at all.

This hinders progress in the Web which affects everybody to the point that even IE’s competitor, Mozilla (the maker of Firefox), is willing to go the extra mile to make IE standards compliant if it cannot do so on its own. Here’s a portion of a story I found in Ars Technica through Wisdump.com:

Most browser implementors are quick to adopt emerging Internet technologies, but Microsoft can't or won't make Internet Explorer a modern web browser. Despite some positive steps in the right direction, Internet Explorer still lacks many important features. Its mediocrity has arguably hampered the evolution of the web and forced many site designers to depend on suboptimal proprietary solutions.

IE's shortcomings won't hold back the Internet for much longer, however, because Mozilla plans to drag IE into the next generation of open web technologies without Microsoft's help. One of the first steps towards achieving this goal is a new experimental plugin that adapts Mozilla's implementation of the HTML5 Canvas element so that it can be used in Internet Explorer.

I heard that the latest incarnation of IE which is IE 8 (still in beta at the moment) will be more standards compliant than the current IE 7. I don’t know if this includes proper XML support. If it does, then the Web just might be the information database I hope it would be. As of the moment, the most standards compliant browser is Firefox which you can download by clicking here. Aside from standards compliance, this browser also offers more for the Web users which you can read about in the following links:

Hopefully, if everybody could pull their acts together and put the common good in the forefront instead of their own proprietary interests, designers and content authors would not have to live with those limitations and the power of the Web could be fully utilized for the benefit of all.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Wednesday, February 4, 2009

The Benefits of Supporting Free and Open Source Software and Why You Should Do It


First of all, I am not a so-called “fanboi”. The purpose of making this post is not because I feel that bashing proprietary software companies is the best thing to do in my spare time. On the contrary, I like a lot of proprietary products. This post, for instance, is made with the latest release of Windows Live Writer (which is a great software, by the way) running on Windows XP. Their keyboards are also superb.

However, there are a lot of benefits in using Free and Open Source Software, which I will call FOSS from here on. Cost is clearly one of them. But there are other subtle and less obvious but more important benefits.

One quality of FOSS is that its innards are open to view and inspection. This means that if ever an error occurs, it could be resolved by the user himself without relying on the publisher since the code or the gears that make the software tick is accessible.

Not technically inclined nor capable? No problem. There are a lot of other users in Internetville who eat code for breakfast. Fixes made by these folks are available to all of us and thus, benefits all including the technically challenged among us. In short, availability and accessibility of the code benefits you even if you, on your own, cannot code yourself out of a paper bag.

Malwares like trojans and adwares are some of the risks of living an online life. Any malicious programmer could create malware and distribute it on the internet. If you download a free program (a free program is not always Open Source though most Open Source programs are free) how would you know that it won’t do anything malicious? Even with established proprietary programs, how could you be so sure that it is not spying on your spending or surfing habits? FOSS on the other hand, cannot contain malicious code as that would be visible to users.

Those are great benefits but like what the tv commercial says: wait, there’s more! FOSS catalyzes software improvement. Imagine, for a moment, that the text editor has not been invented yet and Jane needs one. Because of the unavailability, Jane wrote her own text editor and released it as FOSS.

If another user, Jill, also needs a text editor but with a spell check capability, she does not need to make her own text editor with spell check functionality. She can just take Jane’s code and add the new functionality and maybe also improve on some of Jane’s original code. Now, if Jesse also wants a text editor with syntax highlighting, she again do not have to start from scratch.

The result of all these is faster development and better debugging or error correction. Errors in Jane’s original code could be corrected by Jill; and if any slips further, Jesse would handle it. Imagine if you increase the scale.

The FOSS development method enables FOSS to improve at a very fast rate. But supporting FOSS has another beneficial side effect—ironically, it also improves proprietary software. A software publisher is certain to burn the midnight oil to stay a step ahead of FOSS; otherwise, how could they justify the price? In this situation, the users win. Therefore, even if you are a Dreamweaver user, it still makes sense to support N|vu or KompoZer by contributing code templates, for instance.

For these reasons, I urge you to support FOSS even if just by using them. A large user base could certainly help. If you need software, try to look at Open Source alternatives first. You might be delightfully surprised that it is all you need.

Those who cannot afford proprietary software like Photoshop, for example, should refrain from using pirated and cracked versions of the software. Use the GIMP instead. You will be both helping FOSS and avoiding trouble. Even for those who can afford it, there’s no point in shelling out $665 for Photoshop if the GIMP could serve your needs at zero cost. I know that Photoshop has more features than the GIMP; but the latter, specially with the plug-ins available for it, also offers a lot and not every Photoshop user needs all of the features found in Photoshop. So, you might as well use the GIMP, donate to the project a tiny fraction of the price Adobe asks for Photoshop, and save the rest. You will be an agent of change and improvement along the way.

But of course, I am not saying that you should use FOSS to the exclusion of proprietary software even if it does not serve your needs; otherwise, I am no better than a fanboi. It should still be “the right tool for the job”. What I merely want to do is to empower users and inform those who still do not know that they have a choice.

Do I want FOSS to take over the world? No, Not really, but I would like a world with software that are cheap, are free from bugs and do what I needed them to do—nothing more, nothing less. FOSS can bring us there.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Monday, February 2, 2009

Types of WYSIWYG Blog Editors


Someone left a comment in my previous blog post and related a problem his wife is having over the WYSIWYG functionality of her blog post editor. An image with some text wrapped around it looks one way in her blog editor and another way in her blog. In short, what she had seen (in her blog editor) was not what she got in her blog.

I have never thought of that problem before. When I draft my posts, I already know the width of my blog’s post area; so, I would not insert any image wider than that. For wider images, I would crop or resize them first or use the height and width attributes of the image element. As to text wrapping, I only do it when the image width is less than or equal to half the width of my blog’s post area.

But users should not be forced to know these things and the comment reminded me of that. Working so long as a techie made me forget how normal people use software. Software should serve people and not the other way around. It was a refreshing eye opener and all software developers should receive comments of that sort and pay attention to it.

And looking at the current crop of blog editors, it would seem like developers are paying attention and are trying to address the issue as best as they could. I found out, based on looking at the post editors I have downloaded, that they address it using three main approaches:

  1. The blog editor allows you to specify a local stylesheet or to enter style definitions or properties, which mimic the style of your blog, in the editor itself;
  2. It publishes your post every time you hit preview and displays your blog in a browser then deletes the post afterwards; and,
  3. It downloads your blog’s template once and uses it locally every time you do a preview.

The first way for a blog client or post editor to have some recognizable form of WYSIWYG functionality is to allow the user to specify a file in her computer containing CSS statements or properties. It could also allow the user to enter CSS style properties directly in the editor itself. The editor then uses this information to display the contents in the preview window every time the user tries to preview. This is good—but only if you know CSS in the first place. Also, you need to know the particular properties used in your blog and their corresponding values; otherwise, this is good exercise of guesswork.

The second method I have seen post editors do is to instantly publish your unfinished post. Let us say that you’d  like to preview your post while still halfway through it. Everything you have written up to that point will be published “temporarily” to your blog. Your blog is then loaded in a browser and you see your post in it. After you close the preview pane or window, that post is deleted from your blog.

It could be argued that this is the most accurate method because what you see in preview is your actual blog so that is really what you’ll get. One problem I have with this, though, is that you might forget to close the preview window and leave it open for a long time. Your unfinished post is public during that time and visitors might be able to see it dangling in your blog. So, if you use this type of post editor, close the preview window first before you answer that phone!

The final method is the one I like most. The post editor downloads your blog’s template during setup or configuration and uses it offline to preview your post. What is displayed during preview is not the real blog like in the previous case but it’s close enough. For layout purposes, this should be sufficient—and safer.

So far, these are the methods used by post editors to give you WYSIWYG functionality that I know of. Each have their own set of advantages and disadvantages. Knowing them helps you decide the best one for you and avoid potential pitfalls.

Stumble Upon Toolbar Add to Technorati Favorites Delicious Add to Mixx!

Posts You Might Be Interested In