Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Randy Edmunds
@redmunds
You can only use Dev Tools to debug Brackets (e.g. Debug > Show Developer Tools)
If you open a page in Live Preview, you cannot use Dev Tools on that page -- this is a known limitation
Brackets uses Chromium Embedded Framework (CEF) v3, so I'm guessing the Flash plugin is enabled (but Brackets does not use it).
SAPlayer: the only time I see problem opening Dev Tools is when I open Dev Tools window, close it, and try to open it again. Is that what you're seeing?
...in that case, I restart Brackets and it works again
Anachron
@Anachron
@redmunds I can never open the Developer Tools inside brackets, just wont do anything. Same with node debugger. No matter if I reinstall brackets or simply restart with no extensions.
Randy Edmunds
@redmunds
What about if you try to go to http://localhost:9234/ in a Chrome Window?
Be sure to stable Chrome
Be sure to use stable Chrome
More things to try in the Troubleshooting Guide: https://github.com/adobe/brackets/wiki/Troubleshooting
Anachron
@Anachron
Ok I think its because I use a portable chrome version. Should I open a ticket for Chrome portable support? Or can I already change it with preferences file entries?
Randy Edmunds
@redmunds
Yes, open an issue here: https://github.com/adobe/brackets/issues And be sure to explain what a Chrome "portable version" is, because I'm not quite sure. Thanks.
Anachron
@Anachron
Now that Atom.io is open source, will you go and check its source or maybe even use some of its code?
Kevin Dangoor
@dangoor
@Anachron a good deal of it was open source before yesterday, actually. I've looked at some of the code
I did some experiments around configurable keybindings in Brackets, for one
Anachron
@Anachron
Okay I see. So there is not much that can be used in Brackets?
Kevin Dangoor
@dangoor
Not directly, but certainly bits and pieces
Anachron
@Anachron
By the way, is there NodeJS support yet on the roadmap? What about Quick Edit for Metalangs like Jade/Handlebars and such? I am sure many people are not using plain HTML/Javascript/CSS. Mostly like Jade/Handlebars, Coffeescript/TypeScript and LESS/SASS.
Kevin Dangoor
@dangoor
their keybinding stuff, for example, could mostly be made to work, I think
Anachron
@Anachron
That sounds good. Also I love the quick menus that they built like Sublime Text.
Kevin Dangoor
@dangoor
We have done some thinking about support for template languages, but more in the context of live preview. Quick Edit may be easier
Anachron
@Anachron
You know what I mean? The global action menu where you can just type anything you wanna do, like install theme, disable plugin or even run grunt-scripts.
Kevin Dangoor
@dangoor
what kind of NodeJS support were you thinking of?
check out the Brackets Commands Quick Search extension
Anachron
@Anachron
I was thinking off I tell Brackets which is the server-file, and it will start the server.js (or even compile server.coffee) and run it with node. (Or I will pass a custom command to start the live-preview, if not running already, brackets will run it in background)
Kevin Dangoor
@dangoor
that lets you run any Brackets command
there is a NodeJS simple application manager extensions
Anachron
@Anachron
I tested it and its not really working with the latest version.
Kevin Dangoor
@dangoor
oh
you could try filing a bug with the author
we've been more focused on client-side stuff
Anachron
@Anachron
Understandable. Just throwing out the ideas I have.
As I know rarely anyone who codes in plain js/html/css.
Kevin Dangoor
@dangoor
yeah, indeed that's true
there are a ton of different client side technologies and server side technologies in use
(good thing Brackets is extensible :)
Anachron
@Anachron
Yes, and I guess thats one of the biggest reasons why its still alive, I guess ;)
Kevin Dangoor
@dangoor
True. Plus, people definitely have varied desires when it comes to their tools
Anachron
@Anachron
I switched from Sublime Text 3 to Brackets, not because I have all of the functionality, but I like the project and it feels good to know what is actually inside your editor. Plus, Brackets got a lot faster and more stable, no more crashes for me and it feels good to work with. I have a handful of extensions, one of which is Git, and it feels a lot better than ST3.
Kevin Dangoor
@dangoor
for some, the ability to do Live Preview with HTML and CSS is killer while they're designing
cool
I was also an ST user pre-Brackets, and I agree about the feel
obviously, that's subjective. vim and emacs still have plenty of fans!
Anachron
@Anachron
Hahaha yeah, that's true. Funny thing, there is even a plugin for atom that turns the editor into vim: https://github.com/atom/vim-mode
Kevin Dangoor
@dangoor
there's Vimderbar for Brackets as well
Anachron
@Anachron
Crazy, I choose editors like Atom/Brackets/ST because of the special design, and people keep porting vim design to their favorite text editor because they are too used to the old one :)
Kevin Dangoor
@dangoor
maybe Neovim will quiet them down and they'll just stick with vim at that point :)
Anachron
@Anachron
Hm hopefully, like the project!
Anachron
@Anachron
Can you guys help me out?
adobe/brackets#8352