Writing my own upload PHP script isn’t all that bad, since I can do things that CKEditor/CKFinder wouldn’t do otherwise, like image resize. After actually writing the script I realized that it works, but it doesn’t pass the dialog the link. I noticed, that my server side JavaScripts actually get parsed, so I figured, why not write this simple feature myself. After 1-2 hours of finding out how the whole CKEditor plugin/dialog system works I found out that for some reason the script I generate server side doesn’t see my global variables in the document, not even, if I use the window object, so I figured, this could mean only one thing: this whole thing runs in an IFrame, but not only that, there is a strange way that this should work, basically instead of the AJAX style it uses IFrames and JavaScript callbacks .

After realizing all this, I finally found the proper solution here, which looks like this(if of course we are using PHP server side):

<script type="text/javascript">
window.parent.CKEDITOR.tools.callFunction( <?php echo $_GET['CKEditorFuncNum']?>, '<?php echo "$uploaded_file_url"?>' );
</script>
This is what is needed to be generated server side for the upload dialog to function correctly, absolutely not a simple concept but only needed here.

The original post was made on reddit, and here is a little video that shows what’s the game like:

Now what me and a lot of people didn’t get is why did the Chrome developers choose GTK over Qt on the Linux port without any real reason, they should have went with Qt it would have suited better the purpose of Chrome, because what I like is that Chrome tries to be really platform independent, it tries to avoid platform specific things as much as possible, which is a very good thing, I agree that the browser should have a world of it’s own and not to be tied with the operating system.

Another major innovation that I think Chrome pioneered, is the compactness of the browser’s user interface, they god rid of those useless menu bars and made used the title bars as a place for tabs, this conserves space and makes the browser a lot more clean and easy to use.

The Google Chrome team expressed that they wanted to do a browser from scratch, and do it the right way this time because most browsers are pretty much stuck in the last century, they highlighted that back then there were web pages, but now there are web applications, that is why they did thing differently than other modern browsers. They fixed a lot of issues that have plagued other browsers for years, like speed, security and stability.

Although Chrome is the best for browsing, it lacks extensions and developer tools, that I was familiar with from Firefox, so I still use Firefox for development, because it beats most browsers when it comes to developing.

The bottom line is, give it a try, it’s worth the time.

This is considered the ‘original’ bug.

They even have a patch, which tough only works for KDE, but since I’m still not used to KDE 4′s look and feel, so that’s out of the question. So I guess that they are working on it, and they said that even it it doesn’t get fixed they will at least mention it in the release notes.

Keep up the good work guys!

There are two particular bugs that I think that should have been addressed long ago:

1) [Karmic] [i945] Screen flickers due to constantly changing brightness level

Reported on: 2009-08-14

2) [Karmic] USB hotplug system doesn’t detect anything after boot

Reported on: 2009-09-07

None of these seemed to get the deserved priority and Karmic is going to be released but it will fail on a whole product line, well at least for the general consumers, I still love and use Ubuntu, but I wish they would take a deep look into issues that matter, it’s a pity because on the UI front they really outdone themselves. Let’s hope for the best.