Category: Firefox

Posted on

Managing my bookmarks on Firefox over various computers

When you work on multiple computers as well as multiple platforms, the one thing that is a chore is keeping up with all of your bookmarks.

I’ve tried a variety of browsers and methods, and some have worked better than others. Firefox has become my mainstay of default browser, so I’ve gone through a few variations of what is possible with various add-ons and plugins you can get for it.

Let it be said that Google Browser Sync was one of the best plugins for bookmark sharing, period. Install it on your main computer, sync it, move to the next computer, install it there, and you basically had a mirrored setup. Sadly, Google killed the project when Firefox released version 3.0 of their browser, and I think there was a good reason for them doing so.

Simply put, you can do relatively the same thing with the Google Toolbar. It lacks the syncing aspect that made Google Sync very powerful, but you can install the toolbar on Internet Explorer as well. The management of your book marks is less intuitive, but it is nice when you are doing web development over various machines and browsers.

Recently, I discovered Foxmarks, another plugin for Firefox that replicates a lot of the functionality that I missed since the loss of Google Sync. For every bookmark you actually make inside of Firefox, whether it’s in the “Bookmarks” menu or in the “Bookmarks Toolbar”, those links will be synced to any other machine you have Foxmarks installed within Firefox, regardless if it’s Mac, Windows, or Linux. If you add or delete a bookmark, the same thing happens across the other installations.

I have to say that after using this service for over a month now, the functionality of it has been very pleasing. Even better is that Foxmarks currently has a beta version of their plugin in operation for Internet Explorer and Safari. I don’t have any experience with those versions, but the thought is very encouraging.

If you’ve been looking for a way to share bookmarks over multiple browsers or machines, then you have my recommendations over what works for me. And I have to say, it’s been working really well.

Posted on

Checking out Firefox 3 beta RC3

In an effort to at least post something in about a week, I thought I would make a quick mention of some initial thoughts I had when I downloaded Firefox 3 beta 3. Now to get that in normal people speak, that would be version 3.0 of Firefox, but it’s still in the beta phase of development, meaning that it’s not ready for official, widespread release and/or use. The second 3 means that it’s third in a series of release candidates for the big day when Firefox 3 is finally here.

You still with me?

The first thing I noticed, on my Powerbook G4 with a 1GHz processor circa 2003, is the speed that this browser works. It’s fast. The current release of Firefox, 2.0.0.12, is rough on my laptop. I can only achieve half the speed of the latest beta by plugging in a hard wire connection, and that only makes me even more sad to the reality that this beautiful laptop is ending its life cycle, but that’s a whole other story.

Rebecca has been using it a bit more than I after I told her about how well it operated, but it starts and stops with the speed. There are some minor bugs that still need to be worked out. There are key commands for WordPress that don’t work in the beta release, but that’s less important than the numerous plugins that I rely on daily which need to be updated and ported into this new version. That will come in time, but certainly makes me hesitate to make the upgrade before I get all my tools lined up and readily available.

Phillip sent me a Twitter the other night when I mentioned this, asking if he should download it. I would say that it wouldn’t hurt if you are a multi-browser user. Firefox is my main workhorse, but I also bounce in and out of Safari and Camino. I expect to do the same with this beta release as well, so if you think you are along those lines, then go for it. Otherwise, hold off. This beta release (beta being the very important word here) isn’t quite ready for the big time.

Posted on

Dinking with things that dink with content

I’ve been cramming a lot into my brain over the past few days. For one thing, I’ve been exploring the lovely world of Drupal. After all the things I’ve seen and heard about it, I’ve been impressed. It’s everything that it’s said to be. Content management system, and they ain’t kidding.

I set it up locally and played quite a bit yesterday. Every time I tried to do something that would be complicated by doing it stupidly, Drupal had some sort of built-in way to do what I wanted. Very interesting. Not sure that I like it from a blogging aspect, but it has that too. It can be oh so much more.

I’m experimenting with WordPress more and more. I’ve been a long time user of the visual rich editor. However, not anymore. It’s come to be such a pain, and the WYSIWYG interface gets so annoying after a while. Being a user of only version 2.0 and on, this is what previous versions did. I’ve gotta say that I like this, non-rich editor, much more. Loads faster in FireFox and has no lag. I’ll stick with this for now.

