Sleep

Sleep, Sleep, Sleep

Nap, Nap, Nap

Life is pretty unexciting here. Sleep, drink liquids. I'm waking up, though, will go and get the mail (can you believe that I've not gotten the mail since I got back from my trip?) and warm up some leftover Tom Ka Gai soup and get ready to do this Bryce Talk event in an hour and a half.

Tom Ka Gai soup is where it's at. Wonderful Stuff! (Thai food, in case you don't recognize it right off the bat)

Pike observations I'm writing this in Pike. Aha! I discovered, under the File Menu, the option to change the title.

One thing I've discovered so far is this: Netscape Communicator 4.6 supports drag and drop in its text entry areas. MSIE does not. Neither does Pike. I use drag and drop in my work all the time. I have a keyboard macro that will type out an empty href tag, like so:



I get that by typing this text: "hreftag" TypeIt4me then expands that text to an empty href anchor. Usually, the text that goes inside the tag is to one side. In Netscape I select it and drag it inside. Also, I usually have at least two browser windows open. The one that belongs to me, and the one I'm referring to. I just drag the little bookmark from the other window into the double quotes area.

So I'll do an update--This is a page that shows updates on the weblogs.com site Nope. I couldn't drag and drop it from the Browser to here. Had to copy and paste. Pretty Please: Add drag and drop capability!

Another Pike alpha-beta observation: If the cursor is in the middle of a line, and I want to start a new line from that point, typing return adds a new line, but doesn't move the text to the right of the cursor to the new line. Pretty Please!

Another observation: When I changed the title a little while ago, it turns out that all the stuff that was in this window so far was also saved to the page. I don't know that I mind or not--hey, it's a way to do a partial posting, which I think is kinda nice. But it was unexpected behavior: I just wanted to change the title.

All piking thus far has been done with straight text, double returns, no outlining at all. My brains and body are frying at little over 99 degrees, so you may take these comments with a grain of feverish salt. But include the "pretty please," too.

p.s. I know I lied to you yesterday about the pictures. Gawd, I'm such a tease. But I had a good excuse; someone cast a sleep spell on me! : )

BryceTalk Farewell Steve Lareau, the inventor of the Wheeee! chairspin, did one last chairspin for posterity's sake

Comments

[Dave Polaschek]

Another Pike alpha-beta observation: If the cursor is in the middle of a line, and I want to start a new line from that point, typing return adds a new line, but doesn't move the text to the right of the cursor to the new line. Pretty Please!

That's the way the outliner in Frontier works, too. I assume they share a lot of code, so it's not that surprising. Some would call it a feature. I find myself doing a lot of shift-down-arrow cut return paste. If I were smarter, it would probably be a macro.

And actually what Pike is adding isn't so much a new line as a new subhead. It works out to being a new line with the default behavior of the PikeRenderer, but it doesn't have to be....

And when you start using the levels in the outliner more (the tab key is your friend), you'll probably find the arrow keys don't behave exactly as you'd like. After a while you get used to it and only say "D'Ohh!" about once a week. Or at least I do. Well, in Frontier. I say "D'Ohh!" a lot more than that.

Hope you feel better soon. Sleep is a good thing. So is Thai food. So are liquids.

[Donald W. Larson]

Another Pike alpha-beta observation: If the cursor is in the middle of a line, and I want to start a new line from that point, typing return adds a new line, but doesn't move the text to the right of the cursor to the new line. Pretty Please!
That is the way Frontier works and it appears that Pike is a subset of Frontier.
Hope you feel better soon. :-)