Thank you Erik for your answers. I've starred both bug reports. I'll work on user notification by icon changes, it's not really a bad idea, I think a blinking icon will attract enough user attention.
Also, I've set up a website for this extension in http://cezarsa.github.com/chromed_bird/, you're all welcome to help testing it. :) On Mon, Nov 2, 2009 at 11:41 AM, Erik Kay <erik...@chromium.org> wrote: > On Sun, Nov 1, 2009 at 9:56 PM, Cezar Sá Espinola <ceza...@gmail.com> wrote: >> I've been playing around with Chromium extensions and decided to >> experiment a little with Browser Actions trying to create a Twitter >> extension. The result was Chromed Bird - >> http://github.com/cezarsa/chromed_bird >> I've faced some limitations but now it's working pretty well, and it >> lets you do common stuff like browse your friends timeline and write, >> reply and RT tweets, and I'm really using it all the time. :) Also, >> autoupdate is enabled, and the extension try to be smart about not >> hitting twitter.com too often as there is a rate limit for API calls. >> >> Now, after playing a lot, I have some questions about the problems I had. >> >> * The main limitation I faced was not being able to open the popup >> window from the background page, so it could warn the user when there >> were new tweets. Is this feature planned? > > No. The popup will only be openable with direct user action. The > best practice here is to change the icon to indicate that there's > something new. In your case you could use SetBadgeText to give an > "unread count" for the new messages. > >> * There seem to be some issues with popup window resizing, it doesn't >> shrink back once it's contents shrink. Is there a way to force popup >> window resizing? > > Yes, there's a known bug where the height doesn't shrink back. I > couldn't find the original in the bug database, so I filed a new one > as http://crbug.com/26471 > > >> * There are some focusing problems in the popup window. I wasn't able >> to manually set focus() on input elements. Also, using TAB to move >> focus between input elements isn't working. So, is this a known issue, >> or I'm missing something? > > I'm not sure about the manual calls to focus(), but it's probably > related to the second issue you mention, which is a known bug: > http://crbug.com/22654 > > > Erik > > > >> PS: All the source code is hosted in >> http://github.com/cezarsa/chromed_bird please, feel free to tweak and >> contribute in any way. :) >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensions@googlegroups.com To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
