Re: Wiki, [was: Re: [Chicken-users] Powered by Spiffy/Scheme logo?]
On 3/12/06, Shawn Rutledge [EMAIL PROTECTED] wrote: It's a regular wiki, currently with a rather llimited set of editing commands and it uses some homegrown markup. I could have used Alejandro's excellent stream-wiki, but the idea is to provide a simple to process internal format, since I'd like to support programmatic access (via some HTTP-based API, or even by allowing sandboxed Scheme code - I'm not sure yet). Is that why the syntax is different? I agree that it's a good idea to support programmatic extensions somehow. Is the source available? Yes, see: http://galinha.ucpel.tche.br/coop-repo (it's a darcs repository) cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: Wiki, [was: Re: [Chicken-users] Powered by Spiffy/Scheme logo?]
On 3/12/06, Mario Domenech Goulart [EMAIL PROTECTED] wrote: Some suggestions: - syntax highlight for scheme code Yes, that would be nice. Noted. - Link the RSS feed at the start-page or at the top of recent-changes (I just deleted a text suggesting an RSS feed because I hadn't seen it at the bottom of the recent-changes page. :-)) Ok. - wiki syntax for lists Hm. I'll take a look. - add a link to the wiki syntax page at the footer of the pages (wiki help or something like this). Good point. (It doesn't feature a powered-by-spiffy-logo yet, but will definitely do so in the next days. :-) I've put the ones we have so far at http://galinha.ucpel.tche.br/coop?page=Spiffy%20logo Please, somebody make them look better! :-) Thanks! cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: Wiki, [was: Re: [Chicken-users] Powered by Spiffy/Scheme logo?]
On Sat, Mar 11, 2006 at 10:58:34PM -0700, Shawn Rutledge wrote: Another feature (which might or might not be a good idea) is to have folders, rather than a single namespace. A problem arises when you try to use a conventional wiki for multiple projects - you have to be careful to choose sufficienty verbose titles for the pages, so that you don't use up all the good names for one project. So I think I will make it possible to partition parts of the wiki in actual directories on the server. That way different directories can have different permissions too. At work, we used mediawiki for a while, and then pretty soon people wanted to have some stuff be public, and some be private to our department, and we didn't find a way to do it. So we had to make the whole thing private (using a .htaccess file). What does Spiffy have for security? See the spiffy-access-file parameter. It's a much more flexible and powerful access mechanism then .htaccess. It allows you to define a function that determines if one is allowed to view the file or not. (it returns a boolean, #t if access allowed, #f if denied) Maybe people who are more familiar with Apache could contribute some macros that it easier to specify access in a declarative fashion. For course-grained access control, there's the spiffy-deny-access parameter, which is a regex. Access is denied to any file that matches the regex. Regards, Peter -- http://www.student.ru.nl/peter.bex -- The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music. -- Donald Knuth pgp6RoyPUKhYT.pgp Description: PGP signature ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: Wiki, [was: Re: [Chicken-users] Powered by Spiffy/Scheme logo?]
On Sat, 11 Mar 2006 22:54:10 +0100 felix winkelmann [EMAIL PROTECTED] wrote: On 3/10/06, Mario Domenech Goulart [EMAIL PROTECTED] wrote: Thanks to all of you for your kind comments. Attached you can find some more attempts, which may (or may not :-)) look better. But I'm afraid I'm at the limit of my skills to use graphics software. Which is nearly always an indication of good programming skills. ;-) Ah, how I wish it was the case... :-) Maybe we can use the chicken wiki (or another location you find more convenient) to put together the suggestions we have so far. Speaking of wikis: I've put together yet another feeble attempt of writing web software (boy, am I modest, or what?) at this place: http://galinha.ucpel.tche.br/coop It's a regular wiki, currently with a rather llimited set of editing commands and it uses some homegrown markup. I could have used Alejandro's excellent stream-wiki, but the idea is to provide a simple to process internal format, since I'd like to support programmatic access (via some HTTP-based API, or even by allowing sandboxed Scheme code - I'm not sure yet). That's really nice! :-) Ideas and comments are naturally welcome. And additions to the wiki, too, of course! Some suggestions: - syntax highlight for scheme code - Link the RSS feed at the start-page or at the top of recent-changes (I just deleted a text suggesting an RSS feed because I hadn't seen it at the bottom of the recent-changes page. :-)) - wiki syntax for lists - add a link to the wiki syntax page at the footer of the pages (wiki help or something like this). (It doesn't feature a powered-by-spiffy-logo yet, but will definitely do so in the next days. :-) I've put the ones we have so far at http://galinha.ucpel.tche.br/coop?page=Spiffy%20logo Please, somebody make them look better! :-) Best wishes, Mario ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
