December 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] eating some obsolete dog food

by Nicolas Cellier

2012/12/8 Igor Stasenko <siguctua(a)gmail.com>: > :) > > On 7 December 2012 23:59, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> 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.. No problem to load/merge MC,. The problem I encountered was most probably related to keyboard events and their interpretation. It disappeared using correct VM. Nicolas > 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. >

Dec. 8, 2012

Re: [Pharo-project] Please use 20431 I rollback 20432 and 20433

by StÃ©phane Ducasse

On Dec 8, 2012, at 9:25 AM, StÃ©phane Ducasse wrote: > Hi guys > > Sorry for my mistake. I rollbacked 20432 and 20433 since the changes are too intrusive. https://ci.inria.fr/pharo/job/Pharo-2.0/75/ > > Stef

Dec. 8, 2012

[Pharo-project] Please use 20431 I rollback 20432 and 20433

by StÃ©phane Ducasse

Hi guys Sorry for my mistake. I rollbacked 20432 and 20433 since the changes are too intrusive. Stef

Dec. 8, 2012

Re: [Pharo-project] eating some obsolete dog food

by StÃ©phane Ducasse

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 >

Dec. 8, 2012

Re: [Pharo-project] Progress Update

by StÃ©phane Ducasse

On Dec 7, 2012, at 9:10 PM, Igor Stasenko wrote: > please fix the progress bars. i downloaded latest image today > and it blocks all existing windows from being accessible. > the only cure i found is tell world to remove all windows. > new windows working normally. Or I will rollback the change. Sorry my fault. > > > > -- > Best regards, > Igor Stasenko. >

Dec. 8, 2012

Re: [Pharo-project] eating some obsolete dog food

by Igor Stasenko

:) On 7 December 2012 23:59, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> 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.

Dec. 8, 2012

[Pharo-project] eating some obsolete dog food

by Nicolas Cellier

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. Nicolas

Dec. 7, 2012

Re: [Pharo-project] [ANN] Pharo 2.0 enters BETA

by Tudor Girba

Hi, On 6 Dec 2012, at 22:22, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Dec 6, 2012, at 8:37 PM, Tudor Girba wrote: > >> Great. >> >> We will release Moose 4.7 on top of Pharo 1.4 soon (probably next week or so), and afterwards we will immediately switch to Pharo 2.0. > > Doru I will try sunday to concentrate and see if I can understand the bug in metacello I got. That would be really great. Doru > >> >> Cheers, >> Doru >> >> >> On 6 Dec 2012, at 18:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> Hi, >>> >>> Today I finished the pending integrations for move to Pharo 2.0. >>> There is still a problem with the VMs (for NB), but that's not a stopper for moving on. >>> >>> What does this means? >>> Starting now, no new changes of API will be allowed, just bug fixes and minor enhancements that does not change the system behavior. >>> We still have a long stabilization path until we can release, but we hope a couple of months will put us in shape :) >>> >>> Esteban >> >> -- >> www.tudorgirba.com >> >> "Presenting is storytelling." >> >> > > -- www.tudorgirba.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."

Dec. 7, 2012

Re: [Pharo-project] NBFFICallback fnSpec

by Jimmie Houchin

On 12/6/2012 1:29 AM, Igor Stasenko wrote: > On 5 December 2012 22:28, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >> Hello, >> >> In one of my callbacks I have an fnSpec with an enum. >> >> ^#( void (enum sessionStatus)) >> >> from >> >> typedef void (*SESSION_STATUS_CALLBACK)(O2GSessionStatus eSessionStatus); >> >> How are enums handled in NB? >> What would be the proper type for the fnSpec and how do I access the values >> in an enum in my class? > enums are unsigned integer values , so you must change the signature > to use 'uint' > or 'uint32' type. > Then make a shared pool with constants , initialize them with proper values > and you done. Thank you very much. You have been a great help. And thank you for taking on the initiative for this vital infrastructure project. I think you are very right in your video. It is a lot of fun to do low level programming in a high level language. Thanks for making this possible. Jimmie

Dec. 7, 2012

Re: [Pharo-project] Progress Update

by Igor Stasenko

please fix the progress bars. i downloaded latest image today and it blocks all existing windows from being accessible. the only cure i found is tell world to remove all windows. new windows working normally. -- Best regards, Igor Stasenko.

Dec. 7, 2012