> Rather than this new config option, I would be much happier seeing the > shell plugin directly indicating whether it supports input methods or > not.
I'm not too sure about this, but I think the text backend has to be initialized first so I don't know how it can be launched or configured from the shell plugin. > If you add a config option like this, then the user must somehow know, > that when using this particular plugin, he should set this other config > option too. That seems cumbersome, because the plugin itself certainly > knows if it supports an input method or not. Why should the user be > second-guessing the plugin? The way I stopped the user having to specify the config option was by shipping a "my-cool-plugin.ini" file which had all the neccessary options(shell .so file, disabling features that dont work and extra plugin-specific config options). Then the user can just type 'weston --config=my-cool-plugin.ini' and everything is taken care of. > If you really need a config option, how about setting [input-method] > "path" explicitly to empty to disable loading the input method client? I'm not sure if you mean change it so that it doesent try to launch the input method if path is empty, but currently it will try and fail even if the path is empty. > Rather than this new config option, I would be much happier seeing the > shell plugin directly indicating whether it supports input methods or > not. I completely agree, but I have no idea how this can be done. Thank you. Murray
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
