How to set the server debugger in seaside?

Hi guys

I hate so much this bad configuration interface of seaside.
I lose all the time 20 min to find how to set the debugger.
So I have to do a presentation and I cannot show the debugger.
What a great wonderful experience.

How can I configure seaside to get the debugger?

Stef

On 02/02/2016 09:47, stepharo wrote: If I remember well on http://localhost:8080/config add a Filter. Then
click on «Configure» next to «WAExceptionFilter». In «Exception Handler»
select the debugger.

--
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France

Thanks this is so inintuitive that I forget 5 min after.

Le 2/2/16 09:56, Cyril Ferlicot Delbecque a écrit :

Le 04/02/2016 22:42, stepharo a écrit :
> Thanks this is so inintuitive that I forget 5 min after.
>
>
>

If I don't use seaside for more than a week, I need 5-10min to find it.

Maybe you can set it at the registry like:

MyComponant class>>initialize

    (WAAdmin register: self asApplicationAt: 'myApp') exceptionHandler:
WADebugErrorHandler


And remove it for production.

--
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France

On 02/02/16 09:47, stepharo wrote:
> Hi guys
>
> I hate so much this bad configuration interface of seaside.
> I lose all the time 20 min to find how to set the debugger.
> So I have to do a presentation and I cannot show the debugger.
> What a great wonderful experience.
>
> How can I configure seaside to get the debugger?

We've added some convenience methods for this, making it easy to deploy
both production and development, and making it possible to make the
application the default application.

QCApplication class>registerAt: anApplicationName
        ^(WAAdmin register: self asApplicationAt: anApplicationName)
                preferenceAt: #sessionClass put: self sessionClass;
                addLibrary: JQDeploymentLibrary;
                addLibrary: JQUiDeploymentLibrary;
                yourself

QCApplication class>registerForDevelopmentAt: anApplicationName
        | application |
        WAAdmin enableDevelopmentTools.
        application := self registerAt: anApplicationName.
        application filter configuration at: #exceptionHandler put:
WADebugErrorHandler.
        (self overridesDefaults includes: WAAdmin defaultDispatcher defaultName)
                ifTrue: [ WAAdmin defaultDispatcher defaultName: anApplicationName ].
        ^application

QCApplication class>registerForProductionAt: anApplicationName
        | application |
        application := self registerAt: anApplicationName.
        WAAdmin disableDevelopmentTools.
        WAAdmin defaultDispatcher defaultName: anApplicationName.
        ^application

Stef,

You know you can contribute and improve it?

You should remember a bit more the talk of Kim Mackinnon in Cambridge…
This negative way of talking about work of others is not the way to get things done.
I don’t think you would appreciate someone mailing this way about the Pharo interface.

In 3.2, the debugger exception handler is the default for development.
There is also the programmatic way of changing this:

(WAAdmin defaultDispatcher handlerAt: ‘YourApp’) exceptionHandler: WADebugErrorHandler

cheers
Johan