I'll have to update the mmenu 'manual' on the wiki ne of these days, since so much has gone in since system release.
Regarding the custom category stuff I'm still working out the details and coding (hopefully more time tnight to wrap it up, should have a beta update tomorrow sometime), but its more or less like ..
I've rather figured out that what I have meant for 'strict freedesktop enforcement' is that pnds should follow the spec; so the last couple builds have been doing enforcement at the end of the pipe (after ovr processing has modified everything), what we really want is the standards enforcement ont he _pnd_ (to ensure lazy devs defaults are sensible or shitcanned), but leave ovr's alone and _Assume_ users know what they're doing when they create overrides. (Which may not be the case .. but we can't protect everyone from everything; if someone creates a total mess with ovr's, thats really their problem and is easily cleaned up.. remove the ovr files
So, the code is being updated so when an ovr says something, mmenu trusts it implicitly (warts and all, try not to hang yourself); ie: trust the ovr, but dont' trust the pnds, since apparently half or most devs made bad categories in their app packaging
This actually separates two concepts that were rubbing up against each other with great friction; app tabs, and category creation. So now the app tabs are pulled from ovr, or if not present, from the pnd (and if the pnd's categories are bad relative to Standards, we toss the app into Other.) And mmenu has an category / subcategory override menu now so you can assign apps as you see fit to Standard categories. (Thus, to currently assign to custom category, you'd have to manually edit the ovr-file)
So tonight I'll code up some basic UI for creating custom categories (create them, delete them, list them, etc); note that this is just a UI for maintaining the tab-list that mmenu will show you when you want to assign an app to a tab. ie: When you try to re-assin the categoryof an app in the UI (and mmenu creates the ovr file for you), then you can pick from a list.. that list will be Standards + Customs, and tis new UI I'm coding will let you edit th Customs list.
Thus,
1) mmenu will trust ovr's; if you've hand rolled some already, they'll "just work" in the next mmenu beta build (like they used to, but also with support for subcat-folders new feature!)
2) You'll be able to edit the list of categoris mmenu lets you assign an app to.
This shoudl let you be flexible power users, but also coudl let you hang yourself. Such is life
Anyway, more detail later..
Who has time to write it up here, got code to do
jeff
EDIT:
I wonder, perhaps (to avoid letting people hang themselves), I should require custom categories to not share the name of a Standard category. ie: "Game" is a standard top level category; if you go and create a custom category "Game" thats a child of something, it just makes things get weird, for instance. I can see a case them for custom cats to be called something else .. if you really wanted a "Game" tab, thn you coudl create "Games" perhaps, or "Game_" or something, perhaps. That'd make a lot othings simpler.(Or just create it by hand by hand editing an ovr.) ie: Its ugly when you create a custom category that is the wrong ancestry.. create Game as a child, or Emulator as a parent, for instance.
