Convert "config" to a proper server-side command

[jbrinkman]

The current "config" command is implemented in JavaScript and does not work as documented. This command should be implemented as a server side command.

[david-poindexter]

Just out of curiosity, what specifically is not working for you @jbrinkman ? I have yet to experience any issues with this command.

[dnndev]

@nvisionative config is a carry-over from when Prompt was a skin object. It's intent is provide configuration options for the prompt console (themes, width, height, etc)... As a Skin object, Prompt used to pop-up from the bottom of the browser, so you could set its height using any CSS-valid height value. After moving to the Persona Bar, however, height has become irrelevant and the config command is currently a vestige.

[dnndev]

@jbrinkman Prompt should have a client-side configuration command - one that governs the personalization of the console (colors, fonts, and maybe scripts, etc.) and is stored in cookies or similar. We don't have to call it config of course. I suppose that we could also store this information on the server.

[jbrinkman]

surely you are not suggesting we put a UI on the CLI ;) I agree we should have settings, but it seems that in the spirit of the commandline those settings should be configurable using commands.

We can still do all the client side execution of script and cookie manipulation to do the actual setting, but the command itself would be a server-side bit of code.

[dnndev]

Don't call me Shirley ;)

No. I'm not suggesting that. However, everyone likes to make the shell their own - just like with editors... So providing themes (colors and font choice) is a good call. People might want to use a different monospace font, for instance (I like H&Co's Operator Monotype font myself). They may also want to adjust background, foreground colors to suit color blind users or just to reduce eyestrain and improve their readability.

When you say it should be configurable using commands, I think we're saying the same thing. That is what the config command was intended for originally. Whether it gets executed on the client or server is immaterial I think -- only that it executes where it is most efficient.

In my mind, since it doesn't affect the server and only impacts the client, it should be a client-side command. If there's a reason for it being on the server, let me know. I'm not aware of such a need yet -- unless you want to store those settings on the server for each user for later retrieval. In that case, I'm in total agreement.

[jbrinkman]

Well, I don't believe that my settings should be lost because I changed machines or browsers so storing my settings in cookies seems fragile. I think we can leverage the personalization API on the server side so that every admin has Prompt configured to their own liking. Also a great way to introduce people to a 10 year old API that no one uses ;)

[dnndev]

Sounds perfectly reasonable :) Let's do it.

[dnndev]

If you want to tackle it, just assign it to yourself :)