HOPomodoro (was Contribution CI Semantics)

> philippeback:
> I started this little thing, anyone welcome to improve it...
>
> http://smalltalkhub.com/#!/~philippeback/HOPomodoro

Cool idea! I fixed the layout for the Morph and the control button so it doesn't look like:




Cheers,
Sean

p.s. if you add me to the repo, I'll commit myself next time ;)

Cool :)

Benjamin Van Ryseghem-2 wrote

What I thought was cool is a pomodoro which block the ui during pauses, log the changes during sessions, and commit in the package-cache at the end of each iteration :P

Wow, I like that a lot! The beauty of turtles all the way down... not even thinkable with a web timer.

b.t.w.
    Gofer it
        smalltalkhubUser: 'philippeback' project: 'HOPomodoro';
        package: 'HighOctane-Pomodoro';
        load

I knew a slew of ideas would come :-)

And save the image with the pomodoro time stamp.

I have written a bunch of shell scripts for doing something like that, like:

opw : open pharo workspace x
rli: run latest image
lsli: list latest image

so, I do now:

opw xxx
rli

or

pharo `lsli` save NEWNAME

Phil

2013/3/25 Sean P. DeNigris <[hidden email]>:

Ben & Sean added to the repo.

I didn't had this effect, but the buttons were not resizing well.
In fact, I used standard buttons but then moved to UIManager kind of things.

We need to write something on that UIManager beast...

Phil

2013/3/25 DeNigris Sean <[hidden email]>:

philippeback wrote

I used standard buttons but then moved to UIManager kind of things.

Why not Spec?

Cause I wanted my Pomodoro to work to help with the Pomodoro technique
and do the actual work instead of turning my Pomodoro into new work
:-)

Jokes aside, I like to understand what goes under and even if I know
enough about Spec to make it work, I just felt it fine to do it like
that.

What I think is that little thingy is small enough to make people
understand how to do things from the old way to the spec way with
intermediate steps.

So, take me to the new step: Spec :-) You've go the commit rights.

Phil

2013/3/26 Sean P. DeNigris <[hidden email]>:

Interesting post on just that from one of my reference guys (from Fusebox era):

http://www.halhelms.com/blog/index.cfm?mode=entry&entry=057F0E9E-FF20-683A-FD6044016B235045

Forget git and let's make images or package-cache saves.

That's what triggered me to do the rli (run latest image) thing (attached sh)

aliases in my .profile are:

alias pharo=/usr/local/pharo/bin/vm-ui.sh
alias pharocli=/usr/local/pharo/bin/vm.sh
alias pharo20='/usr/local/pharo/bin/vm-ui.sh
/usr/local/pharo/image/20/Pharo.image'
alias pharo14='/usr/local/pharo/bin/vm-ui.sh
/usr/local/pharo/image/14/Pharo-1.4.image'

. ~/MyScripts/extracommands.sh

e.g.

opw Pomodoro
rli

opw Pomodoro
pharocli `lsli` save HODev20130336_1130
rli

Thinking of which, I'd add rpw and cpw and lspw (remove pharo
workspace, copy pharo workspace, ls pharo workspaces).

Ha, it is time to do that in Pharo itself with a command line
handler... More to learn but FileSystem is going to help for sure :-)

Phil

2013/3/25 Benjamin <[hidden email]>: