Re: [Pharo-dev] API docs?

2013-10-25 Thread Torsten Bergmann
projectVALIS wrote: I'm wondering if there are online API docs like there are for Java (here's a link http://docs.oracle.com/javase/7/docs/api/ for all you non-Java types). I've already got a copy of 'Pharo by Example' and 'A Guide to Work with Squeak Morph Classes', but neither are what I'm

Re: [Pharo-dev] API docs?

2013-10-25 Thread projectVALIS
perfect! this is enough to get me going -- thanks!!! -- View this message in context: http://forum.world.st/API-docs-tp4716945p4717010.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] VM for Athens Graphics

2013-10-25 Thread Stéphane Ducasse
Ok I was not aware you were thinking about that. So this is good to have this path in my radar. Yes, this is actually what we discussed recently with Esteban about possible alternatives and low-hanging fruits :) I like these ones :) Concerning ARM: - Damien Pollet works on ARM

Re: [Pharo-dev] Issue #11876 (Do not allow shouldnt:raise: Error) and Seaside dev. on Pharo 3.0

2013-10-25 Thread Stéphane Ducasse
yes, people are not willing to change code all the time… We are willing to change the code where there is a clear benefit. For example it's hard to argue that the new filesystem is an improvement over FileDirectory. We have a partically working Spec based UI for the servers. We would

Re: [Pharo-dev] Issue #11876 (Do not allow shouldnt:raise: Error) and Seaside dev. on Pharo 3.0

2013-10-25 Thread Stéphane Ducasse
tx! On Oct 24, 2013, at 1:55 PM, Torsten Bergmann asta...@gmx.de wrote: From the comments I think we can agree that it is a better to have a lint rule instead of breaking things the way it was introduced by the original issue #11876. I therefore opened an issue

Re: [Pharo-dev] Issue #11876 (Do not allow shouldnt:raise: Error) and Seaside dev. on Pharo 3.0

2013-10-25 Thread Stéphane Ducasse
With respect to Seaside (and its cross-platform-ness), this is probably a good decision, for now. But it is fundamentally unfair to call this an arbitrary unimportant change meant to annoy people. On the contrary ! I even think that there are too many methods in TAssertable and the

Re: [Pharo-dev] Startup Preferences: An Alternative

2013-10-25 Thread Stéphane Ducasse
this is what I do for the PharoTopics :) On Oct 24, 2013, at 4:17 AM, Igor Stasenko siguc...@gmail.com wrote: On 23 October 2013 20:21, Sven Van Caekenberghe s...@stfx.eu wrote: This is really cool, is that in the image already ? What about plain HTTP repos ? indeed, what could be

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

2013-10-25 Thread Stéphane Ducasse
rant It's part of the Pharo manifesto: Not backward compatible /rant Levente I hope that writing this little pun created some jubilation to you. Or I do not understand your point. But this is ok for me. If pun on Pharo helps you then this is ok and they make me smile, and I'm serious If I

Re: [Pharo-dev] UpdatingMenuMorph

2013-10-25 Thread Camille Teruel
On 25 oct. 2013, at 09:50, Stéphane Ducasse stephane.duca...@inria.fr wrote: I was only use in stupid halos and the code is not really good. Now if somebody does a pass on it we could readd it to the basis. (right now I just put it back for the sound package - but the sound package shows it

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Nicolas Cellier
So action=create object=directory you want to be sure that you create a directory? What if it already exists? Since you want to be sure to create, will you erase and re-create? You see the kind of misunderstanding this could create... IOW, self ensureCreateMisunderstanding 2013/10/25 Stéphane

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Norbert Hartl
Am 25.10.2013 um 10:11 schrieb Nicolas Cellier nicolas.cellier.aka.n...@gmail.com: So action=create object=directory you want to be sure that you create a directory? What if it already exists? Since you want to be sure to create, will you erase and re-create? You see the kind of

[Pharo-dev] DeepCopierisItTimeToCheckVariables

2013-10-25 Thread Martin Dias
Hi, This method in DeepCopier has no senders (in Pharo 3) and it's the only who references the class variable NextVariableCheckTime. The time stamp says 1999... Unused code to remove? isItTimeToCheckVariables | now isIt | NextVariableCheckTime ifNil: [ NextVariableCheckTime := Time

[Pharo-dev] [pharo-project/pharo-core] ee26c3: 30521

2013-10-25 Thread GitHub
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: ee26c3a454be5ecb199f0447700a856def4bde24 https://github.com/pharo-project/pharo-core/commit/ee26c3a454be5ecb199f0447700a856def4bde24 Author: Jenkins Build Server bo...@pharo-project.org Date:

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

2013-10-25 Thread GitHub
Branch: refs/tags/30521 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] DeepCopierisItTimeToCheckVariables

