search

nicktelindert / nextspace-build-iso

GNU General Public License v3.0
8 stars 7 forks source link

Add base applications #3

Closed nicktelindert closed 4 years ago

nicktelindert commented 4 years ago
trunkmaster commented 4 years ago

Transmission, MPV, Emacs, Dia, GIMP, VirtualBox. I've attached my app wrappers. AppWrappers.zip

BertrandDekoninck commented 4 years ago

GNUstep apps : ProjectCenter, Gorm, Gemas, PikoPixel, BattMon. I don't if it is easy because those should be build using Nextspace versions of base and gui. The CentOS rpm packages of gnustep apps will conflict.

nicktelindert commented 4 years ago

I now use your packages of gnustep so it should work fine, but i probably should compile it when building the ISO. But that counts for every gnustep app i add. The appwrappers could be a problem, because appwrappers i am working on automatically generating appwrappers after installing apps. That generation process will now update the whole applications directory with new Xappwrappers so it will destroy old wrappers. I will have to add a feature to ignore the system apps so prevent them wrong getting updated.

trunkmaster commented 4 years ago

@nicktelindert, I'm afraid it's not possible to create perfect appwrapers for non-GNUstep applications automatically. The perferct appwrapper for NEXTSPACE should contain executable name that consists of WM class and WM name separated by period (emacs.Emacs). You can check it with xprop utility and check for WM_CLASS value. For example for Emacs xprop's output for WM_CLASS is "emacs", "Emacs". So app executable must be named as emacs.Emacs.

If executable name is not correct you should observe appicon in launching state after application quit.

nicktelindert commented 4 years ago

@nicktelindert, I'm afraid it's not possible to create perfect appwrapers for non-GNUstep applications automatically. The perferct appwrapper for NEXTSPACE should contain executable name that consists of WM class and WM name separated by period (emacs.Emacs). You can check it with xprop utility and check for WM_CLASS value. For example for Emacs xprop's output for WM_CLASS is "emacs", "Emacs". So app executable must be named as emacs.Emacs.

If executable name is not correct you should observe appicon in launching state after application quit.

Perfect wrappers is indeed impossible. Basic wrappers work fine for me though for only launching stuff. But i will use mainly the precreated wrappers and keep my script installed for creating a basic wrapper if someone needs it.