Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

news.ycombinator.com

Post reply on HN
Print view View original

191–200 of 360 posts

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#191

Post by callmevlad »

codegeek wrote: post #186
callmevlad wrote: post #178

Earlier quoted context omitted.

(Disclaimer: I'm working on http://www.webflow.com to try to solve this exact problem.) I've been thinking about this issue a lot over the last year, and it's really as hard as you state (and then some). We ended up having to create our own supersets of the DOM/CSSOM in order to keep track of individual elements/selectors as they are created/removed/changed. I would be very surprised (and pleased) if Mozilla was able…

I tried to enter my email address to get notification of your launch. Nothing happened when I clicked the button (using IE 8)

Woah, oops - thanks for letting me know. Trying to stand up a VM right now so I can see what's going on.

Edit: Should be fixed now.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#192

Post by johnrob »

Right now, Web Developer Toolbar lets me live edit HTML in the browser. I'd like the same feature, but instead of editing in the browser, I want to edit the actual html file. So, this would be some sort of "live edit mode" where open a url to your local html file, and any edits you make to the file get applied in realtime (just like the Web Developer feature). It would be nice to use my regular editor (and the true html source file) instead of a browser text field.

I suppose support for CSS could work as well.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#194

Post by nnnnnn »

mbell wrote: post #73

This is a big request: Improve "design in the browser" capabilities. i.e. pushing CSS/HTML and maybe JS changes made in Dev Tools back to the source files without manual shenanigans in the middle. I probably waste more time copying CSS / HTML tweak diffs from the browser back into the related source files than anything else with in browser dev tools. Due to the nature of 'losing changes' if I happen to hit refresh or…

If you're using Chrome, try out: http://tin.cr/ It seems to be at least very similar to what you're looking for!

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#196

Post by ptgloden »

grayrest wrote: post #125

Webkit dev tools timeline in frame mode is bar none the most useful tool for tracking down performance issues. Looks like it's on your roadmap but it's far, far more useful in tracking down actual perf issues in large codebases than any other tool in any developer tools toolbox because it's cross-cutting and bottlenecks tend to be a combination of factors and the frame-sizing lets you find what's on the critical path…

Agreed on the console not displaying objects well. I find that to be especially true with DOM nodes.

FF:

  >>> document.getElementsByTagName('div')
  (pocs:({}), pocs0:({}), pocs1:({}), pocs2:({}), cst:({}), mngb:({}), ... )
Firebug:

  >>> document.getElementsByTagName('div')
  HTMLCollection[div#pocs, div#pocs0, div#pocs1, div#pocs2, div#cst, div#mngb, ... ]
Chromium:

  >>> document.getElementsByTagName('div')
  [​…​​, 
  ​…​​, 
  ​…​​, 
  ​Press Enter to search.​​,
  ​​, 
  ​…​, ... ]
(edit: formatting)

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#197

Post by javajosh »

Move toward cloning MS Access from around 1997, but with open web technologies. And yes, I am very serious about this. We have needed this for a long time, and I don't think anyone but a browser vendor has the expertise to make it happen. Clearly you understand that the browser is an important development environment, so why not go whole hog and create something that can solve roughly 90% of developer's software needs?

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#199

Post by jlgreco »

gcp wrote: post #54
[deleted] wrote: post #43

Earlier quoted context omitted.

[deleted]

How exactly does this help web developers? This has been considered and rejected as inferior to the current approach. The Android browser used this and it was rewritten to get rid of it. Let's focus on doing things that improve the user experience rather than blindly copying features from other browsers without considering if they make sense. Moreover, it has absolutely nothing to do with the question asked.

I'm not sure what he said, but I assume he said something about Electrolysis.

Didn't they ditch Electrolysis because of issues with many nsplugins? I am not aware of other reasons it was shitcanned.

Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

#200

Post by jimmaswell »

d0m wrote: post #169

Thanks for asking. Here are some ideas associated with their pain points in no particular order. 1) I'd like to environment to feel more "dev" when I'm in the debug tools. Ctrl-L should clear the console, C-a should get to the beginning, etc. Ideally, there should be standard console mode (Vim-like, Emacs-like) so programmers can feel more at home while in the firefox console. There should also be a way, maybe a json…

> console-like tools to make programmers feel at home

A good portion of programmers don't use CLIs for development and only use IDEs. why would that be assumed to make devs more at home?

Post reply on HN