Status Update

3 views
Skip to first unread message

Christoph Dorn

unread,
Jun 21, 2010, 11:05:01 PM6/21/10
to FireConsole
I want to give everyone an update as to the status of FireConsole
since the alpha release in February.

Based on feedback and testing I had to make some changes to various
areas and put further releases on hold.

For the past few months my focus has been on smoothing the transition
for existing FirePHP users, stabilizing the communication protocol and
various other supporting projects.

As some of you may be aware, FireConsole is to replace the existing
FirePHP extension for the purpose of logging from PHP to Firebug. This
is a limited use-case for the overall concept of logging-based
debugging.

In designing FireConsole and FirePHP 1.0 I split the original FirePHP
components into several projects that can support much more advanced
features than simply logging to the Firebug Console. These new
projects [1][2] are structured in such a way that they may be ported
to other programming languages.

On the client side I have been working on an alternative client for
FirePHP called FirePHP Companion. The idea behind FirePHP Companion is
to provide simple console-based logging (just like FireConsole) but go
a step further by evolving the logging-based debugging concept in
various areas. Some of this functionality is now available, much more
is coming.

You can take a look at what is now possible with FirePHP 1.0 by taking
a look at the FirePHP Companion preview:

http://companion.firephp.org/

My plan is to officially release FirePHP Companion and then bring
FireConsole up to speed. FireConsole will use the same rendering
templates as FirePHP Companion but focus on rendering data in various
Firebug panels. Once the next FireConsole release is done I will be
actively maintaining both projects and making parallel releases on a
regular basis.

I am looking for feedback on FirePHP Companion and the FirePHP 1.0
library. FirePHP Companion is a for-fee product but anyone who
participates in the testing and feedback process will receive a
lifetime license (including updates).

Christoph

[1] - http://github.com/cadorn/wildfire
[2] - http://github.com/cadorn/insight

Gunnar Wagenknecht

unread,
Jun 22, 2010, 3:10:30 AM6/22/10
to firec...@googlegroups.com
Hi,

Am 22.06.2010 05:05, schrieb Christoph Dorn:
> I am looking for feedback on FirePHP Companion and the FirePHP 1.0

> library. [...]

I'm monitoring this list because I've written a Wildfire based logging
integration for SLF4J which is released under EPL here:

CVS View:
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.gyrex/platform/bundles/org.eclipse.gyrex.log.http/?root=Technology_Project

Project URL:
http://www.eclipse.org/gyrex/

The only feedback that I have is that I'd appreciate some more
clarification between the amount of tools that are coming. It's a bit
challenging for me to identify the tools that I need to support in
future. Will it be FirePHP, FireConsole, Fire PHP Companion, Insight, or
yet another client/extension? Is there a roadmap somewhere and some
guide on what I need to implement in order to support X/Y/Z?

What should also help would be some screencasts demonstrating the
various tools and libraries and how they are intended to work together.

HTH,
Gunnar

--
Gunnar Wagenknecht
gun...@wagenknecht.org
http://wagenknecht.org/

Christoph Dorn

unread,
Jun 23, 2010, 6:19:02 PM6/23/10
to firec...@googlegroups.com
On 10-06-22 12:10 AM, Gunnar Wagenknecht wrote:
> Am 22.06.2010 05:05, schrieb Christoph Dorn:
>> I am looking for feedback on FirePHP Companion and the FirePHP 1.0
>> library. [...]
>
> I'm monitoring this list because I've written a Wildfire based logging
> integration for SLF4J which is released under EPL here:
>
> CVS View:
> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.gyrex/platform/bundles/org.eclipse.gyrex.log.http/?root=Technology_Project
>
> Project URL:
> http://www.eclipse.org/gyrex/

I have added your library to the wiki:

http://www.firephp.org/Wiki/Libraries/Java


> The only feedback that I have is that I'd appreciate some more
> clarification between the amount of tools that are coming. It's a bit
> challenging for me to identify the tools that I need to support in
> future. Will it be FirePHP, FireConsole, Fire PHP Companion, Insight, or
> yet another client/extension? Is there a roadmap somewhere and some
> guide on what I need to implement in order to support X/Y/Z?

You make a valid point :)

I have not had the chance to put together a roadmap nor implementers
guide. You can find an overview of the projects and how they fit
together here:

http://groups.google.com/group/fireconsole/browse_thread/thread/9016d98190158233/05901931b6ca4344

In summary, once we have a java port of wildfire and insight you can
simply provide your own wrapper that hooks into the frameworks you are
using.

If you are interested in assisting with the Java port please let Thomas
and I know.


> What should also help would be some screencasts demonstrating the
> various tools and libraries and how they are intended to work together.

I will begin publishing screencasts shortly. If there are specific
topics please let me know.

Christoph


Christoph Dorn

unread,
Jul 22, 2010, 2:41:06 PM7/22/10
to FireConsole
I have put up a screencast introducing FirePHP Companion:
http://companion.firephp.org/

Christoph

Christoph Dorn

unread,
Jul 26, 2010, 9:58:18 PM7/26/10
to FireConsole
FirePHP Companion and FirePHP 1.0 (server library) development is
progressing: http://reference.developercompanion.com/Companion/News/

If you have not had a chance to check out FirePHP Companion I
encourage you to do so: http://companion.firephp.org/

Christoph
Reply all
Reply to author
Forward
0 new messages