Christoph Wilhelms wrote:
> Hmm... The current Antidote Forms are pretty generic and not really
> "composable".
I was composing new forms.
> Additionally I am not shure how complex a form within Antidoe could
> become, so that I see the value of using a visual gui designer, but let's wait
> and
Hi Jack
> > Oh-o... Let's see the generated GUI code, then. I never liked the
> > GUI-code NetBeans created.
>
> It's got its quirks but I am used to it. It allows really quick redesign
> of forms.
Hmm... The current Antidote Forms are pretty generic and not really
"composable". Additionally I a
Christoph Wilhelms wrote:
> Hi Jack!
>
> > 1. Check in minimal setting properties for Ant runs
> > from inside Antidote.
> >o May not really be useable but will preserve
> > some hard-worked code.
>
> Let's have a look :-)
Okay, as soon as I am able.
> >o Oops, anot
Hi Jack!
> 1. Check in minimal setting properties for Ant runs
> from inside Antidote.
>o May not really be useable but will preserve
> some hard-worked code.
Let's have a look :-)
>o Oops, another issue here: I'm using NetBeans
> so there are .form files I
Christoph Wilhelms wrote:
>
> >2. Another user mentioned on the mailing list that he can't set an
> > 'id' attribute in Antidote.
>
> Not shure what that means
See the archived message:
http://marc.theaimsgroup.com/?l=ant-dev&m=107832607829162&w=2
> > 4. GUI code editor
>
> Yes,
Hi Jack!
> 1. Set properties when running Ant from Antidote.
Yep! One of the most important things for the usability of Antidote!
> 2. Wizards
>1. project wizard.
>2. scripting wizard
Agreed
> 3. Simple functional features:
>1. Keeping up with Ant.
Very important
Let me expand on that list:
1. Set properties when running Ant from Antidote.
2. Wizards
1. project wizard.
2. scripting wizard
3. Simple functional features:
1. Keeping up with Ant.
2. Another user mentioned on the mailing list that he can't set an 'id'
attribut
