"Jack J. Woehr" wrote:
> I'll have to look at the sizing code for the editors to make this really nice.
I'm starting to think we're already at that point Swing programmers reach
when they realize they need a custom layout manager.
--
Jack J. Woehr # You measure democracy by the freedom it
S
Christoph Wilhelms wrote:
> > This diff makes window size persistent. It may not be the
> > most important persistent property, but it sure is annoying
> > to continually have to stretch the window to a size that
> > allows the editor gadgets to render themselves in a
> > reasonable fashion!
>
> F
Hi Jack!
> This diff makes window size persistent. It may not be the
> most important persistent property, but it sure is annoying
> to continually have to stretch the window to a size that
> allows the editor gadgets to render themselves in a
> reasonable fashion!
Fair improvement! Useful an
Puh! - I´m not the one who did the mistake :-)
Jan
> -Original Message-
> From: Jack Woehr [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 15, 2003 6:40 PM
> To: Ant Developers List
> Subject: Re: antidote diff
>
>
> peter reilly wrote:
>
> > i
peter reilly wrote:
> if the -d is missing, cvs does not check for new directories.
Arghh! Caught by the oldest trap in the business! :-)
--
Jack J. Woehr# "[F]ar in the empty sky a solitary esophagus slept
http://www.well.com/~jax # upon motionless wing; everywhere brooded stillne
On Monday 15 September 2003 16:48, Jack Woehr wrote:
>
> Hmm, I just updated my tree and ./build.sh yields the following:
>
> src/main/org/apache/tools/ant/types/selectors/SelectorContainer.java:59:
> package org.apache.tools.ant.types.selectors.modifiedselector does not
> exist import
You need t
Erik Hatcher wrote:
>
> I just committed a couple of fixes to bring proposal/xdocs back up to
> speed. Let me know if you encounter any issues running it. Again, run
> the "docs-from-scratch" target to get the full picture. Also, you'll
> need to bump up your memory allocation to get XDoclet ha
I just committed a couple of fixes to bring proposal/xdocs back up to
speed. Let me know if you encounter any issues running it. Again, run
the "docs-from-scratch" target to get the full picture. Also, you'll
need to bump up your memory allocation to get XDoclet happy. I do this:
se
On Monday, September 15, 2003, at 01:41 AM, Christoph Wilhelms wrote:
Atidote was relying on dtd description of tasks and types but i changed
this to introspection to gain more flexibility. Additionally the DTDs
quickly became outdated! There had be a plan to aotomatically generate
metadata/metain
Christoph Wilhelms wrote:
> It's an old, but just in some points outdated TODO-list. Feel free to
> pic up a task!
This is the same checked-in TODO list that is in the CVS tree, right?
Maybe the first step is to update the TODO list :-)
Let's look at some items from TODO List:
* Cleanup bu
[EMAIL PROTECTED] wrote:
> Christoph Wilhelms wrote:
>
> > One thing that has been started, but has never finished is a Wizard
> > for build-files! Would be nice if you could pick that task up!
>
> Is there a spec or design for this?
There's just the implementation you find in the code (wizard
Christoph Wilhelms wrote:
> One thing that has been started, but has never finished is a Wizard for
> build-files! Would be nice if you could pick that task up!
Is there a spec or design for this?
> Another thing not implemented is support for "xml-import"
Can you explain xml-import, please?
>
> [EMAIL PROTECTED] wrote:
> Christoph Wilhelms wrote:
>
> > Regarding Jacks Question:
> >
> > IIRC the only GUI-generated code in Antidote is the
> > dependency chooser
> > dialog, and it had been generated using VisualAge 2.0 (by myself in
> > early 2001). All other GUI code you find in Antid
Christoph Wilhelms wrote:
> Regarding Jacks Question:
>
> IIRC the only GUI-generated code in Antidote is the dependency chooser
> dialog, and it had been generated using VisualAge 2.0 (by myself in
> early 2001). All other GUI code you find in Antidote is particualry
> highly generic and hand cod
Hi Sefan, Jack and Conor!
> Antidote has had two or three phases of increased development
> efforts with longer breaks of inactivity in between. The
> last one has been winter/early spring this year IIRC. The
> Ant committer who's currently most interested in Antidote has
> switched jobs by
Stefan Bodewig wrote:
> How would that work I anybody wanted to modify the GUI, say add a
> button or something. Not using NetBeans, that is.
Well, that could be a pain. Not that you couldn't do it, and not that it would
be even difficult
- but -
the NetBeans fanatic would have to clean up af
On Thu, 11 Sep 2003, Jack J. Woehr <[EMAIL PROTECTED]> wrote:
> Forgive me, Stefan, I believe we have a misunderstanding.
Yes, we had.
> Use NetBeans to maintain the GUI classes.
As long as it doesn't prevent the GUI to be altered using a different
IDE, I'm totally on the fence here. Never use
Conor MacNeill wrote:
> IMHO, I don't think development should be tied to a single IDE.
Well, this is true, but a .java file GUI-edited under NetBeans is hand-editable.
You just don't hand-code inside the areas delineated by guard comments. I
hand-edit
Netbeans projects all the time.
It's just
Stefan Bodewig wrote:
> On Wed, 10 Sep 2003, Jack Woehr <[EMAIL PROTECTED]> wrote:
>
> > though since the last changes seem to have been February there is
> > probably a lot of scope for the interested coder!?
>
> Antidote has had two or three phases of increased development efforts
> with longer
On Thu, 11 Sep 2003 02:12 am, Jack Woehr wrote:
> If I were "attack" the GUI in that fashion (tossing it back into NetBeans)
> would that be acceptable or would that cross some guideline?
IMHO, I don't think development should be tied to a single IDE. You can, of
course, use the features of your
On Wed, 10 Sep 2003, Jack Woehr <[EMAIL PROTECTED]> wrote:
> though since the last changes seem to have been February there is
> probably a lot of scope for the interested coder!?
Antidote has had two or three phases of increased development efforts
with longer breaks of inactivity in between. T
On Wed, 10 Sep 2003, Lajos Pajtek <[EMAIL PROTECTED]> wrote:
> This cvs diff should fix the remaining javadoc warnings in
> antidote.
committed, thanks.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
Hi,
This cvs diff should fix the remaining javadoc warnings in
antidote.
LP.
--- "Jack J. Woehr" <[EMAIL PROTECTED]> wrote:
> Hi --
>
> I posted this on user@ ... maybe not the right place.
>
> Trivial antidote diff that clears up 7 of 15 javadoc warnings
> during build.
>
> Let me know if th
Stefan Bodewig wrote:
> > Trivial antidote diff that clears up 7 of 15 javadoc warnings during
> > build.
>
> Will be committed in a few seconds, thanks
Well, thank you. Will continue to wander through the source in my spare moments.
I grasp Antidote, not sure how far I can go, though since the
On Tue, 09 Sep 2003, Jack J. Woehr <[EMAIL PROTECTED]> wrote:
> I posted this on user@ ... maybe not the right place.
True, development stuff (including patches) should be on the dev list.
> Trivial antidote diff that clears up 7 of 15 javadoc warnings during
> build.
Will be committed in a few
25 matches
Mail list logo
