On Sep 11, 2012, at 10:44 PM, Mariano Martinez Peck wrote:
> Hi Simon. I have just run it in Tanker. It already help me to detect a couple
> of things :)
> Some feedback:
>
> 1) Is there a way to set the package of the Manifest class?
normally it should always go to the package automatically.
I started to use it, and I will have suggestion on the GUI.
Cheers,
Alexandre
On Sep 11, 2012, at 1:52 PM, Stéphane Ducasse wrote:
> excellent!
> Simon what about producing a video so that the world can see your nice tool
> in action.
>
> Stef
>
>
> On Sep 11, 2012, at 4:21 PM, Simon Allie
excellent!
Simon what about producing a video so that the world can see your nice tool in
action.
Stef
On Sep 11, 2012, at 4:21 PM, Simon Allier wrote:
> I have fix the error found by Camillo, now it works with all packages and
> rules in the last pharo 2.0 image.
>
> On Sep 11, 2012, at 4:
I have fix the error found by Camillo, now it works with all packages and
rules in the last pharo 2.0 image.
On Sep 11, 2012, at 4:13 PM, Mariano Martinez Peck wrote:
>
>
> On Mon, Sep 10, 2012 at 11:53 PM, Simon Allier wrote:
> Hi,
>
> I have published a new version of the Critics Browser
On Mon, Sep 10, 2012 at 11:53 PM, Simon Allier wrote:
> Hi,
>
> I have published a new version of the Critics Browser (menuWorld > Tool >
> CriticBrowser).
> The new version is
> - refactoring friendly. Yes we listened to you :).
>
hehehe I felt touched by that ;(
Thanks Simon, these are reall
On 2012-09-11, at 13:46, Simon Allier wrote:
> Thank for the feedback.
> On Sep 11, 2012, at 12:06 PM, Camillo Bruni wrote:
>
>> hey, I almost got it running :)
>>
>> - I got an error on ConfigurationOfRefactoringBrowser in the latest 2.0
>> image.
>> However if I manually load all the packa
On 2012-09-11, at 13:57, Alexandre Bergel wrote:
> I've tried in a 1.4, and it does not work "SystemAnnouncer uniqueInstance
> weak" raises an error.
> What is the status of 2.0? Is it usable now?
nope, there are still nasty bugs with RPackage around, for instance:
https://code.google.com/p/p
I've tried in a 1.4, and it does not work "SystemAnnouncer uniqueInstance weak"
raises an error.
What is the status of 2.0? Is it usable now?
Cheers,
Alexandre
On Sep 11, 2012, at 6:24 AM, Camillo Bruni wrote:
> I presume that's 1.4 only? since I cannot load it in 2.0...
>
> On 2012-09-10, a
Thank for the feedback.
On Sep 11, 2012, at 12:06 PM, Camillo Bruni wrote:
> hey, I almost got it running :)
>
> - I got an error on ConfigurationOfRefactoringBrowser in the latest 2.0 image.
> However if I manually load all the packages from the squeaksource repos it
> works :)
>
I dont have
hey, I almost got it running :)
- I got an error on ConfigurationOfRefactoringBrowser in the latest 2.0 image.
However if I manually load all the packages from the squeaksource repos it
works :)
- Running all the Critics with all the classes in the Image raises an DNU on nil
aContext protoco
I presume that's 1.4 only? since I cannot load it in 2.0...
On 2012-09-10, at 23:53, Simon Allier wrote:
> Hi,
>
> I have published a new version of the Critics Browser (menuWorld > Tool >
> CriticBrowser).
> The new version is
> - refactoring friendly. Yes we listened to you :).
>
Hi,
I have published a new version of the Critics Browser (menuWorld > Tool >
CriticBrowser).
The new version is
- refactoring friendly. Yes we listened to you :).
- the browser has been improved. It works with the latest Spec.
With the Critics browser you can inspect violatio
On Apr 18, 2012, at 4:32 PM, Stéphane Ducasse wrote:
> Thanks simon.
> I will try on citizen and Kozen then after on all the packages I can find and
> I know :)
>
> Gofer
> new
> url: 'http://www.squeaksource.com/PharoTaskForces';
> package: 'ConfigurationOfManifest';
> load.
> ((Smalltal
Thanks simon.
I will try on citizen and Kozen then after on all the packages I can find and I
know :)
Gofer
new
url: 'http://www.squeaksource.com/PharoTaskForces';
package: 'ConfigurationOfManifest';
load.
((Smalltalk at: #ConfigurationOfManifest) project version: #stable) load
On Ap
Hi,
i have published a new version:
- the package Manifest-Core is split in two packages: Manifest-Core and
Manifest-CriticBrowser.
- the unique identifier for a rule is now a string, not a number. For example,
in the manifest we have ruleBadMessageRuleV1FalsePositive rather than
ruleBadMessage
Hi,
On 10 Apr 2012, at 21:31, Stéphane Ducasse wrote:
>>
>> I do not get it. You want an identifier. Why is a brittle and
>> obfuscated number better than the name of the class, which is already
>> a proper identifier? If you do not want to rely directly on a class
>> reference, you can store it
>
> I do not get it. You want an identifier. Why is a brittle and
> obfuscated number better than the name of the class, which is already
> a proper identifier? If you do not want to rely directly on a class
> reference, you can store it as a symbol.
sure this is not the problem numbers solve. We
Hi,
On Sat, Apr 7, 2012 at 9:14 AM, Stéphane Ducasse
wrote:
> Thanks
>
>> Hi,
>>
>> Thanks.
>>
>> I gave it a short try, and here are some comments:
>> - The Manifest-Core should contain only the core of the manifest engine. For
>> example, I see here some mechanism for traversing Manifest class
Hi,
On Tue, Apr 10, 2012 at 2:18 PM, Simon Allier wrote:
> Thanks for this comments
>
>> Thanks
>>
>>> Hi,
>>>
>>> Thanks.
>>>
>>> I gave it a short try, and here are some comments:
>>> - The Manifest-Core should contain only the core of the manifest engine.
>>> For example, I see here some mech
Thanks for this comments
> Thanks
>
>> Hi,
>>
>> Thanks.
>>
>> I gave it a short try, and here are some comments:
>> - The Manifest-Core should contain only the core of the manifest engine. For
>> example, I see here some mechanism for traversing Manifest classes and
>> retrieving data from
Thanks
> Hi,
>
> Thanks.
>
> I gave it a short try, and here are some comments:
> - The Manifest-Core should contain only the core of the manifest engine. For
> example, I see here some mechanism for traversing Manifest classes and
> retrieving data from them. Everything else that is specific
Hi,
Thanks.
I gave it a short try, and here are some comments:
- The Manifest-Core should contain only the core of the manifest engine. For
example, I see here some mechanism for traversing Manifest classes and
retrieving data from them. Everything else that is specific to SmallLint should
be
Hi pharoers
Since a couple of months the Pharo team has been working on improving the
support for rules checking and in particular the handling of false positives
(there is nothing more boring that to get all the time the same warnings that
we know are not adequate).
We added a manifest mechani
23 matches
Mail list logo