Hi guys That discussion seams to be very interesting for a web app developer like me ! I think I understand the issue that anyone will face trying to implement that popular 'save' feature in firebug. Correct me if I'm wrong, but the main problem is to map the changes made by the developer in firebug interface (let's call them objects built by firefox, or live object) and the source code. This is a big issue because from source files to DOM and CSS contents built by the browser, there is a long path (first server side computations, then style calculation from DOM tree and CSS, then possibly modification by a script and finally by user preference or another firefox plugin).
So I propose to start with something that reduce those problems to the minimum. First, CSS content is perhaps the one that is less changed before the browser loads it (generally no server side computation). Second, inline styles could be banned in order to focus only on external stylesheets. Third, the idea could be to create a new external stylesheet that can be saved locally, instead of modifying the source one, so that the addition of source one and our new firebug.css one would result in what developer obtained by modifying firebug built objects. Do you think this is the good direction to look to ? Personally, I don't think that integrate a text editor would be a good idea. I like the rigid edition possibilities offered by firebug : you can only do what is allowed (I mean that any meaningless code is immediately removed), and autocompletion is great ! Is there any news on the side of the small Firebug extension you started John J Barton ? If I can help you for this plugin development or test, it would be a pleasure. How can I fetch/compile/integrate/run/ test your piece of code ? Fabien On 31 déc 2008, 19:00, John J Barton <[email protected]> wrote: > 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: > savethe edits back to the server. Need server cooperation. > savethem 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 tosavechanged 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 -~----------~----~----~----~------~----~------~--~---
