 |
|
|
 |
Everyone's been lovey dovey over the new WYSIWYG editor (JfZ, future, forum guide, hacks) While I, despite my initial "enthusiasm", still think that it has lots of problem room for improvement.
The WYSIWYG editor is at the very core, the most important feature on Blogdrive. Without it... you would be wondering how a blog host can ever be a blog host. And we really don't expect writers to be able to write properly, right?
1)  Insert Link opens a new window? This has to be the most annoying small problem. Everytime I need to insert a link, I'll need to wait till the new window loads before I can do anything else. This is a pain especially on MSIE because it takes a long time for MSIE to open a new window. Blogdrive should really just reduce to using a "prompt" javascript function to do the magic. It's less complicated and faster. Not to mention no new HTTPrequest to the Blogdrive server while editing.
Another problem is that it'll not work if the text you highlighted contains an apostrophy ' or ' . For example if you write: "Seige's dog", and wanting to add a link to these words, it'll not copy the "Seige's dog" to the window. This is a Javascript bug.
2) Different browser syntax rendering - on Firefox it's "XHTML Transitional" while on MSIE it's "plain old HTML" with CAPITALS. You can notice the differences if you use the "HTML View" feature located at the right bottom of the editor. It's odd although
3) Up Down Left Right button doesn't work sometimes - can't move the focus of the text cursor basically but the weird thing about this is... it only happen sometimes. And as for me, I can't identify what is the source of this problem.
4) In HTML View, the text cursor isn't always where it should be - more often than not it appears to be one or two characters away. How and why this happens is a mystery. It usually happens when I have a long entry that I needed to edit. It has something to do with miscalculating the string lengths or something along those lines.
5)   Undo/Redo doesn't work sometimes - Again, this is odd and I can't tell why it doesn't work. It happens to both Firefox and MSIE.
6)   Outdent/Indent uses different elements sometimes - I would really prefer the editor to implement the <BLOCKQUOTE> elements, it works great on MSIE but on Firefox, it uses <div> with margins set to indent it... how cruel.
7) Save post to clip board works on MSIE only - it doesn't work on Firefox mainly because Firefox is stupid for not supporting the copy-to-clipboard function. Sadly.
8) Firefox browser crash when reloading editor sometimes - Again, this is another one of the "sometimes" problem. It's just weird and I just can't make it out why. Don't take me wrong that it could be other webpages I'm viewing because the window crashed a few times and it's always during reloading of the editor in Firefox.
9) Can't insert Scripts or Objects - That's due to security reasons but for someone like me who do need to use some Javascripts, it's  . Though... I shouldn't fret because I still have the beloved PTE.
10) Help Guide is coming soon ever since the big bang - See that "?" up there on the top right hand corner? Ever clicked on it, No? Don't bother.
I somehow realise that all these problems have almost everything to do with browser inconsistencies. Still I don't see why an editor should be flawed just because of certain browser not working perfectly well.
Wondering if Blogdrive will ever be bothered to fix these minor things? Nah, never. Not in a century or two.
Ever since Blogdrive fixed the PTE, it has so far been a million times better than WYSIWYG editor. Although it doesn't mean it's all great (because it doesn't work all well in Firefox/Opera), it's still better than WYSIWYG editor.
Tags: Blogdrive, WYSIWYG, Plain Text Editor, PTE, Editor,
Firefox appears to be one of the "better" browser with additional features and allows installation of Plugins. I love using it and it's my prefered browser for many reason, mainly due to it's tabs ability. Allowing me to open several window at the same time.
I don't use Opera much despite it's amazing ability in memory management. It lacks many basic feature a web-browser should have.
MSIE, the most commonly used browser, is still the BEST browser around. It's more stable and have better support for most website on the internet. I don't use it only because it doesn't support tabs.
So, that leaves Firefox. Although it's my most prefered web browser, I HATE It.
There's so many thing wrong with it, it can't find or search within textareas. It takes a long time to start up. It always have problem with memory management (crash easily). And it CRASH anytime it feels like it.
Worst of all, it always crash when I'm trying to load Blogdrive's WYSIWYG Entry Editor. WTF?
it's nothing wrong with Blogdrive's Editor, rather it's firefox not being able to support the complexity of Blogdrive' s editor.
Damn you FIREFOX! Would you for once, not crash at all?
Tags: Firefox, Blogdrive, WYSIWYG, browser,
One of the thing I dislike most about Firefox is the inability to use the find function within textareas. This is very annoying when it comes to editing php/js codes or templates which have very lengthy and complicated structures.
The Find (Ctrl+F) is especially useful to skim through a large number of words to get to the specific terms easily. I use it all the time either surfing, reading, or coding.
So, a little search on google I found this:
http://www.geektronica.com/2005-11-10-firefox-find-doesnt-work-in-textareas
http://www.liewcf.com/blog/archives/2004/10/firefox-pr10-cannot-search-in-textarea/
https://bugzilla.mozilla.org/show_bug.cgi?id=252371 (official bug report)
So (again) why isn't it implemented? Are they disabled on purposed for some sort of security reasons? Or is it just like what the other guy said that they just haven't fixed it?
It's really annoying when I can't get things done due to limitations. And it have a very serious performance hit. The only way I can get this done is to "View Source" and find through the source code. It doesn't work all the time especially when it comes to situations with escape HTML tags such as <(<) >(>) "(")
Does anybody know if there's a fix / greasemonkey-hack / firefox-extension
that I can download?
Tags: Firefox, Find, Textarea, Search, View Source,
Instead of moaning of the problem over and over again, Xr decided to write up a GreaseMonkey fixer for the BlogDrive PTE Posting Dates problem. Greasemonkey is a Firefox extension which lets you to add bits of DHTML ("user scripts") to any web page to change its behavior. If you uses Firefox and have the Greasemonkey installed on your computer, You may use this tool. Download the script here. Below are the details, note the explanation: Blogdrives gives the time based on configured timezone. However, when creating a new entry, "Current" doesn't mean anything. In those cases, the hours are set to local time. Think about it if the machine from which you edit your blog is not set to the same timezone as your blog. // Blogdrive PTE Fixer v 0.2.2
// Copyright (c) 2006, Xr
// Released under the GPL license
// http://www.gnu.org/copyleft/gpl.html
//
// This is a Greasemonkey script. if you don't have GM, go to
// http://greasemonkey.mozdev.org/
// GM is an extension for Firefox (http://www.mozilla.com/firefox/)
//
// Known bugs :
// - Blogdrives gives the time based on configured timezone. However, when
// creating a new entry, "Current" doesn't mean anything. In those cases,
// the hours are set to local time. Think about it if the machine from which
// you edit your blog is not set to the same timezone as your blog.
//
// Version history :
// 0.2.2 : Fixed date systm where "09" would be interpreted as octal
// Fixed date showing GMT instead of local time.
// 0.2.1 : Title is not lost anymore
// 0.2 : Moved to a better way of getting input field, fields are now selected
// depending on posted date / current date
// 0.1 : Initial script
//
//
// ==UserScript==
// @name Blogdrive PTE Fixer
// @description Allows Plain Text Editor to correctly edit dates
// @namespace http://xr.i-jeuxvideo.com/?cat_id=progs
// @include http://www.blogdrive.com/manage/blog_entries*
// ==/UserScript==
// Get the invalid <input> field. I have not tested it, but looking through the codes it appears to be doing it right since it's well organised and written. Try it out if you uses Greasemonkey. References: Plain Text Editor (PTE) bugs and issues, Dates of Edited Posts, Can't Change My 'Publish Date', BlogDrive PTE Fixer, Greasemonkey,
Tags: BlogDrive, WYSIWYG, Editor, Firefox, Greasemonkey,
|
 |
 |
 |
|
 |
|
|
|
|
 |
