would be interesting to give a try.
Now I'm concerned by our resources.
Stef
On Jul 7, 2009, at 10:50 AM, Damien Cassou wrote:
> On Mon, Jul 6, 2009 at 12:18 AM, Reinout Heeck wrote:
>> Load (more precisely: use -- we might not be able to load it) a /
>> specific/ version of the Squeak tool, and
On Mon, Jul 6, 2009 at 12:18 AM, Reinout Heeck wrote:
> Load (more precisely: use -- we might not be able to load it) a /
> specific/ version of the Squeak tool, and then apply a separate (Pharo-
> maintained) set of patches to make it Pharo compliant.
> Define a process to specify how bug fixes ar
>>
>
> No, quite the opposite:
>
> The Pharo maintainers maintain the Pharo compliance patches for every
> tool we import, the tool developer should not be bothered with these
> -- should not even see them.
I agree but it means that other pharoers should stand up and sign for
that
because I'm fu
>>
>> I think we should consider cribbing from the model that Linux distros
>> use:
>>
>> Load (more precisely: use -- we might not be able to load it) a /
>> specific/ version of the Squeak tool, and then apply a separate
>> (Pharo-
>> maintained) set of patches to make it Pharo compliant.
>
> bu
On Jul 6, 2009, at 10:49 AM, David Röthlisberger wrote:
>
> You can get the fix by executing 'ScriptLoader loadOBAlpha' in a
> workspace.
>
Yo, thanks -- I'll start all this studying this week ;-)
R
-
___
Pharo-project mailing list
Pharo-project@
may be the future is that a small company offers pharo support.
But it will depend on you :)
Stef
> Hi Reinout,
>
> Just to say - I'm in pretty similar position as you, trying to use
> Squeak and friends for my commercial work (which is still on
> VisualWorks
> for now), that's why I really lik
Hi Reinout,
Just to say - I'm in pretty similar position as you, trying to use
Squeak and friends for my commercial work (which is still on VisualWorks
for now), that's why I really like the progress Pharoers did so far and
I'm supporting them as much as I can.
Which does not mean I stopped suppo
>
>> the update is only working for the core because OB is not part of
>> pharo but an add-on.
>> And the add-on are not managed by the pharo stream of changes but by
>> an update of
>> the projects in the pharo Universe (yes this is complex but we do not
>> want that people can
>> say that we are
Hi Reinout
> What is the status of the dev-image? As delivered the tools are broken
> (because context menus on the source pane raise an UHE that is induced
> by OB-Enhancements, issue 904), is it actively used by the main
> committers or is the core image the place to be?
> Even more confus
Hi Stef!
Thanks for the in-depth answers, some remarks/further questions:
> the update is only working for the core because OB is not part of
> pharo but an add-on.
> And the add-on are not managed by the pharo stream of changes but by
> an update of
> the projects in the pharo Universe (yes thi
> Please note that Pharo is not even yet in beta, so some of the snags
> you mention will no doubt get fixed as the feature list finalizes.
> As an open source project, there will be a certain amount of bias
> toward what is important to the heavy contributors. I hope those
> will includ
>
>
> > The process of updating the dev image is excruciatingly slow, is this
> > normal?
>
Yes, this proccess is slow. However, I noticed sometimes is VERY low. Are
you using Nod32? If you do, please exclude the directory where squeak is and
you will see the difference :) This is because .chang
Hi reinout
> Please bear in mind that I'm a newbie to Squeak, so some of these
> questions may be rather naive.
We welcome newbie like you :)
> One of my motivations is to evaluate the future viability of Pharo as
> a vehicle for commercial applications and whether it warrants to lobby
> for re
ut it.
Bill
-Original Message-
From: pharo-project-boun...@lists.gforge.inria.fr
[mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Reinout Heeck
Sent: Sunday, July 05, 2009 6:36 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: [Pharo-project] Loads of Pharo develo
I'm having trouble wrapping my head around how the Pharo development/
maintenance process is supposed to work.
Most of these seem to be missing info on the wiki which merely need
fleshing out there, I would update the wiki pages myself if only I
knew what to write...
Please bear in mind that
15 matches
Mail list logo
