But I'm finding it hard to do more things. For example: one of the panel is a php.log "tail", and I would like to alert me some how (for example changing the title of the panel adding the number of new lines in the file). How can I dinamically change the panel properties, open it, things like that? After registering the panel, how can I get it and work with it?
> But I'm finding it hard to do more things. For example: one of the panel is
> a php.log "tail", and I would like to alert me some how (for example
> changing the title of the panel adding the number of new lines in the
> file). How can I dinamically change the panel properties, open it, things
> like that? After registering the panel, how can I get it and work with it?
Well, if I strip out the XUL files, everything was straight forward for creating a panel in Lite. Some things like menu options did not work though.
Automatically generated docs from code would be great. I suppose I can manage reading the code too. I intend to share what I'm building too at some point.
On Tuesday, June 19, 2012 4:49:28 AM UTC-3, Jan Honza Odvarko wrote:
> On Jun 19, 5:23 am, Jose Luis Canciani <jose.canci...@gmail.com> > wrote: > > Hello! I'm using Firebug Lite in a custom dev framework I'm building.
> > I've follow Jan's excellent tutorials: > http://www.softwareishard.com/blog/firebug-tutorial/extending-firebug... > > and managed to build a panel that communicates with a node.js daemon to > > retrieve live information of whats going on in the server. > Note that the tutorial is for Firebug (the extension) not Firebug > Lite.
> I don't know about any tutorial for Firebug Lite.
> Would docs automatically generated from the source help in your case? > Or is reading formatted comments just ok?
> Honza
> > But I'm finding it hard to do more things. For example: one of the panel > is > > a php.log "tail", and I would like to alert me some how (for example > > changing the title of the panel adding the number of new lines in the > > file). How can I dinamically change the panel properties, open it, > things > > like that? After registering the panel, how can I get it and work with > it?
On Jun 19, 7:32 pm, Jose Luis Canciani <jose.canci...@gmail.com>
wrote:
> Well, if I strip out the XUL files, everything was straight forward for
> creating a panel in Lite. Some things like menu options did not work though.
Yep, some API are the same.
> Automatically generated docs from code would be great. I suppose I can
> manage reading the code too.
> > Automatically generated docs from code would be great. I suppose I can > > manage reading the code too. > We have been generating docs for Firebug source base in the past, > take a look here: > http://getfirebug.com/developer/api/firebug1.7/
I told you that the API docs could be useful, Honza.
I don't have time to code, I barely have time for my own projects ouside my
work, but I can help with moving to git (which I have experience with) and
maybe with time who knows.
Jose
On Wed, Jun 20, 2012 at 10:21 AM, Sebastian Zartner <
> I told you that the API docs could be useful, Honza.
> Sebastian
> --
> You received this message because you are subscribed to the Google
> Groups "Firebug" group.
> To post to this group, send email to firebug@googlegroups.com
> To unsubscribe from this group, send email to
> firebug+unsubscribe@googlegroups.com
> For more options, visit this group at
> https://groups.google.com/forum/#!forum/firebug
<sebastianzart...@googlemail.com> wrote:
> > > Automatically generated docs from code would be great. I suppose I can
> > > manage reading the code too.
> > We have been generating docs for Firebug source base in the past,
> > take a look here:
> >http://getfirebug.com/developer/api/firebug1.7/
> I told you that the API docs could be useful, Honza.
Of course it *could* be useful, but I am still not convinced
it's worth of the time/work. But you are welcome to maintain
the site Sebastian..
On Jun 20, 4:01 pm, Jose Luis Canciani <jose.canci...@gmail.com>
wrote:
> I don't have time to code, I barely have time for my own projects ouside my
> work, but I can help with moving to git (which I have experience with) and
> maybe with time who knows.
Simple transfer/copy to GIT is not that big issue.
I think that someone who is interested being involved should start
with examination
of the current directory structure and use the shift to GIT as an
opportunity
to improve it.
> > I told you that the API docs could be useful, Honza. > Of course it *could* be useful, but I am still not convinced > it's worth of the time/work. But you are welcome to maintain > the site Sebastian..
Generating the docs doesn't work on my system. If it were just some clicks, I'd do it. Though I also don't have much time for maintaining anything that goes beyond that.
