makarel wrote:you could just do a shell script o install all required and apply configs..
seems you preffer bloated/resource hungry interfaces.. 2 bad.. on this side of he screen im thinking of dropping luci...
It doesn't have to be default bload.
But it would be nice to have the option to by installing a package that adds this.
For me it is also bload if i need to manually open a console, browse to whatever file, open it in a text editor and do all stuff that could be avoided. Specially for new users this could build a bridge back to the console...
Today most people can't even imagine a CLI... So letting them view the naked config file in all its glory might get them a little exited and curious what all the 'CLI-porn' is about.
I think it's better to have hint's already in the system instead of scaring them away with CLI talk on the first day they show a little interest. CLI is not that hard, but it is a learning curve. And for me that learning curve would have been less steep if some stuff would have been introduced to me in the GUI .
So why use CLI for stuff that makes more sense in a GUI?
Now when people see the contents of a config file and how their GUI settings change it, then they might ask.. Hey, how do I edit this file...
Answer: Connect with SSH and type nano <filename>
And since they then already know about the changes in the config they will have less questions about that...
See it as intergated education
Noobedu.ipk
But yeah, bload is evil.