April 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [pharo3 issues] down to 17 issues

by Ben Coman

Marcus Denker wrote: > Hi, > > We are down to 17 open issues that are tagged âmust fixâ or higher: > > https://pharo.fogbugz.com/f/filters/64/3-0-TODO > > two of those have code that is in need of review. > > Marcus > > That is really great Marcus. Thanks for your efforts and those of the other integrators. cheers -ben

April 5, 2014

Re: [Pharo-dev] Build process of Pharo image

by Marcus Denker

On 05 Apr 2014, at 13:50, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > Ã temps, suspends ton vol! > > I will add this quote: It is costless to get things done right than undone. Yes, we need to look into a more modular build in Pharo4â¦ to not just load updates on the server but instead build from a small core (and possibly even from a bootstrap). Marcus

April 5, 2014

Re: [Pharo-dev] Build process of Pharo image

by Hilaire Fernandes

Ã temps, suspends ton vol! I will add this quote: It is costless to get things done right than undone. Hilaire Le 05/04/2014 13:16, Marcus Denker a Ã©crit : > Time. The secret is that in the end only those things are done that are done. -- Dr. Geo http://drgeo.eu

April 5, 2014

Re: [Pharo-dev] Build process of Pharo image

by Marcus Denker

On 05 Apr 2014, at 13:08, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > Hello, > > I have a question regarding the way the Pharo image is technically and > socially built. > One of the Pharo aim is to be a small and clean environment one can use > to develop and build dedicated application. > Dedicated tools as Metacello and Gofer are developed for this purpose. > Many architecture and dev tools are developed and replacing the old > ones: spec, nautillus, etc. > Now from the my peripheral point of view, it looks like these tools are > carved in the image, breaking the idea of a small and clean core image; > making difficult to build dedicated application image. > My question: why those tools were not developed to be loadable in a Pharo? > Time. The secret is that in the end only those things are done that are done. Marcus

April 5, 2014

Build process of Pharo image

by Hilaire Fernandes

Hello, I have a question regarding the way the Pharo image is technically and socially built. One of the Pharo aim is to be a small and clean environment one can use to develop and build dedicated application. Dedicated tools as Metacello and Gofer are developed for this purpose. Many architecture and dev tools are developed and replacing the old ones: spec, nautillus, etc. Now from the my peripheral point of view, it looks like these tools are carved in the image, breaking the idea of a small and clean core image; making difficult to build dedicated application image. My question: why those tools were not developed to be loadable in a Pharo? Thanks Hilaire -- Dr. Geo http://drgeo.eu

April 5, 2014

Re: [Pharo-dev] [pharo3 issues] down to 17 issues

by Marcus Denker

On 04 Apr 2014, at 18:22, MartinW <wm(a)fastmail.fm> wrote: > When i add a new bug to the issue tracker it is automatically tagged as "fix > if time". Am i supposed to change this label to higher priority if i think > it's appropriate - Yes! > or is someone reviewing new entered bugs and assigning > priorities to them? That too, but there is no automatism. People look at the tracker and check and change/sort, and over time some consensus is found what status an issue should have. (it would be nice to have more people looking at the tracker from time to time to help with this) > Anyway here's the bug: https://pharo.fogbugz.com/f/cases/13175/ > I put it higher so we do not forget to merge it withthe other duplicated reports. Marcus

April 5, 2014

Re: [Pharo-dev] ConfigurationOfMongoTalk load?

by Norbert Hartl

Strange! I downloaded a fresh image and could load it just. Can you tell what the error is saying? It is hard to help without information. Norbert > Am 04.04.2014 um 23:28 schrieb Sebastian Sastre <sebastian(a)flowingconcept.com>: > > sorry yeah itâs a fresh image, latest version: > 30814 > > I can only load it using bleedingEdge > > > > >> On Apr 4, 2014, at 4:50 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Loads fine in a fresh 3.0 image for me. How did you load it? You should give some version numbers along with the problem! >> >> Norbert >> >>> Am 04.04.2014 um 21:30 schrieb Sebastian Sastre <sebastian(a)flowingconcept.com>: >>> >>> #load complains about no defined stable* >>> >>> should I load bleeding edge or development? >>> >>> BTW they sound like the same thing, whatâs the difference between those branches? >>> >>> >>> >>> *suggestion: even if itâs beta or alpha I would make a stable just to set a foundation that does not confuses the users > >

April 5, 2014

Re: [Pharo-dev] ConfigurationOfMongoTalk load?

by Sebastian Sastre

On Apr 4, 2014, at 8:21 PM, Ben Coman <btc(a)openInWorld.com> wrote: > I strongly disagree with defining #stable when its not. This completely breaks trust in #stable. Alternatively, it might be good that when #load complains about missing #stable, it suggests the other tags that are defined. > cheers -ben I get your point. Then what would make sense is to fallback to a #beta or #alpha release right? Right now weâre falling back to an exception that would be understood only by the ConfigurationOf priesthood. We need as much gentle starts of high return and good practices as possible guysâ¦ >>> bleeding edge or development? >>> >>> BTW they sound like the same thing, whatâs the difference between those branches?

April 4, 2014

Re: [Pharo-dev] ConfigurationOfMongoTalk load?

by Ben Coman

April 4, 2014

Re: [Pharo-dev] font folder on win7

by Ben Coman

April 4, 2014