[Pharo-project] what do we do for OmniBrowser?

Stéphane Ducasse stephane.ducasse at inria.fr
Thu Feb 3 09:21:13 CET 2011


Excellent!
Tx a lot!!!!!!!

Stef
(I'm loading keymapping :)

On Feb 3, 2011, at 4:13 AM, Guillermo Polito wrote:

> 
> 
> On Wed, Feb 2, 2011 at 3:47 PM, Stéphane Ducasse <stephane.ducasse at inria.fr> wrote:
> Ok guys here is what I suggest:
> 
>        - create a PharoOB or something like that
> 
> You ask for it, you have it:
> http://www.squeaksource.com/PharoOB
> Respository with licence MIT, global Read and Write access.
>  
>        - push using gofer all the code from lukas repository 
>        - check the configuration for 1.1 
>        - check the configuration for 1.2
> 
> We have the configs already in MetacelloRepository.  We should move them to the new repo to have everything together.
>  
>        - there are some fixes we can integrate but we should make sure that the tests are always green.
> 
> I'm integrating already the fixes into PharoTaskForces.  If I have some tome tomorrow I'll push OB from Lukas repo to PharoOB and merge.
> 
> Guille :)
>  
> 
> Stef
> 
> > I agree with Hernán. OB is incredibly valuable, and I was delighted to
> > see that it was included out of the box in 1.2 (when switching to
> > Pharo from Squeak). We cannot let it slide or remove it (btw, I still
> > can't believe we as a community let SeasideTesting be broken in 1.2).
> >
> > Hernán -- I would love to offer any sort of help maintaining it. I
> > don't know much about GUI/Morphic coding, though of course I'd like to
> > learn. But I would definitely be willing to help test it, etc.
> >
> > ~Dmitri
> >
> > On Wed, Feb 2, 2011 at 9:48 AM, Hernán Morales Durand
> > <hernan.morales at gmail.com> wrote:
> >> Just to give some feedback because I mostly use the core image. OB is
> >> one of our most valuable tools, it would be a pity if cannot be
> >> integrated.
> >> I could help mantaining but not alone, I'm sick of programming in isolation.
> >>
> >> Hernán
> >>
> >> 2011/2/2 Stéphane Ducasse <stephane.ducasse at inria.fr>:
> >>> Ok so far no reaction.
> >>> So may be we should remove OB from 1.2 dev?
> >>>
> >>> Stef
> >>>
> >>>
> >>>> Lukas will not maintain OB for Pharo 1.2 and personnally I will not do it because I do not have the knowledge and the time.
> >>>> So now this is time to know what do we do for OmniBrowser. I have all my ears open.
> >>>>
> >>>>
> >>>> The first step I would do
> >>>>       - host OB for 1.1 in a repository where we have write access.
> >>>>       - create a configurationOf for OB and save it there
> >>>>
> >>>>
> >>>> Stef
> >>>
> >>>
> >>>
> >>
> >>
> >
> 
> 
> 





More information about the Pharo-project mailing list