Re: [Tclweb-admin] hello!

[Brent W. <we...@aj...>]

I'm interested in helping.
It looks like "dev.scriptics.com" will remain up for the indefinite
future, by the way, although I will probably be dismantling some features
that don't make as much sense anymore.  I'm also not %100 happy with
AOLserver there.  *BUT*, I am very happy with the Tcl infrastructure
I've created for TclHttpd and ported to AOLserver.  Unfortunately,
KAP doesn't support the 100's of pages I have developed, nor the
more flexible extension mechanism (not just templates, but a means
to "eval" a Tcl command to implement a page.)  If you can do a very
basic, general eval hook in KAP, then I can implement whatever
framework I need.  Any progress on that?

>>>"Mark Harrison" said:
 > If you're receiving this message, it's because at some time or
 > another we have discussed tcltk.com.  Now that some of the other
 > things I've been working on for the TCT (such as sourceforge)
 > are well under way, I want to get this project going.
 > 
 > If you're not interested, then maximum apologies to you.
 > 
 > I want to make the new tcltk.com (also known as tcltk.org)
 > a useful site that works in conjunction with the sourceforge
 > site.
 > 
 > I would like to recruit a number of "content editors" who are
 > interested in working on a particular part of the website
 > which might interest them.  That's why you're receiving this
 > message.
 > 
 > Here is my vision for how things will be set up:
 > 
 > We have a linux box hosted by Verio running
 >     apache
 >     KAP (embeds tcl into web pages)
 >     mysql
 > 
 > All the web content is managed via cvs.  I've had some good
 > luck with this approach at some of our customer sites.  You
 > can back things out, see what crackers have done, etc.
 > It's also nice for distributed management, since modifications
 > are made to the repository instead of being put directly
 > on the site.
 > 
 > I've created the "tclweb" project to support this.  Changes are
 > pushed onto the "tclweb" cvs repository, and then populated (by
 > some means) to the server machine.
 > 
 > This is an easily clonable setup, which gives two advantages:
 > 
 > 1.  It's easy for someone to set up a mirror site.  Put the
 >     software on your system, and checkout the content from
 >     sourceforge.
 > 
 > 2.  It's easy for someone to stage... if you're a content
 >     editor, just run the software on your own linux box and
 >     edit the content as you like.  When it's reached the
 >     point of perfection, just "cvs commit" and have it
 >     automatically pushed onto the web site.  If you goof
 >     up, do any of the normal cvs things and have the content
 >     restored as you like it.
 > 
 > My own feeling is that tcltk.com does not need to be a
 > "comprehensive" portal site, but should be a good starting
 > point for anyone needing to find tcl resources.  That's why
 > my first efforts were aimed at pushing as many things as possible
 > over to sourceforge.  I don't want to do everything, but instead
 > focus on the maximum return on (time) investment.
 > 
 > I'm also tending to downplay this quarter's suddenly hot "p2p"
 > personalization trend.  It can provide some value, but I think
 > that the relative effort is a bit high for the value received.
 > 
 > Anyways, I'm interested in what you think...  let me know!
 > 
 > Mark
 > 
 > --
 > Mark Harrison                          AsiaInfo Holdings, Inc.
 > ma...@us...                Beijing/Santa Clara
 > 
 > _______________________________________________
 > Tclweb-admin mailing list
 > Tcl...@li...
 > http://lists.sourceforge.net/mailman/listinfo/tclweb-admin

--	Brent Welch	<we...@aj...>
	http://www.ajubasolutions.com
	Scriptics changes to Ajuba Solutions
	scriptics.com => ajubasolutions.com