January 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] Help us to have really cool Pharo 3 release!

by Norbert Hartl

Iâve started two weeks ago porting my first project to pharo3. Well, I donât know the real name for the action because it was not a real porting. It just loaded in pharo3 without any interaction by me. Ok, I think this is called âinstallationâ :) Very nice! Norbert Am 04.01.2014 um 11:17 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi guys, > > As you know, we are now in beta for Pharo 3. > That means we are just fixing bugs and improving stability (they are some attempts from some very impatient people to add yet new features, but so far we are managing them with the ability of a goal keeper :) ) > > What we need now is your help! How? > > 1) Is NOW the moment of porting your projects to Pharo 3. Yesâ¦ is not stable, but it improves everyday and if you help us catching bugs, it will in march, when the release should happen) > 2) Report BUGS. Yepâ¦ we still have many of them. Best way to report a bug is: to add a bug entry and to open a discussion in dev mailing list. Just one of both does not works fine because we are in the run, and: if you just open the bug, we can miss his importance, if you just start a thread, we are for sure owing to be covered of work and we will forget your important change. . > 3) If you feel in the mood, you can fix some of your annoying bugs by yourself. With the introduction of Komitter (thanks Ben!) you donât even need to work in a separate imageâ¦ it can be fixed in your working image and you can send a SLICE with just the changes you want. > 4) or you can just help us reviewing fixes (usually in status âFix Reviewed By The Monkeyâ, they need to be moved to âFix To Includeâ, and that in some cases (when is UI related, for instance) requires human intervention. > > Donât wait until tomorrow! > Pharo needs you TODAY! > > cheers, > Esteban

Jan. 4, 2014

Help us to have really cool Pharo 3 release!

by Esteban Lorenzano

Hi guys, As you know, we are now in beta for Pharo 3. That means we are just fixing bugs and improving stability (they are some attempts from some very impatient people to add yet new features, but so far we are managing them with the ability of a goal keeper :) ) What we need now is your help! How? 1) Is NOW the moment of porting your projects to Pharo 3. Yesâ¦ is not stable, but it improves everyday and if you help us catching bugs, it will in march, when the release should happen) 2) Report BUGS. Yepâ¦ we still have many of them. Best way to report a bug is: to add a bug entry and to open a discussion in dev mailing list. Just one of both does not works fine because we are in the run, and: if you just open the bug, we can miss his importance, if you just start a thread, we are for sure owing to be covered of work and we will forget your important change. . 3) If you feel in the mood, you can fix some of your annoying bugs by yourself. With the introduction of Komitter (thanks Ben!) you donât even need to work in a separate imageâ¦ it can be fixed in your working image and you can send a SLICE with just the changes you want. 4) or you can just help us reviewing fixes (usually in status âFix Reviewed By The Monkeyâ, they need to be moved to âFix To Includeâ, and that in some cases (when is UI related, for instance) requires human intervention. Donât wait until tomorrow! Pharo needs you TODAY! cheers, Esteban

Jan. 4, 2014

Re: [Pharo-users] Porting to Bleeding Edge (was Spotlight Demo)

by Sven Van Caekenberghe

Hi Sean, I seem to remember that building up to 2.0 you fixed lots of usability bugs/problems ;-) Yes, we have a new debugger and inspector (and the browser is evolving as well), which does indeed mean that there are sometimes issues with these essential tools. This is annoying, but the only way to move forward is to eat our own dogwood and help report and fix the remaining issues. Ultimately, it is your own choice, of course. Depending on your needs, the good old trusted 2.0 might be a better (business) choice indeed. But for new developments like your demo, using 3.0 might be more logical, as Doru suggested. I am/have been using 3.0 exclusively as well. Sven On 04 Jan 2014, at 05:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tudor Girba-2 wrote >>> You would recommend 3.0 even for production systems? >> I certainly do recommend it. I am using it since 3 months in production, >> and for my purposes (mainly using Moose for various analyses), it works >> perfectly. > > I debated whether to post this, since I certainly do not want to discourage > people from porting, or take away any enthusiasm for the upcoming release, > but thought it was an important user experience... > > I took the seemingly unanimous advice from the Spotlight thread, and tried > to work in 3.0. The first time I brought up a debugger (which is a frequent > occurrence in my workflow), I tried to DoIt "self selectedItem", and the > debugger replied that it did not know the variable selectedItem and would I > like to create an instance/temporary variableâ¦ huh?! I quickly ran into a > few more slowdowns and annoyances (like all-repos-shown-in-MC-browser). > > So I was in the position that I had invested part of my limited time window > getting set up on 3.0, only to figure out that I couldn't do something > essential. Even to report the bug would've eaten up more time. I slunk back > to 2.0 and got back to work for the time I had left. > > Do we want 3.0 to be banged on as much as possible? Yes! > Is it amazingly stable given the breath and depth of changes to core? Yes! > > But I don't think the decision is a slam dunk no-brainer just yetâ¦ > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Porting-to-Bleeding-Edge-was-Spotlight-Demo-tp4734028… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Jan. 4, 2014

