Hi Lawrence, hi Alfonso! Lawrence, yes, being able to create mappings between the content shown in the browser and the related resources on the server is a good idea. As Alfonso mentioned, the Firefox DevTools already have a feature that goes into that direction, which is called source maps <https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Use_a_source_map> . Firebug has a feature that allows you to open the HTML, CSS or JavaScript in an external editor, though only the contents you're seeing inside the browser. It doesn't offer any mapping to the server sources.
Therefore your suggestion would be nice as enhancement request for the Firefox DevTools, though it fails my request for features which Firebug has and the DevTools should implement to close the gaps between both tools. Sebastian On Thursday, May 5, 2016 at 5:59:00 PM UTC+2, alfonsoml wrote: > > It seems that you want this: > https://developers.google.com/web/tools/setup/setup-workflow > > Even if it doesn't match exactly what you want, it's a thousands times > closer to anything that Firebug offers > one day you'll ask yourself why you have been focused for so long only on > Firebug instead of looking at other options. > > On Thursday, May 5, 2016 at 7:51:18 AM UTC+2, San wrote: >> >> Erik, I believe there is some facility in the extension I'm using >> (Dafizilla ViewSourceWith) to map to server scripts as well -- as you say, >> to define a "source map" -- but I'm not sure because I don't bother with it. >> >> All I want is for the main, core HTML file (corresponding to what I'm >> looking at in Firefox) to pop up in my code editor. It makes no difference >> whether the page is completely static (rare) or has PHP server code that >> partially generates the "final" HTML -- if I wanted to see the final >> composited result, I'd ask to see the browser's own generated/cached source >> in one of the usual ways. What I'm getting with my approach is just the >> master HTML file from the server; that's all I want. If there are (for >> example) calls to PHP in there, they show up as calls to PHP, not as the >> result. This is *complementary* to seeing the final/generated code that >> the browser uses and can show you; it doesn't *replace* that other >> meaning of "viewing the source." >> >> In fact, I haven't even bothered figuring out how the ViewSourceWith >> extension handles other *client* languages (i.e, CSS and JS) -- although >> I know it can -- because my main code editor (BBEdit) has its own popdown >> menu showing me all the CSS, JS, PHP, etc. that is linked to that page, and >> I use that menu to access the resources associated with the current HTML >> file, as needed. >> >> As I said, I really wish that Firebug could add this live-mapping >> feature, so I wouldn't be dependent on another tool to do this. >> >> On Wed, May 4, 2016 at 5:43 PM, Erik Krause <[email protected]> wrote: >> >>> Am 04.05.2016 um 18:41 schrieb Lawrence San: >>> >>>> My workflow is based on browsing through the website I'm building, >>>> in Firefox, and when I see something that needs editing (content or >>>> code), >>>> I click one button in the Firefox toolbar and the actual server page >>>> pops >>>> up in my code editor (in my case, BBEdit on the Mac, or Notepad++ in >>>> Windows). If I edit the code there and Save, I'm updating it*for real*. >>>> >>> >>> This would be very nice indeed. And it might run for static pages. But >>> as soon as some server side language is involved (like PHP, JSP, ASP etc.) >>> the only way to do that would be to provide a source map. This should >>> already work in the firefox dev tools (and hence for firebug.next) for JS >>> and CSS. But I don't have any clue whether this would be possible for >>> server side languages as well... >>> >>> -- >>> Erik Krause >>> http://www.erik-krause.de <http://Sanstudio.com> >>> >> >> -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/f17813a1-4b1e-4d04-bdf5-145d600e6cad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
