DISQUS

This really sucks.

The city is awesome though.

Really? I don’t think you will find this thing somewhere else.

Thanks for sharing them with us John.

My eyes are dazzled with your limos.

They look so cute while playing tug of war.

What did you get in your goodies?

Thanks for sharing all the nice pics.

Something I maybe didn't make clear enough is that I actually don't want the fine-grained history in the repository. I might make a checkpoint every five minutes, and many of these checkpoints are pretty low quality; I don't want them persisted.

It would be nice to have all the checkpoints persisted until the next persistable commit, and then blow them away at that point. (I just made up "persistable commit" to mean one that I want to keep in the repository, as opposed to the ones that represent ephemeral checkpoints, if I implement checkpointing as commit.) The alternative for doing that that I mention is to commit checkpoints, and then rebase them away. One disadvantage of doing this is the extra step of the rebase, along with having to remember where to rebase from. The other is that "git diff head" won't tell me what I want. Maybe tagging every persistable commit solves both these problems.

Or I could, as you suggest, make a branch, commit my checkpoints into it, "merge -squash" it into the target branch, and then delete the branch. Then a persistable commit becomes "git checkout {original}; git merge --squash wip; git commit; git checkout -b wip", where {original} depends on which branch I started from. And "git diff head" becomes "git diff {original}", where, again, {original} depends on where I started. This is heavier weight than I want, but again, maybe some scripting and/or tags makes it easier.

Right now I like the fact that "git checkout head .", "git stash", and "git checkout -m -b" operate on everything since the last persistable commit. All those things would be harder, or I'd need to write more scripts/tagging to do them, if checkpoints were commits too.

Anyway, I really started out trying to draw a picture of how the index fit in, not to try to promote my particular workflow. I've added a disclaimer paragraph to try to make this clearer.

Ouch! (But very funny.)

Thanks! It's an OpenLaszlo application; the core looks like this:

[code language="xml"]
<canvas>
<include href="filter-effects.lzx">
<class name="oflip" width="${canvas.width}" height="${canvas.height}" resource="oflip.swf" stretches="both">
<view id="outer" x="${canvas.width/2}" y="${canvas.height/2}">
</view><view id="rotor">
<oflip id="inner" x="${-canvas.width/2}" y="${-canvas.height/2}" onclick="spin()">
<blurfiltereffect name="fx">
</blurfiltereffect></oflip>
</view>

<script>
function spin() { rotor.animate('rotation', 180, 1500, true) }
</script>
</class></include></canvas>
[/code]

@class@ defines a view that's scaled to the canvas size and that embeds a Flash movie of the image. The three levels of view hierarchy are because 'rotation' is relative to the origin (the upper left corner); the @x@ and @y@ on @inner@ place the center of the image at the origin of the rotor, and the @x@ and @y@ on @outer@ place the origin of the rotor at the center of the canvas. With matrices you rotate around a point by sandwiching the rotation between a translation and its inverse; instead I represent each transformation as a view and let the rendering engine do this, so that I can animate the @rotation@ attribute and let the animation system handle the rest.

To get the shadow, move the @x@ and @y@ from @inner@ to the definition of @oflip@ in the code above, and then make two more copies of @oflip@ right above @rotor@. An interval timer copies the rotations from @inner@ -> @s1@ -> @s2@ on each frame.

[code language="xml"]
<view id="shadows">
</view><view id="s2" opacity="0.25"><oflip></oflip></view>
<view id="s1" opacity="0.5"><oflip></oflip></view>

[/code]

Mouse tracking uses Math.atan2 and the mouse position relative to outer. Motion blur animates the blur effect's blur radius up to 4 when the image is spinning and back down to 0 when it stops. Both of these piggy-back on the same interval timer that makes the shadow. I tried to turn off the effects when the frame rate got slow, but I don't think this worked, and I ran out of time.

The modified function actually _does_ guarantee the order of execution: that the code that follows the call to @requestProductDetails@ will _always_ execute prior to the invocation of the continuation parameter.

Making each part of program not rely on the order of execution may seem like a good thing, but it increases the number of required test cases exponentially, if nothing else. Some indeterminacy is inherent in distributed processing; the rest can be determinized.

