anonymouse: time will not continue to move forward, and as you point out, this does reduce the usable scope for the gem. I would LOVE to put this feature into Timecop, but it’s not something I’ve looked into.

I imagine a usable solution would involve the following:

1) Take the new time/date from the #travel() function and store it.
2) Compute deltas (offsets) for Time.now, DateTime.now and Date.today
3) Mock Time.now, DateTime.now and Date.today to return the current time + those deltas (rather than just returning the original mock)

It sounds do-able to me, perhaps a project for a free weekend! If you feel so inclined, the project is available on github (http://github.com/jtrupiano/timecop). Otherwise, it’s certainly something to put on my to-do list.

Thanks for checking in.

To get started, check out Adobe’s quickstart page on skinning:
http://www.adobe.com/devnet/flex/quickstart/skinning_components/

For more advanced skinning, especially for drawing skins, you might want to check out the Degrafa [http://www.degrafa.com] libraries.

You can also create a class of skins for the button:

[in the css file]
.myButtonStyle{
skin: ClassReference(”your.project.skins.MyButtonSkin”);
}

Then you would just define skins for all the states in that class. To go into the Degrafa skinning would really need another blog post and there’s a lot of info already out there on that. Hope this helps!

I love screen, but it still requires you to run the command 4 times instead of just one command, and it requires a lot more keystrokes to set up.

This way lets you change quickly which files you’re accessing by just typing them in the command.

Also to pre-empt another expected comment, yes I know about tail -f.