On Tue, Mar 17, 2009 at 1:00 AM, Aaron Boodman <[email protected]> wrote:
> > Extensions comrades, > > Here are my takeaways on what we can improve based on Glen's experience: > > * Make the id field optional for development mode > * We should add a temporary alert box saying "success" after > installation of a crx file, until we have a proper install UI > * We should reuse the current process when a crx file is opened by a > chrome instance (we talked about this today) > * We should add some easy way to create a crx file using chrome.exe or > a website or something Agree with these points, but here's a slightly less annoying cheat for the install UI: - open up raf's extension ui page in a tab and highlight the newly installed extension > > > - a > > On Mon, Mar 16, 2009 at 11:54 PM, Aaron Boodman <[email protected]> wrote: > > On Mon, Mar 16, 2009 at 10:52 PM, Glen Murphy <[email protected]> wrote: > >> I created a content script this evening. If it helps you refine the > >> doc, here are the things I ran into. I was using a nightly build > >> (11818): > > > > Thanks a lot for the feedback! > > > >> - I didn't expect, and was thankful for the manifest validation error > >> messages. I wonder where these should go. > > > > Whee. I love error messages and am glad you found them helpful. I also > > don't know where they should go yet, but I don't want to remove them > > until we have a better place because they are so useful. > > > >> - Sometimes the script seemed to fail to load - particularly after > >> hitting reload. > > > > That is weird, I've never noticed that. The only thing that I can > > imagine is that because the reload is asynchronous, you were beating > > it, but that seems hard to believe. Did you notice that the second > > time you refreshed you'd see your changes? > > > >> - Couldn't see JS errors for the extension in the inspector, but I > >> think the inspector is pretty hosed regardless. > > > > What do you mean? JavaScript errors from content scripts? Or other > > types of extension errors? You should definitely see errors, and I > > know I've seen them before. > > > >> - Because of both of the above, I always just restarted Chrome > >> whenever I made any changes, setting my homepage to my test page. > > > > That sucks, I really want a edit-reload development experience. > > > >> - I missed the bit about the ID being a 40-digit hex number and spent > >> a long time trying all sorts of stuff with my name in it. > > > > Yeah, we should just remove the requirement for the ID altogether from > > the development mode. > > > >> - I also missed the bit about Python 2.6 and spent a reasonable amount > >> of time figuring out how to install the non-default dep (SimpleJSON) > >> in my Python 2.5, as the ez_setup only pretended to work. > >> - I put chromium_extension.py in the same dir as the files. It then > >> included itself in the CRX. > > > > We want to add a feature to Chrome itself where you can just use it to > > create the package. > > > >> - The doc isn't clear about what to do with the CRX. Dragging it onto > >> Chrome downloads it, and setting Chrome as the default opener for the > >> filetype results in an infinite tab-spawning download loop (opening it > >> downloads it again, after which it autoopens : repeat). If it's not > >> implemented, can we say so? > > > > Dragging it onto Chrome should download it, then install it, but there > > is no UI letting you know that anything happened right now, and it > > also doesn't work correctly when you're using a Chrome that isn't your > > default installation. > > > > I will update the doc and try and fix these issues. > > > >> - Either way, you may find it here: > >> <http://glenmurphy.com/tmp/portal.crx> OR > >> <http://glenmurphy.com/tmp/portal.zip> (5KB) - it's a version of that > >> content-clipping script we wrote a few years ago. alt+drag to create, > >> double-click to spawn. > > > > Both files appear to be invalid?? > > > >> - I was worried that all of the content-scripting I'd forgotten would > >> come and bite me, but apart from brief confusion over scope > >> ('document' working, but 'window' requiring 'contentWindow'), writing > >> the code itself was easy as pie. > > > > 'window' shouldn't require contentWindow, unless you want to access > > the content window's global scope, which doesn't seem necessary for > > what you're trying to do (but I can't remember exactly what feature > > you're talking about). > > > > - a > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
