Hi John - I was thinking that defining an API would allow people to write server-side implementations of that API in a couple of common web languages, and the implementations could be shared with the firebug community.
Then, if someone wants to write a firebug plugin that logs some result on a server, they can just hook into the API, and assume the user has installed one of the implementations, instead of rolling their own back-end. As far as my particular use cases, you get a lot of email--more than I can keep up with--and I'm mainly interested in floating the API concept. But I'd like to use firebug to (1) edit js files and (2) save changes on the server-side. With the syntax highlighter and related plugins already out there, it seems like a 'save' or 'save and commit' button is the only missing piece. I'm not thinking about CSS, just JS. ________________________________ From: johnjbarton <[email protected]> To: Firebug <[email protected]> Sent: Thursday, July 30, 2009 2:26:46 PM Subject: Re: firebug server-side API? Do you mean: 1) Support for debugging Javascript/HTML/CSS running in a server? or 2) Support for debugging web pages in Browsers with additional interaction with servers? In the latter case, which I guess is your goal, see FirePhp. jjb On Jul 30, 9:56 am, Jared Hirsch <[email protected]> wrote: > Hi - I've been looking around on the web, but I can't find any discussion of > a server-side API for firebug. > > Is there interest in this? > Has it been discussed somewhere I haven't looked? > Is there a trivial reason not to bother that I've missed? > > Here's my thought: adding a generic server-side component would make it > super-easy to extend the usefulness of many plugins. My two motivating > use-cases are: > > (1) using such an API to allow performance-measurement tools to log results; > and > > (2) creating a firebug plugin to save edited javascript over the file on the > server-side, or save, then commit to the server-side VCS, which would make > firebug a 'real' IDE. > > Publishing an official API would allow devs to implement the > server-side component in their favorite server-side language without coupling > the client-side firebug plugin to a particular server-side implementation. > > Having server-side components already written and available would save that > much time for plugin developers. > > Any thoughts? Thanks - Jared --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
