Cooking in the kitchen...
Wednesday, February 3, 2010 7:41:54 PM
Wednesday, February 3, 2010 7:41:54 PM
Sunday, September 20, 2009 11:54:37 AM
Sunday, April 5, 2009 11:13:25 AM
Wednesday, April 1, 2009 3:46:58 PM
Thursday, February 5, 2009 8:21:06 AM
Tuesday, October 16, 2007 12:40:14 PM
Wednesday, October 10, 2007 11:09:20 AM
Tuesday, May 22, 2007 3:41:10 PM
Sunday, July 30, 2006 4:58:13 PM
Monday, April 24, 2006 1:46:54 AM
) really is almost free.
) you might like to look at the music and trailers from SXSW this year - lots of music and film trailers, made available by the artists.Saturday, April 15, 2006 5:12:27 AM
Tuesday, April 4, 2006 3:44:43 PM
ping. That sends a little bit of information to some other computer on the net, and measures how long it takes to get back, if it does.
Friday, November 25, 2005 4:23:07 PM
Tuesday, November 22, 2005 10:56:46 PM
Monday, November 21, 2005 11:35:56 PM
I managed to get the same slides to appear in fullscreen mode (the OperaShow presentation mode), in a different style for normal on-screen reading, and to show them on my phone in a presentationoptimised for the phone. It wasn't rocket science, and I thought I would share how I did it. (Thanks Tommy for the photographic evidence that this works on a real phone running Opera Mini)
(The next bit involves digging into the HTML source code. If you think that's boring, skip to the slides themselves - if you have Opera you can switch from fullscreen (which won't work before December - only the mobile version is uploaded) to small screen rendering and see how it comes out, then write a comment saying "Oooh, Aaaah" and I will be grateful
).
So what did I do? The first thing was to write some slides, to use OperaShow. I originally did this with the online tool, because it made the stylesheet for me. I copied the entire stylesheet into a seperated file, and I edited it a bit. Then I started to look at my own slides. I had some simple XHTML - this is what OperaShow is based on - its structure is the one I got from teh generator, and it works well for me even after hacking around. I added a link to the external stylesheet I had created, and said it was for several media types:
<link rel="style" type="text/css" href="slides.css" [B]media="print, tv, projection, screen"[/B] />Then I added an internal stylesheet:
<style type="text/css" [B]media="handheld"[/B]><[CDATA[ /* Style rules go here */ ]]> </style>(Why the funny extra brackets? Because this is real XHTML, following real XML rules. Just in case someone wants to build a really basic browser that only understands real XML, and skips all the error-correcting that Opera does to make the web that's out there actually work).
What rules do I actually put in? The following isn't exactly the same as the source. I've improved a bit, left out a few repetitive things, but you should get the idea. The first ones are to reduce the margins, padding and so on to something more obvious for mobiles, and remove the big bullets from lists. Stuff like:
ul,ol,ul li { margin: 3px ; padding: 3px ; list-style: none }
There are a number of images used in the screen and projection version. Most of them are more than 50kb, they are fairly large, and they are not really cool for mobiles. Fortunately, they are all styled with a couple of classes. I added a link to a very small, mobile-optimised picture, and gave it a special class that is set not to render in the linked stylsheet. While I was there, I decided to tell a logo image to show itself small (it's not too heavy, but its normal size was much too big), and I decided the first slide was not worth seeing as a slide. Those two things have an id, so I styled them too.
#mwi {width:55px;height:58px}
.r {float:right; padding:0px; margin:0px}
.topleft, .right, #s1 {display:none}
Then I decided I wanted to make the slides stand out a bit. Put a box around them, add a little slide number to each box, like a real slideset
(This uses some CSS 2 - the counter won't work on some basic browsers, but the content is still there):
div.slide { counter-increment: slide; }
.slide { border: 1px black solid; padding: 4px; margin: 0px 0px 5px}
.slide:before { content: "Slide " counter(slide); float:right; }
By this time, I was messing around in the depths of stylesheets I never really understood before. (I found things like background images included through the use of data: URIs and all sorts of wierd and wonderful stuff). One of the things I found in the print style was that it put lots of metadata into the print version, but I was too slack to add metadata yet. (I'll dig back in and do that, because it is pretty useful as well as cool to see it printing). But I did use a couple of rules I found to add some simple metadata:
head { display: block; border: 1px black; padding:5px; width:100%}
title { display: block; padding: 0px; margin: 0px;
text-align:center ; font-weight: bold;}
If you look at the real source, you'll see the slight differences. You can look at how the other stylesheets work, too. But you're better off asking a different expert about the details of those - all I did that was special is trim them down to something I can manage, and make the mobile-friendly version work. (Even then, I could have done a bit more... maybe next time I'll explain that instead).
Friday, October 28, 2005 2:55:03 PM
It's silly, it's simple, it's gross, and it's cool
Dumb demos of simple things widgets can do.
Twitter is quick, but not always great. I always wanted a blog made up of comments - and this link category is a step in making one :)
Response to well-written blog explaining why "WYSIWYG Editors hate HTML5". I agree there are problems, I think there are solutions available.
Further exploration of how things really are and what can usefully be done.
JAWS got it wrong. Just handing over the keyboard is stupid - even if the role itself is not.
Respuestas a los comentarios sobre una entrevista de Jan Standal (de Opera).
Fotos que quero (e não)
Una conversación sobre la Web Móvil
It's not about one magic solution - this is a complex problem and lots of things need to be done.
Cool ways to manage your own location data
Porque ser abierto no es la diferencía entre exito y la muerte.
CSSquirrel suggests that listening to more people would make HTML better. I agree, but there are people who already influence HTML and should think about how they can do it better.
There is a big difference between (disabled) people achieving something, and expecting that everyone should do things "like us".