On Oct 3, 4:51 pm, James Carpenter <[email protected]> wrote:
> Thank you,
>
> An extension seems like a logical approach. I didn't head that way
> originally due to my lack of experience creating them.
>
> Having said that, I would greatly appreciate any assistance you could
> provide to get me started on the extension.
OK, I'll crate a skeleton extension for you.
I'll probably put the code on my github.com/janodvarko account and
then we can share it.

> I am looking to roll a
> solution out to my internal team of developers ASAP, as this is a real pain
> point for us.
>
> My top priority would be getting this working for the less CSS output, as
> the Sass world already has a extension that works (though we are not using
> Sass, so that is an assumption).
>
> I was also wondering if it was possible to get access to the cached version
> of the style sheet that firebug has already loaded from within an extension
> (as I am doing from within the code I sent a pull request for).
I need to yet go over your pull request, but we can improve Firebug
API if it isn't already possible to do what you need from within an
extension.

> From my
> minimal understanding of the Sass plugin, it looks like it is loading and
> caching the stylesheets (pulling every sheet for a 3rd time? between the
> browser, firebug, and the Sass plugin).  Again, I may be misunderstanding
> this, but I don't want to create this plugin at the expense of reasonable
> performance.
>
> I will create an issue report and set up a public facing demo in the near
> future.
Great, thanks

Honza

>
> Thanks again for you help and feedback.
> James Carpenter
>
>
>
>
>
>
>
> On Wednesday, October 3, 2012 2:34:27 AM UTC-4, Jan Honza Odvarko wrote:
>
> > We have been discussing the feature at yesterday's Firebug weekly
> > meeting
> > and this is what we agreed on.
>
> > 1) The feature is great, but it would be better to have it implemented
> > as an extension that shows how it works and can be used to get
> > feedback
> > from users
>
> > 2) Any fixes and/or API improvements in Firebug code base that are
> > needed to actually implement the extension can be committed of course.
>
> > 3) It would be great to have an issue reported in Firebug issue list
> > so, we can track progress on the extension and any requirements for
> > Firebug API improvements.
>
> > Please let me know if you want me to help with the basic skeleton
> > of the extension. I can do it for you.
>
> > Honza
>
> > On Oct 1, 9:06 pm, James Carpenter <[email protected]> wrote:
> > > Thank you very much for pointing me in the right direction.
>
> > > I have spent several days reviewing the code so I can hopefully offer a
> > > contribution without "mucking up the works."
>
> > > I submitted a pull request with a detailed explanation of what the
> > change
> > > does and why it is important as the server side CSS frameworks become
> > > more prevalent.  I hope that it is strongly considered.
>
> > > If the pull request should be denied, is it even possible to modify the
> > > reported css file and line number in the script panel?  I was looking
> > > through the API, and it appears like I can do a LOT with it, but I am
> > not
> > > seeing how I would modify the Style Sidebar Panel, or even how I would
> > know
> > > what object structure to start traversing. (Please forgive my lack of
> > > understanding of the plugin. While I have been using it for a long time,
> > > and I am spending a lot of time with it as of late, I am still VERY new
> > to
> > > the inner-workings of Firebug)
>
> > > Thanks again for all your help,
> > > James Carpenter
>
> > > On Tuesday, September 25, 2012 1:48:59 PM UTC-4, James Carpenter wrote:
>
> > > > Hello All,
>
> > > > I am working on a custom mod to firebug that would make it be aware of
> > CSS
> > > > frameworks like less. (I know there is a plugins for sass, but we are
> > using
> > > > less)
>
> > > > I am trying (unsuccessfully) to locate the file where the css files
> > are
> > > > parsed, and the line numbers are calculated.  I hope to make a custom
> > build
> > > > of firebug with a minor tweak to make it aware of the debug output
> > from a
> > > > less css install.  I will be posting my work to Github, and will make
> > the
> > > > code available once I have it up and running.
> > > >https://github.com/jc4rp3nt3r/firebug
>
> > > > Thanks ahead of time for pointing me in the right direction.
>
> > > > James Carpenter

-- 
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
https://groups.google.com/forum/#!forum/firebug

Reply via email to