Thanks for the corrections. You kindly titled your comment "I think your 10,000 foot view is off by a few miles.." [Title comments don't seem to show up in this blog theme :-( ]. It looks like I was off by about 5,000 miles -- I _like_ my thesis, but it looks like it isn't _true_.

I use these _with_ jQuery. The "jQuery utilities":http://docs.jquery.com/Utilities include the equivalents of Array#forEach, Array#map, Array#indexOf, and String#trim. That's a tad more than 10% of the Collections library, and nothing from the other two.

Thanks for the comment. You raise an interesting set of observations and questions, and I'll think more about it at length.

A quick update on queue ball: you can download it from http://github.com/osteele/mop-js, and you can get a little bit of a taste for how to use it in the specs in that repo, but I haven't had a chance yet to write up exactly how to use it for the problem described here.

ja kui uuematele Sony Ericssonidega seadistada Gmail IMAP protokolliga kirju vastu võtma, siis tekib menüüsse "Enable Pushmail" ning telefon hoiab pidevalt IMAP ühendust üleval ja uued kirjad jõuavad automaagilised koheselt telefoni kui nad ka serverisse jõuavad.

Thanks, Vidar! I make most of my illustrations, including this one, with "Omnigraffle":http://www.omnigroup.com/applications/omnigraffle/ -- in fact, it's one of the reasons that I switched back to the Mac. Nothing automated, just lots of tweaking -- which I enjoyed, because I'm trying to learn the rudiments of graphic design, and I usually learn things better if I do them by hand before trying to automate them.

Merci pwrdesc, j'ai pu installer l'application avec ton tuto, mais problème quand j'ouvre l'application je choisi le pays pour la recherche de chaines et l'appliquation se ferme...
Je suis bloqué, quoi faire maintenant?
Par contre j'ai l'icone Digital TV.
Merci pour ton aide...

Thanks, John, this is definitely worth noting.

I prefer to place the 'var' where the variable is first defined, but this is misleading to anyone coming from Java (or practically any other language), so it's a real trade off.

(I also prefer to treat variables as read-only except where there loop indices, which somewhat mitigates the problem, at least.)

I agree that thinking in types saves headaches. The point of the post was to extend code that worked only if @products@ had type Array! (a non-nullable Array, to borrow ECMAScript 4.0 notation), such that it could handle Array? (analogous Haskell Maybe [], or Scala Option[List] -- arrays aren't the same as lists, but JavaScript arrays are used where Haskell and Scala use lists). The new code is only valid if the type of @products@ is a nullable array. It won't work if you throw arbitrary data at it. After all, if products could be _anything_, it might be an object with a @length@ _method_, and then @count@ would end up with the wrong type too.

Putting scare quotes around bigotry probably doesn't help, either.

Thanks, Will!

These typos happen to exactly illustrate my point -- that when you add a temporary variable just to get a value from one line to the next, you've introduced an error site -- but I won't pretend that I did this on purpose. I've fixed these (I think) now.

Kristjan, Google readeris näitab selle blogi pealkirirjaks (title unknown). Kas see peabki nii olema?


"(title unknown)" has no unread items.

Dubai is NOT America The fight over Roan Plateau is about the issue of citizens and local communities asserting themselves into what should be public discussions in the first place--for years the oil and gas industry has been able to lease, drill, and do what it wants. 

For groups like IPAMS and 'Americans for American Energy' (which I believe describes what Hugo Chavez believes he's doing, putting multi-national energy companies under the rule of Americans (in this case, Venezuelans...but I digress), any citizen involvement that runs counter to the agenda of industry getting what it can while the gettings good  is dangerous and must be stopped. 

Over time, BLM plan would destroy what is special about Roan Palteau Over time, BLM's plan for Roan Plateau would put over 1,000 new wells on top of the Plateau, force recreation and other uses elsewhere (of which there there will soon be very little left in the Piceance), cause permanent damge to unique resources like the genetically pure strins of native trout that live in the streams atop the Plateau, result in an 18% mortality of mule deer in the area (in just the first twenty years)...

That is all spelled out specifically in the BLM plan and EIS, BTW, not spun from my head.