I understand the point of marcus but still it is unclear why certain
tools should be in and not others.
Now I would prefer that we have a process that
1 := take a miniimage AND load the tools
check that we can unload them (just to check)
and only then declare
pharo := 1.
It is the configurationBrowser (but an old configuration)
DependencyAnalyser (guillermo I thought that I fixed the text:
deprecation but apparently not)
or in PharoExtras
MCHttpRepository
location:
'http://www.smalltalkhub.com/mc/PharoExtras/Tool-DependencyAnalyser/main'
user: ''
2015-04-23 19:18 GMT+02:00 Mark Rizun :
> Hi,
>
> I was investigating how to play sounds in Pharo, and found SoundSystem
> class.
> It is stated that you should subclass it, like DummySoundSystem does.
> Is there any cool subclass (besides DummySoundSystem =D ) already
> implemented so I can use i
Hi,
I was investigating how to play sounds in Pharo, and found SoundSystem
class.
It is stated that you should subclass it, like DummySoundSystem does.
Is there any cool subclass (besides DummySoundSystem =D ) already
implemented so I can use it?
Thanks,
Mark
--
View this message in context:
I'd like to use it in a Linux box, but as you told me Linux is not yet
supported, I'm using a Mac OS X Yosemite (version 10.10.2).
Thanks
2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk :
> Hi Rafael,
>
> I will take a look. Which operating system are you using?
>
> Uko
>
> On 23 Apr 2015, at 17:30, Ra
Hi Rafael,
I will take a look. Which operating system are you using?
Uko
> On 23 Apr 2015, at 17:30, Rafael Luque wrote:
>
> Hi,
>
> I installed ViDI on Pharo 4 following the project instructions detailed in
> its GitHub page:
>
> Gofer new
> smalltalkhubUser: 'YuriyTymchuk'
> project:
Hi,
I installed ViDI on Pharo 4 following the project instructions detailed in
its GitHub page:
Gofer new
smalltalkhubUser: 'YuriyTymchuk'
project: 'Configuration';
configurationOf: 'Vidi';
load.
#ConfigurationOfVidi asClass loadStable
When I launch a review session over any package I al
Hi Cyril,
I’ve checked the problem. It could be indeed easier if the rule pointed to it
:).
So you have PRFileInclusion>>replace: and it is identical (not taking empty
lines into account) to PRTransformer>>replace:.
So the rule is correct. You override a method with an identical method.
Uko
Hi,
I just moved the Versionner repository from
http://smalltalkhub.com/#!/~demarey/Versionner/ to
http://smalltalkhub.com/#!/~PharoExtras/Versionner/.
It will ease contributions and it will be easier to find with other tools /
library of Pharo.
Regards,
Christophe.
smime.p7s
Description: S/M
I changed that but i still have the warning from quality assistant.
On 23 April 2015 at 12:44, Cyril Ferlicot wrote:
> Oh, ok ! Thank you Guillermo !
>
> On 23 April 2015 at 11:58, Guillermo Polito wrote:
>> Hi Cyril,
>>
>> Your problem is caused because abstract methods should be marked with
>>
Oh, ok ! Thank you Guillermo !
On 23 April 2015 at 11:58, Guillermo Polito wrote:
> Hi Cyril,
>
> Your problem is caused because abstract methods should be marked with
> "subclassResponsibility" and not "shouldBeImplemented".
>
> - shouldBeImplemented means "this is a method I did not implement y
Hi Cyril,
Your problem is caused because abstract methods should be marked with
"subclassResponsibility" and not "shouldBeImplemented".
- shouldBeImplemented means "this is a method I did not implement yet, I
should replace *this* method with another implementation"
- subclassResponsibility means
fixed
> On 21 Apr 2015, at 19:11, Marcus Denker wrote:
>
> This is not correct… can you enter an issue?
>
>> On 21 Apr 2015, at 19:07, Johan Fabry wrote:
>>
>> Hi all,
>>
>> finally having some time to develop again, I downloaded the 4.0 image
>> sources and vm (http://files.pharo.org/get-
Stef,
where is "the tool"?
Norbert
> Am 23.04.2015 um 08:01 schrieb stepharo :
>
> Two things:
>
> One:
> We paid a guy to work on a tool to help us identifying dependencies, The tool
> works well is fast.
> if this tool would be in the image, everybody could check that there are bad
> depen
Can someone explain to me what is the difference between "loading a tool" and
"put something in the image" ?
I thought we all agree that the atomic image should shrink as far as it can and
everything should be loaded on top. If that is the case we can also agree that
we don't want to release th
I totally agree with Stef that we should be able to do a rock solid setup of
what tools we want to use in our everyday image.
But on the other hand we have to design what Pharo is. Because we can even go
Ruby style and say that debugger is not a part of the main system, but I see
that our stren
Le 23/4/15 09:05, Marcus Denker a écrit :
I do not understand how “having a modular tool in the image ” (that does not
add dependencies to anything)
makes the system less modular.
Then why the dependency Browser was not integrated? Why roassal for
drawing dependencies
and other aspects of the
17 matches
Mail list logo
