Re: [Chicken-users] Wiki design
Matt, On 30.08.2014 4:08, Arthur Maciel wrote: Matt and Yaroslav, thanks for your opinions! (more below)Yaroslav, I also don't like the current background, but I still prefer it comparing to the colors you've suggested. Probably we will also need some (color) theory to inspire any change. Otherwise we will fall into a complex territory called taste :) What do you think? As we say in Russia: There is no friend in questions of color and taste (Every man to his taste is the closest English idiom) :) I agree with you that current bg color is somewhat too heavy to look at so we could choose something different. I suggest you play with it and show some different colors you would like - may be we shall choose one of them. As to the font size - I suppose it is okay now. I suspect that shall we let it unspecified and browser will substitute one that is more close to user or system settings. -- Thanks, Yaroslav Tsarko ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Wiki design
Hi, On 29.08.2014 10:47, Matt Gushee wrote: length is best. A common rule of thumb is 50-60 characters. Okay, agree with that. But anyway, current wiki design makes me feel uncomfortable. May be we could try with different color background? Instead of current color (ffba54) should we try some lighter color? For example: fcd294 or fce5c3? They feel more airy and not so strong. At least they disturb less when reading text of the wiki. -- Thanks, Yaroslav ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Wiki design
Greetings everyone!
I do not know who is responsible for this, so I will post to this
mailing list. As of now, layout of http://wiki.call-cc.org is broken
(please see attached screenshot). Please, fix it ASAP because that looks
creepy :)
My system:
Linux yt 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Firefox 31.0 from official Ubuntu repositories.
On 08.08.2014 23:08, Arthur Maciel wrote:
Attached follows a correction on chicken.css that handles the order in
menu vs content divs on paste.call-cc.org http://paste.call-cc.org.
So the only changes I propose are adding menu to tests. and
salmonella{...}.call-cc.org http://call-cc.org.
And if more people like it, some testing on many platforms would be
appreciated. Here I can only test on linux mint with firefox and chrome.
Best wishes,
Arthur
2014-08-08 1:26 GMT-03:00 Arthur Maciel arthurmac...@gmail.com
mailto:arthurmac...@gmail.com:
I know this isn't the best comment after pasting a change
proposal, but in my overall appreciation of our site I really
think it is ugly and deserves a *real* web designer to take care
of it. Probably changing color and font scheme would be of high
priority to me. The actual design doesn't look professional to me
and this project deserves a professional face.
Best wishes,
Arthur
2014-08-08 1:20 GMT-03:00 Arthur Maciel arthurmac...@gmail.com
mailto:arthurmac...@gmail.com:
Dear ones, I changed again CHICKEN wiki design. It is simpler
than the one I've pasted before, because I've only changed the
chicken.css file. I can't do any further without changing the
wiki HTML generation.
Unfortunately I had to put a min-width property on body,
because the HTML generated for the search box and specific
links for wiki edit is not included in a single div. So when
I shrink the browser window size, they overlap. The min-width
is currently the default behaviour.
There are some caveats and it would be really great if someone
more experinced than me (and authorized to do so) could
correct them:
- pastes.call-cc.org http://pastes.call-cc.org generates the
div id='menu' ... *after* the div id='content' ... and
this messes things up. Menu should be the first content within
body as it is in most pages.
- code.call-cc.org http://code.call-cc.org doesn't include
the search bar and the specific-links for wiki edit.
- salmonella and tests.call-cc.org http://tests.call-cc.org
don't include the default menu nor the search bar and specific
links for wiki edit.
After correcting these stuff the next step is to replace
chicken.css with the one provided in
/wiki.call-cc.org/chicken.css
http://wiki.call-cc.org/chicken.css.
I'm not an experienced web designer so I apologize for the
ugly code. ATM the code Just Works and there should be caution
when applying it.
https://dl.dropboxusercontent.com/u/621606/chicken-wiki-testcase.tar.gz
Best wishes,
Arthur
2014-02-14 14:44 GMT-02:00 Mario Domenech Goulart
mario.goul...@gmail.com mailto:mario.goul...@gmail.com:
On Fri, 14 Feb 2014 12:25:34 +0100 Christian Kellermann
ck...@pestilenz.org mailto:ck...@pestilenz.org wrote:
* Mario Domenech Goulart mario.goul...@gmail.com
mailto:mario.goul...@gmail.com [140213 21:40]:
On Thu, 13 Feb 2014 18:26:49 -0200 Arthur Maciel
arthurmac...@gmail.com mailto:arthurmac...@gmail.com
wrote:
Mario, is there some Salmonella 'best' sample page I
should take a
look at? Maybe in two weeks I could try to fit the
CSS and avoid some
problems.
Recently there have not been changes in the salmonella
reports/diffs
layout. You can see them here, for example:
http://salmonella-linux-x86.call-cc.org/master-debugbuild/gcc/linux/x86/2014/02/13/salmonella-report/
http://salmonella-linux-x86.call-cc.org/master-debugbuild/gcc/linux/x86/2014/02/13/yesterday-diff/
There's also http://paste.call-cc.org/,
http://code.call-cc.org/ and
http://www.call-cc.org/, as far as I remember.
paste.call-cc.org http://paste.call-cc.org uses the
same css resource as the wiki IIRC.
Yeah. I mean all the aforementioned sites use the same
css as the wiki.
Best wishes.
Mario
--
http://parenteses.org/mario
___
Chicken-users mailing list
Chicken-users@nongnu.org
Re: [Chicken-users] UTF-8 support in eggs
On 09.07.2014 02:15, Oleg Kolosov wrote: IMO just enable utf8 by default and let them break. Is it's not 80's anymore, latin1 only software should die. + 1. For specific use cases (backward compatibility, logging or minimizing runtime size for example) it should be possible to disable multi-byte encoding handling (i.e. current behaviour) by using compilation option or a feature declaration. +1 again. Let`s remember Python 2.x vs Python 3.x with all that buzz regarding Unicode support and how one should tackle with that depending on Python version. IMHO should we implement UTF-8 in the core and make it a build option (to disable in cases where it is really, really not required) will give us totally transparent support for Unicode to end users and eggs and eliminate many problems with string processing. -- Thanks, Yaroslav ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] UTF-8 support in eggs
Hi, On 08.07.2014 16:40, Mario Domenech Goulart wrote: On the other hand, we risk breaking eggs that operate on latin1 text. UTF-8 support may also affect performance-sensitive code. Best wishes. Mario Isn`t UTF-8 backward-compatible with Latin-1 and ASCII encodings? AFAIR UTF-8 is the best choice for software which operates on one-byte ASCII/Latin1 strings. -- Thanks, Yaroslav ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] UTF-8 support in eggs
Hi, On 08.07.2014 18:03, Mario Domenech Goulart wrote: They are compatible only in the 7-bit ASCII range. The remaining bit in the byte makes the whole difference. :-) In UTF-8 it means either here's your 8-bit character or look at the next byte. In latin1 it always means here's your 8-bit character. Best wishes. Mario Oh, I see now, thank you. -- Thanks, Yaroslav ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] UTF-8 support in eggs
Hi, On 08.07.2014 00:58, Mario Domenech Goulart wrote: To properly handle UTF-8, we have the utf8 egg. If I understand correctly, the only way for eggs to properly support UTF-8 is by using the utf8 egg (or an equivalent implementation). Best wishes. Mario Why don`t just add *(use utf8)* line explicitly to all the eggs that handle strings? That will ultimately fix the problem and will clearly indicate that egg performs string manipulations and is capable of handling UTF-8 encoding. Or am I missing something? -- Thanks, Yaroslav ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Fwd: Re: Active Windows users poll
Original Message Subject:Re: [Chicken-users] Active Windows users poll Date: Mon, 16 Jun 2014 14:52:40 +0200 From: Richard plui...@freeshell.de To: Yaroslav Tsarko eriktsa...@googlemail.com Hello Oleg, I too would greatly welcome a Window build. Thank you On 06/16/14 13:24, Yaroslav Tsarko wrote: Hi Oleg! Those are great news! I am very interested in this project since native Windows build is preferable when you work on Windows rather than mingw tricks. This will greatly shorten Chicken dependency list for Windows - one don`t need to install mingw stuff to build Chicken with eggs on Windows and use platform tools instead. On 15.06.2014 01:21, Oleg Kolosov wrote: Hello All! I'm working on new build system for Chicken, based on CMake which, besides more configurability and faster build times, can offer native Windows and MacOSX support with Visual Studio, XCode and other IDEs integration. I also can make installer with few eggs bundled and such. The system already allows seamless integration with CMake projects and tested on Linux. But doing full Windows port is more involved unfortunately. So, if anybody interested in native Windows port of Chicken, give your vote. ___ 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] Active Windows users poll
Hi Oleg! Those are great news! I am very interested in this project since native Windows build is preferable when you work on Windows rather than mingw tricks. This will greatly shorten Chicken dependency list for Windows - one don`t need to install mingw stuff to build Chicken with eggs on Windows and use platform tools instead. On 15.06.2014 01:21, Oleg Kolosov wrote: Hello All! I'm working on new build system for Chicken, based on CMake which, besides more configurability and faster build times, can offer native Windows and MacOSX support with Visual Studio, XCode and other IDEs integration. I also can make installer with few eggs bundled and such. The system already allows seamless integration with CMake projects and tested on Linux. But doing full Windows port is more involved unfortunately. So, if anybody interested in native Windows port of Chicken, give your vote. ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] dbus egg crashes when sending message fails
Hi guys! I have encountered a crash inside dbus library when sending message to receiver that is absent on the bus. Crash happens because dbus_message_iter_init API is called with NULL for its first argument. The attached patch fixes this crash. Could you please apply it to the main egg repository. -- Thanks, Erik --- dbus.original.scm 2014-01-31 11:39:43.0 +0400 +++ dbus.scm 2014-02-06 17:41:52.557720859 +0400 @@ -679,7 +679,7 @@ (for-each (lambda (parm) (iter-append-basic iter parm)) params) (free-iter iter) -(let* ([reply-msg ((foreign-lambda* message-ptr ((connection-ptr conn) (message-ptr msg)) +(and-let* ([reply-msg ((foreign-lambda* message-ptr ((connection-ptr conn) (message-ptr msg)) ;; idealistic code here; todo: error checking ;; todo: timeout comes from where? (make-parameter) maybe DBusMessage *reply; @@ -710,7 +710,7 @@ (iter-append-basic iter parm)) params) (free-iter iter) ;; TODO: pull this out into a helper function - (let* ([reply-msg ((foreign-lambda* message-ptr ((connection-ptr conn) (message-ptr msg)) + (and-let* ([reply-msg ((foreign-lambda* message-ptr ((connection-ptr conn) (message-ptr msg)) ;; idealistic code here; todo: error checking DBusPendingCall* pending; dbus_connection_send_with_reply(conn, msg, pending, -1); ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
