[Chainsaw] Release point goals (was RE: new version moving into log4j-sandbox)

[Paul Smith <Pa...@lawlex.com.au>]

> It will be great if putting Scott's code into the sandbox will get
> the traction required to take the next version of Chainsaw from
> prototype to release quality. It does look great, but needs some
> good documentation and bugs ironed out.

That does raise a couple of interesting questions.  What should the group
decide is of sufficient quality for a supported release?  Just thinking
ahead of eventual integration back into the main jakarta-log4j module, we
should lay down some ground rules early on, so we can specifically target
those as important.

I'll start off this thread off by saying what features I think should be in
before release, others please add to the list, I can modify the Wiki with
all of them:

* Chainsaw should be as simple to install and run as possible, including
detailed documentation in a ReadMe.txt file to get it started.  Event an Ant
build.xml would be a nice bundled addition.  The easier it is to get
started, the more viral it becomes (just like Log4j is!).

* Chainsaw should be distributed with complete online help, via the Welcome
Panel that's currently in Scott's jar that's flying around at the moment, or
equivalent.  This online help should go through a walkthrough of important
features of Chainsaw (filtering, colouring, preferences, tips etc).

* All major UI action elements should have appropriate Hotkeys, mnemonics,
menu, toolbar integration.

* A list of test suites, which may have to be manually run, to determine
whether the GUI passes a level of quality.  ie. Loading of a specific XML
file of events and verifying output, and following a series of mouse clicks
to ensure expected behaviour (be nice to automate this, but... ?) This is
particularly important as we move on from the initial supported release.

Really Nice to haves, but not critical:

* A nicer Logo in the Title bar than the default Java logo!  I tried the
Log4j logo, but it just don't look professional at that small size... Anyone
with some design skills, or some buddies who could make one? 

thoughts anyone?

cheers,

Paul Smith

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

Re: [Chainsaw] Release point goals (was RE: new version moving into log4j-sandbox)

[Richard Bair <rb...@yahoo.com>]

> What about using one of JUnit extensions for testing
> Java GUI / Swing?
> Some have recording features.
> 
> http://www.junit.org/news/extension/gui/index.htm
> 
> R.Parr
> Temporal Arts

Wow, there are a lot of 'em!  Any experience with
these, which work best etc?

Richard

__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

Re: [Chainsaw] Release point goals (was RE: new version moving into log4j-sandbox)

["Randall J. Parr" <RP...@TemporalArts.COM>]

Richard Bair wrote:

>>* A list of test suites, which may have to be
>>manually run, to determine
>>whether the GUI passes a level of quality.  ie.
>>Loading of a specific XML
>>file of events and verifying output, and following a
>>series of mouse clicks
>>to ensure expected behaviour (be nice to automate
>>this, but... ?) This is
>>particularly important as we move on from the
>>initial supported release.
>>    
>>
>
>Well, it isn't open source, but Rational has a product
>that does "macro" style automated testing.  I don't
>have it, but if someone does, you could do the "click"
>test.
>  
>
What about using one of JUnit extensions for testing Java GUI / Swing?
Some have recording features.

http://www.junit.org/news/extension/gui/index.htm

R.Parr
Temporal Arts



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

Re: [Chainsaw] Release point goals (was RE: new version moving into log4j-sandbox)

[Richard Bair <rb...@yahoo.com>]

> * A list of test suites, which may have to be
> manually run, to determine
> whether the GUI passes a level of quality.  ie.
> Loading of a specific XML
> file of events and verifying output, and following a
> series of mouse clicks
> to ensure expected behaviour (be nice to automate
> this, but... ?) This is
> particularly important as we move on from the
> initial supported release.

Well, it isn't open source, but Rational has a product
that does "macro" style automated testing.  I don't
have it, but if someone does, you could do the "click"
test.

Richard

<irrelevant_question>
    I wonder if Rational products can be purchased as
plugins for eclipse since they use the eclipse
framework?
</irrelevant_question>

__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

RE: [Chainsaw] Release point goals (was RE: new version moving into log4j-sandbox)

[Oliver Burn <ol...@puppycrawl.com>]

What you describe sounds good. Remember, the more features, the more
tests and document to be written. ;-)

Oliver

> -----Original Message-----
> From: Paul Smith [mailto:Paul.Smith@lawlex.com.au]
> Sent: Thursday, 24 April 2003 15:06
> To: 'Log4J Developers List'
> Subject: [Chainsaw] Release point goals (was RE: new version moving into
> log4j-sandbox)
>
>
> > It will be great if putting Scott's code into the sandbox will get
> > the traction required to take the next version of Chainsaw from
> > prototype to release quality. It does look great, but needs some
> > good documentation and bugs ironed out.
>
> That does raise a couple of interesting questions.  What should the group
> decide is of sufficient quality for a supported release?  Just thinking
> ahead of eventual integration back into the main jakarta-log4j module, we
> should lay down some ground rules early on, so we can specifically target
> those as important.
>
> I'll start off this thread off by saying what features I think
> should be in
> before release, others please add to the list, I can modify the Wiki with
> all of them:
>
> * Chainsaw should be as simple to install and run as possible, including
> detailed documentation in a ReadMe.txt file to get it started.
> Event an Ant
> build.xml would be a nice bundled addition.  The easier it is to get
> started, the more viral it becomes (just like Log4j is!).
>
> * Chainsaw should be distributed with complete online help, via
> the Welcome
> Panel that's currently in Scott's jar that's flying around at
> the moment, or
> equivalent.  This online help should go through a walkthrough of
> important
> features of Chainsaw (filtering, colouring, preferences, tips etc).
>
> * All major UI action elements should have appropriate Hotkeys,
> mnemonics,
> menu, toolbar integration.
>
> * A list of test suites, which may have to be manually run, to determine
> whether the GUI passes a level of quality.  ie. Loading of a specific XML
> file of events and verifying output, and following a series of
> mouse clicks
> to ensure expected behaviour (be nice to automate this, but... ?) This is
> particularly important as we move on from the initial supported release.
>
> Really Nice to haves, but not critical:
>
> * A nicer Logo in the Title bar than the default Java logo!  I tried the
> Log4j logo, but it just don't look professional at that small
> size... Anyone
> with some design skills, or some buddies who could make one?
>
> thoughts anyone?
>
> cheers,
>
> Paul Smith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org