brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

[CLOSED] Feature request: invoking Google search via Quick Open #6504

Open core-ai-bot opened 3 years ago

core-ai-bot commented 3 years ago

Issue by larz0 Thursday Mar 13, 2014 at 20:54 GMT Originally opened as https://github.com/adobe/brackets/issues/7194


Something like this:

brackets_googlesearch_001

It should show the search results in Chrome (same browser as live preview).

core-ai-bot commented 3 years ago

Comment by peterflynn Thursday Mar 13, 2014 at 21:01 GMT


@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...

core-ai-bot commented 3 years ago

Comment by larz0 Thursday Mar 13, 2014 at 21:11 GMT


Ahh that led me to this https://github.com/peterflynn/brackets-editor-nav. Maybe we could just extend your extension and see what happens :)

core-ai-bot commented 3 years ago

Comment by peterflynn Thursday Mar 13, 2014 at 21:46 GMT


@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.

core-ai-bot commented 3 years ago

Comment by TomMalbran Thursday Mar 13, 2014 at 22:33 GMT


Another option would be to just use a bottom panel that loads any of those pages inside Brackets.

core-ai-bot commented 3 years ago

Comment by larz0 Thursday Mar 13, 2014 at 22:43 GMT


I'm able to load Bing in Brackets but not Google because of Google's same origin policy.

http://github.com/larz0/bottom-browser

core-ai-bot commented 3 years ago

Comment by peterflynn Friday Mar 14, 2014 at 00:50 GMT


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.)

core-ai-bot commented 3 years ago

Comment by dangoor Wednesday Mar 19, 2014 at 18:32 GMT


Closing as extension idea