I'd like us to group the projects we list on projects.shtml into groups (let's keep the number of groups low to begin with: database, graphics, utility, network, I don't know). In addition it would be nice to add a oneliner description for each project, like:
Database
pg - PostgreSQL interface over tcp/ip, no libraries needed.
Or somesuch.
However, just keeping up with adding projects and debugging various problems with email, anon cvs etc that shows up every now and then keeps me as busy as I want to be. Do we have a volunteer?
Erik.
Erik Enge erik@nittin.net writes:
I'd like us to group the projects we list on projects.shtml into groups (let's keep the number of groups low to begin with: database, graphics, utility, network, I don't know). In addition it would be nice to add a oneliner description for each project, like:
Database
pg - PostgreSQL interface over tcp/ip, no libraries needed.Or somesuch.
However, just keeping up with adding projects and debugging various problems with email, anon cvs etc that shows up every now and then keeps me as busy as I want to be. Do we have a volunteer?
Well, I can do it, but it will be next week. How about the following categories.
Database
Graphics
Network
System
Web-programming
Text processing (regex, defdoc, cl-typesetting)
Games (there was a MUD engine, right?)
Extensions
Interfacing
...?
Regards, Mario.
On Wed, 3 Mar 2004, Mario Mommer wrote:
Well, I can do it, but it will be next week. How about the following categories.
Goodiegood. A couple of random thoughs:
System
Stuff like asdf/defsystem, or stuff like osicat?
Extensions
Interfacing
These two also make me wonder what they mean. Is extensions essentially portable CL extensions to CL, and Interfacing CL interfaces to foreign libraries?
One (probably _bad_) higly alternative idea would be to use "category" like labels only as keywords, and make the taxonomy "less boring".
Like:
Eye Candy
Kludges
Heute die Welt!
Lith^H^Hsp
Morgen das Sonnensystem
Bits and Pieces
Reinventing The Wheel
Not Invented Here
Just blathering,
-- Nikodemus
Nikodemus Siivola tsiivola@cc.hut.fi writes:
On Wed, 3 Mar 2004, Mario Mommer wrote:
Well, I can do it, but it will be next week. How about the following categories.
Goodiegood. A couple of random thoughs:
System
Stuff like asdf/defsystem, or stuff like osicat?
Yep, osicat.
Extensions
Interfacing
These two also make me wonder what they mean. Is extensions essentially portable CL extensions to CL,
Yes, like your anaphoric macro package
and Interfacing CL interfaces to foreign libraries?
yes, + file formats, like the binary file format package by Andreas Fuchs. One wonders if XML tools go here.
My list of categories does not cover slime and the NYLispniks CD. Just one category "IDE"?
Where do we put Brians C to Lisp translator?
One (probably _bad_) higly alternative idea would be to use "category" like labels only as keywords, and make the taxonomy "less boring".
[snip]
:-)
The problem with this is that this becomes less funny with time, and people will find it not very usefull. Google et al are also locked out. When was the last time you where looking for some kludge to load down?
Regards, Mario.
On Mar 4, 2004, at 9:23 AM, Mario Mommer wrote:
My list of categories does not cover slime and the NYLispniks CD. Just one category "IDE"?
IDE for slime but NYLispnisk CD doesn't really fit into any category. So:
Where do we put Brians C to Lisp translator?
How about a "miscellaneous" category for stuff we are unable to categorize until we have more of them to warrant their own category.
Erik.
On Tue, 2 Mar 2004, Erik Enge wrote:
I'd like us to group the projects we list on projects.shtml into groups (let's keep the number of groups low to begin with: database, graphics, utility, network, I don't know). In addition it would be nice to add a oneliner description for each project,
Sounds like a good idea.
However, I think this might work best if we allow projects to categorize themselves. Start with a small number of categories, adding more when requested.
However, just keeping up with adding projects and debugging various problems with email, anon cvs etc that shows up every now and then keeps me as busy as I want to be. Do we have a volunteer?
Now that my connectivity is restored, I can do more "stuff", so whenever you're too busy and it's someting I can manage, feel free to give me a nudge. But I'd hesistate to commitmy self to either writing an engine that the users could use to manage the raxonomy, or maintaining it by hand.
Sigh. So many things to do, so little time.
However, to end on a positive note, how about adding
/project/foo/config.sexp
Looking like so:
((:long-name "Project Thingmajik") (:owner "Mr. King") (:short-description "Project to do stuff.") (:long-description "This project is very ambitious and will do lot's of stuff. However, I'm very busy and won't be able to do any of it, so volunteers are NEEDED!") (:categories "System" "Help Wanted" "Tomorrow The Solar System" "Ping Pong"))
Even if we do nothing with it right now, it still would be neat. ;-) And people could maintain those themselves (by hand) until someone hacks up a webinterface.
Cheers,
-- Nikodemus Siivola
Nikodemus Siivola tsiivola@cc.hut.fi writes:
On Tue, 2 Mar 2004, Erik Enge wrote:
I'd like us to group the projects we list on projects.shtml into groups (let's keep the number of groups low to begin with: database, graphics, utility, network, I don't know). In addition it would be nice to add a oneliner description for each project,
Sounds like a good idea.
However, I think this might work best if we allow projects to categorize themselves. Start with a small number of categories, adding more when requested.
However, just keeping up with adding projects and debugging various problems with email, anon cvs etc that shows up every now and then keeps me as busy as I want to be. Do we have a volunteer?
Now that my connectivity is restored, I can do more "stuff", so whenever you're too busy and it's someting I can manage, feel free to give me a nudge. But I'd hesistate to commitmy self to either writing an engine that the users could use to manage the raxonomy, or maintaining it by hand.
Sigh. So many things to do, so little time.
However, to end on a positive note, how about adding
/project/foo/config.sexp
Looking like so:
((:long-name "Project Thingmajik") (:owner "Mr. King") (:short-description "Project to do stuff.") (:long-description "This project is very ambitious and will do lot's of stuff. However, I'm very busy and won't be able to do any of it, so volunteers are NEEDED!") (:categories "System" "Help Wanted" "Tomorrow The Solar System" "Ping Pong"))
Even if we do nothing with it right now, it still would be neat. ;-) And people could maintain those themselves (by hand) until someone hacks up a webinterface.
I while back a handful of Bay Area Lispniks started working on a website that was intended to be a directory of Lisp libraries (L3, the Lisp Library List). We ran out of steam (or the project is on hold depending on how charitable you want to be). Anyway, came up with a few good bits including some stuff similar to what you just mentioned.
Feel free to take a look at the following url's and make whatever use of what's there. I may even be able to help out a bit as I think this is would be an important addition to what common-lisp.net is already offering. Though I'm pretty busy these days so don't want to promise too much. Anyway here are some of the good bits:
http://www.lispniks.com/l3/code/l3.lisp -- Code for generating and managing entries in a sexp database of meta information about library. Data driven the basic model of what information we are storing is easily visible.
http://www.lispniks.com/l3/data/l3-master.sexp -- A sexp database of a few libraries. Each DEFLIB form is similar to what you envisioned above. Our idea was to extract these from the library itself, either from a separate config.sexp file or from the .asd file itself.
http://www.lispniks.com/l3/code/asd-extract.lisp -- Some code that extracts as much information as possible from an ASD file in order to build a DEFLIB.
http://www.lispniks.com/l3/code/l3-html.lisp -- Some code for generating HTML from the sexp database. Uses templates that can be found in http://www.lispniks.com/l3/html-templates/.
The resulting HTML (essentially mockups) are at:
http://www.lispniks.com/l3/package-index.html http://www.lispniks.com/l3/private-catalog.html
-Peter
On Mar 8, 2004, at 2:23 PM, Peter Seibel wrote:
I while back a handful of Bay Area Lispniks started working on a website that was intended to be a directory of Lisp libraries (L3, the Lisp Library List).
This is good stuff. I wanted to something similar and figure a static grouping in webpages would be an acceptable babystep towards that. With L3 we can go there directly. Mario, think we can just use this?
Erik.
Erik Enge erik@nittin.net writes:
On Mar 8, 2004, at 2:23 PM, Peter Seibel wrote:
I while back a handful of Bay Area Lispniks started working on a website that was intended to be a directory of Lisp libraries (L3, the Lisp Library List).
This is good stuff. I wanted to something similar and figure a static grouping in webpages would be an acceptable babystep towards that. With L3 we can go there directly. Mario, think we can just use this?
We can, but note that the above is actually somewhat orthogonal to our concerns, which for the moment are to write a little catalog. I presume that one can do that in this way, but that would require some hacking.
I'll go now for the simple catalog we had planned in the beginning. We will, however, need some automatization for this in the future.
Regards, Mario.
Mario Mommer mommer@igpm.rwth-aachen.de writes:
Erik Enge erik@nittin.net writes:
On Mar 8, 2004, at 2:23 PM, Peter Seibel wrote:
I while back a handful of Bay Area Lispniks started working on a website that was intended to be a directory of Lisp libraries (L3, the Lisp Library List).
This is good stuff. I wanted to something similar and figure a static grouping in webpages would be an acceptable babystep towards that. With L3 we can go there directly. Mario, think we can just use this?
We can, but note that the above is actually somewhat orthogonal to our concerns, which for the moment are to write a little catalog. I presume that one can do that in this way, but that would require some hacking.
I'll go now for the simple catalog we had planned in the beginning. We will, however, need some automatization for this in the future.
Have you begun work on that catalog? If you have anything at all, maybe I can look at it and see if I can fit it into the L3 framework (adapting my code as necessary to generate whatever output you want.)
-Peter
Peter Seibel peter@javamonkey.com writes:
Mario Mommer mommer@igpm.rwth-aachen.de writes:
We can, but note that the above is actually somewhat orthogonal to our concerns, which for the moment are to write a little catalog. I presume that one can do that in this way, but that would require some hacking.
I'll go now for the simple catalog we had planned in the beginning. We will, however, need some automatization for this in the future.
Have you begun work on that catalog? If you have anything at all, maybe I can look at it and see if I can fit it into the L3 framework (adapting my code as necessary to generate whatever output you want.)
Here is what I have until now as an attachment. There is also a bit of discussion here
http://www.common-lisp.net/macho-archives/clo-devel/2004-3/213.html
Regards, and thanks!
Mario.
Mario Mommer mommer@igpm.rwth-aachen.de writes:
Peter Seibel peter@javamonkey.com writes:
Mario Mommer mommer@igpm.rwth-aachen.de writes:
We can, but note that the above is actually somewhat orthogonal to our concerns, which for the moment are to write a little catalog. I presume that one can do that in this way, but that would require some hacking.
I'll go now for the simple catalog we had planned in the beginning. We will, however, need some automatization for this in the future.
Have you begun work on that catalog? If you have anything at all, maybe I can look at it and see if I can fit it into the L3 framework (adapting my code as necessary to generate whatever output you want.)
Here is what I have until now as an attachment. There is also a bit of discussion here
http://www.common-lisp.net/macho-archives/clo-devel/2004-3/213.html
Regards, and thanks!
Is this being run yet--the Projects doesn't look like it's using this. Since you went ahead and used a sexp database + HTML generation, what do you see as the next step?
-Peter
Peter Seibel peter@javamonkey.com writes:
Mario Mommer mommer@igpm.rwth-aachen.de writes:
Peter Seibel peter@javamonkey.com writes:
Have you begun work on that catalog? If you have anything at all, maybe I can look at it and see if I can fit it into the L3 framework (adapting my code as necessary to generate whatever output you want.)
Here is what I have until now as an attachment. There is also a bit of discussion here
http://www.common-lisp.net/macho-archives/clo-devel/2004-3/213.html
Regards, and thanks!
Is this being run yet--the Projects doesn't look like it's using this. Since you went ahead and used a sexp database + HTML generation, what do you see as the next step?
Well, the next step is to render it into cl-net-stylish html. The current code was kept basic exatly because I didn't know what the step after that next step might be :-)
I suspect that it will be
* Integrating the safe READ routine by Nikodemus.
* Writing the code that will do the automatic generation each 24h.
If you have sugestions/ideas, just bring 'em on!
Regards, Mario.
-
Erik Enge -
Mario Mommer -
Nikodemus Siivola -
Peter Seibel