-
-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[desktop integration] Make the dialog text "nicer" #209
Comments
Well, the point about AppImage is that you do not need to "install" them. You can, optionally, integrate them with the system by the use of .desktop files. However, a .desktop file not only can add it to the menus (in fact, there are some which don't - e.g, xdgurl) but could also install URL handlers or MIME associations etc. |
@probonopd what you say is true, but desktop integration does more than just install a desktop entry file (e.g. it also installs icons) and as you say it could do more besides (e.g. manuals, bash completion, etc). Perhaps the message could be?
Of course, it would be nice to agree on a directory (e.g. |
@shoogle thanks for your text suggestion, which I like. Since we do not control what goes into the AppImage, it is basically up to the upstream application authors what to put into the desktopintegration bash script. Be aware that not each application might do all of the above, especially set up file associations. I disagree on the idea that there should be only certain locations from where AppImages work (or even work better, for that matter). One of the key ideas of AppImages is that they run from any location. |
@probonopd Agree that the wording I suggested probably isn't the best. Although, I do like @shoogle's suggestion. I think it just needs to be more obvious as to what is going to happen when the user clicks "Yes", because saying a desktop file is going to be installed will probably mean nothing to a novice Linux user, they might think that the AppImage will be copied to their desktop. |
How do I do i18n in bash? Switch statement on $LANG? |
This article on localising Bash scripts is an interesting read: You put strings and translations in a separate text file and then use A more concise guide is here: http://stackoverflow.com/a/26273036 Follow the guide exactly, except...
install fr.mo Application.AppDir/share/locale/fr/LC_MESSAGES/PRJ.mo From inside the Application.AppDir directory you can do this:
Or alternatively... LANGUAGE=fr TEXTDOMAIN=PRJ TEXTDOMAINDIR=$PWD/share/locale gettext -s "Hello world" Output:
|
Pull request welcome :-) |
@shoogle want to give it a try? |
@probonopd maybe in a week or two. I have a big project coming to a close very soon. |
electron-builder message changed to #209 (comment), thanks. |
A bit late, but I support that proposal as I'm one of the mentioned "average" persons and had no clue what a desktop file is. Tried - obviously in vain - to assess, whether my yes/no decision made a difference with respect to certain issue I had with the actual *.AppImage ... Almost unrelated: is there a command line option to not have this dialogue pop up? |
@benboggart thanks for the feedback. @shoogle will try to get it translatable, and then we will change it to the new text. The command line command to not have this dialogue pop up: |
this works for all AppImages? cause i was wondering a way to ignore the Desktop integration in AppImages as I will have the AppImageMonitor running by default and tested some of your prebuilt AppImages and the desktop integration would pop up lol and been trying to figure a work around |
Don't know about AppImageMonitor, it should set the environment variable |
maybe i should do more testing with more app images main one that did this was VLC and there was some QT app that did also IDK will play around more with them after I finish compiling packages for my repos |
well just was looking through the monitors code while i had some stuff compiling and i didn't see in any the scripts where it sets environment variable unless it does so in the AppRun. but honestly maybe its just better for me to set that globally in the OS since my OS runs it by default anyway |
It's possible that AppImageMonitor doesn't do it (but should), that's a bug in AppImageMonitor then. |
well til it gets fixed i will just set the environment variable in either the global profile or environment files in /etc |
... no such path on my system. Am I right to assume that this is for building an AppImage without that dialogue? |
But this is something the user should do, not the system. If the system uses a daemon such as AppImageMonitor, then the daemon should export |
It works (with your firefox*.AppImage), thank you! |
Are this desktop integration dialogs still supported/recommended? |
Yes; I think we can close this since we don't support desktop integration scripts inside the AppImage anymore as we have already 3 different optional tools for desktop integration now (which in fact we are trying to unify); and I think the grand scheme of things where we want to go is outlined roughly in AppImageCommunity/appimaged#30 |
To me, the dialog text for desktop integration text that is used could be made simpler
Could this be made a little nicer like this?
or:
I'm just thinking that the average person might not know what a desktop file is, and showing the full path to the AppImage could look messy.
Any thoughts?
The text was updated successfully, but these errors were encountered: