Re: [Pharo-dev] About Magritte Seaside

Hi Dale, Le 6 oct. 2015 à 20:23, Dale Henrichs a écrit : > > > On 10/6/15 5:10 AM, stepharo wrote: >> >> >> Le 6/10/15 11:40, Stephan Eggermont a écrit : >>> On 06-10-15 11:11, stepharo wrote: I will do a separate configuration of magritte seaside. >>> >>> You need to load the correct g

Re: [Pharo-dev] Issue Tracker Choice

> On Oct 6, 2015, at 8:30 PM, Sean P. DeNigris wrote: > > Damien Cassou-2 wrote >> could you please tell us what you don't like about FogBugz > > The main thing is that it's not designed for open source projects. Requiring > account creation before one can even search the open issues is a huge

Re: [Pharo-dev] ARM Cogit

Hi alex First we are discussing with inria to see if one of their engineer can work a month to check what jb did. Because JB was revisiting the VM from scratch but he did not finish. It will be on the roadmap for the new engineer the consortium will hire. Second you can find information about

Re: [Pharo-dev] Issue Tracker Choice

but on the other hand - it is there - it works (even if I do not like the interface) - it is a pro tools (they should not close in the next 3 months). - so the message is also that we use a pro environment Stef Le 7/10/15 05:30, Sean P. DeNigris a écrit : Damien Cassou-2 wrote

Re: [Pharo-dev] UserManager removed - alternative?

;) Ah, but http://objology.blogspot.fr/2011/09/one-of-best-bits-of-programming-advice.html You've got a score of two ending -er in a single class, tsss... ;) Nicolas

Re: [Pharo-dev] Issue Tracker Choice

Damien Cassou-2 wrote > could you please tell us what you don't like about FogBugz The main thing is that it's not designed for open source projects. Requiring account creation before one can even search the open issues is a huge barrier. I would guess most new people will hit that wall and give u

Re: [Pharo-dev] UserManager removed - alternative?

Ah, but http://objology.blogspot.fr/2011/09/one-of-best-bits-of-programming-advice.html You've got a score of two ending -er in a single class, tsss... ;) Nicolas 2015-10-06 21:53 GMT+02:00 Aliaksei Syrel : > Hi Stef, > > Thanks for explanation! I agree and looking forward to see a new solution

Re: [Pharo-dev] ARM Cogit

Alex, have you tried building a Cog VM from the Cog svn sources? I expect, provided you hack around the NativeBoost uses, that the VM will work. On Tue, Oct 6, 2015 at 12:55 PM, Aliaksei Syrel wrote: > Hi > > Any news on Pharo VM for android? ;) > > Cheers, > Alex > > On Thu, Apr 23, 2015

Re: [Pharo-dev] FogBugz-Filter

https://pharo.fogbugz.com/default.asp?pg=pgManageFilters (button next to cases > manage filters) (or https://pharo.fogbugz.com/default.asp?pg=pgFilter&ixFilter=36 ) Maybe caused by this http://forum.world.st/issue-tracker-6-issue-fixed-in-external-package-needs-to-be-pushed-into-pharo-td4853574.ht

[Pharo-dev] FogBugz-Filter

Someone changed the fogbugz filter "Fixed To Review" now it shows the same results like "fixed upstream", how can it be changed it back?

Re: [Pharo-dev] ARM Cogit

Hi Any news on Pharo VM for android? ;) Cheers, Alex On Thu, Apr 23, 2015 at 7:54 AM, stepharo wrote: > This is really excellent! > Keep pushing this. > I'm eager to play with a raspberry. > We should continue to revisit the UI elements to consume less in any case. > Because I'm convinced that

Re: [Pharo-dev] UserManager removed - alternative?

