- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] "Browser" on a single class

by Yuriy Tymchuk

My main interest in fact is recategorisation of methods. And dragging them into protocols looks pretty good for now. Can I do the same with glamour? Uko > On 03 Oct 2014, at 13:26, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> >> On 03 Oct 2014, at 13:14, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> >> Am 03.10.2014 12:34 schrieb "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >> > >> > Hi. >> > >> > I want to make something like a browser on a single class. I.e. just use 2 last lists out if 4 in standard browser. >> > >> > Is there already something like that? If not, should I use existing widgets, or implement my own using spec? >> > >> > Cheers! >> > Uko >> > >> > Sent from my iPhone >> >> I think that is pretty easy with some spec models. >> Maybe there is already an example >> > yes, but a few models means a few classes :) > in a single class, it will e a lot easier glamour (which btw, is specially designed for that: to make browsers). > > Esteban >> Hilaire asked for a simple Method editor and >> i wrote a simple example build with DynamicComposableModel, search the Mailingliste. >>

Oct. 3, 2014

Re: [Pharo-dev] Poll: What should we use to replace cmd+o in GTPlayground?

by kilon alios

yeah sorry for the confusion, no idea why i pressed i instead of 1. On Fri, Oct 3, 2014 at 2:47 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 03 Oct 2014, at 13:44, Richard Wettel <wettel(a)gmail.com> wrote: > > I assume you selected x and inspected it before evaluating the assignment > statement, in which case remains uninitialized. > > Cheers > Ricky > â > Sent from Mailbox <https://www.dropbox.com/mailbox> > > > On Fri, Oct 3, 2014 at 1:40 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > >> actually i just tried it >> >> I opened the Playground and typed >> >> x := 1. >> >> > no, it is > > x := i > > which evaluates to nil, and yes, GTInpsector just shows a grey area for > nilâ¦ (which I think was not intentional) > > Marcus > > > and I clicked inspect and it opens an inspector window that is empty >> completely.... I assume this is a bug ? >> >> this is how it looks --> >> <Inspector bug.JPG> >> >> >> On Fri, Oct 3, 2014 at 2:25 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Yes, it is meant to replace the classic inspector. Did you notice that >>> anything is missing? >>> >>> Doru >>> >>> On Fri, Oct 3, 2014 at 1:24 PM, kilon alios <kilon.alios(a)gmail.com> >>> wrote: >>> >>>> will gtinspector replace the existing inspector ? will it offer all the >>>> functionality that the existing inspector offers ? >>>> >>>> if yes, then I think its obvious that cmd+i is the best choice here. >>>> >>>> I also think that is time for pharo to get its own shortcut manager so >>>> you guys not have to worry about these things. So it makes it easy to map >>>> keys to functionality. >>>> >>>> 2014-10-03 13:27 GMT+03:00 <estebanlm(a)gmail.com>: >>>> >>>> Si tienes problemas para visualizar o enviar este formulario, puedes >>>>> rellenarlo online: >>>>> >>>>> https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW… >>>>> >>>>> Formulario sin tÃtulo >>>>> *Obligatorio >>>>> >>>>> What should we use to "open gtinspector in playground" (formerly >>>>> cmd+o) * >>>>> - let's remap cmd+i, it is the best option >>>>> - I prefer to use other map, let's use cmd+g (or e) >>>>> Nunca envÃes contraseÃ±as a travÃ©s de Formularios de Google. >>>>> >>>>> Con la tecnologÃa de >>>>> [image: Formularios de Google] >>>>> Este contenido no ha sido creado ni aprobado por Google. >>>>> Informar sobre abusos >>>>> <https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW…> >>>>> - Condiciones del servicio <http://www.google.com/accounts/TOS> - Otros >>>>> tÃ©rminos <http://www.google.com/google-d-s/terms.html> >>>>> >>>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > >

Oct. 3, 2014

Re: [Pharo-dev] Poll: What should we use to replace cmd+o in GTPlayground?

by Marcus Denker