Re: [Pharo-users] Porting to Bleeding Edge (was Spotlight Demo)

by Marcus Denker

On 04 Jan 2014, at 10:36, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > you just hit *the* bug we were havingâ¦ but AFAIK it should fixed now. > Which version did you tried? > Yes, and it was an unfortunate bugâ¦ I nearly reverted the causing issue 20 minutes after introducing it. But then I did not, and then it was christmas, and then we had (have) trouble with the buildâ¦ so it took more than one week to get it fixed. (introduced friday, fixed monday a week later). > Esteban > > On 04 Jan 2014, at 05:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> Tudor Girba-2 wrote >>>> You would recommend 3.0 even for production systems? >>> I certainly do recommend it. I am using it since 3 months in production, >>> and for my purposes (mainly using Moose for various analyses), it works >>> perfectly. >> >> I debated whether to post this, since I certainly do not want to discourage >> people from porting, or take away any enthusiasm for the upcoming release, >> but thought it was an important user experience... >> >> I took the seemingly unanimous advice from the Spotlight thread, and tried >> to work in 3.0. The first time I brought up a debugger (which is a frequent >> occurrence in my workflow), I tried to DoIt "self selectedItem", and the >> debugger replied that it did not know the variable selectedItem and would I >> like to create an instance/temporary variableâ¦ huh?! I quickly ran into a >> few more slowdowns and annoyances (like all-repos-shown-in-MC-browser). >> >> So I was in the position that I had invested part of my limited time window >> getting set up on 3.0, only to figure out that I couldn't do something >> essential. Even to report the bug would've eaten up more time. I slunk back >> to 2.0 and got back to work for the time I had left. >> >> Do we want 3.0 to be banged on as much as possible? Yes! >> Is it amazingly stable given the breath and depth of changes to core? Yes! >> >> But I don't think the decision is a slam dunk no-brainer just yetâ¦ >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Porting-to-Bleeding-Edge-was-Spotlight-Demo-tp4734028… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> > >

Jan. 4, 2014

Re: [Pharo-users] Porting to Bleeding Edge (was Spotlight Demo)

by Esteban Lorenzano

you just hit *the* bug we were havingâ¦ but AFAIK it should fixed now. Which version did you tried? Esteban On 04 Jan 2014, at 05:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tudor Girba-2 wrote >>> You would recommend 3.0 even for production systems? >> I certainly do recommend it. I am using it since 3 months in production, >> and for my purposes (mainly using Moose for various analyses), it works >> perfectly. > > I debated whether to post this, since I certainly do not want to discourage > people from porting, or take away any enthusiasm for the upcoming release, > but thought it was an important user experience... > > I took the seemingly unanimous advice from the Spotlight thread, and tried > to work in 3.0. The first time I brought up a debugger (which is a frequent > occurrence in my workflow), I tried to DoIt "self selectedItem", and the > debugger replied that it did not know the variable selectedItem and would I > like to create an instance/temporary variableâ¦ huh?! I quickly ran into a > few more slowdowns and annoyances (like all-repos-shown-in-MC-browser). > > So I was in the position that I had invested part of my limited time window > getting set up on 3.0, only to figure out that I couldn't do something > essential. Even to report the bug would've eaten up more time. I slunk back > to 2.0 and got back to work for the time I had left. > > Do we want 3.0 to be banged on as much as possible? Yes! > Is it amazingly stable given the breath and depth of changes to core? Yes! > > But I don't think the decision is a slam dunk no-brainer just yetâ¦ > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Porting-to-Bleeding-Edge-was-Spotlight-Demo-tp4734028… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Jan. 4, 2014

Re: [Pharo-users] ZdcSecureSMTPClient mail sending.

by Sven Van Caekenberghe