Hi Stef, Thanks for explanation! I agree and looking forward to see a new solution :) Cheers, Alex On Tue, Oct 6, 2015 at 8:26 AM, stepharo wrote: > Hi Aliak > > The design of the UserManager was plain bad. It was reintroducing > this ugly facade singleton pattern (monolitic and global

Re: [Pharo-dev] Slack?

2015-10-06 15:12 GMT-03:00 stepharo : > Not sure that yet another tool will help me to be more productive. > Don't count me in it. I don't think it aims at making somebody more productive, but instead to gather people with similar interests and avoid querying the mailing list for trivial things.

Re: [Pharo-dev] Slack?

2015-10-06 13:03 GMT-03:00 Dimitris Chloupis : > Quite frankly, the reason why IRC is so extremely popular, is because it > does its job very well and has some very nice clients. I am active at #Pharo > because I use several IRC channels, #Blender , #C++ , #Opengl , #MACOS , > #unrealengine , #emac

Re: [Pharo-dev] About Magritte Seaside

On 10/6/15 11:43 AM, stepharo wrote: Stef, I hope you and Christophe are considering cross platform considerations when implementing "new dependencies declarations at the package level" ... MonticelloConfigurations had "package level dependencies" and the implementation was extremely rigi

Re: [Pharo-dev] About Magritte Seaside

Stef, I hope you and Christophe are considering cross platform considerations when implementing "new dependencies declarations at the package level" ... MonticelloConfigurations had "package level dependencies" and the implementation was extremely rigid to the point where it wasn't possible

Re: [Pharo-dev] Mongo - find object by id

This is great I will reread soon the mongo chapter. I should start to code a real app (if only I could have the time). stef Le 7/9/15 09:00, Sabine Manaa a écrit : Hi Stephane, my changes have been integrated into the document by Johan and I checked as ok, so it is done. Regards Sabine 201

Re: [Pharo-dev] [Reflectivity] more link options and enforcing link options per Class

+ 1 Symbols and strings and arrays are dead limited objects. Not even zomby objects. No behavior no fun. The latest image now has some more options for meta links. The complete list is listed in the #defaultOptions method of MetaLink class: defaultOptions ^ #( + optionInlineMetaObject

Re: [Pharo-dev] [ANN]: AconcaguaAddOns

welcome back. Stef Le 6/10/15 16:12, Sean P. DeNigris a écrit : Sorry, just completed a massive (non-programming) project and I'm coming back to coding... hernanmd wrote First thanks for sharing this You're welcome :) hernanmd wrote Now I suppose this was AconcaguaDeluxe before? Do you h

Re: [Pharo-dev] Slack?

Not sure that yet another tool will help me to be more productive. Don't count me in it. Le 6/10/15 12:23, Yuriy Tymchuk a écrit : Hi guys, I’m thinking whether live chat can make sense for communication. And I know that there is IRC, but for some reason it’s not working for me (maybe becau

Re: [Pharo-dev] About Magritte Seaside

On 10/6/15 5:10 AM, stepharo wrote: Le 6/10/15 11:40, Stephan Eggermont a écrit : On 06-10-15 11:11, stepharo wrote: I will do a separate configuration of magritte seaside. You need to load the correct groups. Separate configurations are a bad practice and should be eliminated, not encou

Re: [Pharo-dev] Slack?

Quite frankly, the reason why IRC is so extremely popular, is because it does its job very well and has some very nice clients. I am active at #Pharo because I use several IRC channels, #Blender , #C++ , #Opengl , #MACOS , #unrealengine , #emacs , #blendercoders and #blenderpython. So the incredibl

Re: [Pharo-dev] Slack?

2015-10-06 11:41 GMT-03:00 Esteban A. Maringolo : I think it would be better than the IRC alternative, no matter how good your IRC client is. >>> >>> why? because is new? #irc is around since a lot and it has work fine for >>> many groups of different sizes. > > Ey! I know IRC and used i

Re: [Pharo-dev] Issue Tracker Choice

Sean P. DeNigris writes: > Now that the dust has settled after the move to FogBugz, maybe we should take > another look. I know that we're already spread thin, but we all know it's a > poor fit for our / OSS workflows, and I shudder to think at how many > potential contributors gave up due to th

Re: [Pharo-dev] Slack?

2015-10-06 11:31 GMT-03:00 Esteban Lorenzano : Slack works very well for large groups. I'm already using it with a group that is larger than this one. >>> >>> +1 >> >> -1 >> I do not thing a tool will change community culture (because is not about >> tools, is about community culture

Re: [Pharo-dev] Slack?

> On 06 Oct 2015, at 16:31, Esteban Lorenzano wrote: > >> >> On 06 Oct 2015, at 16:29, Esteban Lorenzano wrote: >> >> >>> On 06 Oct 2015, at 16:10, Esteban A. Maringolo wrote: >>> >>> 2015-10-06 7:56 GMT-03:00 Craig Latta : Slack works very well for large groups. I'm alr

Re: [Pharo-dev] Slack?

> On 06 Oct 2015, at 16:29, Esteban Lorenzano wrote: > > >> On 06 Oct 2015, at 16:10, Esteban A. Maringolo wrote: >> >> 2015-10-06 7:56 GMT-03:00 Craig Latta : >>> >>> >>>Slack works very well for large groups. I'm already using it with a >>> group that is larger than this one. >> >> +

Re: [Pharo-dev] Slack?

> On 06 Oct 2015, at 16:10, Esteban A. Maringolo wrote: > > 2015-10-06 7:56 GMT-03:00 Craig Latta : >> >> >> Slack works very well for large groups. I'm already using it with a >> group that is larger than this one. > > +1 -1 I do not thing a tool will change community culture (because i

[Pharo-dev] Issue Tracker Choice

Now that the dust has settled after the move to FogBugz, maybe we should take another look. I know that we're already spread thin, but we all know it's a poor fit for our / OSS workflows, and I shudder to think at how many potential contributors gave up due to the IMHO significant barriers to entry

