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

[Ben Coman]

kilon alios 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. 


+1 - but I know there are many things on the plate, and that might stay 
on the menu for now.




2014-10-03 13:27 GMT+03:00 >:


Si tienes problemas para visualizar o enviar este formulario, puedes
rellenarlo online:

https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aWs/viewform?c=0&w=1&usp=mail_form_link





  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
Formularios de Google
Este contenido no ha sido creado ni aprobado por Google.
Informar sobre abusos


- Condiciones del servicio  -
Otros términos 

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

[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 
wrote:

>
> On 03 Oct 2014, at 13:44, Richard Wettel  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  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 -->
>> 
>>
>>
>> On Fri, Oct 3, 2014 at 2:25 PM, Tudor Girba  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 
>>> 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 :

  Si tienes problemas para visualizar o enviar este formulario, puedes
> rellenarlo online:
>
> https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aWs/viewform?c=0&w=1&usp=mail_form_link
>
>  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
> 
> - Condiciones del servicio  - Otros
> términos 
>
>

>>>
>>>
>>>  --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>>
>>
>>
>
>

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

[Marcus Denker]

On 03 Oct 2014, at 13:44, Richard Wettel  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  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 --> 
> 
> 
> 
> On Fri, Oct 3, 2014 at 2:25 PM, Tudor Girba  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  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 :
> 
> Si tienes problemas para visualizar o enviar este formulario, puedes 
> rellenarlo online: 
> https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aWs/viewform?c=0&w=1&usp=mail_form_link
> 
> 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"
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

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

[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  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  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  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 :
>>>
>>>  Si tienes problemas para visualizar o enviar este formulario, puedes
 rellenarlo online:

 https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aWs/viewform?c=0&w=1&usp=mail_form_link

 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
 
 - Condiciones del servicio  - Otros
 términos 


>>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>

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

[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  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  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 :
>>
>>  Si tienes problemas para visualizar o enviar este formulario, puedes
>>> rellenarlo online:
>>>
>>> https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aWs/viewform?c=0&w=1&usp=mail_form_link
>>>
>>> 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
>>> 
>>> - Condiciones del servicio  - Otros
>>> términos 
>>>
>>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>

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

[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  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 :
>
>  Si tienes problemas para visualizar o enviar este formulario, puedes
>> rellenarlo online:
>>
>> https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aWs/viewform?c=0&w=1&usp=mail_form_link
>>
>> 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
>> 
>> - Condiciones del servicio  - Otros
>> términos 
>>
>>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

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

[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 :

>  Si tienes problemas para visualizar o enviar este formulario, puedes
> rellenarlo online:
>
> https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aWs/viewform?c=0&w=1&usp=mail_form_link
>
> 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
> 
> - Condiciones del servicio  - Otros
> términos 
>
>

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

[estebanlm]

Te he invitado a rellenar el formulario Formulario sin título. Para
rellenarlo, visita:
https://docs.google.com/forms/d/14y9NJfSk-hsrmcpCMc8sY2cy6za8GAYQ_lipRFL6aWs/viewform?c=0&w=1&usp=mail_form_link