Thread: [Plplot-cvs] CVS update notice (plplot/examples/tcl) (Page 3)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv24820/examples/tcl

Modified Files:
	tclIndex 
Log Message:
completed support and examples of plmap

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv8021/examples/tcl

Modified Files:
	x01.tcl 
Added Files:
	x19.tcl 
Log Message:
plmeridians added, including demo

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv23244

Modified Files:
	x01.tcl 
Log Message:
Drop extraneous pladv that was just put in.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv3667/examples/tcl

Modified Files:
	x01.tcl x02.tcl 
Log Message:
Put in the required extra pladv at the start of the first tcl and python
examples.  For both the first and second examples, comment the reason why
this extra pladv call is required before the call to plssub.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv13038

Modified Files:
	tcldemos.tcl 
Log Message:
Allow x19.tcl to run

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv21677a

Modified Files:
	x19.tcl 
Log Message:
Dropped plflush.  The documentation says this should rarely if ever be used,
and everything seemed fine without it.

Dropped pleop at end.  I think this will cause extra blank pages for some
drivers, and no other example uses this except for weird situations
with plssub.

The new version was tested with the xwin, tk, psc, and png devices under
pltcl and no problems were found.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv5997

Modified Files:
	x09.tcl 
Log Message:
speed up demo

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv10498/examples/tcl

Modified Files:
	x08.tcl 
Log Message:
Include plotfc3d in tcl API and change example 8 to use it.  The result
is identical to C and python examples 8.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv2456

Modified Files:
	README.tcldemos 
Log Message:
Change documentation to be consistent with new tclsh recipe.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv17445/examples/tcl

Modified Files:
	x08.tcl 
Log Message:
Add support for plsurf3d() and remove plotfc3d() and plotsh3d() wich are now obsolete.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv9557

Modified Files:
	x08.tcl 
Log Message:
Remove opt from title to be consistent with revised C example.
Remove extraneous cmap1_init call since that does not affect plplot3d call.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory usw-pr-cvs1:/tmp/cvs-serv4274/examples/tcl

Modified Files:
	x08.tcl 
Log Message:
Use a syntax that seems to improve accuracy, as per Vince Darley advice.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory sc8-pr-cvs1:/tmp/cvs-serv24720/examples/tcl

Added Files:
      Tag: AT
	.cvsignore Makefile.am 
Log Message:
Finish AT tcl binding.  These are only small fairly non-consequential 
refinements that I did while trying to debug the extended search problem
(which had a simple solution which I will discuss on list).

Prepare the start of the tk and tk-x-plat bindings by dropping "plplot/"
from the #include statements in the source files.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory sc8-pr-cvs1:/tmp/cvs-serv3785

Modified Files:
      Tag: AT
	README.tcldemos 
Log Message:
Better commentary which includes discussion of setting PL_LIBRARY when the
tcl search routine cannot find the plplot system tcl scripts.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory sc8-pr-cvs1:/tmp/cvs-serv1878

Modified Files:
      Tag: AT
	.cvsignore 
Removed Files:
      Tag: AT
	tclIndex 
Log Message:
tclIndex is a generated file so it does not belong in cvs.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory sc8-pr-cvs1:/tmp/cvs-serv13122/examples/tcl

Modified Files:
	README.tcldemos 
Added Files:
	.cvsignore Makefile.am 
Removed Files:
	tclIndex 
Log Message:
Merged AT branch into MAIN, a new configuration era has started

Update of /cvsroot/plplot/plplot/examples/tcl
In directory sc8-pr-cvs1:/tmp/cvs-serv4686/examples/tcl

Modified Files:
	Makefile.am 
Log Message:
Tweak install logic for cases where python, tcl, or tk are not enabled.

Update of /cvsroot/plplot/plplot/examples/tcl
In directory sc8-pr-cvs1:/tmp/cvs-serv24055

Modified Files:
	.cvsignore 
Log Message:
tweak

Update of /cvsroot/plplot/plplot/examples/tcl
In directory sc8-pr-cvs1:/tmp/cvs-serv3076

Added Files:
	tclIndex 
Log Message:
adding tclIndex to allow win-tk to operate correctly

Vince Darley writes:
 > Update of /cvsroot/plplot/plplot/examples/tcl
 > In directory sc8-pr-cvs1:/tmp/cvs-serv3076
 > 
 > Added Files:
 > 	tclIndex 
 > Log Message:
 > adding tclIndex to allow win-tk to operate correctly

This file should be generated at build time, not checked into the repository.

-- 
Maurice LeBrun    mj...@ga...
Research Organization for Information Science and Technology of Japan (RIST)

If plplot would like to be more friendly to windows, it would be easier if
this were not the case, especially since this file is hardly one that
changes every few months...

If you feel strongly, please delete and I'll add a workaround to the
win-tk directory.

Vince.

On Fri, 20 Dec 2002, Maurice LeBrun wrote:
>  > adding tclIndex to allow win-tk to operate correctly
> This file should be generated at build time, not checked into the repository.

It's a bad thing to have in there, b/c the version of tclIndex produced by the
build is always going to be definitive.  Thus the cvs copy of tclIndex is
going to be nearly constantly out of date.  So yeah, if you don't want to
build this under windows, you should make a static copy and keep it in the
system-dependent dirs, but realize then that you are personally responsible
for keeping it up to date.  If indeed we go for a year without you needing
to update it then great.  