On 04 Jan 2014, at 04:41, irfankhan1 <irfankhan(a)hotmail.ca> wrote: > Hi i am trying to send mail using ZdcSecureSMTPClient class, here is the code > i tried on workspace. > | mailMessage | > mailMessage := MailMessage empty. > mailMessage setField: 'subject' toString: 'ZdcSecureSMTPClient Test'. > mailMessage body: (MIMEDocument > contentType: 'text/plain' > content: 'This is test from Pharo Smalltalk'). > ZdcSecureSMTPClient > sendUsingGMailAccount: 'sender(a)gmail.com' > password: 'mypass' > to: 'reciever(a)gmail.com' > message: mailMessage. > > Everytime i try running this code , it gives me a debugger saying > "connection timedout: cannot connect". I tried this with pharo 2.0 and pharo > 3.0 on ubuntu OS both versions had the same problem, But this worked fine > on windows 7 when i added *SqueakSSL.dll*. I am not sure if i need some ssl > plugin for ubuntu?? <http://forum.world.st/file/n4734027/1.png> Yes, you need an SSL plugin next to the VM, the Pharo VM comes with the SSL plugin included. What does [ ZdcPluginSSLSession new destroy. true ] on: ZdcPluginMissing do: [ false ]. return (on Linux) ? Do the unit tests for Zodiac pass (on Linux) ? Sven

Jan. 4, 2014

Porting to Bleeding Edge (was Spotlight Demo)

by Sean P. DeNigris

Tudor Girba-2 wrote >> You would recommend 3.0 even for production systems? > I certainly do recommend it. I am using it since 3 months in production, > and for my purposes (mainly using Moose for various analyses), it works > perfectly. I debated whether to post this, since I certainly do not want to discourage people from porting, or take away any enthusiasm for the upcoming release, but thought it was an important user experience... I took the seemingly unanimous advice from the Spotlight thread, and tried to work in 3.0. The first time I brought up a debugger (which is a frequent occurrence in my workflow), I tried to DoIt "self selectedItem", and the debugger replied that it did not know the variable selectedItem and would I like to create an instance/temporary variableâ¦ huh?! I quickly ran into a few more slowdowns and annoyances (like all-repos-shown-in-MC-browser). So I was in the position that I had invested part of my limited time window getting set up on 3.0, only to figure out that I couldn't do something essential. Even to report the bug would've eaten up more time. I slunk back to 2.0 and got back to work for the time I had left. Do we want 3.0 to be banged on as much as possible? Yes! Is it amazingly stable given the breath and depth of changes to core? Yes! But I don't think the decision is a slam dunk no-brainer just yetâ¦ ----- Cheers, Sean -- View this message in context: http://forum.world.st/Porting-to-Bleeding-Edge-was-Spotlight-Demo-tp4734028… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 4, 2014

ZdcSecureSMTPClient mail sending.

by irfankhan1

Hi i am trying to send mail using ZdcSecureSMTPClient class, here is the code i tried on workspace. | mailMessage | mailMessage := MailMessage empty. mailMessage setField: 'subject' toString: 'ZdcSecureSMTPClient Test'. mailMessage body: (MIMEDocument contentType: 'text/plain' content: 'This is test from Pharo Smalltalk'). ZdcSecureSMTPClient sendUsingGMailAccount: 'sender(a)gmail.com' password: 'mypass' to: 'reciever(a)gmail.com' message: mailMessage. Everytime i try running this code , it gives me a debugger saying "connection timedout: cannot connect". I tried this with pharo 2.0 and pharo 3.0 on ubuntu OS both versions had the same problem, But this worked fine on windows 7 when i added *SqueakSSL.dll*. I am not sure if i need some ssl plugin for ubuntu?? <http://forum.world.st/file/n4734027/1.png> -- View this message in context: http://forum.world.st/ZdcSecureSMTPClient-mail-sending-tp4734027.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 4, 2014

Re: [Pharo-users] Number slider

by Benjamin

Not that I know. But itâs pretty easy to do :) Ben On 03 Jan 2014, at 15:01, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > Hello, > > Do we have number slider Morph like this one: > http://diveintohtml5.info/i/input-type-number-opera.png > > Thanks > > Hilaire > > > -- > Dr. Geo http://drgeo.eu > >

Jan. 3, 2014

Number slider

by Hilaire Fernandes

Hello, Do we have number slider Morph like this one: http://diveintohtml5.info/i/input-type-number-opera.png Thanks Hilaire -- Dr. Geo http://drgeo.eu

Jan. 3, 2014