Yes, we reorganized this because it was just *one* menu item inside a submenu 
(in PharoCore).

I also moved it away from the top level into the system submenu because there 
is no help content yet. When this is going to be a great help system that is 
used a lot, then I agree we should move it to the top level. But for now I 
would leave it in the system menu.

Cheers,
Adrian

On Jun 14, 2010, at 11:36 , Stéphane Ducasse wrote:

> Guys 
> 
> this is already a menu! 
> this is a menu with only one item right now. so we think that this it is good 
> where it is.
> 
> Stef
> On Jun 14, 2010, at 11:16 AM, Mariano Martinez Peck wrote:
> 
>> 
>> 
>> 2010/6/14 laurent laffont <[email protected]>
>> On Mon, Jun 14, 2010 at 10:25 AM, Stéphane Ducasse 
>> <[email protected]> wrote:
>> this is in system>help
>> because we do not want a long menu and the help got in our way several times.
>> 
>> I understand we need to be careful about long menus, but I vote for having a 
>> help menu.
>> 
>> me too. +1
>> Help menu is standard, useful and user friendy.
>> Every app in the world has a Help menu. 
>> 
>> Anyway, if you decide to reintegrate it, the slice is in inbox: 
>> SLICE-Issue-2442-RestoreHelpMenu-LaurentLaffont.1
>> 
>> Cheers,
>> 
>> Laurent.
>> 
>> 
>> 
>> Stef
>> 
>> On Jun 14, 2010, at 10:21 AM, Mariano Martinez Peck wrote:
>> 
>>> 
>>> 
>>> 2010/6/14 laurent laffont <[email protected]>
>>> On Sun, Jun 13, 2010 at 11:19 PM, Mariano Martinez Peck 
>>> <[email protected]> wrote:
>>> Hi folks. There is a new Pharo 1.1 rc2 image for beta testing. It is based 
>>> in PharoCore rc2 11400.
>>> 
>>> Help menu is gone ?
>>> 
>>> Thanks for reporting. Yes, it seems to have disappeared. I have just 
>>> checked in PharoCore 11400 and it is not there neither. So, it is not "Dev" 
>>> fault at least.
>>> 
>>> Was fixed in http://code.google.com/p/pharo/issues/detail?id=2442
>>> 
>>> Maybe re integrate it ?
>>> 
>>> Cheers
>>> 
>>> Mariano
>>> 
>>> 
>>> Laurent Laffont
>>> 
>>> 
>>> http://pharocasts.blogspot.com/
>>> http://magaloma.blogspot.com/
>>> 
>>> 
>>> A little remark is that this is the first release candidate, not the second 
>>> one. There was a problem when building the PharoCore rc1 and thus, we used 
>>> PharoCore RC2. To be concistent we call it Pharo 1.1 rc2 to this image.
>>> 
>>> We are getting closer to the stable release of Pharo 1.1 so we would really 
>>> appreaciate any kind of feedback. Use it, load your packages and 
>>> applications, run tests, etc.
>>> 
>>> The download link is: 
>>> https://gforge.inria.fr/frs/download.php/27159/Pharo-1.1-11400-rc2dev10.06.1.zip
>>> 
>>> Cheers
>>> 
>>> Mariano
>>> 
>>> 
>>> _______________________________________________
>>> Pharo-users mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>> 
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
>> 
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
>> 
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> 
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to