Vince Darley writes:
 > If plplot would like to be more friendly to windows, it would be easier if
 > this were not the case, especially since this file is hardly one that
 > changes every few months...
 > 
 > If you feel strongly, please delete and I'll add a workaround to the
 > win-tk directory.
 > 
 > Vince.
 > 
 > On Fri, 20 Dec 2002, Maurice LeBrun wrote:
 > >  > adding tclIndex to allow win-tk to operate correctly
 > > This file should be generated at build time, not checked into the repository.

-- 
Maurice LeBrun    mj...@ga...
Research Organization for Information Science and Technology of Japan (RIST)

On Fri, 20 Dec 2002, Maurice LeBrun wrote:
> It's a bad thing to have in there, b/c the version of tclIndex produced by the
> build is always going to be definitive.  Thus the cvs copy of tclIndex is
> going to be nearly constantly out of date.  So yeah, if you don't want to
                    ^**********^

Sorry, I didn't realise the Tcl examples directory was nearly constantly
under development ;-)

I do think it is a shame that you suggest such a unix-centric approach,
however.  It doesn't encourage non-unix developers when they see a
supposed build directory littered with weird files that don't really
belong there, and are harder to keep up to date by virtue of being in an
out of the way place.

It is already a hassle building plplot on any other platform, especially
with random configuration, include and version changes which need to be
followed so I don't really understand why you're trying to raise the bar
even higher.

As Alan points out, of course all this stuff *can* be generated by me or
others or for a distribution, but the question is *why*.  If someone is
actually fixing some Tcl code, presumably they know enough about Tcl to
run 'auto_mkindex' when needed and commit the change.  That way the job
happens just once, and by someone who knows what they're doing.  Instead
the position which seems to be advocated is that this should be encoded
with some rule in some makefile or configuration file (or, god forbid,
some special makefile to build a distribution).

As you can see, we seem to have some philosophical differences here about
what is truly 'simpler' and what is 'a pain in the neck'.  I'm sure your
position is perfectly accurate from a unix perspective.  So that's the
kind of user and developer you are likely to attract to plplot, and the
others will be more likely to be turned off.

I'll finish my rant now and commit the necessary changes so it is at least
possible to use plplot with Windows-Tk again.

cheers,

Vince.

Vince Darley writes:
 > On Fri, 20 Dec 2002, Maurice LeBrun wrote:
 > > It's a bad thing to have in there, b/c the version of tclIndex produced by the
 > > build is always going to be definitive.  Thus the cvs copy of tclIndex is
 > > going to be nearly constantly out of date.  So yeah, if you don't want to
 >                     ^**********^
 > 
 > Sorry, I didn't realise the Tcl examples directory was nearly constantly
 > under development ;-)

When I said "out of date", I am talking from a cvs perspective.  When the
package is built, it will produce a new version of tclIndex every time an
example program is changed *in any way*.  Then next time you run 'cvs status'
or 'cvs -nq update' you will see that tclIndex needs to be checked in, even
though there may be no actual changes of consequence to it.  So then you
either ignore the false out-of-date-ness (bad, because 1/100 times it may not
actually be false), or you commit a new version of tclIndex every time you
make any change no matter how trivial to any example program (stupid).

This kind of situation is dangerous and easily avoided.

 > I do think it is a shame that you suggest such a unix-centric approach,
 > however.  It doesn't encourage non-unix developers when they see a
 > supposed build directory littered with weird files that don't really
 > belong there, and are harder to keep up to date by virtue of being in an
 > out of the way place.

I'm coming from a tool-centric approach, i.e. make & cvs & Tcl, as well
as the general rule of thumb that generated files do not belong in a
cvs repository.  It's ok to make some exceptions to this but tclIndex
files are easy & quick to build; you just need a tcl shell of the
right type which you are guaranteed to have at the end of the build.

 > It is already a hassle building plplot on any other platform, especially
 > with random configuration, include and version changes which need to be
 > followed so I don't really understand why you're trying to raise the bar
 > even higher.

I don't understand what it is about cygwin that makes including generating
a tclIndex so hard.

 > As Alan points out, of course all this stuff *can* be generated by me or
 > others or for a distribution, but the question is *why*.  If someone is
 > actually fixing some Tcl code, presumably they know enough about Tcl to
 > run 'auto_mkindex' when needed and commit the change.  That way the job
 > happens just once, and by someone who knows what they're doing.  Instead
 > the position which seems to be advocated is that this should be encoded
 > with some rule in some makefile or configuration file (or, god forbid,
 > some special makefile to build a distribution).

Things that can be automated, should be automated, because the fewer petty
details a developer has to remember, the less mistakes one makes, and the
better one can focus on real issues.

-- 
Maurice LeBrun    mj...@ga...
Research Organization for Information Science and Technology of Japan (RIST)

On Fri, 20 Dec 2002, Vince Darley wrote:

> If plplot would like to be more friendly to windows, it would be easier if
> this were not the case, especially since this file is hardly one that
> changes every few months...
>
> If you feel strongly, please delete and I'll add a workaround to the
> win-tk directory.

I agree strongly with Maurice on this one.  Probably there are some
exceptions which we are still hunting down, but we generally have been able
to keep all generated files out of CVS since we assume our CVS users have a
full application environment.  The real judgement call is whether to
generate those files for the distribution tarball (thus relieving general
users of the requirement of importing special applications [e.g., swig is
required for generating the python interface source code, and perl is
required for generating the tcl interface code].) Assuming you put together
some nmake rule for generating tclIndex, will that rule require a special
application like swig or perl?  Or can you generate tclIndex using tcl?

Alan

email: ir...@be...
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6
__________________________

Linux-powered astrophysics
__________________________

Thread: [Plplot-cvs] CVS update notice (plplot/examples/tcl) (Page 3)

Cross-platform, scientific graphics plotting library

plplot-cvs