On 03 Oct 2014, at 13:44, Richard Wettel <wettel(a)gmail.com> wrote: > I assume you selected x and inspected it before evaluating the assignment statement, in which case remains uninitialized. > > Cheers > Ricky > â > Sent from Mailbox > > > On Fri, Oct 3, 2014 at 1:40 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > > actually i just tried it > > I opened the Playground and typed > > x := 1. > no, it is x := i which evaluates to nil, and yes, GTInpsector just shows a grey area for nilâ¦ (which I think was not intentional) Marcus > and I clicked inspect and it opens an inspector window that is empty completely.... I assume this is a bug ? > > this is how it looks --> > <Inspector bug.JPG> > > > On Fri, Oct 3, 2014 at 2:25 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Yes, it is meant to replace the classic inspector. Did you notice that anything is missing? > > Doru > > On Fri, Oct 3, 2014 at 1:24 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > will gtinspector replace the existing inspector ? will it offer all the functionality that the existing inspector offers ? > > if yes, then I think its obvious that cmd+i is the best choice here. > > I also think that is time for pharo to get its own shortcut manager so you guys not have to worry about these things. So it makes it easy to map keys to functionality. > > 2014-10-03 13:27 GMT+03:00 <estebanlm(a)gmail.com>: > > Si tienes problemas para visualizar o enviar este formulario, puedes rellenarlo online: > https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW… > > Formulario sin tÃtulo > > > > *Obligatorio > > What should we use to "open gtinspector in playground" (formerly cmd+o) * > let's remap cmd+i, it is the best option > I prefer to use other map, let's use cmd+g (or e) > > Nunca envÃes contraseÃ±as a travÃ©s de Formularios de Google. > Con la tecnologÃa de > > Este contenido no ha sido creado ni aprobado por Google. > Informar sobre abusos - Condiciones del servicio - Otros tÃ©rminos > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > >

Oct. 3, 2014

Re: [Pharo-dev] Poll: What should we use to replace cmd+o in GTPlayground?

by Richard Wettel

I assume you selected x and inspected it before evaluating the assignment statement, in which case remains uninitialized. Cheers Ricky â Sent from Mailbox On Fri, Oct 3, 2014 at 1:40 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > actually i just tried it > I opened the Playground and typed > x := 1. > and I clicked inspect and it opens an inspector window that is empty > completely.... I assume this is a bug ? > this is how it looks --> > On Fri, Oct 3, 2014 at 2:25 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Yes, it is meant to replace the classic inspector. Did you notice that >> anything is missing? >> >> Doru >> >> On Fri, Oct 3, 2014 at 1:24 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >> >>> will gtinspector replace the existing inspector ? will it offer all the >>> functionality that the existing inspector offers ? >>> >>> if yes, then I think its obvious that cmd+i is the best choice here. >>> >>> I also think that is time for pharo to get its own shortcut manager so >>> you guys not have to worry about these things. So it makes it easy to map >>> keys to functionality. >>> >>> 2014-10-03 13:27 GMT+03:00 <estebanlm(a)gmail.com>: >>> >>> Si tienes problemas para visualizar o enviar este formulario, puedes >>>> rellenarlo online: >>>> >>>> https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW… >>>> >>>> Formulario sin tÃtulo >>>> *Obligatorio >>>> >>>> What should we use to "open gtinspector in playground" (formerly >>>> cmd+o) * >>>> - let's remap cmd+i, it is the best option >>>> - I prefer to use other map, let's use cmd+g (or e) >>>> Nunca envÃes contraseÃ±as a travÃ©s de Formularios de Google. >>>> >>>> Con la tecnologÃa de >>>> [image: Formularios de Google] >>>> Este contenido no ha sido creado ni aprobado por Google. >>>> Informar sobre abusos >>>> <https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW…> >>>> - Condiciones del servicio <http://www.google.com/accounts/TOS> - Otros >>>> tÃ©rminos <http://www.google.com/google-d-s/terms.html> >>>> >>>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >>

Oct. 3, 2014

About ways to participate in community and general negativity

by Esteban Lorenzano

