Warning: Cannot modify header information - headers already sent by (output started at /home/jdobbels/www/blog/inc/config.php:40) in /home/jdobbels/www/blog/inc/clearbricks/common/lib.http.php on line 222

Warning: Cannot modify header information - headers already sent by (output started at /home/jdobbels/www/blog/inc/config.php:40) in /home/jdobbels/www/blog/inc/clearbricks/common/lib.http.php on line 224

Warning: Cannot modify header information - headers already sent by (output started at /home/jdobbels/www/blog/inc/config.php:40) in /home/jdobbels/www/blog/inc/public/lib.urlhandlers.php on line 65

Warning: Cannot modify header information - headers already sent by (output started at /home/jdobbels/www/blog/inc/config.php:40) in /home/jdobbels/www/blog/inc/clearbricks/common/lib.http.php on line 247
JDobbelstein.dev() - Tag - www To infinity, and beyond ! 2011-01-10T00:04:33+01:00 Johan urn:md5:98d5e93307cb5ee6e20feba0dc3f35eb Dotclear A new version for the "Deep Blue" DotClear theme urn:md5:a74ac83d4bab225d4b59a2fb8f410444 2010-05-02T23:40:00+02:00 Johan network cssdotclearwww <p>After three whole nights and more than 30 cups of tea, my blog is using a new version of my "deep blue" theme. Key new features are:</p> <ul> <li>Elastic CSS, this implies no more bitmap pictures :(</li> <li>Refactoring of DotClear2 template to shift the center of the page to the left. This leaves a small opening for a side image on the right. This is a new proof that my poor CSS skills cannot overcome the xHTML tags and document structure of the original DotClear2 pages.</li> <li>After many thoughts on the <em>right</em> CSS layout, I choose to use a CSS width based on <code>em</code>. Layouts based on page percent width are very tricky when it comes to displaying lines of code because text lines could be wrapped. CSS <code>em</code> attribute should garantee a similar appearance among screens and, let's dream, browsers. New pages width should be almost/at least 80 characters long. This might keep a text layout constant, even if you are zooming in/out, even if you are using different font sizes. Too wide or too big screens will be under-used. I don't care, use the space left to play with tiling window managers. Too small screens will have to go full screen and zoom out. Anyway if you cannot read 80 characters-long-line text, you should use another graphical terminal.<em> (note: in fact, and perhaps due to limitation on the fonts, the length of text lines will never be constant. I've just tried to assure a minimal quality. See the <a href="http://www.jdobbelstein.eu/blog/post/2010/05/01/A-new-version-for-the-Deep-Blue-DotClear-theme#lengthMyth">next section</a> for a concrete example)</em></li> <li>Experimenting the CSS3 property <code>rgba(r,g,b,alpha)</code> to add some eye candy.</li> <li>Experimenting another CSS3 property with the <code>background-size</code> declaration to scale the background image to full page height. Strangely browsers like Opera zoom both text and images, this can lead to unesthetic result.</li> </ul> <p>Fixed line length is a myth The following paragraphs contain a dummy lorem ipsum text for reference and two 80 characters long strings. If you zoom or play with your font family/size you will see that this CSS with cste em block width is far from perfect. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed accumsan sollicitudin... <em><a href="http://www.jdobbelstein.eu/blog/post/2010/05/01/A-new-version-for-the-Deep-Blue-DotClear-theme">Read</em> A new version for the &quot;Deep Blue&quot; DotClear theme</a></p> Sondage dcWave urn:md5:26d2e15848e6156f726321459c46346a 2009-12-20T02:51:00+01:00 Johan network dotclearfrwavewww <p>Petit test pour tester l'usage de cette chose hautement inutile.</p> <p>Bon alors la question est simple : j'ai un p'tit plug-in sous la main qui permet d'inclure plus ou moins sans soucis des Google Waves sous DotClear. Je cherche un logo pour le plug-in (et un occasion de poster sur DotClear / créer une Wave). Petit rappel, les logos de Wave et DotClear sont les suivants : Les propositions sont les suivantes :... <em><a href="http://www.jdobbelstein.eu/blog/post/2009/12/20/Sondage-dcWave">Read</em> Sondage dcWave</a></p> Wave plugin 0.2 urn:md5:99d0e1396a0268aceb477e344a9a587d 2009-12-18T01:01:00+01:00 Johan network dotclearwavewww <p>The GoogleWave plug-in for DotClear 2.x is updated with improvements and bugfixes.</p> <p>Let's start with a pretty summary : jDS@toto ~/dev.dcWave $ git diff --stat --summary v0.1..v0.2.0 _admin.php | 97 +++++++++++++++----- _define.php | 6 +- _install.php | 23 ++++-- _prepend.php | 3 + _public.php | 8 +- inc/class.dcwave.config.php |... <em><a href="http://www.jdobbelstein.eu/blog/post/2009/12/18/Wave-plugin-0.2">Read</em> Wave plugin 0.2</a></p> Wave plugin 0.1 urn:md5:394da198976f82f223877d0ca193eeb2 2009-12-15T01:59:00+01:00 Johan network dotclearwavewww <p>Dotclear is great. Dotclear is simple (until you try to read and understand the code). Dotclear is W3C compliant. But ... there is not yet a plug-in to easily include a Google® Wave. ... so let's try to add a wave smoothly.</p> <p>Edit: move from googleWave 0.1 to dcWave 0.2.0. Old div.waves on this pages do not work any more with my new javascript wrapper. To get the latest news, please go on the next entry No worries, I've looked everywhere on the web to find some clues on how to do it. The first version of the Dotclear plug-in gives the following result : Wave v0.1... <em><a href="http://www.jdobbelstein.eu/blog/post/2009/12/15/Wave-plugin-0.1">Read</em> Wave plugin 0.1</a></p>