[Bese-devel] UCW: The Future.

[thomas.elam at wipro.com]

Thanks for the great news, Drew!

I used ucw-ajax 2 years ago for over half a year and loved it. I created
AJAX-based buttons overlaying an image so the end-user could get and set
some information related to employee's workstations on a particular
floor of a building by `calling' a new component containing tables and
textareas -- and returning results to the `calling' component. Linear
coding based on Web continuations! I'm sold!

The user could view maps of different floors at the same time, each in
its own Dojo tab. He could also view the results of my very flexible and
simple queries from an Elephant persistent-object database (on top of
bdb) in a Dojo SortableTable rendered in other Dojo tab. This was all at
a time when Dojo would have been at its 0.4 release level, I think.

I am still very interested in UCW and might use it in my current
project. (I also want to see whether and how it is possible to do Web
continuations using client-side closures, perhaps obviating UCW.)

I volunteered and worked a tiny bit on Ties Stuij's `UCW Intro'
(http://trac.common-lisp.net/ucw/wiki/UcwIntro), but I don't know if any
of my words are still there.

I hereby volunteer to help you with some writing work. I don't consider
myself a Lisp wizard, though. Navigating UCW's code and examples was a
bit tough for me last time I looked.

Regards,
Tom

-----Original Message-----
From: bese-devel-bounces at common-lisp.net
[mailto:bese-devel-bounces at common-lisp.net] On Behalf Of Drew Crampsie
Sent: Wednesday, April 30, 2008 3:23 AM
To: bese-devel at common-lisp.net
Subject: [Bese-devel] UCW: The Future.

Hello UCW users/developers,

The UCW project has been without direction for quite a while now.
We've got one of the most advanced web application development
environments out there, but it's not used widely, unstable,
underdocumented and a bit of a mess. In order to alleviate this
situation, and to bring UCW into the mainstream lisp web world, I've
volunteered to step in as maintainer/visionary.

I'd like to find out who's using UCW, how they are using it, what
versions they are using (-dev, -ajax, -something-else) and what they'd
like to see happen to the project. I'm going to be very aggressive in
following a few ideals/guidlines for UCW that should make it more widely
usable.

1) No arbitrary breaking. The test suite will be run and its results
included in every commit message. the API will not change drastically
all the time. Libraries will not be added/removed without taking steps
to make sure things work. A buildbot will be setup. UCW will become a
lot more professional.

2) No reader macros, defclass*, cl-def or other 'syntax' will be used in
the base library.

3) An effort will be made to maintain a coding style consistent with
that of the larger lisp community, as well as internally consistent.

4) documentation will be written, and maintained. Now new features will
be added unless documented and tested.

5) modularization will be more explicit. I added a patch a while ago to
allow a more 'plugin' like architecture, and this will be exploited.
component libraries, form libraries etc will not be part of UCW proper
as there are many possible implementations. Rather, a good flexible
modular architecture will let the user choose to mix and match higher
level code, be it Lisp-on-Lines, ucw-ajax, or what-have-you.

6) Javascript will _not_be required, but will be well supported. A
'simple' set of ucw operators will be introduced and used for the
examples and documentation.

I have great plans for UCW over the next couple months. I'd like to ask
everybody who reads this to chime in now and say your piece...
lets make UCW the poster-boy for lisp web frameworks!

Cheers,

drewc
_______________________________________________
bese-devel mailing list
bese-devel at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/bese-devel

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com