[Chicken-users] The eggs index needs release dates displayed
Hi all, Haven't played around with scheme in a while, but recently was motivated to take a peek at what eggs were currently available. I noticed at the [egg index](http://wiki.call-cc.org/chicken-projects/egg-index-4.html) that although there is much useful info provided (such as description, license, and egg version), there are no egg release dates listed --- only the egg version number. While I understand that some may be hesitant to display dates, since there are likely many chicken eggs that are good but also were released some time ago (and you may not want to give the impression that you've got old eggs), it makes it difficult for new users to get an idea of what's current/active vs possibly inactive. Date of the egg's release is just as important to see as its version or other info, and also sends a clear message that the egg index is more than just a showcase but is in fact *the* tool for finding and selecting eggs. Does the egg packaging format support a field for release date? Thanks, -- John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] The eggs index needs release dates displayed
How about instead adding a link to its online repo (at github, gitlab, bitbucket, ...)? Is there a way to add those links to the eggs index page? That would be an excellent improvement. When I look at a project's online repo, seeing recent commits, issues, available docs, number of "stars"/"watchers", changelog, etc. gives me a good idea of how the project is doing and if it'll work for me. On Wed, Feb 21, 2018, at 3:10 PM, John Cowan wrote: > I think that would be a mistake for the reason you give: it's often > the case that an egg hasn't been updated in a long while because it's > complete and nobody has found any bugs in it. Lisp/Scheme code tends > to be extremely durable: McCarthy's theorem prover from 1958 is still > runnable with only a few surface repairs.> > On Wed, Feb 21, 2018 at 2:45 PM, John Gabriele > wrote:>> Hi all, >> >> Haven't played around with scheme in a while, but recently was >> motivated to take a peek at what eggs were currently available. I >> noticed at the [egg index] >> (http://wiki.call-cc.org/chicken-projects/egg-index-4.html) that >> although there is much useful info provided (such as description, >> license, and egg version), there are no egg release dates listed >> --- only the egg version number.>> >> While I understand that some may be hesitant to display dates, since >> there are likely many chicken eggs that are good but also were >> released some time ago (and you may not want to give the impression >> that you've got old eggs), it makes it difficult for new users to >> get an idea of what's current/active vs possibly inactive. Date of >> the egg's release is just as important to see as its version or >> other info, and also sends a clear message that the egg index is >> more than just a showcase but is in fact *the* tool for finding and >> selecting eggs.>> >> Does the egg packaging format support a field for release date? >> >> Thanks, >> -- John >> >> ___ >> Chicken-users mailing list >> Chicken-users@nongnu.org >> https://lists.nongnu.org/mailman/listinfo/chicken-users ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] The eggs index needs release dates displayed
On Wed, Feb 21, 2018, at 4:36 PM, Mario Domenech Goulart wrote: > Hi John, > > On Wed, 21 Feb 2018 16:09:28 -0500 John Gabriele > wrote: > > > How about instead adding a link to its online repo (at github, gitlab, > > bitbucket, ...)? Is there a way to add those links to the eggs index > > page? That would be an excellent improvement. When I look at a > > project's online repo, seeing recent commits, issues, available docs, > > number of "stars"/"watchers", changelog, etc. gives me a good idea of > > how the project is doing and if it'll work for me. > > Documentation of eggs not in the CHICKEN svn repository usually have a > link to to their repository. Those that don't have a link to the source > repository are either in svn or the documentation is simply missing the > link. In the latter case, feel free to fix the documentation in the > wiki by adding a section "Repository" with a link to the source > repository. Ah, I didn't realize that the eggs index page as well as each individual egg's info pages are all wiki pages. Also didn't realize that many eggs are in the chicken svn repo. So, it sounds like the egg index page for a given release is somewhat autogenerated at some point early on, and then manually edited as changes happen? > You can see the mapping between eggs and their repositories here: > http://bugs.call-cc.org/browser/project/release/4/egg-locations (the > links are actually to the .release-info file, but you can guess the > repository from there). Yes. Thanks for the link. > Instructions to fetch eggs from svn can be found here: > http://code.call-cc.org/#eggs-repository > > Now that the canonical option to host eggs is not the CHICKEN svn > anymore, I think eggs in svn should also contain a link to their source > repositories and, ideally, instructions on how to check them out (I have > a feeling that using svn is considered a lost art nowadays). The eggs index could contain a column with a little graphic that indicates one of: chicken svn hosted, github, gitlab, bitbucket, etc. Thanks, -- John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] minor build warning (twice) : runtime.c
Hi, Just built chicken on Ubuntu 10.04 (on x86_64) and saw this warning come up twice: gcc -fno-strict-aliasing -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -I. -I./ \ -c -Os -fomit-frame-pointer \ \ -DC_BUILDING_LIBCHICKEN runtime.c -o runtime-static.o runtime.c: In function ‘C_number_to_string’: runtime.c:7328: warning: ignoring return value of ‘gcvt’, declared with attribute warn_unused_result and gcc -fno-strict-aliasing -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -I. -I./ \ -c -Os -fomit-frame-pointer -fPIC -DPIC \ -DC_BUILDING_LIBCHICKEN runtime.c -o runtime.o runtime.c: In function ‘C_number_to_string’: runtime.c:7328: warning: ignoring return value of ‘gcvt’, declared with attribute warn_unused_result ---John ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Curious: why the name "Chicken Scheme"?
Hi, I looked around the wiki but did not see an answer to this. Just curious: why is it named "Chicken Scheme"? :) Thanks, ---John ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] editing the wiki
Hi, Maybe I'm missing something obvious, but how does one create an account on the wiki in order to edit content? Also, I tried just clicking the "edit" link on a give page, but the wiki just hangs. Thanks, ---John ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] wiki not colorizing colorize sample
Hi, On the wiki's "Edit Help" page https://wiki.call-cc.org/edit-help , it doesn't seem to be syntax highlighting the example showing off syntax highlighting (the C sample under "Syntax coloring"). Looking at the wiki syntax for the example, it seems correct. ---John ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] problem adding link to internal page in wiki
Hi, On this page https://wiki.call-cc.org/manual/Extensions I added a link to the eggs tutorial like so: > For more details on creating extensions, see the [[/eggs tutorial|eggs > tutorial]]. The wiki automatically adds a hyphen to the generated link so it points to https://wiki.call-cc.org/eggs-tutorial instead of http://wiki.call-cc.org/eggs%20tutorial , which results in a broken link. (If you're taking votes, I prefer the hyphens to the spaces in urls. :) ) On a related note, at this page http://wiki.call-cc.org/tips%20and%20tricks the link to "compiler or interpreter?" has the same problem (haven't checked the other links there -- they seem to be mixed; some contain spaces, some contain hyphens). ---John ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] wiki not colorizing colorize sample
On Thu, Oct 14, 2010 at 5:15 PM, Moritz Heidkamp wrote: > Hey guys, > > Peter Bex writes: >> Maybe Moritz can add some more nifty styling :) > > I did! Actually, there was some styling in place already but it seems > the HTML generated by colorize has changed, is that possible? The > selector I used assumed that symbols are always nested within an > element. Well, long story short, it looks nicer now :-) Hi, I just noticed a glitch in the code sample at http://wiki.call-cc.org/egg/qwiki under "Create a subversion repository". I'm seeing the comment ";; checked out" show up syntax highlighted like a comment, but the comment line above it is not -- even though it is also a comment. Also, is there any reason why the strings are rendering the same color as the code around them? ---John ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Another DVCS to look at: fossil
On Fri, Oct 15, 2010 at 9:57 AM, Christian Kellermann wrote: > Hi there, > > I just noticed the fossil scm a couple of weeks ago and I wanted > to have a look at it. I have converted the chicken-core git repo > to it for fun and I have put the database online at > http://pestilenz.org/~ckeen/chicken.fossil. Ah, I just remembered seeing something about fossil recently: http://sheddingbikes.com/posts/1276624594.html Here's the corresponding HN thread: http://news.ycombinator.com/item?id=1433387 And also a slightly older HN thread: http://news.ycombinator.com/item?id=809493 ---John ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: dbus:send bug
On Wed, Mar 16, 2011 at 4:45 PM, Peter Bex wrote:
> On Wed, Mar 16, 2011 at 04:52:45PM -0300, Stephen Eilert wrote:
>> > Almost all the "extracted" documentation I've seen is of shitty quality;
>> > people tend to use automatic extraction of docs as an excuse not to
>> > write proper documentation.
>>
>> As opposed to not writing it at all, or having it get out of sync with
>> the code, as they live in different places.
>
> That's an invalid argument; I've seen countless cases of inline docs
> which say one thing while the code *right below it* does something
> completely different. When the docs are elsewhere, at least you
> won't be tempted to skim the comments and skip the code while reading
> the source.
>
>> Also, it is trivial to extract documentation for, say, an older egg
>> version. Which is in sync with the code, by default.
>> When you have documentation in the code, it goes wherever that code goes.
>
> That much is true.
>
> {snip}
>> One can make the argument that it would be *easier* to document the
>> code because you are looking at it, it is sitting right next to the
>> docs.
>
> You can also make the argument that you're being distracted by the way
> the code is laid out. If you are documenting completely separately,
> you can think about the flow of text that makes most sense, grouping
> procedures that fit together logically. {snip}
A system that I think works pretty well is:
1. separate standalone docs for things like overview, tutorial,
cheatsheet, cookbook
2. API docs in the source code file (easily extracted), though, all
placed together at the end
3. comments for low-level explanations of why something is done a certain way
For example, often in Perl 5:
* (1) are put in separate .pod files,
* (2) are put after a special marker at the end of the source code
(__END__) so the compiler can skip it
* both (1) and (2) are accessed the same way using the `perldoc` command
---John
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] configuring readline support; cannot import from undefined module: regex
Hi, Following the instructions at http://wiki.call-cc.org/man/3/Using%20the%20interpreter#auto-completion-and-edition to set up readline support, I get: Error: (import) during expansion of (import ...) - cannot import from undefined module: regex Changing "regex" to "irregex" makes readline seem to work though. Also, both links there pointing to the readline egg page are broken. The instructions at http://wiki.call-cc.org/eggref/4/readline#examples are almost the same as those in the above "Using the interpreter" page except that they use `getenv` (instead of `get-environment-variable`), which fails for me. Should I update both wiki pages? BTW, what does the "NB" acronym (at the readline egg page, examples section) mean? Thanks, ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] configuring readline support; cannot import from undefined module: regex
On Tue, Aug 16, 2011 at 7:26 AM, Moritz Heidkamp wrote: > Hi John, > > John Gabriele writes: > >> Hi, >> >> Following the instructions at >> http://wiki.call-cc.org/man/3/Using%20the%20interpreter#auto-completion-and-edition > > note that you are looking at Chicken _3_ documentation there. The > current version is located at > http://wiki.call-cc.org/man/4/Using%20the%20interpreter#auto-completion-and-edition Thanks for pointing that out, Moritz. I think I accidentally arrived there by following a google search result rather than following the links from the wiki front page. It might be useful if there were a small red banner at the top of previous release manual/wiki pages noting that the reader is looking at the docs from a previous release (and pointing them to the current docs). ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] configuring readline support; cannot import from undefined module: regex
On Tue, Aug 16, 2011 at 3:08 AM, Christian Kellermann wrote: > Hi John, > > * John Gabriele [110816 05:47]: >> Should I update both wiki pages? >> > > Yes please do. Ok, edited the current (chicken v4) pages, and only fixed the readline link at https://wiki.call-cc.org/man/3/Using%20the%20interpreter#auto-completion-and-edition (chicken v3). ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] FrOSCon 2011 Talks
On Sun, Aug 21, 2011 at 6:25 AM, Christian Kellermann wrote: > > Newcomers, please have a look and if you happen to have some spare > time, get me some feedback on what can be improved. Wow. These are great resources. Thank you! :) For now, a few comments about the chickenista guide (html slides): * slide 3, (elevator pitch), I would add a bullet point containing, "Friendly and involved community." Also, maybe put the "Hello, World" example on its own page, and use (print) instead of (display) (newline)? * slide 5: s/packages/Chicken distributions/ (otherwise people might think you're talking about eggs) * slide 12: put ":P" after "rotten eggs" * slide 17: s/benefits by/benefits of/ and s/A magnitude/An order of magnitude/ * slide 18: Did you mean to add more to the 2nd bullet point? Or maybe "utils"? * slide 22: I don't understand the first bullet point (about "units"). * slide 23: maybe put the name "Chickadee" at the top? * slide 35: 3rd bullet may not be displaying correctly. I get "chicken-install -deploy will copy all dependencies into th at" ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] FrOSCon 2011 Talks
On Sun, Aug 21, 2011 at 6:25 AM, Christian Kellermann
wrote:
> Hi Chicken-fans,
>
> {...}
>
> A somewhat badly formatted handout can be found at
> http://pestilenz.org/~ckeen/chickenista-guide.pdf
>
> Newcomers, please have a look and if you happen to have some spare
> time, get me some feedback on what can be improved. I would like to
> reuse this on the chicken wiki as an introduction.
>
Hi again, Christian,
Regarding the chickenista guide pdf, some minor issues I noticed:
* on page 2, after wget line you also need `tar xzf chicken-4.7.0.tar.gz`
* on page 3, chicken-status shows currently *installed* eggs,
correct? Wouldn't currently available eggs be ones that you could
install via chicken-install if you wanted to?
* page 5: s/ships with extension/ships with extensions/
* bullet list starting at the bottom of page 5 could use colons
between unit names and descriptions
* page 6: s/the are/they are/
* page 7: s/deviatoins/deviations/
* page 8: This sentence needs rewording: "It is easier to use the
API search chickadee for this."
* page 9: "The home of bugs: Chicken's bug tracker" is rendered as
section 4.5.5. Since section 4.5 is about documentation, was the bug
tracker section supposed to be one level up (that is, section 4.6)?
Same with the section after it ("Getting help from humans").
* page 11: s/a mp3/an mp3/
Finally, I notice some inconsistent capitalization of "Chicken"
(sometimes "CHICKEN" and "chicken") and "Scheme" (sometimes "scheme").
Also "lisp" on page 10.
As far as more substantial feedback on the content itself, I would've
liked longer descriptions for most of the bullet points in section
4.4, as well as more explanation about what exactly a "unit" is and
what the differences are between units, extensions, eggs, and modules.
Thanks again for the docs!
---John
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] wiki account creation
Hi, How can I create an account on the wiki? Thanks, ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] script to generate html from wiki-formatted text?
Does anyone have (or would anyone whip up?) a script for converting wiki markup to html? Something to be used like: chicken-wiki-to-html foo.txt > foo.html (BTW, the Chicken wiki uses qwiki, correct?) Thanks, ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] script to generate html from wiki-formatted text?
On Tue, Aug 30, 2011 at 4:13 PM, Mario Domenech Goulart wrote: > Hi John, > > On Tue, 30 Aug 2011 16:15:20 -0400 John Gabriele wrote: > >> Does anyone have (or would anyone whip up?) a script for converting >> wiki markup to html? Something to be used like: >> >> chicken-wiki-to-html foo.txt > foo.html > > Here's one: http://parenteses.org/mario/misc/wiki2html.scm Thanks, Mario! It requires that I install qwiki, but installation failed because it couldn't locate `apr-1-config`. I'm on Ubuntu, and so installed libapr1-dev. Tried `chicken-install qwiki` again. Got a little further, but... Failed again, this time it seemed to be svn-client that was having a problem. I got: In file included from svn-client.c:13: svn-client-base.c:5:22: error: svn_auth.h: No such file or directory svn-client-base.c:6:24: error: svn_client.h: No such file or directory svn-client-base.c:7:24: error: svn_config.h: No such file or directory ... Looked like I might need libsvn-dev, so installed that and tried again. Success! Do egg doc pages generally list external prereqs (such as how qwiki required libapr1-dev and libsvn-dev)? Should I add a "Prerequisites" section to the doc for qwiki? Thanks again, ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] script to generate html from wiki-formatted text?
On Tue, Aug 30, 2011 at 6:23 PM, Jim Ursetto wrote: > John, > Another option is to look at manual-labor, which uses svnwiki-sxml and > chicken-doc-html under the hood. Thanks. That also works nicely for me. The styling reminds me of chickadee. > A further option is hyde. At the moment, I only need a simple tool to use as a previewer for a potential wiki doc, but thanks for pointing it out. ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] script to generate html from wiki-formatted text?
On Thu, Sep 1, 2011 at 6:04 AM, Christian Kellermann wrote: > > Ok, I will start hacking on this. > Thanks! (set! Christian (+ Christian 1)) :) ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Porting modules to Chicken from other Schemes?
Hi, How much work is generally required to port modules from other Schemes to Chicken? Are there any organized efforts to gather free software modules from elsewhere, port them to Chicken, and add them to the egg repository (similar to how, say, Debian packages software into .deb packages)? Thanks, ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] wiki pages and h1 title
Hi all,
I've noticed that some of the wiki pages have an h2 title at the top,
some don't. For the ones that have have a table of contents, some have
an h2 above the toc, some have it below.
I think pages look a bit odd if they have no title at the very top.
Looking at the source for a few pages, I haven't seen any h1 tags anywhere.
The [editing help](https://wiki.call-cc.org/edit-help) page says not
to use "= title", as h1's are reserved for use by the wiki itself.
I think most pages would probably look best if there's always an h1
title at the top which is not part of the table of contents (if there
is indeed a toc).
Is the wiki indeed using h1's for anything?
Does the wiki generate a portion of a page's tag using the
first h2 on the page?
I think it would make sense for every page to have an h1 ("= Page
Title") at the top, which would not be part of a toc (if present),
which would be rendered at the top of the page body (above the toc, if
present), and which would be used to generate the first portion of the
page's . What do you think?
Thanks,
---John
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] wiki pages and h1 title
On Sat, Sep 10, 2011 at 1:13 PM, Peter Bex wrote:
> On Sat, Sep 10, 2011 at 12:56:59PM -0400, John Gabriele wrote:
>
>> I think it would make sense for every page to have an h1 ("= Page
>> Title") at the top, which would not be part of a toc (if present),
>> which would be rendered at the top of the page body (above the toc, if
>> present), and which would be used to generate the first portion of the
>> page's . What do you think?
>
> I think that is ugly since it would repeat this title:
>
> == foo
> blabla
>
> gets rendered to
>
> foo
> foo
>
I don't understand what you mean. I'd expect this wiki markup:
= Title Goes Here
[[toc:]]
== Intro
Some content here.
to produce something like:
Title Goes Here - The Chicken Scheme Wiki
Title Goes Here
{ ... toc ...}
Intro
Some content here.
Where the only duplication is "Title Goes Here" lands in the
as well as in the , which I believe is as it should be.
---John
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] wiki pages and h1 title
On Sat, Sep 10, 2011 at 12:56 PM, John Gabriele wrote:
> {...}
> I think it would make sense for every page to have an h1 ("= Page
> Title") at the top, which would not be part of a toc (if present),
> which would be rendered at the top of the page body (above the toc, if
> present), and which would be used to generate the first portion of the
> page's . What do you think?
Here's a good example issue: the eggs tutorial page
http://wiki.call-cc.org/eggs%20tutorial .
Currently, when I have that page open, it doesn't say anywhere that
it's the Eggs Tutorial page. My browser window title says
"Introduction - The Chicken Scheme Wiki" and my browser tab says
"Introduction". Looking at the page, there's no indication to the
reader what page they're looking at unless they check the actual url.
I'd bet many pages start with an Introduction, Overview, or Getting
Started section.
I could add "== Eggs Tutorial" to the top of the eggs tutorial page
(above the `[[toc:]]`), and it would kinda' look right, except:
1. "Eggs Tutorial" would be at the same level (h2) as the other
sections, but it shouldn't be -- it's the title of the page, and
2. The ToC would list it as section 1, containing no content, followed
by section 2, Introduction.
which might be acceptable, and wouldn't require any work, but I don't
think it's optimal.
---John
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] wiki pages and h1 title
On Sat, Sep 10, 2011 at 3:18 PM, Peter Bex wrote:
> On Sat, Sep 10, 2011 at 02:29:13PM -0400, John Gabriele wrote:
>
>> which might be acceptable, and wouldn't require any work, but I don't
>> think it's optimal.
>
> I don't really understand what you want; {...}
What I want (what I think would benefit the wiki) is this:
http://www.unexpected-vortices.com/temp/eggs-tutorial-2.html
instead of this:
http://www.unexpected-vortices.com/temp/eggs-tutorial.html
The stopgap measure though, would appear to be this:
https://wiki.call-cc.org/eggs%20tutorial (I just now added the h2
heading to it.)
---John
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] some wiki css
Hi, Reading the wiki, I'm finding that my eyes aren't very good at picking out procedures on the page, but a couple of small changes help. For example, a sample taken from http://wiki.call-cc.org/man/4/Unit%20srfi-1 : http://www.unexpected-vortices.com/temp/current.png http://www.unexpected-vortices.com/temp/modified.png (I changed the definiton background color to #edf, and the pre border color to #e5e5c5.) Having those procedure names stand out more (especially relative to the code blocks) helps. ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] some wiki css
On Wed, Sep 21, 2011 at 7:02 AM, Moritz Heidkamp wrote: > I have now changed it to be generally a > bit less heavy on the eyes but hopefully procedures stand out more > now. Let me know if it's still too light for you! The procedures stand out nicely now, thank you! They look highlighted (as in, with a highlighter marker), which seems to be just right. I think the code blocks also look better as well (and they are subtle enough that they don't overpower the procedures). You might also try adding a "border: 1px solid #eee;" to them. ---John ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
