I’ve been using wapple for a few days and I have some comments:
the use of an X symbol in some windows, like the file manager, can be very misleading, as normally it would just mean “close the window”, but in this case it erases a file: quite dangerous indeed.
The user interface is in general very pleasant-looking, but absolutely non-standard from a Windows-like practice. This is quite confusing and requires some time to get accustomed to. Why did you not adopt a more standard user interface ?
the use of a dark-only theme for the environment, apart from the text editor, can cause eye fatigue. Is it possible to change from all-black to something else ?
We have tooltips on every button in file manager, which show what the buttton does. Usually, when its a closing button, it's located on top right (as a standard implementation):
As regards in particular the File Manager, where I did accidentally erase a couple of files, I personally do not think that tool tips are enough, as a seasoned user like me would click on symbols instinctively, expecting e.g. an X to mean always “close” and an open folder always to mean “open”. Furthermore I would suggest that the same symbol (X for example) have the very same meaning in every context: no change of meaning.
Why don’t you use, for example, a waste bin icon, regularly, to indicate the action of erasing a file or a folder?
Concerning the interface (UI) I would expect a main menu in top part of the window; remember the Common User Access specs written by IBM and Microsoft at the end of the last century ? They may be a good starting reference, not excluding other menus in other parts of the window. This applies largely also to some Linux UI variants (mint for example).
As regards the dark theme, it is a somewhat minor criticism as I can live with it.
By the way, I have another suggestion: as I use regularly both a visual tool, like Wappler now, but also feel the need of editing the HTML or CSS code, in Visual Studio 2019, could the Wappler text editor be endowed with additional capabilities, like adding comments to lines or line blocks and syntax checking ?
Thanks and best regards and keep improving a very intriguing program.
I think you make some good points. While it’s never occurred to me that the X in File Manager would close a window, I think a waste bin icon would be better.
The icons for creating files and folders in File Manager and Server Actions are different. I expect this difference was made because some users might not be aware that creating a server action involves creating a file (I expect that’s also why the file extensions are not displayed). However, given that you can create folders in which to put these actions, it would probably be better to make it obvious that they are just files and make the icons consistent. As it is, it looks a little odd.
There was a main menu at the top of the window in earlier versions of Wappler. It was little used and took up space unneccessarily; I doubt if anybody misses it. The replacement, which includes the previous menu items, is the panel which appears if you click the vertical dots at the top right of the window. This contains more options and takes little space. I think it’s an improvement although I personally hardly ever use it as shortcut keys can be used instead.
The text editor in Wappler has improved a great deal since earlier versions. Previously I frequently transferred code from Wappler to work on in other editors - now I rarely do this. For adding comments to lines or blocks of code: Ctrl+/ (it toggles comment/uncomment). I think this works as well or better than in other editors. It will comment out html, css and even htaccess files (only single lines in PHP).
Wappler certainly does syntax checking - if anything a little over-enthusastically. As soon as you start typing, sections of bright pink code will appear. Eg, here I’ve just typed a <.
The error will be indicatd in the margin and a list of errors is summarised at the top of the editor. I think this syntax checking is pretty impressive considering that Wappler must be ‘watching’ each key stroke to check the syntax, as well as keeping Design View and App Structure in sync with the code.
I agree with your earlier comment about the non-standard UI from a Windows point of view. However, I wouldn’t have thought this should be a goal, given Wappler’s UI is consistent across Windows, Mac and Linux platforms (as far as I know anyway - I don’t use Linux).
I’m sure the Wappler team will be interested in any suggestions you have. They are very responsive to suggestions and criticisms. I certainly agree there is room for improvement in the UI and have raised a few topics on the matter.