Hi, Iâm writing this because Iâm sad about what is happening in this list. Iâm seeing a lot of general negativity and non constructive ways to discuss things. Iâm also seeing more and more people using Pharo for their particular interests (which is of course a good thing) but less and less people who contribute back to Pharo. Finally, Iâm seeing more frequently an attitude of âcustomerâ, more than the conviction than this, Pharo, is also yoursâ¦ Please people, we (the pharo âcoreâ team) cannot do everything. We do not have the manpower or the resources to hire manpower. We would like, but we just do not have the resources (is already a blessing that we can work on this, for now: INRIA is paying, but what it pays is *research*, not âpharo the languageâ, so this is a collateral advantageâ¦.) So, having an OPEN SOURCE project, with limited resources means that there is a lot of things that depend on the community. It depends on the community not just to fix, but to enlarge the ecosystem in general too. So, I refuse to believe that we cannot be a cool and helpful community. I refuse to believe that general negativity and bad humor can overcome the joy of participating in this collective effort. So, here some recommendations for enhance the way we participate: - Be positive. Just âthis is a s**tâ does not help. Even if it is. - Be propositional. Just âthis is a s**tâ, and not telling what you want/prefer does not help. - Be proactive. Just âthis is a s**tâ, and not report, discuss and (at least time to time) provide a fix/enhancement does not help. In conclusion: not helping does not help :) After all, this is the âpharo-devâ list. I mean, the list of people wanting to participate from this great, community effort. cheers, Esteban, still grateful of belonging to this community

Oct. 3, 2014

Re: [Pharo-dev] Poll: What should we use to replace cmd+o in GTPlayground?

by kilon alios

actually i just tried it I opened the Playground and typed x := 1. and I clicked inspect and it opens an inspector window that is empty completely.... I assume this is a bug ? this is how it looks --> On Fri, Oct 3, 2014 at 2:25 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Yes, it is meant to replace the classic inspector. Did you notice that > anything is missing? > > Doru > > On Fri, Oct 3, 2014 at 1:24 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > >> will gtinspector replace the existing inspector ? will it offer all the >> functionality that the existing inspector offers ? >> >> if yes, then I think its obvious that cmd+i is the best choice here. >> >> I also think that is time for pharo to get its own shortcut manager so >> you guys not have to worry about these things. So it makes it easy to map >> keys to functionality. >> >> 2014-10-03 13:27 GMT+03:00 <estebanlm(a)gmail.com>: >> >> Si tienes problemas para visualizar o enviar este formulario, puedes >>> rellenarlo online: >>> >>> https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW… >>> >>> Formulario sin tÃtulo >>> *Obligatorio >>> >>> What should we use to "open gtinspector in playground" (formerly >>> cmd+o) * >>> - let's remap cmd+i, it is the best option >>> - I prefer to use other map, let's use cmd+g (or e) >>> Nunca envÃes contraseÃ±as a travÃ©s de Formularios de Google. >>> >>> Con la tecnologÃa de >>> [image: Formularios de Google] >>> Este contenido no ha sido creado ni aprobado por Google. >>> Informar sobre abusos >>> <https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW…> >>> - Condiciones del servicio <http://www.google.com/accounts/TOS> - Otros >>> tÃ©rminos <http://www.google.com/google-d-s/terms.html> >>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Oct. 3, 2014

Re: [Pharo-dev] "Browser" on a single class

by Esteban Lorenzano

> On 03 Oct 2014, at 13:14, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > Am 03.10.2014 12:34 schrieb "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > > > > Hi. > > > > I want to make something like a browser on a single class. I.e. just use 2 last lists out if 4 in standard browser. > > > > Is there already something like that? If not, should I use existing widgets, or implement my own using spec? > > > > Cheers! > > Uko > > > > Sent from my iPhone > > I think that is pretty easy with some spec models. > Maybe there is already an example > yes, but a few models means a few classes :) in a single class, it will e a lot easier glamour (which btw, is specially designed for that: to make browsers). Esteban > Hilaire asked for a simple Method editor and > i wrote a simple example build with DynamicComposableModel, search the Mailingliste.

Oct. 3, 2014

Re: [Pharo-dev] Poll: What should we use to replace cmd+o in GTPlayground?

by Tudor Girba

