March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] https://pharo.fogbugz.com : can I have an account there?

by Esteban Lorenzano

you can get account directly going to the monkey place: bugs.pharo.org Esteban On Mar 23, 2013, at 4:16 PM, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > Can I also get an account? > > Cheers, > Andrei > > On Fri, Mar 15, 2013 at 10:07 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >> On 2013-03-15, at 21:10, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Can I get an account, too? >> >> done >> >>> Doru >>> >>> >>> On Mar 15, 2013, at 5:31 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>>> >>>> On 2013-03-15, at 17:25, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: >>>> >>>>> Will the bugtracker be open one day? >>>>> >>>>> Can I have an account? >>>> >>>> you're in, request a new password when you connect and everything should work. >>>> >>>>> >>>>> Esteban A. Maringolo >>>>> >>>>> >>>>> 2013/3/8 phil(a)highoctane.be <phil(a)highoctane.be>: >>>>>> 'k thx. >>>>>> >>>>>> I do use FBZ since quite a while (v3), so good :-) >>>>>> >>>>>> 2013/3/8 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: >>>>>>> For now we are just migrating, but soon the doors will be open : >>>>>>> >>>>>>> Steps needed before official announcement: >>>>>>> - Migrate all issues ( we are currently at 7026 issues migrated) >>>>>>> - Deploy the Penelope website (to register easily to the issue tracker and >>>>>>> have a list of open issues) >>>>>>> - Fix dependency between issues (blockedOn:) >>>>>>> - Polish a bit statuses in fogbugz >>>>>>> The plan is to announce it at the same time that the announcement of >>>>>>> Pharo2.0 release :) >>>>>>> >>>>>>> Ben >>>>>>> >>>>>>> On Mar 8, 2013, at 11:13 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>>>> >>>>>>> patience, patience :D, we will announce that pretty soon. >>>>>>> until then you can still report on the old issue tracker. >>>>>>> >>>>>>> On 2013-03-08, at 10:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>>>>>> >>>>>>> How to do? >>>>>>> >>>>>>> Guess bug reporting occurs there now. >>>>>>> >>>>>>> Regards, >>>>>>> Phil >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "We cannot reach the flow of things unless we let go." >>> >>> >>> >>> >> >> >

March 23, 2013

Re: [Pharo-project] https://pharo.fogbugz.com : can I have an account there?

by Andrei Vasile Chis

Can I also get an account? Cheers, Andrei On Fri, Mar 15, 2013 at 10:07 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-03-15, at 21:10, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Can I get an account, too? > > done > >> Doru >> >> >> On Mar 15, 2013, at 5:31 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> >>> On 2013-03-15, at 17:25, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: >>> >>>> Will the bugtracker be open one day? >>>> >>>> Can I have an account? >>> >>> you're in, request a new password when you connect and everything should work. >>> >>>> >>>> Esteban A. Maringolo >>>> >>>> >>>> 2013/3/8 phil(a)highoctane.be <phil(a)highoctane.be>: >>>>> 'k thx. >>>>> >>>>> I do use FBZ since quite a while (v3), so good :-) >>>>> >>>>> 2013/3/8 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: >>>>>> For now we are just migrating, but soon the doors will be open : >>>>>> >>>>>> Steps needed before official announcement: >>>>>> - Migrate all issues ( we are currently at 7026 issues migrated) >>>>>> - Deploy the Penelope website (to register easily to the issue tracker and >>>>>> have a list of open issues) >>>>>> - Fix dependency between issues (blockedOn:) >>>>>> - Polish a bit statuses in fogbugz >>>>>> The plan is to announce it at the same time that the announcement of >>>>>> Pharo2.0 release :) >>>>>> >>>>>> Ben >>>>>> >>>>>> On Mar 8, 2013, at 11:13 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>>> >>>>>> patience, patience :D, we will announce that pretty soon. >>>>>> until then you can still report on the old issue tracker. >>>>>> >>>>>> On 2013-03-08, at 10:51, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>>>>> >>>>>> How to do? >>>>>> >>>>>> Guess bug reporting occurs there now. >>>>>> >>>>>> Regards, >>>>>> Phil >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "We cannot reach the flow of things unless we let go." >> >> >> >> > >

March 23, 2013

Re: [Pharo-project] Problem downloading packages with Monticello from Smalltalkhub because of setAcceptEncodingGzip

by Andrei Vasile Chis

Hi Stef, > we will introduce your debugger model in 3.0a. It is ok? Yes, it's ok. Right now this only means adding two new classes. Cheers, Andrei

March 23, 2013

Re: [Pharo-project] one-click is dead, now we have platform specific builds

by Mark Bestley

On 19/03/2013 18:49, phil(a)highoctane.be wrote: > It is good for making OSX apps. For the rest, yeah, it is an alien creature. > And even for OSX it is not well behaved - no program should write to its own app bundle, this has been true since the OS started as NextStep in 1989. All the Application bundle should be assume=d to be in a read only state possibly on a read only drive, On reason is to allow multiple users to use the same Application without overwriting each others work. . In 10.8 and with various setups (see Gatekeeper) the applications are signed to make sure no virus or anything else alter them, I note that Pharo is not signed and so I have to disable signed checks for all applications on OSX. For OSX what should probably happen is that the image is saved to ~/Library/Application Support, either by a stub program copying the image from the app bundle on first startup or by altering the save method >> Thanks for just doing it ;-) >> >> The One-Click concept was/is cool, but it is more a barrier than a solution it seems. >> >> Having a single download that 'just works' and feels native is very important. >> >> Sven Where is this just working download the pharo page <http://www.pharo-project.org/home> still has the one click image. -- Mark

March 23, 2013

[Pharo-project] [update 3.0] #30010

