how do you put things in the luanch menu?
for example i downloaded phicq but i have to start it in file manager ever
time, i want to be able to start it from the launch menu, and not a button
in a shelf.
I did download and install it too, but I made a new entry in the shelf
“start event” and told it to start /user/photon/bin/phicq.
Then I renamed the button phICQ.
I really dont know how you are supposed to do, but it Worked for me 
BTW my UIN is 95405019, see ya there!
BP <bjpearson@home.com> skrev i
diskussionsgruppsmeddelandet:8svhq6$6du$1@inn.qnx.com…
how do you put things in the luanch menu?
for example i downloaded phicq but i have to start it in file manager ever
time, i want to be able to start it from the launch menu, and not a button
in a shelf.
\
try to put mouse pointer over that and press right mouse button… got
it?
BP wrote:
how do you put things in the luanch menu?
for example i downloaded phicq but i have to start it in file manager ever
time, i want to be able to start it from the launch menu, and not a button
in a shelf.
–
BR, Andrej
Andrej Timchenko <silpol@yahoo.com> wrote:
try to put mouse pointer over that and press right mouse button… got
it?BP wrote:
how do you put things in the luanch menu?
for example i downloaded phicq but i have to start it in file manager ever
time, i want to be able to start it from the launch menu, and not a button
in a shelf.
From the QDN Knowledge base entry:
http://qdn.qnx.com/support/bok/solution.qnx?10100
Editing the launch menu
How does one configure the Launch Menu? That is, how can I add, remove,
or edit the items in the Launch Menu?
Edit the file $HOME/.ph/launch_menu.xml to include the changes desired.
When you want to try the changes out, run launchmenu_notify.
Chris
–
BR, Andrej
Greetings,
Actually, Chris the answer in the knowledge base is not strictly correct. If
you look at the launch_menu.xml file you will not that the first group is
called “Programs”. This is the group that ultimately displayed the
categories including “Editors”, “Utilities”, etc. However, that appears to
come from the launch_menu.log file.
So, if I wish to add “nedit” under “Editors” how do I do this? Do I add it
to the launch_menu.log file or can I somehow edit the launch_menu.xml file
to append to the sub-menu that is generated from the launch_menu.log file?
How does one configure the Launch Menu? That is, how can I add, remove,
or edit the items in the Launch Menu?
Edit the file $HOME/.ph/launch_menu.xml to include the changes desired.
When you want to try the changes out, run launchmenu_notify.
I note with interest that the reference you provide is from a question I
asked. However, I think an example of how to create a new item in an
existing group (like my editors question above) would be helpful. Other
samples might also be helpful, like adding a new group and a new item.
]{ristoph
Kristoph A. Cichocki-Romanov <news1@kristoph.net> wrote:
Greetings,
Actually, Chris the answer in the knowledge base is not strictly correct. If
you look at the launch_menu.xml file you will not that the first group is
called “Programs”. This is the group that ultimately displayed the
categories including “Editors”, “Utilities”, etc. However, that appears to
come from the launch_menu.log file.
Yes, I agree it is not correct, I will fix this and add an example…
So, if I wish to add “nedit” under “Editors” how do I do this? Do I add it
to the launch_menu.log file or can I somehow edit the launch_menu.xml file
to append to the sub-menu that is generated from the launch_menu.log file?How does one configure the Launch Menu? That is, how can I add, remove,
or edit the items in the Launch Menu?
Edit the file $HOME/.ph/launch_menu.xml to include the changes desired.
When you want to try the changes out, run launchmenu_notify.I note with interest that the reference you provide is from a question I
asked. However, I think an example of how to create a new item in an
existing group (like my editors question above) would be helpful. Other
samples might also be helpful, like adding a new group and a new item.
Much of the information from the Knowledge base comes from our TS people
scouring these newsgroups and other avenues of support.
Thanks as usual for much of the good input,
Chris
]{ristoph
Leon <guvenc@amigart.com> wrote:
And…without running launchmenu_notify, the system boots very slow, and no
shelfs are being displayed. Only the right click menu can be visible (btw.
how do we edit the right click menu?)
It is refered to as the Quick menu.
This one I know is right and there is an example ;*)
Check out
http://qdn.qnx.com/support/bok/solution.qnx?9430
in the Knowledge base.
Chris
Leon
Edit the file $HOME/.ph/launch_menu.xml to include the changes desired.
When you want to try the changes out, run launchmenu_notify.
Launchmenu’s original purpose was to be a simple way to gain access to
all of the installed applications on your RtP system. Whenever apps are
added or removed, the launch menu is updated to reflect the change.
It was not meant to be customizable in the beginning however the way it
is structured now makes it customizable to a certain degree.
The $HOME/.ph/launch_menu.log file is a record of what apps are installed
on your system. This file is regenerated from scratch whenever a change is
detected on your system. The system is checked 1) when launchmenu starts
up and 2) whenever the launchmenu_notify app is run (usually only by the
package manager). So any changes you make to launch_menu.log will be
reflected in the launchmenu, but will be lost as soon as a change occurs.
It is best to insert your changes into the $HOME/.ph/launch_menu.xml file.
This file defines the “skeleton” of your launchmenu (ie the menu hierarchy)
which is then filled in with the contents of launch_menu.log.
This file is only ever copied over once, when launchmenu is initially
installed (or if you happen to remove the file).
So here I will (unofficially) document the features you need to be aware of
when modifying this file. This is my disclaimer 
Please don’t be too
upset if the features change slightly in the future as there still are
functional requirements of launchmenu that have yet to be satisfied.
Anything in [square brackets] denotes optional parameters.
MENUS/SUBMENUS
The XML tag:
<MENU:group [name=“…”] topics=“…”] accel=“…” [embed=“true”] [flatten=“true”]>
…
</MENU:group>
denotes a top-level menu or submenu. If this item is a submenu, then
name will be displayed for the corresponding item that invokes the submenu.
The topics parameter specifies what topic strings fall into this submenu
hierarchy.
(if you want to specify multiple topics, separate them with colons ‘:’)
The topics correspond to those found in the items in launch_menu.log.
Please note that at present, the menu’s name (if specified) counts as an
additional topic. This might change.
The accel parameter specifies an accelerator key for the menu item.
Pressing that key while the menu is up selects the menu item.
embed=“true” forces the submenu to be “swallowed” into the current menu.
That is, all the submenu items will be embedded directly into the current
menu rather than into a new separate submenu. Note that since submenus
are only displayed if they have any real contents, then this is a convenient
way to conditionally embed separators into menus as well. For example from
the default launch_menu.xml:
<MENU:group embed=“true” flatten=“true”>
MENU:item</MENU:item>
<MENU:group topics=“System”></MENU:group>
</MENU:group>
the separator will only be displayed if there are items inserted whose
topics fall into the “System” category.
flatten=“true” collapses a submenu hierarchy into a single menu, as if all
submenus and submenus of those submenus had embed=“true” set. This setting
does not cause the submenu itself to be embedded into the current menu.
(use embed=“true” also if you want to achieve this)
MENU ITEMS
The XML tag:
<MENU:item [name=“…”] [accel=“…”]>[…]</MENU:item>
denotes a launchable menu item.
As before, name is the name that will be displayed for this item. If not
specified, this item will be a separator (ie a spacer to impose separation
between the preceeding and succeeding menu items).
The contents of the tag (ie what appears between the tag opening and
closing) specifies the command to launch then this item is invoked.
For example the default launch_menu.xml invokes the shelf config utility
with the item:
<MENU:item name=“Configure Shelves”>shelf -c</MENU:item>
Hopefully this will be enough to get you on your way.
Kristoph A. Cichocki-Romanov <news1@kristoph.net> wrote:
Greetings,
Actually, Chris the answer in the knowledge base is not strictly correct. If
you look at the launch_menu.xml file you will not that the first group is
called “Programs”. This is the group that ultimately displayed the
categories including “Editors”, “Utilities”, etc. However, that appears to
come from the launch_menu.log file.So, if I wish to add “nedit” under “Editors” how do I do this? Do I add it
to the launch_menu.log file or can I somehow edit the launch_menu.xml file
to append to the sub-menu that is generated from the launch_menu.log file?How does one configure the Launch Menu? That is, how can I add, remove,
or edit the items in the Launch Menu?
Edit the file $HOME/.ph/launch_menu.xml to include the changes desired.
When you want to try the changes out, run launchmenu_notify.I note with interest that the reference you provide is from a question I
asked. However, I think an example of how to create a new item in an
existing group (like my editors question above) would be helpful. Other
samples might also be helpful, like adding a new group and a new item.]{ristoph
dleblanc@qnx.com wrote:
Thanks a ton, mus
I will add this to the database entry for Editing the Launch menu…
Chris
Launchmenu’s original purpose was to be a simple way to gain access to
all of the installed applications on your RtP system. Whenever apps are
added or removed, the launch menu is updated to reflect the change.It was not meant to be customizable in the beginning however the way it
is structured now makes it customizable to a certain degree.The $HOME/.ph/launch_menu.log file is a record of what apps are installed
on your system. This file is regenerated from scratch whenever a change is
detected on your system. The system is checked 1) when launchmenu starts
up and 2) whenever the launchmenu_notify app is run (usually only by the
package manager). So any changes you make to launch_menu.log will be
reflected in the launchmenu, but will be lost as soon as a change occurs.It is best to insert your changes into the $HOME/.ph/launch_menu.xml file.
This file defines the “skeleton” of your launchmenu (ie the menu hierarchy)
which is then filled in with the contents of launch_menu.log.
This file is only ever copied over once, when launchmenu is initially
installed (or if you happen to remove the file).So here I will (unofficially) document the features you need to be aware of
when modifying this file. This is my disclaimer >
upset if the features change slightly in the future as there still are
functional requirements of launchmenu that have yet to be satisfied.Anything in [square brackets] denotes optional parameters.
MENUS/SUBMENUS
The XML tag:
MENU:group [name=“…”] topics=“…”] accel=“…” [embed=“true”] [flatten=“true”]
…
/MENU:groupdenotes a top-level menu or submenu. If this item is a submenu, then
name will be displayed for the corresponding item that invokes the submenu.The topics parameter specifies what topic strings fall into this submenu
hierarchy.
(if you want to specify multiple topics, separate them with colons ‘:’)
The topics correspond to those found in the items in launch_menu.log.
Please note that at present, the menu’s name (if specified) counts as an
additional topic. This might change.The accel parameter specifies an accelerator key for the menu item.
Pressing that key while the menu is up selects the menu item.embed=“true” forces the submenu to be “swallowed” into the current menu.
That is, all the submenu items will be embedded directly into the current
menu rather than into a new separate submenu. Note that since submenus
are only displayed if they have any real contents, then this is a convenient
way to conditionally embed separators into menus as well. For example from
the default launch_menu.xml:MENU:group embed=“true” flatten=“true”
MENU:item></MENU:item
MENU:group topics=“System”></MENU:group
/MENU:groupthe separator will only be displayed if there are items inserted whose
topics fall into the “System” category.flatten=“true” collapses a submenu hierarchy into a single menu, as if all
submenus and submenus of those submenus had embed=“true” set. This setting
does not cause the submenu itself to be embedded into the current menu.
(use embed=“true” also if you want to achieve this)MENU ITEMS
The XML tag:
<MENU:item [name=“…”] [accel=“…”]>[…]</MENU:item
denotes a launchable menu item.
As before, name is the name that will be displayed for this item. If not
specified, this item will be a separator (ie a spacer to impose separation
between the preceeding and succeeding menu items).The contents of the tag (ie what appears between the tag opening and
closing) specifies the command to launch then this item is invoked.For example the default launch_menu.xml invokes the shelf config utility
with the item:MENU:item name=“Configure Shelves”>shelf -c</MENU:item
Hopefully this will be enough to get you on your way.Kristoph A. Cichocki-Romanov <> news1@kristoph.net> > wrote:
Greetings,Actually, Chris the answer in the knowledge base is not strictly correct. If
you look at the launch_menu.xml file you will not that the first group is
called “Programs”. This is the group that ultimately displayed the
categories including “Editors”, “Utilities”, etc. However, that appears to
come from the launch_menu.log file.So, if I wish to add “nedit” under “Editors” how do I do this? Do I add it
to the launch_menu.log file or can I somehow edit the launch_menu.xml file
to append to the sub-menu that is generated from the launch_menu.log file?How does one configure the Launch Menu? That is, how can I add, remove,
or edit the items in the Launch Menu?
Edit the file $HOME/.ph/launch_menu.xml to include the changes desired.
When you want to try the changes out, run launchmenu_notify.I note with interest that the reference you provide is from a question I
asked. However, I think an example of how to create a new item in an
existing group (like my editors question above) would be helpful. Other
samples might also be helpful, like adding a new group and a new item.]{ristoph
Example to add phicq to the Launch menu
edit the ~/.ph/launch_menu.log file
include this>>>>> item launch=“usr/photon/bin/phicq” topic=Applications/Internet/PHICQ">
This will add a PHICQ option to the internet menu.
if you want to change the label “Internet” to “AAA” change “Internet” to “AAA” this will add AAA label to the menu list and AAA will contain PHICQ option
IF you want to edit the other menu items such as Software, Configure, HelpVeiwer, QuickGuide or to add a new group you would then edit the launch_menu.xml file
remember to run launchmenu_notify after editing the menus.
Charles Lawrence
QNX Software Systems
Previously, Kristoph A. Cichocki-Romanov wrote in qdn.public.qnxrtp.newuser:
- Greetings,
- Actually, Chris the answer in the knowledge base is not strictly correct. If
- you look at the launch_menu.xml file you will not that the first group is
- called “Programs”. This is the group that ultimately displayed the
- categories including “Editors”, “Utilities”, etc. However, that appears to
- come from the launch_menu.log file.
- So, if I wish to add “nedit” under “Editors” how do I do this? Do I add it
- to the launch_menu.log file or can I somehow edit the launch_menu.xml file
- to append to the sub-menu that is generated from the launch_menu.log file?
-
How does one configure the Launch Menu? That is, how can I add, remove,
-
or edit the items in the Launch Menu?
-
Edit the file $HOME/.ph/launch_menu.xml to include the changes desired.
-
When you want to try the changes out, run launchmenu_notify.
- I note with interest that the reference you provide is from a question I
- asked. However, I think an example of how to create a new item in an
- existing group (like my editors question above) would be helpful. Other
- samples might also be helpful, like adding a new group and a new item.
- ]{ristoph
And…without running launchmenu_notify, the system boots very slow, and no
shelfs are being displayed. Only the right click menu can be visible (btw.
how do we edit the right click menu?)
Leon
Edit the file $HOME/.ph/launch_menu.xml to include the changes desired.
When you want to try the changes out, run launchmenu_notify.