On Dec 30, 11:15 pm, AjitK <[email protected]> wrote:
> On Dec 30, 9:46 pm, John J Barton <[email protected]> wrote:
...
> "source" edits. From live edit I meant editing the actual source file
> in a running app (=> live!). From now on I will differentiate between
> live and source edits!
Perhaps we need some other words or description to clarify the
situation. I'm not sure what you mean by "editing the actual source
file in a running app". There are no source files in a running app.
The source coming in can be stored on the side and there are some URLs
attached to data in the running app. One can use these to navigate
from Firebug view to source in an editor to change the files that
built the live object. Then what? Some choices:
save the edits back to the server. Need server cooperation.
save them locally. Then the site is different and may not work.
convince the browser to reload them. Then they are not really saved.
Ultimately you need a combination of these to develop web sites. For
example Aptana serves the files from a local server, so it saves its
edits locally then reloads the browser.
...
> a live edit can be used to save changed contents (which is better than
> nothing) but leaves a lot to be done. Perhaps it can be extended to
> map the changes to the actual source file!
Based on input from other users there is an even smaller starting
point: record the changes so user can map them back to source. This
is more of memory aid, but its a start on understanding the issues. I
started a small Firebug extension to do this,
http://fbug.googlecode.com/svn/diff,
in case that may help you.
jjb
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
