vasm-legacy missing configurators

[roarde]

I'm just not up to fixing what doesn't work. But some things I removed previously work "well enough" and could be returned to the menus, if wanted.

Only thing I'm thinking of right now is "vkmapset" for keyboard selection, since it was recently mentioned on the forum.

Discuss what might be wanted. Please test it first by calling it directly. If you have a ready-made fix for something that's badly needed but presently broken, point to the fix.

Obviously mine to do, but I'm not self-assigning just yet so maybe more people will be moved to offer their entries.

[roarde]

Also, what about removing xdialog from the ISO? Vasm-legacy is the only thing that uses it. It seems that would allow removal of gtk+ from the ISO (it's still a build dependency for a few things).

With xdialog removed, vasm-legacy would open an xterm automatically and start with an ncurses interface, if it wasn't initially started from a terminal. I think most people involved with development prefer that, but no idea what the user opinion in general would be.

[Moises Henriquez]

I agree with vkmapset and maybe in the same area, localization settings that were there.

I would not want xdialog removed. I like the gtk+ (outdated as it may look) UI to vasm when available. I'm just not a fan of xterm + dialog on a full GUI desktop.

[roarde]

Localization settings. You're talking about vlocaleset and its never-ending list of death. Not the only reason localization was removed from the menus, but is the leading one.

So everyone try vlocaleset manually again for a while and let me know whether you want it out or in.

[roarde]

Self-assigned this. Still would like some feedback on vlocaleset inclusion.

[roarde]

Restored vlocaleset and vkmapset to root's menu. Issued pull request #38 to grab the change.

[roarde]

Last chance. I'll be closing this issue soon and will be on to something else. Permanently.

[roarde]

Vkmapset and vlocaleset returned to root's menu. No other changes were requested.