2013-10-25 Thread Marcus Denker
Yes, this can be cleanup up. On 25 Oct 2013 at 11:10:34, Martin Dias (tinchod...@gmail.com) wrote: Hi, This method in DeepCopier has no senders (in Pharo 3) and it's the only who references the class variable NextVariableCheckTime. The time stamp says 1999... Unused code to remove?

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

2013-10-25 Thread GitHub
Branch: refs/tags/30522 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 30a35f: 30522

2013-10-25 Thread GitHub
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 30a35f96d7a19a6c2d1c95ff359c2cdaa1dde9bf https://github.com/pharo-project/pharo-core/commit/30a35f96d7a19a6c2d1c95ff359c2cdaa1dde9bf Author: Jenkins Build Server bo...@pharo-project.org Date:

Re: [Pharo-dev] DeepCopierisItTimeToCheckVariables

2013-10-25 Thread Martin Dias
Reported: https://pharo.fogbugz.com/f/cases/12002/DeepCopier-isItTimeToCheckVariables-is-candidate-to-be-removed On Fri, Oct 25, 2013 at 12:57 PM, Marcus Denker marcus.den...@inria.frwrote: Yes, this can be cleanup up. On 25 Oct 2013 at 11:10:34, Martin Dias

[Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523

2013-10-25 Thread GitHub
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 4021f31ef110a3f16862ef02329c66f4e04ffa40 https://github.com/pharo-project/pharo-core/commit/4021f31ef110a3f16862ef02329c66f4e04ffa40 Author: Jenkins Build Server bo...@pharo-project.org Date:

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

2013-10-25 Thread GitHub
Branch: refs/tags/30523 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] RB AST node positions off by one or more characters with Opal ?

2013-10-25 Thread Marcus Denker
On 25 Oct 2013 at 11:16:35, Goubier Thierry (thierry.goub...@cea.fr) wrote: Hi all, has anybody noticed that, when getting node positions from a RB parse of the AST, they seem to be off by one character or more? It happens in smart suggestions type of commands for me, but it seems to also

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Stéphane Ducasse
can we focus on real problems? The method has a comment. Stef On Oct 25, 2013, at 10:39 AM, Norbert Hartl norb...@hartl.name wrote: Am 25.10.2013 um 10:11 schrieb Nicolas Cellier nicolas.cellier.aka.n...@gmail.com: So action=create object=directory you want to be sure that you create a

Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523

2013-10-25 Thread Christophe Demarey
Why do we need to remove configurations of projects loaded into the image? I would say the opposite: all projects in the image should have their configuration loaded. It is part of the project. Le 25 oct. 2013 à 14:00, GitHub a écrit : 12005 unload BaselineOfFileTree, BaselineOfMetacello

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

2013-10-25 Thread GitHub
Branch: refs/tags/30524 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] fdec0d: 30524

