Cool idea - it reminds me of a conversation from last year:
https://groups.google.com/forum/#!searchin/mozilla.dev.developer-tools/dom/mozilla.dev.developer-tools/0bbkEFQYmuY/hLW39ObUxL0J.
It sounds like there is some overlap, except that in this case we
wouldn't try to save external resources to disk and rewrite the URIs to
match, but instead change the resolution of the existing links on the page.
A few of questions regarding the use case for such a tool:
1) Is it important/useful to save the current state of the page, or just
start from the page source?
2) Is it important to include and run JS from the original page on the
virtual page?
3) Would you want this virtual page to download fresh copies of
stylesheets from the network so it would be updated if the remote
sources changed?
I like the idea of downloading a copy of the page on disk (including all
resources), since then the 'preview' button could just load an iframe
with the file URI. Also, if someone wanted to open up their normal text
editor or other tools on the files they could do so. But, I'm not sure
of the full complexity of either approach and depending on desired usage
one may be better than the other.
Brian
On 2/27/15 12:31 PM, Jet Villegas wrote:
> Hello Dev Tools:
>
> A feature I've always wanted to see in web authoring tools is a "New from
> Source" menu item next to Tools > WebDev > Page Source. It would be very
> useful for sketches, comps, testing, and other web design workflow gaps.
> Existing authoring tools lack the preview fidelity that only a browser
> could render.
>
> What it does:
>
> 1. A new virtual HTML file is created in memory with the contents of the
> Source page.
>
> 2. The user edits the HTML text within the browser's editor window--all URI
> links are resolved relative to the Source file's URL. The user could also
> copy that text for editing in their own text editor and paste it back later.
>
> 3. A "preview " button shows the edited file in context as though it was
> already on the server (no actual uploading occurs--the browser handles the
> resolution locally.)
>
> I know there's lots of problems to solve here re: UX, security, rendering,
> etc. but it would be so cool :)
>
> Would the dev tools team be interested in implementing it? I can help with
> the Rendering bits.
>
> Thanks,
>
> --Jet
> _______________________________________________
> dev-developer-tools mailing list
>
dev-devel...@lists.mozilla.org
>
https://lists.mozilla.org/listinfo/dev-developer-tools