[01:34] <OvenWerks> Eickmeyer: http://i.imgur.com/fpxGVwV.png
[01:35] <Eickmeyer> OvenWerks: So, is the filename absolute path?
[01:36] <OvenWerks> The filename is only text, no path, no extension. The .desktop will get added and the file placed in ~/.local/share/applications/
[01:36] <OvenWerks> That will over ride anything
[01:38] <Eickmeyer> Okay, that makes sense. So, should it say filename, or application name? I'm just trying to think from a user perspective.
[01:39] <Eickmeyer> People aren't going to necessarily understand the term "Desktop File" especially if they are coming from Mac or Windows.
[01:39] <OvenWerks> if there are no spaces application name is ok... but really if the user wants to override a system file it has to have the same name.
[01:41] <OvenWerks> Also, people are used to not being able to use any odd character in a file name
[01:42] <Eickmeyer> Fair enough.
[01:43] <OvenWerks> I actually put the file detection in with the wrong button (edit) when it should be (save)
[01:45] <OvenWerks> my idea is to create a temp file with a copy of the original file (if it exists) or a template (if it doesn't) and use that to call exo-desktop-item-edit
[01:46] <OvenWerks> Then when that exits and save is pressed, The temp file is copied on top of the original or created.
[01:47] <Eickmeyer> Yeah, that's a great idea. Keeps it non-destructive until finalized.
[01:47] <OvenWerks> Hmm, I guess I need a "remove" button. not sure what to call it, that removes the file from ~/.local/share/applications/ and lets the system file work.
[01:48] <OvenWerks> Anyway, I want to get it working first... right now the about button works :)
[02:40] <Eickmeyer> Well, that's a start. :)
[02:40] <OvenWerks> When it can at least make a file I will upload it
[02:41] <Eickmeyer> Cool.
[02:42] <Eickmeyer> I just got done removing the standalone jack clients from the lsp-plugins. They required a shared object in /usr/lib and that's a huge no-no. vorlon wasn't letting it into the archive based on that alone.
[05:09] <OvenWerks> Well, I actually get a new item in my menu... will upload tomorrow.
[05:10] <OvenWerks> so far it always starts from scratch. It does not look to see if it already exists and then read in the old one as a template for the new.
[05:13] <OvenWerks> Right now, I do a straight cp temp file to new file, I will be doing a line by line save in the future though to look for no show lines and catagories lines to replace them according to user choices.
[05:17] <OvenWerks> The show check box is already there (but not yet used). I want to add a dropdown that has all sub menus listed and a second dropdown with any sub sub menus
[05:20] <OvenWerks> Coming up with a catarories line that is unique for each is the goal... we may need to change -menu for best results.
[05:23] <OvenWerks> I would like to have a window similar to the icon selection window that shows all the desktop files with icon/menu text so that the user can select one of those as the template.
[05:26] <Eickmeyer[m]> Sweet! Sounds like a big job though.
[15:25] <OvenWerks> Well that was silly... I uploaded before commit... so no executable  :P
[15:56] <OvenWerks> Eickmeyer: how do we change: https://code.launchpad.net/~ubuntustudio-dev/+git/ubuntustudio-menu-add into a project? (lp:ubuntustudio-menu-add)
[16:01] <Eickmeyer[m]> OvenWerks: I will do that in a bit. FYI, I will be out of town and low on communication the next couple of days, but I'll be doing what I can.
[16:01] <OvenWerks> no problem, nothing I am doing is urgent
[16:21] <Eickmeyer> OvenWerks: Done.
[16:22] <Eickmeyer> https://code.launchpad.net/ubuntustudio-menu-add/+git
[16:24] <OvenWerks> Thank you
[16:28] <Eickmeyer> You're quite welcome.
[16:28] <Eickmeyer> You'll have to re-clone that to make sure you have the right upstream.
[16:28] <OvenWerks> Ya, I know.
[16:29] <Eickmeyer> :)
[16:59] <OvenWerks> Eickmeyer: I don't know if you will have time to look at menu-add (not sure if that is a good name or not)
[16:59] <OvenWerks> when you do... there is a point I am not sure how to deal with
[16:59] <Eickmeyer> Nah, my Studio machine is packed in a bag right now. Probably later.
[17:00]  * Eickmeyer is waiting for his ride for a 3 hour drive
[17:00] <Eickmeyer> I try to keep my 2-in-1's installation simple.
[17:00] <Eickmeyer> With only 2GB of RAM, it has to be.
[17:01] <OvenWerks> when you hit save on the editor it just saves to the temp file. then the menu item has to be saved in the main window to be seen
[17:01] <OvenWerks> I was thinking of adding a dialog, but people who use the app a lot might get anoyed with that
[17:02] <Eickmeyer> Yeah. MIght cause dialog fatigue.
[17:02] <OvenWerks> Maybe I should change the "Save" button in the main window to "Install"
[17:02] <Eickmeyer> Yeah, but that comes with a bunch of different connotations.
[17:03] <OvenWerks> "activate"
[17:03] <OvenWerks> ??
[17:05] <OvenWerks> Actually, that may be the best way to go. I could then have a "Deactiveate" to remove something from the users local directory.
[17:06] <Eickmeyer> Not bad.
[17:06] <Eickmeyer> "Apply"?
[17:07] <Eickmeyer> OvenWerks: ^
[17:09] <OvenWerks> Eickmeyer: I think I will add another check button that says "active"
[17:10] <Eickmeyer> That might work.
[17:10] <OvenWerks> Apply also has the wrong idea for me.
[17:10] <Eickmeyer> ok
[17:11] <OvenWerks> I want to have a file selector that lists users made menu items (anything in ~/.local/share/appliacations)
[17:12] <OvenWerks> That way the user can choose from those to edit or deactivate
[17:13] <OvenWerks> The question is, should a deacivated item still be saved? I guess so, deactivate would rename from base.desktop to base.saved
[17:13] <Eickmeyer> I think so.
[17:16] <OvenWerks> exo-desktop-item-edit requires something that is called base.desktop I think, so I still have to start with a temporary file.... I will try with an odd named file.
[17:23] <Eickmeyer> So, touch base.desktop?
[17:36] <OvenWerks> I actually put some things in there to begin
[17:37] <OvenWerks> exo-desktop-item-edit requires -c to create but I want to be able to edit already active files and I want to be able to add catagories and don't show and...
[17:39] <OvenWerks> so I create a base.desktop in .config that I send exo-desktop-item-edit to. Then copy to final on save... but that will change.
[17:40] <OvenWerks> I had the save button so that the person could change the catagories and shown after editing and then save it.... I will set it up so that any change save anyway.
[17:42] <OvenWerks> I will need to check the file to make sure it has a name and exec (or url).
[17:42] <OvenWerks> trying to make it active without will give an error dialog
[18:08] <Eickmeyer> Well, early stages, I guess.
[21:15] <OvenWerks> Eickmeyer: in menu_add... should there be a checkbox to add the desktop file to the desktop? I just thought of this one... I was going to just add the word desktop to the menu folder choices, but really even a desktop icon should have reasonable catagories and also show up in the menu.... execpt, I have also added the possibility to create a link as well as an application and maybe a link 
[21:15] <OvenWerks> really belongs only on the desktop. Should I even allow Links at this stage?
[21:16] <OvenWerks> Hmm that may be too long a message, it may be missing the last part of the top line.
[21:16] <OvenWerks> I understand you are on the road so I am not expecting a quick reply.
[21:42] <OvenWerks> Eickmeyer: Answered my own question, the user can create urls on their desktop by just dragging them from the browser... and the application is a menu item creater.
[23:08] <Eickmeyer[m]> Yeah. Last I checked that works in pretty much all desktops.
[23:08]  * Eickmeyer[m] is in Pasco