Re: Classes/methods docs anywhere?
45 views
Skip to first unread message
Jan Honza Odvarko
Jun 19, 2012, 3:49:28 AM6/19/12
to Firebug
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?
>
> Thanks!
> Jose.
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?
>
> Thanks!
> Jose.
Jose Luis Canciani
Jun 19, 2012, 1:32:40 PM6/19/12
to fir...@googlegroups.com
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.
Thanks,
Jose.
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.
Thanks,
Jose.
Jan Honza Odvarko
Jun 20, 2012, 2:03:04 AM6/20/12
to Firebug
On Jun 19, 7:32 pm, Jose Luis Canciani <jose.canci...@gmail.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/
But never got any feedback from dev folks so, we stopped it.
> I intend to share what I'm building too at
> some point.
That would be great!
Note that you can register on getfirebug.com/wiki and
create a new page describing your experience
Also, we currently don't have anyone who would maintain
Firebug Lite code, would you be interested to join us?
First step could be to move Firebug Lite source base
to github.com...
Honza
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.
> 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.
take a look here:
http://getfirebug.com/developer/api/firebug1.7/
But never got any feedback from dev folks so, we stopped it.
> I intend to share what I'm building too at
> some point.
Note that you can register on getfirebug.com/wiki and
create a new page describing your experience
Also, we currently don't have anyone who would maintain
Firebug Lite code, would you be interested to join us?
First step could be to move Firebug Lite source base
to github.com...
Honza
Sebastian Zartner
Jun 20, 2012, 9:21:12 AM6/20/12
to fir...@googlegroups.com
> 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/
Sebastian
Jose Luis Canciani
Jun 20, 2012, 10:01:09 AM6/20/12
to fir...@googlegroups.com
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
Jose
--
You received this message because you are subscribed to the Google
Groups "Firebug" group.
To post to this group, send email to fir...@googlegroups.com
To unsubscribe from this group, send email to
firebug+u...@googlegroups.com
For more options, visit this group at
https://groups.google.com/forum/#!forum/firebug
Jan Honza Odvarko
Jun 21, 2012, 2:30:32 AM6/21/12
to Firebug
On Jun 20, 3:21 pm, Sebastian Zartner
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..
Honza
it's worth of the time/work. But you are welcome to maintain
the site Sebastian..
Honza
Jan Honza Odvarko
Jun 21, 2012, 2:34:22 AM6/21/12
to Firebug
On Jun 20, 4:01 pm, Jose Luis Canciani <jose.canci...@gmail.com>
wrote:
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.
Honza
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.
> work, but I can help with moving to git (which I have experience with) and
> maybe with time who knows.
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.
Honza
Sebastian Zartner
Jun 22, 2012, 8:25:42 AM6/22/12
to fir...@googlegroups.com
> 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.
Sebastian
Though I also don't have much time for maintaining anything that goes beyond that.
Sebastian
Reply all
Reply to author
Forward
0 new messages