Older blog entries for cdent (starting at number 203)

While it can be effectively argued that Microsoft has made great progress with bringing Internet Explorer into the present, IE is still bad mojo. Not only is it the only popular browser limited to a particular suite of operating systems, it is on the wrong side of a very important divide.

Cool web development happens on Unix. Whether that Unix is Linux, BSD, OS X, etc doesn't matter. At some level they are close enough to alike that the job gets done. Then you hop on over to some Windows derivative and things grind to a halt.

So you got some action over on side A and a sizable set of web browsers that run across all these different operating systems. And then you've got this other browser that only runs on side B.

If Microsoft wants to show a real commitment to an open web, they need to start releasing versions of IE for other operating systems. It used to be possible to get IE for Mac and Unix. There was even a time when IE was the clear best choice of browser on a Mac.

If that doesn't happen, why should I bother targeting a tool that I can't run (easily)?

Released a new version of TiddlyWeb (1.2.60) which fixes some minor bugs in HTTP 400 handling.

Deployed TiddySpace 1.0.96, which fixes a decoding bug in ControlView.

APIs and documents on the web are the same thing; how you represent them behind the scenes is up to you, and that's been a core principle of the web since shortly after its inception. Suggesting otherwise profoundly misunderstands how implementation of web services happens

Re: [OAUTH-WG] Web Finger vs. Simple Web Discovery (SWD)

blaine kicks some righteous ass, but gets caught out later in the thread for being perhaps a little too defensive. Whatever, his comments are great.

with stuff

In the tradition of yesterday today had more fixes to edit to cover for differences in browsers' handling of window.location.hash.

/me dies

More digging in the webdav code cooking in the kitchen of fnd.

There's a good conversation started on google groups about how to create a tiddlyapp.

bengillies started work on his own version of tapas that changes the number of visible tiddlers, will eventually have scroll back into the past functionality and distinguishes between tiddlers your friends have written in their space, or anywhere across the server.

We said the following to one another:

6:25pm] cdent: oh
[6:25pm] cdent: that's a bummer
[6:25pm] cdent: i don't much care for that at all
[6:25pm] cdent: as it encourages just having one space
[6:25pm] cdent: I _want_ to know about the full breadth of stuff
[6:26pm] cdent: I certainly don't mind the code being library-ized in various ways and allowing that behavior, but for my own use I would definitely want it by modifier
[6:27pm] bengillies: right
[6:27pm] bengillies: I find it hard to separate stuff I want to know about from stuff I don't care about with modifier
[6:28pm] cdent: i tend to use tapas as a tool for doing an overview, for getting a sense of things
[6:28pm] cdent: so if I see that bengillies has suddenly started creating a bunch of tiddlers in some space called dash, then I know he's got something going on
[6:29pm] cdent: if your change was in place, and we didn't see each other in irc, the first I would have known _anything_ about dash would have been when fnd turned it on in his pace
[6:29pm] cdent: space
[6:29pm] bengillies: that's a good point
[6:31pm] cdent: and for several people I would never see their bookmarks
[6:31pm] • bengillies experiments

The result of ben's experiments changes the output from 3 columns to 4. While this divvies up the info nicely, there's something sort of unbalanced about 4 columns compared to 3.

• Made somes fixes to edit, bugs revealed by the new hashchange event handling.
• Helped fnd with his WebDav for TiddlyWeb stuff.

Both of these tasks have been stymied by differences (both gross and subtle) in implementations between clients. For the first it is browsers handling of the event. For the second it is clients making seemingly arbitrary decisions about how URIs are to be manipulated.

Sometimes I just wanna go live on a mountain, with cats. Mountain lions!

Tidied up edit to add some features:

• ability to create a new tiddler from within the freshly loaded editor
• listened for hashchange event to make it easier to load a different tiddler simply by editing the URI

Worked on a thing called tiddlybeaker which explores using tiddlyweb as the underpinning of a website framework. This is mostly a saw sharpening effort, for understanding other frameworks and some of the issues they attempt to overcome.

testing new edit functionality for new tiddler creation

Is it good enough for you now?

And now you get onhashchange too.