2013-10-25 Thread GitHub
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: fdec0d85c64952aa500fd73ab1818bbcec3c8ae8 https://github.com/pharo-project/pharo-core/commit/fdec0d85c64952aa500fd73ab1818bbcec3c8ae8 Author: Jenkins Build Server bo...@pharo-project.org Date:

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Nicolas Cellier
What are real problems exactly? If you are going to open each and every method to read the comment or the code instead of trusting the name, IMHO that is going to be a real problem. If the focus shall be on real problems, then why change APIs which are not a real problem? 2013/10/25 Stéphane

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Norbert Hartl
Stef, I really don’t want to stretch this into an argue …. but I have problems understanding that. There are refactorings of method selectors because it is said it is important that includesSubString: is written as includesSubstring: and there are other examples. Now we have a selector that

Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523

2013-10-25 Thread Goubier Thierry
Le 25/10/2013 15:27, Marcus Denker a écrit : ... even with the package tags there is too much in the left pane. Yes, I've seen that as well. Either go into the six pane browser of S. Travis Pope, or use the tree to build proper categories of packages like I do in the AltBrowser. I.e.

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Stéphane Ducasse
We already discussed this API it is in the bug tracker: ensureDelete, ensureDeleted…. So do what you want I personally want to focus on more important issues. Once the full world will agree then do not forget to update the FileSystem Chapter that I wrote BTW (this is for the people complaining

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Nicolas Cellier
Yes, I can understand the boring part of it - this is a detail - it's tiring to discuss small details to death - some people speak more than act (me for example :) But can we agree that - details count - critics count (convince yourself that they are not intended for bashing people) - and last

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Stéphane Ducasse
On Oct 25, 2013, at 3:24 PM, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: What are real problems exactly? Here is a list - better API for Compiler - better functionality for OPAL - Cleaning Morph (architecture, package structure) - using Slot for

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Sven Van Caekenberghe
The problem with #ensure style selectors is that they are confusing because they both test something and maybe do something to create a certain condition. The only way to take away the confusion is to make a very long selector. That is why comments are also important. Like Stef said, this was

Re: [Pharo-dev] DeepCopierisItTimeToCheckVariables

2013-10-25 Thread Mariano Martinez Peck
Martin watching the DeepCopier??? I am afraid to ask why ;) On Fri, Oct 25, 2013 at 6:10 AM, Martin Dias tinchod...@gmail.com wrote: Hi, This method in DeepCopier has no senders (in Pharo 3) and it's the only who references the class variable NextVariableCheckTime. The time stamp

[Pharo-dev] [update 2.0] #20625

2013-10-25 Thread Marcus Denker
20625 - 11535 RBBrowserEnvironment packages method is too broad backport https://pharo.fogbugz.com/f/cases/11535 Diff information: http://ss3.gemstone.com/ss/Pharo20/Refactoring-Environment-MarcusDenker.14.diff

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Norbert Hartl
Am 25.10.2013 um 15:52 schrieb Sven Van Caekenberghe s...@stfx.eu: The problem with #ensure style selectors is that they are confusing because they both test something and maybe do something to create a certain condition. The only way to take away the confusion is to make a very long

[Pharo-dev] [pharo-project/pharo-core] ccaa84: 20625

2013-10-25 Thread GitHub
Branch: refs/heads/2.0 Home: https://github.com/pharo-project/pharo-core Commit: ccaa8405f452676d149e42759a742dc3db2c9ea5 https://github.com/pharo-project/pharo-core/commit/ccaa8405f452676d149e42759a742dc3db2c9ea5 Author: Jenkins Build Server bo...@pharo-project.org Date:

[Pharo-dev] Pharo30Inbox commit rights

2013-10-25 Thread Yuriy Tymchuk
Hi guys, can you give me http://smalltalkhub.com/#!/~YuriyTymchuk rights to commit to Pharo30Inbox? Cheers! Uko

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

2013-10-25 Thread GitHub
Branch: refs/tags/20625 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] DeepCopierisItTimeToCheckVariables