Yes, it is meant to replace the classic inspector. Did you notice that anything is missing? Doru On Fri, Oct 3, 2014 at 1:24 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > will gtinspector replace the existing inspector ? will it offer all the > functionality that the existing inspector offers ? > > if yes, then I think its obvious that cmd+i is the best choice here. > > I also think that is time for pharo to get its own shortcut manager so you > guys not have to worry about these things. So it makes it easy to map keys > to functionality. > > 2014-10-03 13:27 GMT+03:00 <estebanlm(a)gmail.com>: > > Si tienes problemas para visualizar o enviar este formulario, puedes >> rellenarlo online: >> >> https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW… >> >> Formulario sin tÃtulo >> *Obligatorio >> >> What should we use to "open gtinspector in playground" (formerly >> cmd+o) * >> - let's remap cmd+i, it is the best option >> - I prefer to use other map, let's use cmd+g (or e) >> Nunca envÃes contraseÃ±as a travÃ©s de Formularios de Google. >> >> Con la tecnologÃa de >> [image: Formularios de Google] >> Este contenido no ha sido creado ni aprobado por Google. >> Informar sobre abusos >> <https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW…> >> - Condiciones del servicio <http://www.google.com/accounts/TOS> - Otros >> tÃ©rminos <http://www.google.com/google-d-s/terms.html> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 3, 2014

Re: [Pharo-dev] Poll: What should we use to replace cmd+o in GTPlayground?

by kilon alios

will gtinspector replace the existing inspector ? will it offer all the functionality that the existing inspector offers ? if yes, then I think its obvious that cmd+i is the best choice here. I also think that is time for pharo to get its own shortcut manager so you guys not have to worry about these things. So it makes it easy to map keys to functionality. 2014-10-03 13:27 GMT+03:00 <estebanlm(a)gmail.com>: > Si tienes problemas para visualizar o enviar este formulario, puedes > rellenarlo online: > > https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW… > > Formulario sin tÃtulo > *Obligatorio > > What should we use to "open gtinspector in playground" (formerly > cmd+o) * > - let's remap cmd+i, it is the best option > - I prefer to use other map, let's use cmd+g (or e) > Nunca envÃes contraseÃ±as a travÃ©s de Formularios de Google. > > Con la tecnologÃa de > [image: Formularios de Google] > Este contenido no ha sido creado ni aprobado por Google. > Informar sobre abusos > <https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aW…> > - Condiciones del servicio <http://www.google.com/accounts/TOS> - Otros > tÃ©rminos <http://www.google.com/google-d-s/terms.html> > >

Oct. 3, 2014

Re: [Pharo-dev] Playground

by kilon alios

Well my problem was that I was caught by suprise, I saw workspace disappear and suddenly I see a new tool that looks and behaves very diffirently and me not able to do even the most basic stuff I was doing with workspace. I now looking throught your links and I understand now that this is no workspace , its a completely diffirent tool , pretty advanced and very powerful and has some very good ideas in like as you said each object defining its own tabs and representations etc. If playground is to really replace workspace then you need to add an "easy mode" something that people will be able to use without having to read 10 links to understand the potential just for basic functionality. Most likely you already considering doing this. Alexander and Esteban want to play the game of "you having a wrong mindset to figure this out because you are used to other sfuff" but its a game they lost the moment I started coding for Pharo . Actually Alexander's "authors experiment" theory falls on its face when you consider that most people using Pharo if not all, are quite experienced coders and yet they chose to use something that turns coding on its head. On the other this ridiculous assumption seem kinda funny when you bring to your mind the popular quote "I am too old for this shit" of Danny Glover in Lethal Weapon. But apparently even he was not "too old for this shit". The important thing is to hear all opinions, finding out why people complain and do not assume that the absence of complaining implies approval. Only voiced approval is approval. I think Playground looks very promising from what I read from these links and thank you for taking the time explaining some of the concepts to me and of course providing documentation. Yes I do still think that the GUI can become more "begineer friendly" I already offered my suggestions , I am sure others will jump in with more suggestions. Its definitely a tool I will try it more thoroughly. On Fri, Oct 3, 2014 at 10:04 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > It is precisely those points that are not so obvious that are important to > discover. That is why your feedback is important. Please keep the questions > and suggestions coming. > > Cheers, > Doru > > On Fri, Oct 3, 2014 at 9:00 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > >> Thanks I will read those and try it in practise this way it will be >> easier to me to connect the dots. I was not aware of them, maybe add them >> to a chapter to Pharo for the Enterprise to make them more visible , they >> will also need to be added to PBE for beginners because many things about >> this tool are not obvious. Still a long way till Pharo 4 is release so you >> have plenty of time to polish things up. >> >> â >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Oct. 3, 2014