Hi,
I think this is a great idea.
Thanks for opening the issues. Now, the only question is where to put these.
You suggest the package Manifest. I think this would work for individual
packages, but as we are moving to projects (with Metacello), I would suggest to
put these methods in the Confi
In context of discussion how to propose Mocketry and StateSpecs to be part
of Pharo?
We often said that Pharo provides the best approach to TDD but we have no
mock library inside. And nobody use mocks for Pharo tests because of that
2016-08-24 6:51 GMT+02:00 stepharo :
> Hi guys
>
> the board got
2016-08-24 9:38 GMT+02:00 stepharo :
> Igor looked at Twisty seriously and I do not think that it could handle
> large cobol files.
>
> (you see funnily denis is doing the same with Seamless - He rewrote it
> from scratch while
> nick worked on it for several years).
>
Just to clarify:
Tw
Hi
2016-08-24 18:58 GMT+02:00 Hernán Morales Durand :
> 2. Features that goes inside Pharo are not decided by vote. They have to
>> add value and share the Pharo vision (pointed in the vision document who is
>> not slightly updated but still guides our steps). We try to reach consensus
>> and if
Hi yuriy
A package manifest is the place where we keep package rules and meta data.
We should add documentation and others.
I think that all the packages should have a XXXManifest.
There we can define a method preUnload and after we can define a class
PackageUnloader (or put the logic in the
> On 27 Aug 2016, at 11:00, stepharo wrote:
>
> You see hernan doing positively is the best way to make that things happen
>
> We can have a
>
>preUnload hook
>
> Now we should check how it fits with cleanForProduction and others.
>
> But we should definitively have a way to express this
So I think that I will keep Eyeinspector for Spec because it works well
using Spec.
I will package BasicInspector
Then we will see. I think that Smalltalk tools inspector is not good
because it is yet another global
while the tools should have a tool context (but with a registration
mechani
May be we should take the one of Pharo30 and review all the code.
Le 27/8/16 à 10:51, stepharo a écrit :
I took the inspector from Pharo20 and I will check if it is working in
Pharo.
Then I will
- check EyeInspector from a package perspective (extensions and
the rest)
- make sure tha
You see hernan doing positively is the best way to make that things happen
We can have a
preUnload hook
Now we should check how it fits with cleanForProduction and others.
But we should definitively have a way to express this.
So let us see how we can design it and then just implement it.
I took the inspector from Pharo20 and I will check if it is working in
Pharo.
Then I will
- check EyeInspector from a package perspective (extensions and the
rest)
- make sure that we can remove EyeInspector
- package the attached file as BasicInspector.
Now if you want to help you
What we should do is to add an unload method to each of the package
manifest of the corresponding projects.
We should make the unload protocol a lot more present.
I will start with Nautilus.
Can you publish the unload process?
Workspace openContents: 'GTPlayground setGTPlaygroundEnable
2016-08-26 6:19 GMT-03:00 stepharo :
>
> About GT I have some concerns too now I see also a lot of improvements. I
>> love GTInspector and we should remove EyeInspector.
>>
>> I want to have once brick is out another minimal environment not based on
>> anything so that we can have a back-door to d
Dne pátek 26. srpna 2016 Hernán Morales Durand
napsal(a):
> Hi Stef,
>
> 2016-08-25 3:48 GMT-03:00 stepharo >:
>
>> Hi hernan
>>
>> Could you reply to my mail? Because what is important is how we can make
>> progres.
>>
>
> Ok, here it is :)
>
>
>> About GT I have some concerns too now I see als
So true. :)
On Thu, 25 Aug 2016 09:05:45 +0200
stepharo wrote:
Yes but we cannot do much
OK. I got it...do you believe it makes sense for a noob to create account
in case there are some low-hanging fruits to pick?
Definitely. And not necessarily that you *solve* an issues, but that
I foun
Definitively :)
I started to do that when I discovered Smalltalk. I wanted to learn and
I read the submissions of people and try to understand and comment.
And I learned a lot about the system, about myself, about quality.
Stef
Le 25/8/16 à 17:31, Gour a écrit :
On Thu, 25 Aug 2016 09:05:4
About GT I have some concerns too now I see also a lot of
improvements. I love GTInspector and we should remove EyeInspector.
I want to have once brick is out another minimal environment not
based on anything so that we can have a back-door to debug when
the other tools have
On Fri, 26 Aug 2016 14:27:24 +0800
Ben Coman wrote:
> Definitely. And not necessarily that you *solve* an issues, but that
> I found a benefit from "goal directed learning".
That's a good point!
> When I started using Pharo I learned a lot from: * trying to reproduce
> issues - which also bene
On Thu, 25 Aug 2016 23:06:51 +0200
Tudor Girba wrote:
> It definitely does! We are all noobs in many parts in our system.
Heh, I'm for the whole system. :-)
> But, if you take your time and are willing to dig, the system is kind
> enough to reveal itself to you :). That is the beauty of this wo
On Thu, Aug 25, 2016 at 11:31 PM, Gour wrote:
> On Thu, 25 Aug 2016 09:05:45 +0200
> stepharo wrote:
>
>> Yes but we cannot do much
>
> OK. I got it...do you believe it makes sense for a noob to create account
> in case there are some low-hanging fruits to pick?
Definitely. And not necessarily
Hi Stef,
2016-08-25 3:48 GMT-03:00 stepharo :
> Hi hernan
>
> Could you reply to my mail? Because what is important is how we can make
> progres.
>
Ok, here it is :)
> About GT I have some concerns too now I see also a lot of improvements. I
> love GTInspector and we should remove EyeInspector
Hi,
> On Aug 25, 2016, at 5:31 PM, Gour wrote:
>
> On Thu, 25 Aug 2016 09:05:45 +0200
> stepharo wrote:
>
>> Yes but we cannot do much
>
> OK. I got it...do you believe it makes sense for a noob to create acount
> in case there are some low-hanging fruits to pick?
It definitely does! We are
On Thu, 25 Aug 2016 09:05:45 +0200
stepharo wrote:
> Yes but we cannot do much
OK. I got it...do you believe it makes sense for a noob to create acount
in case there are some low-hanging fruits to pick?
Sincerely,
Gour
--
From wherever the mind wanders due to its flickering and unsteady
natu
Hi! Hola!
I would like to help with some of this, so I sorted a bit the ideas in
the previous emails to see if we can extract some concrete actions to
apply. So I'll make a step back and put some titles to the topics of
discussion:
!Human/Social/Politics stuff
1) Policies
- Deciding about
Let us know because we do not
I don't get why we don't have more discussions about end-developer
tools : XML, i18n, GIS, simulation & expert systems, big data,
reporting...
Yes the idea is that we would like to try a process for Pharo and that
such process can be used by other projects
Hello,
Looking at bugs is really difficult. There are not enough people
looking and fixing bugs.
just a short note from a Pharo noob...it is, imho, very strange that one
cannot even take a look at bugs *without* creating account at tracker.
We know. Now the company offered us a professiona
Hi,
Thanks Stef for the reply. I completely concur.
@Hernán: About the issues with GT: please do get in touch. We have asked for it
several times, and we are still here. If you have concrete issues, please raise
them but focus on how to improve concretely.
At the same time, also keep in mind t
Hi hernan
Could you reply to my mail? Because what is important is how we can make
progres.
About GT I have some concerns too now I see also a lot of improvements.
I love GTInspector and we should remove EyeInspector.
I want to have once brick is out another minimal environment not based
o
Now I will try to be more positive.
2016-08-24 4:38 GMT-03:00 stepharo :
> Hi Hernan
>
> First thanks for your email because we may disagree but we often agree. :)
> so this is an email for me.
>
> Hi Stef,
>
> Good communication implies being clear when writing about sensitive
> topics, especial
Hi, Esteban,
Please don't take this personal, but we have differences :)
2016-08-24 5:06 GMT-03:00 Esteban Lorenzano :
> Hi,
>
> I want to point just a couple of things:
>
> 1. You may feel hurt, but is my job to say no. If you think I’m doing a
> bad job, is your right to discuss, but do not ex
> On 24 Aug 2016, at 10:07, Gour wrote:
>
> On Wed, 24 Aug 2016 09:38:20 +0200
> stepharo wrote:
>
> Hello,
>
>> Looking at bugs is really difficult. There are not enough people
>> looking and fixing bugs.
>
> just a short note from a Pharo noob...it is, imho, very strange that one
> cannot
On Wed, 24 Aug 2016 09:38:20 +0200
stepharo wrote:
Hello,
> Looking at bugs is really difficult. There are not enough people
> looking and fixing bugs.
just a short note from a Pharo noob...it is, imho, very strange that one
cannot even take a look at bugs *without* creating account at tracker.
Hi,
I want to point just a couple of things:
1. You may feel hurt, but is my job to say no. If you think I’m doing a bad
job, is your right to discuss, but do not expect that what you consider a bad
design decision would be shared by the board (and me as executor of board
policies).
2. Feat
Hi Hernan
First thanks for your email because we may disagree but we often agree.
:) so this is an email for me.
Hi Stef,
Good communication implies being clear when writing about sensitive
topics, especially when communicating through virtual channels. I am
not in Europe, so I cannot discus
Hi Stef,
Good communication implies being clear when writing about sensitive topics,
especially when communicating through virtual channels. I am not in Europe,
so I cannot discuss these things with you face to face. Therefore is not
clear to me (and others) what are your policies in many subjects
Hi guys
the board got a good discussion at ESUG about how to improve and a lot
of the discussion turned around improving communication. We got some
ideas that we will propose soon but I would like to get *your* ideas.
If you have idea about improving communication around pharo please tell us.
35 matches
Mail list logo