night maple in eikando, originally uploaded by lazy fri13th.

autumn in kyoto is very special. it becomes the most beautiful place in japan. if you haven’t experienced it, i strongly recommend.

there’s a big bug in Firefox 2.0. sage’s short cut is duplicated with bookmark shortcut. very uncomfortable. so i searched some brand-new rss service and found some cool site. http://hanrss.com

this site is basically for korean people. it looks very simple and unlike other korean site requires only email address. in that reason, i decide to replace sage with this site. google and other web-based readers are not designed for large amount of rss. they messed up rss contents. i don’t really understand who wants ad-style or fragmented informations?

i think web 2.0 sites in korea will go their own ways and doing somthing cool, sooner or later. korean infra of web is very strong. you guys in the other side of world would probably be surprised.

jdbm v1.0, the simple java text-based database has some critical bugs(though developers of jdbm don’t think so) the file size of db is not reduced when deleting or removing entries. it’s growing only. i know it’s not an easy job to implement delete function in B+tree, but it’s a very critical issue. why they notice it to everyone? making another db file is only a solution, now a day. you must be careful when you choose jdbm as your main db. though i know this bug, i choose to use this db. there’s no better solutions in java world, as far as i know.

these useful articles came from ie7 developer’s blog.. there’s something immediately usable..

http://blogs.msdn.com/ie/archive/2006/08/28/728654.aspx
http://blogs.msdn.com/ie/archive/2006/11/16/ie-javascript-performance-recommendations-part-2-javascript-code-inefficiencies.aspx

i searched ajax enabled browser info but there’s a few useful references in the google’s results. so i decide to make some..

from wikipedia
* Apple Safari 1.2 and above
* Konqueror
* Microsoft Internet Explorer (and derived browsers) 4.0 and above
* Mozilla/Mozilla Firefox (and derived browsers) 1.0 and above
* Netscape 7.1 and above
* Opera 7.6 and above

MSIE 4.0 is developed  in oct, 1997, packaged into Windows 98. in nov, 1997.
Safari 1.2 is packaged into OS X 10.3 in feb, 2004. hardwares installed OSX10.3 by default are iBookG4, PowerBookG4, PowerMacintoshG5, iMacG5. but in almost every OSX version ajax enabled safari can be installed.
there’s a few ajax enabled browser which supports apple’s os9. but who cares?
firefox supports ajax since nov, 2004, gecko engine 1.7 version is used.
any other browsers using gecko engine 1.7 started to support ajax since early 2005.
opera supports ajax since 7.6 beta but, that version was not released publicly. opera 8.0  released in apr, 2005 is the first public version.

i’ve seen many win98 machines working on my clients’ office. they don’t feel any impulsion about updating os. because office program and browsers work well in win98. so if you want to focus realstic browser support problem, only you have to concern is IE4. there’s one more issue on ajax, and this one is very critical. native XML DOM Parser is supported only by IE 5.5+& FF1.0+. i feel very uncomfortable about it.. we don’t have good native xml parser and json converter now. ( i plan to develop and add to my library someday)

IMHO, if the customers suffer from old-browser problem, you don’t need to change your script. just recommending installation of the newest firefox is enough in almost cases ^_^; it’s free and cool browser!

XMLHttpRequest was introduced in late 1997, but till early  2005, it wasn’t a main stream technology. or maybe i can say IE was prevailed so much at that time. 7 or 8 years there was only a few movement occured in web browser market. web programming was very quite and dull. but now it becomes very exciting.. i’m a very lucky guy living this ajax age

there was a big cross-browser problem when the  javascript’s history was started. you had to write quite different codes for IE and NN. at that time, i usually gave up the NN part, and i felt no guilty :-). for my excuse, it was all NN’s fault. but FF & Mozilla doing so well in these days, i always consider cross-browser issues when i make some web apps.

but there’s only a few site who treats only cross-browser problem. do you know about select tag bug in IE? select tag element’s z-index is  highest in IE, so you have to hide when you want to see some css animation in IE. there are so many problems like this. what i aim now is, not so perfectly cross-browser(mainly FF & IE) support javascript library targeted for japanese programmer. it may not so good.. but i need it madly for my project ^_^; there are so many javascript libraries in the world, only a few library is existed for japanese environment.

because this library supports major browsers only, the code is somewhat clean, and easy to implement. and though i give up the perfect cross-browser functionality, i always consider cross-browser issues. the main target i don’t want to support is a NN with document.layer. all other browsers will be supported as far as i can.

i wish the library will be finished someday not so far future from now. but i can’t assure anything.. anyway i started the project few days ago, and it works fine till now ^_^; wish my luck~

p.s. you may be surprised when you know there are so many people still using win98 & IE4. it’s because the hardwares aren’t worn out yet. still need 4-5years maximum. but probably they don’t need my web-apps, i sure. so i decide to ignore’em. and i feel no guilty at all

recently i made some javascript library for work. i mainly referenced yahoo ui, prototype and quirksmode.org. these are most cool javascript stuffs in the world.

http://www.quirksmode.org/

surprisingly, my library works fine! someday i finished it. i’ll release it.

i upgraded FF yesterday. i hadn’t knew, because i was so busy to make something. there are many improvements and bug fixes, also some cool features added, but those may be useless for me.:-) most impressive thing occured in FF2.0 is improvement of tab browsing, now i can quit to use the buggy TabMixPlus. good. update process was smooth enough contrast to 1.0 to 1.5 upgrade case. overall i’m very satisfied.

firebug is javascript debugging plugin for firefox. somewhat useful compared to alert function. and that’s an enough reason to use it

http://www.joehewitt.com/software/firebug/docs.php

i found some special skills, though it’s not a new one, like XmlHTTPRequest.

http://alistapart.com/articles/sprites/

this technique prevents not to flickering and enhances image download speed. because make resembling images into one file increase compression rate. cool, very useful tip!