Re: [Pharo-dev] [ANN]: AconcaguaAddOns

Sorry, just completed a massive (non-programming) project and I'm coming back to coding... hernanmd wrote > First thanks for sharing this You're welcome :) hernanmd wrote > Now I suppose this was AconcaguaDeluxe before? > Do you have a ConfigurationOf for AconcaguaAddOns? I don't recall exact

Re: [Pharo-dev] Slack?

2015-10-06 7:56 GMT-03:00 Craig Latta : > > > Slack works very well for large groups. I'm already using it with a > group that is larger than this one. +1 I think it would be better than the IRC alternative, no matter how good your IRC client is. Also it has native apps for Android, iOS, an

Re: [Pharo-dev] Latest changes broke Icons

nope they where “private”, so why to assume it? of course, they can be reintroduced, I’m not against it… :) (but in that case I would not put a misleading “private” as a category :P) Esteban > On 06 Oct 2015, at 15:51, Stephan Eggermont wrote: > > On 06-10-15 14:04, Esteban Lorenzano wrote: >

Re: [Pharo-dev] Latest changes broke Icons

On 06-10-15 14:04, Esteban Lorenzano wrote: - it you used outside the class some of the private methods (like *IconContents, etc.) I assume the private - utilities methods will remain? Stephan

[Pharo-dev] [pharo-project/pharo-core] 933000: 50368

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 933000762dd7dc73e2d7f5e0cdc7f3dcae2b8b89 https://github.com/pharo-project/pharo-core/commit/933000762dd7dc73e2d7f5e0cdc7f3dcae2b8b89 Author: Jenkins Build Server Date: 2015-10-06 (Tue, 06 Oct 2015

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50368 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] About Magritte Seaside

The many configurations of GT/Glamour have not exactly convinced me. For a configuration that works when just loading #'stable' from the configuration browser, I'd suggest trying with the configuration of BootstrapMagritte. That only runs into the #subStrings: vs #substrings:. Stephan

[Pharo-dev] [pharo-project/pharo-core] 83ee25: 50367

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 83ee253736d9f76a373be77a5b7be1d57add8e61 https://github.com/pharo-project/pharo-core/commit/83ee253736d9f76a373be77a5b7be1d57add8e61 Author: Jenkins Build Server Date: 2015-10-06 (Tue, 06 Oct 2015

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50367 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] About Magritte Seaside

Le 6/10/15 11:40, Stephan Eggermont a écrit : On 06-10-15 11:11, stepharo wrote: I will do a separate configuration of magritte seaside. You need to load the correct groups. Separate configurations are a bad practice and should be eliminated, not encouraged. I totally disagree. And groups

Re: [Pharo-dev] FastTable

Le 04/10/2015 19:12, Alexandre Bergel a écrit : > Hi! > > In the last version of Pharo, the last version of FastTable is not loaded. > Any reason why? > It would be great to have in the base image: > Morphic-Widgets-FastTable-CyrilFerlicot.48 > > It solves some bugs… > > Alexandre > For the n

Re: [Pharo-dev] Latest changes broke Icons

Ho Torsten, No, it is not broken. As I said, is an ongoing change: https://pharo.fogbugz.com/f/cases/16651 ThemeIconPack is finally renamed as ThemeIcons and all external packages extending it will be able to use. Now, some thing will not be backward compatibility: - if you used directly T

Re: [Pharo-dev] [Pharo-users] Better Code Completion

2015-10-06 10:31 GMT+02:00 Yuriy Tymchuk : > > On 06 Oct 2015, at 09:09, Nicolai Hess wrote: > > > Am 04.10.2015 23:53 schrieb "Peter Uhnák" : > > > > This is both rant and list of questions/notes/observations... > > > > ...but first of all: > > do Smalltalkers not like code completion? Because t

Re: [Pharo-dev] Slack?

Slack works very well for large groups. I'm already using it with a group that is larger than this one. -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Re: [Pharo-dev] Slack?

We use slack at work. It’s great, but I doubt its usefulness for a large community (there’s a lot going on even with only 12 people). > On 06 Oct 2015, at 12:23, Yuriy Tymchuk wrote: > > Hi guys, > > I’m thinking whether live chat can make sense for communication. And I know > that there is I

[Pharo-dev] Slack?

Hi guys, I’m thinking whether live chat can make sense for communication. And I know that there is IRC, but for some reason it’s not working for me (maybe because of clients). I’ve seen many teams using Slack [1]. Is anybody willing to try that out. Or also maybe some have already created a ph

Re: [Pharo-dev] About Magritte Seaside

On 06-10-15 11:11, stepharo wrote: I will do a separate configuration of magritte seaside. You need to load the correct groups. Separate configurations are a bad practice and should be eliminated, not encouraged. The configuration has a lot of essential complexity, as many different combinati

