>
> 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 wor
Igor
this is not the point. People do not understand that code can be represented as
text :)
If I save assembly in XML is it XML or assembly.
I think that if you have a dll whose contents does not change then it is ok.
Stef
>>>
>>
>> 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.
tx!
On Oct 24, 2013, at 1:55 PM, Torsten Bergmann 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
>
> https://pharo.fogbugz.com/f
>
> 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 t
this is what I do for the PharoTopics :)
On Oct 24, 2013, at 4:17 AM, Igor Stasenko wrote:
>
> On 23 October 2013 20:21, Sven Van Caekenberghe wrote:
> This is really cool, is that in the image already ?
> What about plain HTTP repos ?
>
>
> indeed, what could be simpler than:
>
> Compiler
>
> It's part of the Pharo manifesto: "Not backward compatible"
>
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 can la
Consistency
ensureActionObject
ensureCreateDirectory
ensureCreateFile
We discuss a lot with camillo when we did it and I think that this is good
right now.
> Out of curiosity, what was the motivation behind Issue 10924: Simplifying
> ensure* and create protocol?
>
> For me #ensureCreateDirecto
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 ages…
the code looks strange).
floatPrecisionForDecimalPlaces: places
"An
On 25 oct. 2013, at 09:50, Stéphane Ducasse 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
> ages… the code looks
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 Duc
Am 25.10.2013 um 10:11 schrieb 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...
>
Am 24.10.2013 um 12:51 schrieb Igor Stasenko :
>
>
>
> On 24 October 2013 08:24, Norbert Hartl wrote:
>
>
> Am 23.10.2013 um 23:28 schrieb Igor Stasenko :
>
>>
>>
>>
>> On 23 October 2013 23:13, Stéphane Ducasse wrote:
>>>
>>>
>>> Well implementing ARM-FFI is largely orthogonal to A
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 totalSecon
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 happens
when the compiler tries to remove unused temporaries and garbles up the
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
Date: 2013-10-25 (Fri, 25 Oct 2013
Branch: refs/tags/30521
Home: https://github.com/pharo-project/pharo-core
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?
isItTim
On 25 October 2013 10:52, Norbert Hartl wrote:
>
> Am 24.10.2013 um 12:51 schrieb Igor Stasenko :
>
>
>
>
> On 24 October 2013 08:24, Norbert Hartl wrote:
>
>>
>>
>> Am 23.10.2013 um 23:28 schrieb Igor Stasenko :
>>
>>
>>
>>
>> On 23 October 2013 23:13, Stéphane Ducasse wrote:
>>
>>>
>>> We
Branch: refs/tags/30522
Home: https://github.com/pharo-project/pharo-core
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
Date: 2013-10-25 (Fri, 25 Oct 2013
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 wrote:
>
>
>
> Yes, this can be cleanup up.
>
> On 25 Oct 2013 at 11:10:34, Martin Dias
> (tinchod...@gmail.com)
> wrote:
>
> Hi,
>
>
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
Date: 2013-10-25 (Fri, 25 Oct 2013
Branch: refs/tags/30523
Home: https://github.com/pharo-project/pharo-core
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 a
can we focus on real problems?
The method has a comment.
Stef
On Oct 25, 2013, at 10:39 AM, Norbert Hartl wrote:
>
> Am 25.10.2013 um 10:11 schrieb Nicolas Cellier
> :
>
>> So action=create object=directory
>> you want to be sure that you create a directory?
>> What if it already exists?
>>
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
>
Branch: refs/tags/30524
Home: https://github.com/pharo-project/pharo-core
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
Date: 2013-10-25 (Fri, 25 Oct 2013
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 Duca
I did it because they are the only ones.
Yes, we need to have them at some point. But having two baselines but nothing
else makes no sense.
And we need to be able to organise package better, even with the package tags
there is too much in the left pane.
On 25 Oct 2013 at 15:19:02, Christoph
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 peo
I agree with this. In particular, the configuration classes offer extra
information that can be used by smart browsers. We need them.
Cheers,
Doru
On Fri, Oct 25, 2013 at 3:18 PM, Christophe Demarey <
christophe.dema...@inria.fr> wrote:
> Why do we need to remove configurations of projects load
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.
it's
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 ab
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 one
On Oct 25, 2013, at 3:24 PM, Nicolas Cellier
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 real
- Removing CodeHolder
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 a
Martin watching the DeepCopier???
I am afraid to ask why ;)
On Fri, Oct 25, 2013 at 6:10 AM, Martin Dias 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... Unuse
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
http://ss3.gemstone.com/ss/Pharo20/NautilusCommon-MarcusDenker.1
Am 25.10.2013 um 15:52 schrieb 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. Tha
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
Date: 2013-10-25 (Fri, 25 Oct 2013
Hi guys,
can you give me http://smalltalkhub.com/#!/~YuriyTymchuk rights to commit to
Pharo30Inbox?
Cheers!
Uko
Branch: refs/tags/20625
Home: https://github.com/pharo-project/pharo-core
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 wa
+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
It looks cool :)
Now I was wondering why Canvas and friends are part of it and not into Graphics
Stef
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 a
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?
https://pharo.fogbugz.com/f/cases/12
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
>
On it!
On 25.10.2013, at 16:26, Stéphane Ducasse 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 Fuel so Fuel guys ca
On Fri, 25 Oct 2013, Stéphane Ducasse wrote:
It's part of the Pharo manifesto: "Not backward compatible"
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 m
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
>
>
>
> On 25 October 2013 00:26, Nicolas Cellier
> wrote:
> Hard to
> 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 righ
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
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 Nautilus-Histor
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
Date: 2013-10-25 (Fri, 25 Oct 2013
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 so
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 back
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 Uzony
Branch: refs/tags/30525
Home: https://github.com/pharo-project/pharo-core
Branch: refs/tags/30526
Home: https://github.com/pharo-project/pharo-core
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
Date: 2013-10-25 (Fri, 25 Oct 2013
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.
Hi Johan,
On 25 Oct 2013, at 22:55, Johan Brichau 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 sources file from
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 wrote:
> Hi Johan,
>
> On 25 Oct 2013, at 22:55, Johan Brichau wrote:
>
>> Hi guys,
>>
>> Just a small note that the sources file for Pharo2.0
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
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 Oc
heads up
o.O
I am using Pharo business wise.
And making money out of it.
It is using Seaside 3 and a ton of packages. They all work fine.
What's your point really? If you want to go Pharo, you go Pharo and you
don't look back.
Or you haven't made your mind. In which case the complaints are useless.
Phil
70 matches
Mail list logo