I did find a really great Flickr plugin for WordPress. Flickr Photo Album adds a nice interface for dropping images from your Flickr account straight into a post, all from within the editor. You can already do this with Flock, but I am still not impressed with its performance. This plugin makes things simple and quick, but the setup takes a little to sort out.

I also got into some Unix[wiki] junk last night. Seems that my external hard drive has the occasional ability of renaming itself at random times and confusing some of my peer to peer programs. How else are we to have our cheap nights in with some ghetto Tivo, aka BitTorrent? This could also cause problems with some of my podcast projects. If I spent enough time with it, Unix could become another language I could start to really understand. I’ve got way too many other things on the list right now. I should get some tape for the middle of my glasses.

Posted on

Noticing some slight bugs in Firefox 2

Firefox 2.0 Screen ShotIt seems that every time I launch Firefox 2.0 on my Powerbook, it never likes to load Google like a good browser should(click on the image to the left to see a screen shot). It takes the logo and positions it almost in the center of my screen rather than the center of the window. Usually resizing the window will solve this and everything goes back to normal. I’m making a post about this and then sending the link as feedback for Mozilla.

There are other issues creeping up with the latest release, but they seem to not be overly critical. They are worth reading up on because users are concerned about security problems, but Mozilla is saying that there is nothing threatening about any of the problems that are showing up. I would expect an update soon, but it’s interesting to note that they are hard at work on version 3.0.

Something else to pass on is this link that I got from BoingBoing about a series of tweaks that you can implement on Firefox. Granted that these are for the more geeky individuals, but it’s really not that hard to do. If those tweaks aren’t enough for you, check out the MozillaZine Wiki for a all sorts of geeky and nerdy stuff that you can do with Firefox.

Posted on

Firefox 2.0 released today

I haven’t had much time to really put Firefox 2 through the test, but it is installed and running on my Powerbook. The main reason that I really wanted to make this post is the inline spell checking that now comes in this version. This is the thing that I have been wanting for a long time and, I finally have it. Hallelujah!

Firefox 2 is the next generation release of the award-winning Firefox web browser from Mozilla.

These Release Notes cover what’s new, download and installation instructions, known issues and frequently asked questions for Firefox 2. Please read these notes and the bug filing instructions before reporting any bugs to Bugzilla.

Give us your feedback through this feedback form.

[mozilla]

After painless installation, I checked to see if the speed up tweaks that I posted about a while back held, and they were all there. I only have two extensions that didn’t want to play nice, but they seem to have been built into the new release. All the additional search engines that I have added are there as well.

For the most part, what I’ve been able to read about this release is that the internal overhaul has been more than the external. There is some noticeable changes, but it’s looks and feels the same for the most part. Then again, I’ve been using a skin that made it appear more like Safari, so that might have something to do with it. Oddly enough, that was one of the extensions that didn’t want to work with this version. The other one was a tabbed browsing extension.

Wow. I love this built-in inline spell checking. Oh how I have missed this.

Posted on

Speeding up Firefox

When I used to do I.T. for WSUI, I pushed for people to use Firefox as their default browser on their PC. Fellow tech support monkeys can understand that for obvious reasons.

I just recalled this tip that I caught wind of about a year or so ago. This is a really great way to speed up Firefox, and it doesn’t require you to download anything to do it. This mostly applies to those folks on broadband, so if you’re on dial-up, this isn’t for you.

  1. Type “about:config” into the address bar and hit return. Scroll down and look for the following entries:
    • network.http.pipelining
    • network.http.proxy.pipelining
    • network.http.pipelining.maxrequests
  2. Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.
  3. Alter the entries as follows:
    • Set “network.http.pipelining” to “true“
    • Set “network.http.proxy.pipelining” to “true“
    • Set “network.http.pipelining.maxrequests” to some number like 30. This means it will make 30 requests at once.
  4. Lastly, right-click anywhere and select “New” -> “Integer“.
  5. Name it “nglayout.initialpaint.delay” and set its value to “0“. This value is the amount of time the browser waits before it acts on information it receives.
  6. Restart Firefox.  You can follow steps 1 through 5 to be sure that your changes saved correctly.
    • Note: You might have to make these settings changes everytime Firefox is updated.

This works for the Mac version, too. Logging into WordPress is a snap, and browsing just got a whole lot faster. Once again, another reason I’m a happy switcher to Firefox.