Re: [Pharo-dev] About Magritte Seaside

> On Oct 6, 2015, at 11:11 AM, stepharo wrote: > > Hi guys > > How can I get Magritte seaside (and a working version not one breaking on XML > I do not what)? > I loaded the published stable version of Magritte into Pharo and there is no > seaside version. > I checked the configuration and it

Re: [Pharo-dev] Latest Build added items that are not yet set as "to include"

I thought that I did it so may be I did it on the wrong issue. Now it would be nice if you could get much nicer with people spending their time to improve Pharo. You are not the only one looking at bug and improving pharo. Stef Le 6/10/15 10:47, Marcus Denker a écrit : On 06 Oct 2015, at 10:

[Pharo-dev] About Magritte Seaside

Hi guys How can I get Magritte seaside (and a working version not one breaking on XML I do not what)? I loaded the published stable version of Magritte into Pharo and there is no seaside version. I checked the configuration and it is so complex I have the impression that we need to distin

Re: [Pharo-dev] [Pharo-users] Better Code Completion

Am 04.10.2015 23:53 schrieb "Peter Uhnák" : > > This is both rant and list of questions/notes/observations... > > ...but first of all: > do Smalltalkers not like code completion? Because the one in Pharo is really poor and not only that nobody is doing anything about it, but also nobody is complain

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50366 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] cfab3a: 50366

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: cfab3a1accc94bdb6c9c3f525c70e5b73e854aeb https://github.com/pharo-project/pharo-core/commit/cfab3a1accc94bdb6c9c3f525c70e5b73e854aeb Author: Jenkins Build Server Date: 2015-10-06 (Tue, 06 Oct 2015

Re: [Pharo-dev] Latest Build added items that are not yet set as "to include"

> On 06 Oct 2015, at 10:45, stepharo wrote: > > Just relax and trust me. It would help me. > that’s not the point. It is about communication. And exactly about that: > They were tested already. I checked that. > The problem is that the monkey is restarting to check because I did not close >

Re: [Pharo-dev] WhatsUp from: 2015-10-05 until: 2015-10-18

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - Revisit

Re: [Pharo-dev] Latest Build added items that are not yet set as "to include"

Just relax and trust me. It would help me. They were tested already. I checked that. The problem is that the monkey is restarting to check because I did not close them fast enough. Le 6/10/15 10:34, stepharo a écrit : Yes I always take time to close them to be sure that everything is integrat

Re: [Pharo-dev] Latest Build added items that are not yet set as "to include"

but it would be good to put them on “to include” before integration. This way we do not do double work (someone reviewing even if it is already ok) or that the monkey re-starts to check them after integration. > On 06 Oct 2015, at 10:34, stepharo wrote: > > Yes I always take time to close them

Re: [Pharo-dev] Latest Build added items that are not yet set as "to include"

Yes I always take time to close them to be sure that everything is integrated :) Tx for the warning. Le 6/10/15 10:17, Henrik Nergaard a écrit : The latest build #50365 added two Issues (#16722 and #15162), but in Fogbugz these are still under review by the Monkey, and not set as “to include

Re: [Pharo-dev] [Pharo-users] Better Code Completion

> On 06 Oct 2015, at 09:09, Nicolai Hess wrote: > > > Am 04.10.2015 23:53 schrieb "Peter Uhnák" >: > > > > This is both rant and list of questions/notes/observations... > > > > ...but first of all: > > do Smalltalkers not like code completion? Because the one in Pharo

[Pharo-dev] Latest Build added items that are not yet set as "to include"

The latest build #50365 added two Issues (#16722 and #15162), but in Fogbugz these are still under review by the Monkey, and not set as "to include". Best regards, Henrik

Re: [Pharo-dev] Latest changes broke Icons

Hi Esteban, It's broken: "Smalltalk ui icons" now returns an instance of ThemeIconPack instead of the usual ThemeIcons/subclass. But most external packages extended ThemeIcons or subclasses with own icons as this is/was up to the change the default way to do it. It's not possible to access th

[Pharo-dev] [pharo-project/pharo-core] 313229: 50365

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 313229ecd6a4b6f5cf5c86b2affc8d3516d674d9 https://github.com/pharo-project/pharo-core/commit/313229ecd6a4b6f5cf5c86b2affc8d3516d674d9 Author: Jenkins Build Server Date: 2015-10-06 (Tue, 06 Oct 2015

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50365 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] ff44b6: 50364

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: ff44b68d3ebb117f5eaa0524d13efb3a5bf8657b https://github.com/pharo-project/pharo-core/commit/ff44b68d3ebb117f5eaa0524d13efb3a5bf8657b Author: Jenkins Build Server Date: 2015-10-06 (Tue, 06 Oct 2015

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50364 Home: https://github.com/pharo-project/pharo-core