Plazes Acquired By Nokia
June 23rd, 2008
- Category:
- Notebook
Plazes – the startup which I am working for – is going to be acquired by Nokia.
Time for some champagne on a monday morning! W000t!!!1!
Jump to: Search, Additional Information.
June 23rd, 2008
Plazes – the startup which I am working for – is going to be acquired by Nokia.
Time for some champagne on a monday morning! W000t!!!1!
May 7th, 2008
“The sad truth about CSS3 selectors is that they really shouldn’t be used at all if you care about page performance. Decorating your markup with classes and ids and matching purely on those while avoiding all uses of sibling, descendant and child selectors will actually make a page perform significantly better in all browsers.”
April 27th, 2008
Dan Webb has written an event delegation plugin the other day (as part of Low Pro for jQuery) – I really like his solution and as soon as you are working with Ajax page updates a lot you got to love the ease the event delegation technique provides.
There is one major drawback though. In IE submit and reset events do not bubble, thus you cannot use delegation here. Same is true for submit events in Safari 2.
In the upcoming Plazes delegation for submit/reset events turned out to be a requirement, so I wrote an event delegation plugin based on Dan Webb’s stuff, in particular on what Yehuda Katz proposed in one of the comments, and added workarounds for IE and Safari, so that you can now use delegation for these events just as you would expect. There were also some issues with using confirm().
I needed to do that quickly, thus the code could use some optimization (later).
Get it here:
http://stilbuero.de/jquery/delegate/
I just noticed that Jörn Zaefferer wrote something similar for the focus and blur events and I’m going to merge the two.
October 26th, 2007
<marquee direction="right">...</marquee>
Try it ;-)
(Courtesy of Sean Treadway – thanks for making my day!)
October 23rd, 2007
Being a part of the jQuery UI project, UI Tabs aka Tabs 3 has been released the other day.
Until today I have fixed a bunch of bugs that popped up and I hope Tabs 3 is stable now. I’ve added a couple of frequently requested features but please be aware that the new Tabs require jQuery 1.2.1 and also that I have left away history support for now. The history plugin itself needs a major overhaul and when that is done I will build it into Tabs again. I have closed down comments on all of the Tabs 2 posts to indicate that this version will not be maintained any longer.
If you’d like to report a bug, I’d like to ask to you to file a ticket. This way it’s much easier to keep track of bugs and if you post a bug in the comments I will create a ticket anyway.
To be consistent with other UI modules, i.e. to conform to some conventions we set up, the Tabs API has changed quite a bit. The documentation, which has been moved from the source file to the jQuery documentation Wiki is your friend (and because it’s a Wiki everybody can help to improve it – remember I’m not a native english speaker and documenting code is not always easy for me). I’ll also write a follow-up post about the most important changes and additions.
Thank you for using Tabs!
May 14th, 2007
Just a short note, I’ve updated the CSS for the Tabs plugin – because people did not stop asking – and tabs have a flexible width and height again. They still maintain a minimal width as well, so that tabs with short titles, as in the demo, will have the same width. Otherwise it would look a little cluttered (well, at least to me). I’m using a sprite technique for the different parts of the tab of course, thus only one image needs to be downloaded.
Important to know is that this required an additional span element nested in the anchor element of a tab.
April 7th, 2007
I’ve added a few requested features and fixed some quirks for the Tabs plugin recently.
February 5th, 2007
I have updated the Tabs plugin the other day. It now supports loading tab
content via Ajax. As one could have expected I did that in an unobtrusive manner.
The HTML you need is slightly different from the one that is used for static tabs: A list of links pointing to existing ressources (from where the content gets loaded) and no additional containers at all (unobtrusive!). They’re going to be created on the fly:
<div id="container">
<ul>
<li><a href="ahah_1.html">Content 1</a></li>
<li><a href="ahah_2.html">Content 2</a></li>
<li><a href="ahah_3.html">Content 3</a></li>
</ul>
</div>
Initialize the tabs interface with the remote option set to true:
$('#container').tabs({remote: true});
Obviously this will degrade gracefully – the links, e.g. the content, will still be accessible with JavaScript disabled.
All other options and history support should be totally unaffected by that.
There’s another option: While the tab content is being loaded a little spinner left to the tab title text is shown (which you will hardly see on the demo, because it’s loading too fast). Just like in Firefox for example. This is controlled by a CSS class, which you can change:
$('#container').tabs({remote: true, loadingClass: 'progress'});
If you don’t want to show a spinner at all just remove the rule
.anchors .tabs-selected .tabs-loading {
...
}
from the style sheet.
February 3rd, 2007
Sweet! I am an official member of the jQuery team since yesterday.
This is pretty exciting and I’m looking forward to bring in my capabilities to an already strong team!