I have been building off Desmond’s work from last year and trying to implement tab drag and drop a.k.a. Bug 160720. I have made some progress: it crashes a lot less and now shows the tab while dragging. I am now starting to take a stab at animating the tab movements, I’ll have more on that later on. I’m going to try to work on this as much as possible so that we can get it polished and tested for possible inclusion in Camino 1.6.

As for Tabsposé, it looks like it is going to be a Camino 2.0 feature. There are still some cool things I want to do with it and thanks to Stuart’s patch the thumbnailing is done at the Gecko level. That means fewer crashes!

A few weeks ago I was asked to give a presentation for my school’s ACM chapter on my Summer of Code experience. The speaker for that week cancelled at the last minute, so I cobbled this presentation up the night before. I talk about what it was like working on Camino specifically and then what its like working with SoC all together.

Google Video | Slides

Summer of Code officially ended on August 20th, so I thought I would write a post that summarized my experiences with Camino and SoC. Better late then never, eh?

The Mozilla Foundation

My goal for the summer was to hack on Objective-C code. There are not many options out there for summer work as far as Cocoa goes, so I applied to Google for an internship as well as for Summer of Code. The first time I looked at the mentoring organizations, the only Cocoa related program I saw was Adium.

I knew that having only one proposal did not have good odds at getting accepted, so I started to seek other organizations that might be Mac-related. There was VLC which had a request out for someone to improve their Mac integration. That however required greater knowledge of C and video codecs than I possessed (and my beard is not quite long enough yet). So, luckily a few days before the deadline I put two and two together and remembered that Camino was a part of The Mozilla Foundation (insert stupid joke here). I checked their ideas for possible projects and was really excited about the Tabsposé request. I then wrote my proposal for Tabsposé as well as another one for Applescript (to better my chances) and then hit the submit button.

Read more...

Ever tried to customize your Camino toolbar and been…disappointed?  You call this customization?  There, what, about 20 items to choose from, and that’s it!  Plus, look at these choices: Back, Forward, Refresh.  I mean, they’re useful, sure, but where’s the excitement?  Where’s the fun?

“I could think of way better toolbar items than this!”

Good news, my friend.  If you can dream it, you can do it!  (Well, almost.) Presenting Script Toolbar Items.  Just write an AppleScript—any AppleScript—give it an icon if you like, and put it in ~/Library/Scripts/Applications/Camino.  Now try customizing your toolbar and—my gosh, it’s unbelievable, it’s right in my toolbar!

“Hello, World” icon unwittingly provided by the fabulous iWoot app.

Anything you can do in an AppleScript, you can do from your toolbar.  In fact, anything anyone else can do in an AppleScript, you can do from your toolbar.

Hang on, pardner, it’s not out yet.  Script Toolbar Items should be landing in the near future, though.  Look for it soon (ish) in nightlies, and eventually in Camino 1.6.

In the meantime, think about this: what do you want in your toolbar?

A quick update on Tabsposé. You can now click through the site previews in Tabsposé. Try it out on the latest trunk build!

I’m back from my 2 week jaunt in Europe. I had a great time and got to see a lot of beautiful places. The picture above is of me with Tim Berners-Lee’s NeXTcube at CERN which acted as the first webserver, home of the first web browser, and the World Wide Web. Since I am now developing for a web browser I thought it was amazing to see the place where its ancestors came from.

Now that I am back look out for click handling and titles landing sometime hopefully soon.

The beginnings of the new AppleScript support has landed on trunk and branch!  That means you’ll see it in all the nightly builds (trunk, branch).  Grab one and open its dictionary in Script Editor.  Anything that doesn’t have to do with bookmarks should be implemented and working.  For instance, you can say:

set website_listing to ""
tell application "Camino"
    repeat with i from 1 to (count browser windows)
        set website_listing to website_listing & "Window " & i ¬
            & return
        repeat with each_tab in tabs of browser window i
            set website_listing to website_listing & "    " & ¬
                (URL of each_tab) & return
        end repeat
    end repeat
end tell
get website_listing

and get something like this:

Window 1
    http://developer.apple.com/reference/Cocoa/idxScripting-date.html
Window 2
    http://developer.apple.com/cocoa/applescriptforapps.html
    https://bugzilla.mozilla.org/show_bug.cgi?id=385989

Not a terribly interesting example, but it shows off what you can do.  Go ahead, be creative!  See what cool uses you can come up with.  And remember: bookmark support is coming soon.

Hot off the heals of Tabsposé landing, I have a patch up that will handle user clicks and switch tabs. Hopefully we’ll see this patch move quickly into the trunk so Tabsposé will actually be useful.

I’m also working on Bug 390576 which will add titles under the thumbnails as shown in earlier screenshots.

Today I leave on vacation for Switzerland and France. I’m taking my work with me and hope to get features done in some beautiful locations . I just got to be extra careful about my iPhone data plan.

After about a month of reviews, the first stage of Tabsposé has made it to the trunk. This means that you can start to play around with it in our nightly builds. Right now the command is ‘ctrl + command + t.’ Remember, this is nowhere near a final version of the feature or the command to start it. Today I will be submitting patches to handle clicks and the page title, so hold back the “why does ____ not work” comments for now.

In addition to the source landing, I now have my first Tabsposé bugs: Bug 390406 & Bug 390401.

Let me know what you think!

Man, is this only my second post here?  I’m not too good at this, am I?

Luckily, I’ve got nothing but good news to report.  The bookmark code is now feature-complete!  It’s also pretty much at zarro boogs.  (Can you be almost at zarro boogs?).  All that’s left is a little code clean up.  About half the existing bookmark code was unused scripting support which I’ve partly used and partly overridden.  I’m going to weed out what’s not being used and move what is being used into my ScriptingSupport.mm silo.  I’m implementing scripting as a series of categories on various classes, which seems like the cleanest, most encapsulated way to do it.  They all reside in one file, ScriptingSupport.mm.  Someday that file may have to split, but at least the scripting support will remain separated from the ordinary implementation of the classes, which I think is important.

Nitty gritty under the fold:

Read more...