Posts Tagged ‘chromium’

Re: Firefox/Iceweasel/Chromium smart-bookmarks

2010.06.27 13:31 by Leo Antunes - 3 Comments

Neil Williams recently commented on the lack of smart-bookmarks in Firefox/Iceweasel/Chromium and since the post doesn’t accept comments, counter-post FTW.
Maybe I didn’t understand exactly what was meant, but I’m personally trying to see the advantage of having a smart-bookmark sit on the toolbar as opposed to just being used via a label. Both FF/IW and Chrome can do the label thing, where you bookmark something like “http://bugs.debian.org/%s” with a shortcut like “bugs” and can then simply Ctrl-L to the address bar and type “bugs 999999”. Done.
Can the way Epiphany does this be more effective? (actually this is the way Galeon did it way back then and I used to love it before I found out I could be way quicker with the keyboard+shortcut thingy. Not to mention having less clutter in the toolbar.)

And granted: Chromium’s interface doesn’t allow the editing of this shortcut and they only work when imported from FF/IW, but I expect this to be fixed eventually. Doesn’t make much sense to have such a “hidden” feature. [UPDATE: nevermind. As handily pointed out by Chris Butler, you can edit the shortcuts under Options→Basics→Default Search→Manage. It might not be the most intuitive of places to put it, but it’s there.]

As for the rest of the reasons for switching mentioned in the original post, I can certainly see where they’re coming from. No real solid counter-arguments there.

Notes on the Google Chrome™ Debian package

2009.12.08 22:23 by Leo Antunes - 9 Comments

Just some quick superficial observations on the Debian/Ubuntu package distributed by Google:

  • Most files are installed in /opt/google/.
  • It attempts to patch /usr/share/gnome-control-center/gnome-default-applications.xml on postinst (maybe legacy compatibility? Someone with more gnome-fu than me care to explain?).
  • The postinst also automatically adds a souce for updates to /etc/apt/sources.list.d and an archive key (this is IMHO the worst part)
  • It includes a daily cronjob that – at least at first glance – tries to do the same things the postinst did (new apt source, archive key, etc) and some further archive configuration. The cron script is called at the end of postinst.
  • A casual look at objdump suggests it’s statically linked to libv8
  • On a slightly more positive note, it at least seems to successfully undo most of the changes once removed, with the exception of the added archive key and the above mentioned patch to gnome’s default apps list (that is: if there’s any situation it actually gets applied).

I understand it might be too much hassle doing it the right way (from the corporate POV), but then why not simply cooperate a bit more with the community? Hopefully they’ll accept some criticism and suggestions.
Or even better: they could simply reuse all the work being done to officially package Chromium.

UPDATE: forgot to mention that the version string (something like “4.0.249.43-r34537”) doesn’t follow policy. Not a huge deal for a non-distributable package, but in the name of forward-compatibility – if Chrome ever becomes fully open-source – it could be smart to adopt something like “4.0.249.43-0.x”.