On Dec 7, 2012, at 11:59 PM, Nicolas Cellier wrote:
This is a long time since I did not contribute to Pharo, so I tried with something easy... http://code.google.com/p/pharo/issues/detail?id=7108
I downloaded latest successful build, Pharo2.0a Latest update: #20433
I broke the last build by integrating progress bar changes⦠:(
Then I updated the 5 methods from a MC merge, and... Err... I cannot type my initials ^H^H^H^H^H^H^H^H full name The dialog insists on selecting any letter I type and next letter will override the previous one. I finally published anonymously, that does not matterâ¦
I thikn that this is the bug I introduced by merging cmaillo' code I will rollback if it is not fixed.
But you know the impact of a first bad UI impression... It would ruin tons of efforts I know you spent cleaning the infrastructure. I believe such cleaning is very ambitious and rarely rewarding in the short termâ¦
This is worse that than we use 2.0 everyday now sometimes we make mistake.
But I'd really like to be more supportive, it's so essential for building the future.
So before ranting loud, I digged a bit further: could it be this warning I had at startup about obsolete VM, yes that was it!
No I know the problem: change 20432 and 20432
So if you are episodic user like me :
******** DON'T FORGET TO DOWNLOAD A PHARO SPECIFIC VM *************
I already spent way more time on this than I wished, hope my mistake helps someone else. ( over-estimating pharo planned obsolescence period is indeed a mistake ;) why would the VM be handled differently ? )
Because we need some specific changes for pharo.
Last thing, maybe you should insist on the download page that 2.0 REQUIRES a pharo specific VM. Not sure I would have read it, but then it would be entirely my fault.
Pharo 2.0 went beta thursday.
Nicolas