Hello,
I've put up a new tarball of ParenScript, 20070801. It is the same as 20070720, with the exception that the tutorial (and correspondingly the manual) has a corrected package definition (the AllegroServe HTML generation facilities have been moved to their own package). For the next release, I plan to go over the example code carefully and fix any issues that come. Long-term, I want to transition the example tutorial to be based on Hunchentoot, because it is the best available Free Software Common Lisp web server right now, and probably LML2 for the server-side HTML generation facilities (because that's what I like to use). Let me know if you have any suggestions about this.
Thanks, Vladimir
issues that come. Long-term, I want to transition the example tutorial to be based on Hunchentoot, because it is the best available Free Software Common Lisp web server right now, and probably LML2 for the
moving the examples to hunchentoot is fine, but saying that it's the best oos lisp web server is a bit strong... :) (thinking about ucw here... :)
Ok, I will put the following disclaimer in the tutorial: IMMBPO (In My Massively Biased Personal Opinion). :)
On 8/2/07, Attila Lendvai attila.lendvai@gmail.com wrote:
issues that come. Long-term, I want to transition the example tutorial to be based on Hunchentoot, because it is the best available Free Software Common Lisp web server right now, and probably LML2 for the
moving the examples to hunchentoot is fine, but saying that it's the best oos lisp web server is a bit strong... :) (thinking about ucw here... :)
-- attila _______________________________________________ parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
Another idea is to drop the example tutorial completely. How to generate things on the server in the web framework of your choice has very little to do with parenscript, so I think it is quite off topic. If the documentation needs improvement I think a faq or common pitfalls is more importtant. But keeping the reference up to date and complete is probably work enough..
/Henrik Hjelte
Good idea about the faq. I kind of agree about the web framework aspect of the tutorial - I think it's better off as a document on a wiki somewhere. I think I'll put it up on cliki. That should make it faster for framework/web server specific changes to make it in, as well as reducing the documentation burden for anyone who contributes to ParenScript itself.
Vladimir
On 8/3/07, Henrik Hjelte henrik@evahjelte.com wrote:
Another idea is to drop the example tutorial completely. How to generate things on the server in the web framework of your choice has very little to do with parenscript, so I think it is quite off topic. If the documentation needs improvement I think a faq or common pitfalls is more importtant. But keeping the reference up to date and complete is probably work enough..
/Henrik Hjelte _______________________________________________ parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
parenscript-devel@common-lisp.net
-
Attila Lendvai -
Henrik Hjelte -
Vladimir Sedach