Re: settings tab when launching

From: Lachlan Deck (lachlan.dec..mail.com)
Date: Wed Mar 25 2009 - 20:42:06 EDT

  • Next message: David Avendasora: "WONoVA Web/Pod/Broadcast"

    On 26/03/2009, at 5:22 AM, Anjo Krank wrote:

    > Am 25.03.2009 um 19:12 schrieb Chuck Hill:
    >> I use it. Certainly some improvements could be made. I could live
    >> without it, but I suspect that it makes other people's lives easier.
    >
    > Does it? There are only a tiny handful settings one normally needs:
    > WOPort, WOHost, WODirectConnect and probably concurrent request
    > handling. And I still maintain that it's *way* easier and clearer to
    > set these as text in the normal launch tab.
    >
    > At the very least, the args should end up in the command line only
    > when they vary from the WO default setting - otherwise you (me) set
    > these things in the text panel and they get overridden by the wo
    > tab...

    I mostly agree with you Anjo though I see for newbies the usefulness
    of tick boxes.

    I don't like how they're all ticked by default overriding settings in
    the app/frameworks either. Usually there's only a few that I want to
    customise differently for a debug config but I find this more
    convenient adding them to named property files [1] and then just
    specifying one or two properties in the launch config to trigger the
    relevant additional properties.
    er.extensions.ERXProperties.OptionalConfigurationFiles=..config.dir@@/
    log4..config.name@@.properties,etc)

    But there are those who don't use wonder. At one point, a few months
    ago, I turned most of them off both in global prefs (for new launches)
    and in the existing launch configs but found that there's a number of
    them that if left unset cause problems. e.g., the lifebeat settings
    etc if left unset don't seem to configure the app to allow it to be
    non-direct connect etc. This is the trap for the uninitiated that I'd
    guess is trying to be avoided.

    Anyway, I'm all for reducing the list of default properties specified.
    It'd be better to only pre-define the defaults that are actually
    needed and allow a drop-down or something to allow the uninitialised
    to know what properties can be specified.

    [1] log4j.configName.properties, jdbc.configName.properties, etc

    with regards,

    --
    

    Lachlan Deck



    This archive was generated by hypermail 2.0.0 : Wed Mar 25 2009 - 20:43:17 EDT