Closed larz0 closed 10 years ago
@larz0 It should be easy to do in an extension if you're willing to have a prefix on the search string (like other Quick Open plugins). Do you actually think this should be default behavior in core? Also, what about other online searches -- GitHub code search, stackoverflow, MDN, etc. might actually feel more relevant to developers. I don't know how much of an assumption we'd want to bake in there...
Ahh that led me to this https://github.com/peterflynn/brackets-editor-nav. Maybe we could just extend your extension and see what happens :)
@larz0 That extension doesn't do any online searches or anything, so it's probably not a good fit there... but it's certainly a good example of how an extension can easily plug into the Quick Open functionality.
Another option would be to just use a bottom panel that loads any of those pages inside Brackets.
I'm able to load Bing in Brackets but not Google because of Google's same origin policy.
I don't think it's same-origin, it's probably a no-frame header. There are security concerns about browsing to arbitrary untrusted web content inside brackets-shell though, so I'd be hesitant about doing this in core. (It also has downsides like no bookmarking, no back/fwd buttons or URL bar for free, no shared cookies with your main browser session, etc.)
Closing as extension idea
Something like this:
It should show the search results in Chrome (same browser as live preview).