:) On 7 December 2012 23:59, Nicolas Cellier <[email protected]> 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 > > 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... > > 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... > 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! > 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 ? ) > > 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. >
Yes, we should mention that, especially since 2.0 now entered beta stage. But apart from this, i am really surprised that you was unable to upload MC package with 'obsolete' VM.. That warning is really just a complaint that you should get more recent VM. And unless you using file browser (which won't function properly on older vms) the other parts of system should work well. At least, this is what i experienced.. but since my development image is 2-3 months behind bleeding edge, (and only few days ago i migrated to most recent one), i cannot guarantee if it still like that i saying :) > Nicolas -- Best regards, Igor Stasenko.
