[OctDev] RE: GUI for Octave programs.

[Julian A. de M. Ph.D <ju...@ma...>]

Hey, what a crazy name you have (pronunciation please?)!

So...

re: the CVS, yes, it's a hairball and I brought that up with Paul K;
partly it's a matter of where the matcompat (biggest/only upload so far)
got situated.  My own feeling is that each "PROJECT" should have its own
parent folder in the CVS.  So

	/matcompat/...
	/tk_octave/...

for starters.  This should clear up any mess, at least from a high-level
perspective it will keep any hairballs localised.  Let me see what the
other devs thinks.

re: JWE, yes, he's reluctant about anything GUI-related (he doesn't even
use X-Windows, strictly a command-line dude as far as I know).  But as
I said before, I think once the code carries its own weight any lead will
naturally turn into gold.  There's still no FORMAL arrangement about
pulling SF work into the main dist, but again I think that if the code
proves itself it will happen one way or another.  JWE runs a tight ship.
SF provides a popular means within the Octave community for parallel
efforts, and is thereby popularly de-facto legit.  TCL/TK is the best
proposition I've ever gleaned from the octave discussion archives on the
GUI issue.

Let me know when you get your SF handles registered.  Be sure to check the
SF HOW-TOs on CVS before you start uploading.

=jo...@us...

-----Original Message-----
From: Przemek Klosowski [mailto:pr...@ja...]
Sent: Tuesday, May 15, 2001 1:15 PM
To: ju...@ma...
Cc: jo...@ja...; pr...@ja...
Subject: Re: GUI for Octave programs.


   You'd get full co-dev access to CVS etc.
   All code @ octave.sourceforge.net is meant for eventual absorption into
the
   main dist.  Details are actually being worked out, but generally folks
agree
   that candidate code ought first demonstrate its worth before
consideration.
   The SF site is the community-preferred place for doing so.  If it seems
scant
   right now that's only b/c we've just gotten it off the ground again
following
   a big hiatus on the part of the original SF folks (had to pry the
passcodes
   out of their hands! -- just kidding).

OK, we'd be honored to work with you. I understand that this is what we'd
be doing:

  export CVS_RSH=ssh
  cvs -z3 -d:ext:dev...@cv...:/cvsroot/octave co
modulename

after we get the accounts and passwords (we'd ask for 'przemek' and 'johnc').

I had a little trouble figuring out the layout of the CVS tree

   contrib                       dld
Attic  scripts       Attic contrib dld scripts
      civil ode            scripts     numeric
    Attic   Attic        civil ode     image
 (newmark)  (ode)                      Attic
                                       (colormaps)

and finally:

                                     octave
Attic Fixes contrib           dld           nodld   non-free        scripts
ver20
            scripts   au/grph/libo/mex/..                     nonnumeric
numeric

so I take it that the correct path for our stuff might be something like

	cvsroot/octave/octave/dld/tk_octave

unless you are planning to move things around there.

Is it possible to collapse the tree by pulling out stuff from under
cvsroot/octave/octave into
cvsroot/octave/{Attic,Fixes,...}

We asked Joao Cardoso, and he responded that he isn't planning to further
develop tk_octave
and basically gave us the permission to carry on with the development (we
have to sort out
if our changes didn't take away any functionality---if not, we agreed that he
will repoint
his own page to sourceforge).

   All code @ octave.sourceforge.net is meant for eventual absorption into
the
   main dist.  Details are actually being worked out, but generally folks
agree
   that candidate code ought first demonstrate its worth before
consideration.

What's the latest on JWE's plans---I take it that he's not planning to have
octave's
sources on sourceforge, but is willing to pull out the most popular pieces
off
octave.sourceforge.net into the mainline release; am I close?

John wasn't enthusiastic about Tcl as a vehicle for GUI building when I
talked to him
last, but I think it's an attractive proposition and I am looking forward to
having
people try it.

			przemek