Hi Rafael,
I will take a look. Which operating system are you using?
Uko
On 23 Apr 2015, at 17:30, Rafael Luque rafael.luque.le...@gmail.com wrote:
Hi,
I installed ViDI on Pharo 4 following the project instructions detailed in
its GitHub page:
Gofer new
smalltalkhubUser:
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 yuriy.tymc...@me.com:
Hi Rafael,
I will take a look. Which operating system are you using?
Uko
On 23 Apr
2015-04-23 19:18 GMT+02:00 Mark Rizun mri...@gmail.com:
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
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:
great!
Stef
Le 21/4/15 17:02, Sean P. DeNigris a écrit :
stepharo wrote
Yes it is in FunWithPharo on github and thanks for the editing pass.
No problem. I just committed the fixes.
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/tinychat-tp4820781p4820832.html
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 dependencies in his
code (and there are many around in nearly anybody's code).
No we prefer that me,
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
I do not understand how “having a modular tool in the image ” (that does not
add dependencies to anything)
makes the system less modular.
Especially if the price we pay for that is a system where good tools are
available, but nobody uses them.
So to me it simply means that we are not
Stef,
where is the tool?
Norbert
Am 23.04.2015 um 08:01 schrieb stepharo steph...@free.fr:
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
fixed
On 21 Apr 2015, at 19:11, Marcus Denker marcus.den...@inria.fr wrote:
This is not correct… can you enter an issue?
On 21 Apr 2015, at 19:07, Johan Fabry jfa...@dcc.uchile.cl wrote:
Hi all,
finally having some time to develop again, I downloaded the 4.0 image
sources and vm
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 my
I changed that but i still have the warning from quality assistant.
On 23 April 2015 at 12:44, Cyril Ferlicot cyril.ferli...@gmail.com wrote:
Oh, ok ! Thank you Guillermo !
On 23 April 2015 at 11:58, Guillermo Polito guillermopol...@gmail.com wrote:
Hi Cyril,
Your problem is caused because
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:
Hi Cyril,
I’ve checked the problem. It could be indeed easier if the rule pointed to it
:).
So you have PRFileInclusionreplace: and it is identical (not taking empty
lines into account) to PRTransformerreplace:.
So the rule is correct. You override a method with an identical method.
Uko
On
14 matches
Mail list logo
