Can not open Browser on a given selector in 2.0
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code: Browser newOnClass: Number selector: #/ Now it bring a DNU Retangle>>topOffset: I can use Nautilus but it opens a full complete browser and I don't want this. I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method. Hilaire
On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code:
Browser newOnClass: Number selector: #/
Now it bring a DNU Retangle>>topOffset:
this is probably due to a missing layoutFrame can you try asLayoutFrame
I can use Nautilus but it opens a full complete browser and I don't want this.
I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method.
Hilaire <Browser-openAsMorphClassEditing.st>
hilaire I trid to understand why the browser is showing a different symbol and I got stuck. Stf On Sep 18, 2013, at 7:17 AM, Stéphane Ducasse <Stephane.Ducasse@inria.fr> wrote:
On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code:
Browser newOnClass: Number selector: #/
Now it bring a DNU Retangle>>topOffset:
this is probably due to a missing layoutFrame can you try asLayoutFrame
I can use Nautilus but it opens a full complete browser and I don't want this.
I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method.
Hilaire <Browser-openAsMorphClassEditing.st>
On Sep 18, 2013, at 8:20 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
hilaire
I trid to understand why the browser is showing a different symbol and I got stuck.
We really should not waste our time with the old browser.
Stf
On Sep 18, 2013, at 7:17 AM, Stéphane Ducasse <Stephane.Ducasse@inria.fr> wrote:
On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code:
Browser newOnClass: Number selector: #/
Now it bring a DNU Retangle>>topOffset:
this is probably due to a missing layoutFrame can you try asLayoutFrame
I can use Nautilus but it opens a full complete browser and I don't want this.
I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method.
Hilaire <Browser-openAsMorphClassEditing.st>
Yes probably much better to write a simple new one. I will try this evening as an exercise. Stef On Sep 18, 2013, at 8:23 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Sep 18, 2013, at 8:20 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
hilaire
I trid to understand why the browser is showing a different symbol and I got stuck.
We really should not waste our time with the old browser.
Stf
On Sep 18, 2013, at 7:17 AM, Stéphane Ducasse <Stephane.Ducasse@inria.fr> wrote:
On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code:
Browser newOnClass: Number selector: #/
Now it bring a DNU Retangle>>topOffset:
this is probably due to a missing layoutFrame can you try asLayoutFrame
I can use Nautilus but it opens a full complete browser and I don't want this.
I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method.
Hilaire <Browser-openAsMorphClassEditing.st>
Le 18/09/2013 08:23, Marcus Denker a écrit :
On Sep 18, 2013, at 8:20 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
hilaire
I trid to understand why the browser is showing a different symbol and I got stuck.
We really should not waste our time with the old browser.
When developping a browser, I like having a working one as fallback. It's hard to correct a bug in your code editor :P With the funny stuff happening between class categories and packages in Pharo, I also like to have a simple browser showing what is really happening with the base system organization. Make it an optional, compatibility package and it will probably die by itself in a few Pharo versions. It's not like you're spending a lot of time on it. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Stef, I corrected that in the slice. Can you have a look? Thanks, Thierry Le 18/09/2013 08:19, Stéphane Ducasse a écrit :
hilaire
I trid to understand why the browser is showing a different symbol and I got stuck.
Stf
On Sep 18, 2013, at 7:17 AM, Stéphane Ducasse <Stephane.Ducasse@inria.fr> wrote:
On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code:
Browser newOnClass: Number selector: #/
Now it bring a DNU Retangle>>topOffset:
this is probably due to a missing layoutFrame can you try asLayoutFrame
I can use Nautilus but it opens a full complete browser and I don't want this.
I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method.
Hilaire <Browser-openAsMorphClassEditing.st>
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
We will remove all the StringHolder hierarchy so I suggest to have a look at the Spec tutorial and write a little mini browser. It should not be difficult based on the examples. We should move on and get rid of old code. Stef On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code:
Browser newOnClass: Number selector: #/
Now it bring a DNU Retangle>>topOffset:
I can use Nautilus but it opens a full complete browser and I don't want this.
I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method.
this is strange
Hilaire <Browser-openAsMorphClassEditing.st>
On Sep 17, 2013, at 10:53 PM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code:
Browser newOnClass: Number selector: #/
Now it bring a DNU Retangle>>topOffset:
I can use Nautilus but it opens a full complete browser and I don't want this.
But the old Browser will be removed. It would have already been removed if there would not be a subclass. (course of a crappy system: even throwing stuff away is difficult)
I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method.
After some people ran into that we added: https://pharo.fogbugz.com/f/cases/11624 But the real mistake was to not clean up the old Browser code. We are wasting our time for nothing maintaining two code bases. Marcus
Hi Hilaire, I uploaded a slice which corrects both problems, in PharoInbox: SLICE-Issue-11624-backport-Pharo2-Add-missing-asLayoutFrame-in-Browser-openAsMorphClassEditing-ThierryGoubier.1 Regards, Thierry Le 17/09/2013 22:53, Hilaire Fernandes a écrit :
With 1.4, I use to open programmatically a *mini* browser on a given selector with the following code:
Browser newOnClass: Number selector: #/
Now it bring a DNU Retangle>>topOffset:
I can use Nautilus but it opens a full complete browser and I don't want this.
I can fix the code adding a asLayoutFrame (see cs) but then the browser does not open on the proper method.
Hilaire
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
participants (4)
-
Goubier Thierry -
Hilaire Fernandes -
Marcus Denker -
Stéphane Ducasse