Page 1 of 1

Feature request. Actually a UI web page request

Posted: 03 Dec 2017, 05:44
by budman1758
Hello all.
Something that I think would be handy is to put the command input box at the top of the Tools page instead of the bottom. I find it quite a hassle when prototyping something to constanly have to scroll down to the bottom of the page to get back to the command box. It would also be nice if the cursor focus would be in the box when the page loads like most browsers focus on the search box. (something that actually annoys me most of the time). Just a minor thing.

What do all of you think? :?: :?:

Or.... Perhaps it could have its own page?

Re: Feature request. Actually a UI web page request

Posted: 03 Dec 2017, 10:06
by TD-er
I think the entire web-interface would benefit from a good redesign.

Would it be good enough if you had a single link to open that command page?
Not to clutter the top bar too much, but just to allow quick access to certain sub pages.

I always like the "basic"/"advanced" approach. Not to overwhelm the new users, but allow advanced features for the more advanced users.

Re: Feature request. Actually a UI web page request

Posted: 03 Dec 2017, 11:11
by grovkillen
You can always trigger it with this URL:

Code: Select all

http://<espeasyip>/tools?cmd=<command>
<espeasyip> is the IP
<command> is the command you want to execute

Re: Feature request. Actually a UI web page request

Posted: 04 Dec 2017, 01:23
by danmero
Maybe a plugin to disable/enable the WebUI from MQTT inport.

Regards,

Re: Feature request. Actually a UI web page request

Posted: 04 Dec 2017, 09:31
by budman1758
TD-er wrote: 03 Dec 2017, 10:06 I think the entire web-interface would benefit from a good redesign.

Would it be good enough if you had a single link to open that command page?
Not to clutter the top bar too much, but just to allow quick access to certain sub pages.

I always like the "basic"/"advanced" approach. Not to overwhelm the new users, but allow advanced features for the more advanced users.
The single link idea sound pretty good. As for the entire web interface redesign methinks not a bad idea but probably a bit much to ask. :shock:
Any web design gurus wanna take a swing at it? :mrgreen:
grovkillen wrote: 03 Dec 2017, 11:11 You can always trigger it with this URL:

Code: Select all

http://<espeasyip>/tools?cmd=<command>
<espeasyip> is the IP
<command> is the command you want to execute
This is quite true but adds to the amount of keystrokes necessary......
I was thinking to move the command box to the top vs the bottom would be the easiest to implement.

Re: Feature request. Actually a UI web page request

Posted: 04 Dec 2017, 11:05
by TD-er
budman1758 wrote: 04 Dec 2017, 09:31 [...]
grovkillen wrote: 03 Dec 2017, 11:11 You can always trigger it with this URL:

Code: Select all

http://<espeasyip>/tools?cmd=<command>
<espeasyip> is the IP
<command> is the command you want to execute
This is quite true but adds to the amount of keystrokes necessary......
I was thinking to move the command box to the top vs the bottom would be the easiest to implement.
You can also run GET requests from the commandline (e.g. using curl), which makes it perhaps easier to test?
Or external tools like Postman, which has several somewhat bookmark like queries you can store and adapt.

Re: Feature request. Actually a UI web page request

Posted: 04 Dec 2017, 14:14
by AndrewJ
+1 for moving the command to the top of the page. For me, it would make it easier to use. :D
AndrewJ

Re: Feature request. Actually a UI web page request

Posted: 10 Dec 2017, 00:21
by grovkillen
I made a PR for it just now. We'll see if it is accepted. :P

Re: Feature request. Actually a UI web page request

Posted: 10 Dec 2017, 22:42
by AndrewJ
Many thanks.

Re: Feature request. Actually a UI web page request

Posted: 19 Dec 2017, 10:43
by grovkillen
AndrewJ wrote: 10 Dec 2017, 22:42Many thanks.
PR is now merged and will appear in the dev13 release. If you cannot wait you can compile a version on your own.