Posted on

Firefox 2 beta 2 released today

Going along with my recent post about converting over to Firefox as my default browser[post], I thought I would also point out that the second beta of Firefox 2 was released today. The features noted in this Wired.com post makes me anxious for the final version. I’m not too keen on the idea of downloading and running this right now, plus not all extensions are fully compatible with this beta version.

There’s too much to detail about what you can expect from 2.0 when it is launched in its final form, so check out the release notes for more details there.

One thing I will say that I am excited about is inline spell checking! This was the one feature about Safari that I loved the most. Finally, we’ll see it on a Mozilla product.

Posted on

Use a bookmark to resize your browser window

I found this tip via Macworld a while ago, but it was meant for use in Safari. However, in making my switch to Firefox, this was a feature that made the jump all the more interesting because it works in this browser as well. Here’s how it breaks down from Macworld.

Launch Safari (or your favorite browser) and create a new bookmark. Most browsers will require that you bookmark a specific site. In Safari, open a site and then choose Bookmarks: Add Bookmark. Give the bookmark a name that will help you remember the screen size, such as 800×600 or 1024×768. Next, edit the address of the bookmark—in Safari, go to Bookmarks: Show All Bookmarks and navigate to your newly created bookmark. Change the Address portion of the bookmark to:

javascript:self .moveTo(0,0);self.resizeTo(800,600);

Open any page in Safari and select the bookmark. You’ll see that page in an 800-by-600-pixel browser window. You can then duplicate this bookmark and create other sizes as needed; just change the name and the relevant code. When you’re done, move your new bookmarks to a convenient location; then click on them when you want to test your pages at different resolutions. [macworld]

I like to have three of these bookmarks in my toolbar. From small, medium, to large, it gets very useful. I’ve even gone as far as making them slightly button-like, naming them “-“, “+”, and “++”. You can minimize and maximize windows all you want, but to make it quick and simple, just hit your bookmark and you’re done.

This might not be too handy for those folks out there that don’t have a lot of real estate on their monitor. If you run a monitor at the screen size of 1024-by-768, then you might not see the advantage. I can’t be sure if this works in the world of PC’s, but it stands to reason that it should. It’s great for previewing how websites you are working on look, but I just like it for the simple reason of keeping everything on my screen in a more controlled state of chaos.

Posted on

Making a switch over to Firefox

Screenshot of my Firefox setup Being the Apple fan that I publicly am, I’ve also been very partial to Safari.  That changed the other day when I launched Firefox while just being curious about how it stacks up to my “usual” browser.

I really like Safari.  That being said, in the past few days, I am not longer using it as my default browser.  The element I really liked about Safari was the RSS feature.  After numerous, spinning beach balls(Apple users will know what I’m talking about), I grew tired of how it behaved.

It’s annoying and time wasting to have that happen.  RSS was made to make getting info more simple and quick.  On top of that, Safari does not fully support WordPress.  So for creating my posts, I ran Camino along side Safari in order to use the “quicktags” feature in WP.  You can’t use that in Safari, so posting with that browser reverts back to manually typing up HTML code as well as your text. Can you see the headache going on here?

I also experimented, briefly, with making Flock my standard browser, if not something to use in conjuntion with Safari and replacing Camino.  I can’t say that I was overly happy with its performance, RSS interface, and overall feel.  I still think that it’s a great browser, but the development needs to keep going on it until I would be comfortable using it full time.  Maybe it’s something to keep revisiting as the built-in blogging and photo sharing support is pretty cool.

That being said, I think I am 80% with being fully converted into using Firefox.  The ability of using plugins has already found me pretty happy.  Using Tab Mix Plus and Wizz RSS News Reader has me feeling even more efficient than I did with Safari.  Additionally, I’ve changed the theme to make it look more like Safari.  That might sound sad to some folks, but having it look like how I’m used to made the change all the more easier.

Pages load quicker than before, and I mean that by being more snappy.  Clicking on a RSS article has the page load in a few seconds.  And if I want to blog about something I read, I open a new tab and make a post.  Even publishing a podcast gets easier because if I need to search for info to add a link into the show notes, eveything is all in one.

These are just some preliminary thoughts about the switch.  I have to say that I’m pleased with how easy it was, but my experience with doing these things might be more than the average user.  For now, I’m sticking with Firefox.