2013-10-25 Thread Martin Dias
xD yes, DeepCopier, our old friend! but it's not about replacing by Fuel or something like that. It was just a random pick for fix a triviality a day, what Marcus proposed some weeks ago. On Fri, Oct 25, 2013 at 3:56 PM, Mariano Martinez Peck marianop...@gmail.com wrote: Martin

Re: [Pharo-dev] ensureCreateDirectory?

2013-10-25 Thread Stéphane Ducasse
+1 The problem with #ensure style selectors is that they are confusing because they both test something and maybe do something to create a certain condition. The only way to take away the confusion is to make a very long selector. That is why comments are also important. Like Stef

[Pharo-dev] about Morphic-Core

2013-10-25 Thread Stéphane Ducasse
It looks cool :) Now I was wondering why Canvas and friends are part of it and not into Graphics Stef

Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523

2013-10-25 Thread Stéphane Ducasse
Indeed I'm all in favor to have ConfigurationOf in the image because they are metaData of the packages and projects!!! I do not understand why UI concerns show up into structure of the system. I do not see why having a long list is a problem: there is a search behavior there is

[Pharo-dev] About BitBlt current - BitBlt (Fuel)

2013-10-25 Thread Stéphane Ducasse
Hi I just pushed a change cleaning some strange usage. BitBlt was sometimes invoked via BitBlt current (which just returned the BitBlt class). Apparently in Squeak they removed it too. Now it touches Fuel so Fuel guys can you merge on your side too?

Re: [Pharo-dev] Pharo30Inbox commit rights

2013-10-25 Thread Marcus Denker
I added you as a contributor there On 25 Oct 2013 at 16:11:09, Yuriy Tymchuk (yuriy.tymc...@me.com) wrote: Hi guys, can you give me http://smalltalkhub.com/#!/~YuriyTymchuk rights to commit to Pharo30Inbox? Cheers! Uko

Re: [Pharo-dev] About BitBlt current - BitBlt (Fuel)

2013-10-25 Thread Max Leske
On it! On 25.10.2013, at 16:26, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi I just pushed a change cleaning some strange usage. BitBlt was sometimes invoked via BitBlt current (which just returned the BitBlt class). Apparently in Squeak they removed it too. Now it touches

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

2013-10-25 Thread Levente Uzonyi
On Fri, 25 Oct 2013, Stéphane Ducasse wrote: rant It's part of the Pharo manifesto: Not backward compatible /rant Levente I hope that writing this little pun created some jubilation to you. Or I do not understand your point. But this is ok for me. If pun on Pharo helps you then this is ok

Re: [Pharo-dev] Unwind error during termination

2013-10-25 Thread Stéphane Ducasse
If I remember correctly andreas wrote the tests. I always like them. Stef The author of the test is Andreas Raab, but I'm not sure who found it (excavating mailing list is hard work) 2013/10/25 Igor Stasenko siguc...@gmail.com On 25 October 2013 00:26, Nicolas Cellier

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

2013-10-25 Thread Stéphane Ducasse
I'm sorry if you guys didn't get my message, but it was as serious as it could be. Ok fair :) I understand that you don't what to be backwards compatible, because it makes it easier to change stuff. As I see, people need various levels of backwards compatibility. Indeed but the right

[Pharo-dev] AspectS, PHANtom - Aspects in Pharo

2013-10-25 Thread p...@highoctane.be
Hello, I was wondering what the state of Aspect programming was in Pharo. Googling a bit turned the title mentioned projects. Do we anything loadable and more or less stable for Pharo2.x? I'd like to use some of that. TIA Phil

[Pharo-dev] [update 3.0] #30525

2013-10-25 Thread Stéphane Ducasse
30525 - - Issue: 12009 BitBlt current - BitBlt https://pharo.fogbugz.com/f/cases/12009/BitBlt-current-BitBlt - Issue: 12013: Zinc Character Encoding and Resource Meta update https://pharo.fogbugz.com/f/cases/12013/ - Issue: 12014 Extract History from

