Hi Steve,

On 29/01/18 08:05, Steve Litt wrote:
On Fri, 26 Jan 2018 14:51:32 +0100
aitor_czr<aitor_...@gnuinos.org>  wrote:

Hi Steve:
I read in the past your page in troubleshooters dedicated to umenu. I
still didn't give it a try, but i'll do.

On the other hand, i'm improving the response time of the header in
the popupmenu. As some user in the IRC channel would say, this part
needs more love:)  Now, you need to add the whole "exec" field in the
*.desktop entries as arguments in the command line, for example:

popupmenu "exo-open --launch FileManager %u" "medit %F"

otherwise, the application will be missing in the header.
Hi Aitor,

I skimmed your source, and also the source of menu-cache.h, which I
found on the net someplace. I couldn't figure out the structure by
which your menu hierarchy is stored on the hard disk. Do you have any
documentation about configuring popupmenu's menu hierarchy?

Does popupmenu's menu hierarchy get updated every time someone installs
a new application? That would be a cool thing to add to UMENU2, but I
have no idea how to do it.

Does popupmenu have, or will it have, a mode by which someone can
modify the menu hierarchy or add/delete/change menu items via an
intuitive form that asks for and acquires user input? That's something
UMENU2 doesn't have yet.

You mentioned that part of popupmenu isn't as fast as you'd like
(presumably slower than the user can type/mouse). Does popupmenu run
anew everytime someone clicks on the start button? I'm pretty sure any
time consumption at all comparable to human typing speed involves
reading from the hard disk. In UMENU Classic I solved this by busting
the hierarchy file into individual single menu files. It was a mess.
UMENU2 puts the entire hierarchy in a directory tree, so the entirety
of the requested menu's information is contained in the direct
subdirectories of that menu entry's directory. Which makes it lightning
fast. Maybe you can do something like UMENU Classic or UMENU2, or
perhaps create an index file to point at specific menus within the
hierarchy. Or maybe the code in menu-cache.h/menu-cache.c is meant to
address this problem.

Thanks for your interest on the popupmenu. I'll replay in more detail to your requests shortly.  For now, i'll only clarify that the popupmenu's hierarchy is in the:

void gen_menu  (MenuCacheDir*, GtkWidget*);

calling itself recursivelly. Clone the newest sources of the popupmenu. I pushed all the tags to the remote repository; so, you don't need to create the upstream/0.1.2  as you can see in the following screenshot, more sublevels are allowed under the root level in the directories hierarchy (in this case, the next level is libreoffice):

http://gnuinos.org/2018-01-30--1517320487_1600x900_scrot.png

I'll try to help you developing the GUI for your UMENU. This will not be very difficult, be sure.

Menus are fun, aren't they?

Yes, they are. This thread will be funny :)

Have a nice day,

  Aitor.



_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to