On Tue, Apr 7, 2009 at 6:03 PM, Ismael Carnales
And make XMonad more begginer friendly
If Newcomers like it
You got another user
With another point of view to contribute to the project
And get more name, jobs, etc :)
And some ranters :)
Anyway here goes some ideas that i spitted out in the xmonad channel, suggest, criticism help and such welcome
* Layout constructors:
Layouts could export alongside their constructors, a constructor function that calls the latter with some default arguments, this allows to aliase more common used layouts and become friendlier with newcomers. Also is good that users don't invoke the "official layout constructor" from their configs so mantainers can change the arguments it takes without breaking compatibility.
Other modules could use the same approach, for ex:
defaultShellPrompt = shellPrompt defaultXPConfig
simpleDefaultConfig
A module that provides an structure to configure XMonad by editing some hooks, instead of hoving to build them, usefull to make some non-default configs default in this module, like modkey, borders, avoidstrust, more friendlier managehook, with hooks for floats, moveTo, etc.
Other configs can be based on simpleDefaultConfig providing some pre-feeded values on some hooks, usefull for statusbars i.e.: dzenStatusSimpleDefaultConfig, xmobarStatusSimpleDefaultConfig.
Or better, simpleDefaultConfig could inherit some defaults from another Config like dzenStatusConfig, so you would pick the parts that suits you.
This approach will give easier entry point to configs for newbies without loosing power, all normal config items would have to be available, these funcions will only provide helpers and shortcuts.
A GridSelect oriented program launcher:
Inspired by "intelligent launchers" we could make an app launcher that shows its options arranged like a keyboard, inteligently ordered, so most used apps will be in the home row an continuing outside.
So something like ShellPrompt using the GridSelect UI? Sounds like a good idea. Does anyone want to do it? -- gwern