[Pharo-dev] [pharo-project/pharo-core] 61fb24: 30525

2013-10-25 Thread GitHub
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 61fb24eb5859e30b04a664958cb7bda70de6dcce https://github.com/pharo-project/pharo-core/commit/61fb24eb5859e30b04a664958cb7bda70de6dcce Author: Jenkins Build Server bo...@pharo-project.org Date:

Re: [Pharo-dev] AspectS, PHANtom - Aspects in Pharo

2013-10-25 Thread Stéphane Ducasse
Not really and frankly I would not use that. What is your case? Stef Hello, I was wondering what the state of Aspect programming was in Pharo. Googling a bit turned the title mentioned projects. Do we anything loadable and more or less stable for Pharo2.x? I'd like to use some of

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

2013-10-25 Thread Levente Uzonyi
On Fri, 25 Oct 2013, Stéphane Ducasse wrote: I'm sorry if you guys didn't get my message, but it was as serious as it could be. Ok fair :) I understand that you don't what to be backwards compatible, because it makes it easier to change stuff. As I see, people need various levels of

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

2013-10-25 Thread Chris Muller
We should not continue this old discussion. We've already debated this ad naseum. Thank you Pharo guys for exploring what can be done when all constraints are removed! Thank you Squeak guys for advancing in a way that caters to legacy applications. On Fri, Oct 25, 2013 at 1:25 PM, Levente

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

2013-10-25 Thread GitHub
Branch: refs/tags/30525 Home: https://github.com/pharo-project/pharo-core

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

2013-10-25 Thread GitHub
Branch: refs/tags/30526 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 9e65f1: 30526

2013-10-25 Thread GitHub
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 9e65f148f79b2b0c5c30be76e1b30818bae4003e https://github.com/pharo-project/pharo-core/commit/9e65f148f79b2b0c5c30be76e1b30818bae4003e Author: Jenkins Build Server bo...@pharo-project.org Date:

[Pharo-dev] Pharo-V20.sources

2013-10-25 Thread Johan Brichau
Hi guys, Just a small note that the sources file for Pharo2.0 (and 3.0) is not easy to get when downloading the VM and the image from the website. I had to finally download the ‘one click’ and extract the sources file from its resources. I believe they used to be included with the image zips.

Re: [Pharo-dev] Pharo-V20.sources

2013-10-25 Thread Sven Van Caekenberghe
Hi Johan, On 25 Oct 2013, at 22:55, Johan Brichau jo...@inceptive.be wrote: Hi guys, Just a small note that the sources file for Pharo2.0 (and 3.0) is not easy to get when downloading the VM and the image from the website. I had to finally download the ‘one click’ and extract the

Re: [Pharo-dev] Pharo-V20.sources

2013-10-25 Thread Johan Brichau
Hey Sven, Thanks for these alternatives. I guess I’m an old-fashioned website user :-) cheers Johan On 25 Oct 2013, at 23:07, Sven Van Caekenberghe s...@stfx.eu wrote: Hi Johan, On 25 Oct 2013, at 22:55, Johan Brichau jo...@inceptive.be wrote: Hi guys, Just a small note that the

Re: [Pharo-dev] AspectS, PHANtom - Aspects in Pharo

2013-10-25 Thread p...@highoctane.be
I am interested in aspects as for crosscutting concerns they are useful. I am now using Traits in my code and it works well indeed. The problem with them is that I have to pepper them around in classes where with aspects, I could define pointcuts in a single place with definitions (I used that in

Re: [Pharo-dev] Pharo-V20.sources

2013-10-25 Thread Levente Uzonyi
On Fri, 25 Oct 2013, Johan Brichau wrote: Hey Sven, Thanks for these alternatives. I guess I’m an old-fashioned website user :-) I had the same problem today. I found them a few clicks away from the general download page at http://files.pharo.org/sources/ Levente cheers Johan On 25