by Marcus Denker

30010 ----- 10076 Cleaning code formatting of criticbrowser https://pharo.fogbugz.com/f/cases/10076/ 10101 Object: remove #class https://pharo.fogbugz.com/f/cases/10101 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Manifest-Tests-MarcusDenker.… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Manifest-CriticBrowser-Marcu… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Manifest-Core-MarcusDenker.1… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Kernel-MarcusDenker.1345

March 23, 2013

Re: [Pharo-project] Configurations PetitParser, Grease and Seaside31 for Pharo20

by Diego Lont

On Mar 22, 2013, at 9:36 PM, stephane ducasse wrote: >>> >> >> Since the configuration of Seaside 3.1 is still unfinished: contact me if you would like to have this configuration, or SeasideRest and/or Magritte, as they depend on Seaside 3.1. >> >> The configurations of Grease and PetitParser are done and load properly. I included them here. Can I put them in the verified repository or does someone wants to check them and upload them here? >> <ConfigurationOfGrease-DiegoLont.189.mcz><ConfigurationOfPetitParser-DiegoLont.30.mcz> > > We migrated the configurationOfPetitParser to its new home. So what is the difference? > The versions of PetitParser were not yet updated in the latest version, causing the stable version to break that "BlockClosure asParser" could not be loaded. So I updated the versions, and adding to stable that for Pharo 2.0 is the stable version is 1.6.1

March 23, 2013

[Pharo-project] [update 3.0] #30009

by Marcus Denker

30009 ----- 10005 floatPrecision: setter is missing from UpdatingStringMorph https://pharo.fogbugz.com/f/cases/10005/ 10100 TaskListMorph: remove unused classVar UseHistoricalShortcuts https://pharo.fogbugz.com/f/cases/10100 10099 Improve CommandLineArgument API optionAt:ifPresent: https://pharo.fogbugz.com/f/cases/10099/ 10095 HandMorph>>userPicture[:aPicture] unused. Can be removed. https://pharo.fogbugz.com/f/cases/10095 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/System-CommandLine-MarcusDen… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Polymorph-Widgets-MarcusDenk… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Morphic-MarcusDenker.1380

March 23, 2013

Re: [Pharo-project] Your earlier problems accessing Monticello

by Guido Chari

Yes, i'm sure this will do the fix. Nevertheless, as soon as i come back home i will send you the confirmation. Thanks 2013/3/23 Camillo Bruni <camillobruni(a)gmail.com> > Guido is right now in Lille :P so you have to wait for a week. > From what I recall it was exactly that bug we had over in Argentina :) > > On 2013-03-23, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Guido, > > > > Some time ago you were unable to access Monticello from inside your > particular network situation. > > > > > http://forum.world.st/Unable-to-use-Monticello-in-last-images-from-Jenkins-… > > > > We just were able to solve a similar case. > > > > > http://forum.world.st/Problem-downloading-packages-with-Monticello-from-Sma… > > > > Would it be possible to verify, first that your old problem still > exists, and then try again with the following patch. > > > > SocketStream>>next: count > > "Read count elements and return them in a collection. > > If the receiver is #atEnd before count elements were read, return > a smaller collection." > > > > ^ self nextInto: (self streamBuffer: count) > > > > That would be most helpful. > > > > Thx, > > > > Sven > > > > -- > > Sven Van Caekenberghe > > http://stfx.eu > > Smalltalk is the Red Pill > > > > > > >

March 23, 2013

Re: [Pharo-project] Your earlier problems accessing Monticello

by Sven Van Caekenberghe

Aah, all this travelling around, it is a wonder you guys actually get any work done ;-) Seriously, it is a good thing we're in contact and that he might be able to test. On 23 Mar 2013, at 11:21, Camillo Bruni <camillobruni(a)gmail.com> wrote: > Guido is right now in Lille :P so you have to wait for a week. > From what I recall it was exactly that bug we had over in Argentina :) > > On 2013-03-23, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Hi Guido, >> >> Some time ago you were unable to access Monticello from inside your particular network situation. >> >> http://forum.world.st/Unable-to-use-Monticello-in-last-images-from-Jenkins-… >> >> We just were able to solve a similar case. >> >> http://forum.world.st/Problem-downloading-packages-with-Monticello-from-Sma… >> >> Would it be possible to verify, first that your old problem still exists, and then try again with the following patch. >> >> SocketStream>>next: count >> "Read count elements and return them in a collection. >> If the receiver is #atEnd before count elements were read, return a smaller collection." >> >> ^ self nextInto: (self streamBuffer: count) >> >> That would be most helpful. >> >> Thx, >> >> Sven >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> > >

March 23, 2013

Re: [Pharo-project] one-click is dead, now we have platform specific builds

by Frank Church

First rule for open source projects: The Customer is always right even if he doesn't pay for the product!! On 22 March 2013 20:26, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>> Hmm, I've got to wonder whether, if it had actually _worked_ the first >> time for him, whether he'd have written those negative comments at >> all. I mean, at first he actually wrote: >> >> "I was excited to get started, so I figured I could download the >> "one-click" for version 1.4 and get started right away." >> >> At that point, he had no problems with the _idea_ of one-click. It >> later seemed it was only the implementation he didn't like. >> >> I'm interested in the topic of app-accessibility, and that's why I'm >> really parsing his words and trying to understand. Since he also >> wrote: >> >> "...and it definitely doesn't show that the developers know how to >> properly distribute their software for multiple platforms..." >> >> I wish he'd have enlightened us all, WHAT is the the way to properly >> distribute one's software for multiple platforms besides the browser.. > > :) > > talking and ranting is easier than doing syndrome as usual :). > > Stef > -- Frank Church ======================= http://devblog.brahmancreations.com

March 23, 2013