1 Like
Yes.
Not being able to see expression due to the stupid bubble UI is already a huge pain.
An extra click at so many places.
Replacing with a title/description means two more inputs to mantain apart from the name of the step, and not to forget, not knowing what the bindings are without one or more extra clicks.
I assume, as a developer, I might adapt and relearn building workflows in the new flow layout, but in the current version, its looks very unproductive. Numerous suggestions above might make it better, hoping.
2 Likes
Good points.
Was also thinking to offer library items and other templates directly from the actions panel to drag from.
1 Like
+1 on keeping the old tree view in place (please!!)
And would love to see improvement in the current tree view instead of a SC Flow Designer, but this is a subject for another topic 
I don’t like flow designers, I can understand better my logic with code / tree view.
Congrats for the SC Flow Designer, but I would like to see more features for professionals devs and lots of very interesting feature request being developed.
3 Likes
Just to confirm, we will be keeping the old tree as well.
Just like with our visual html designer we have Design and Code View, we will have in the Server Connect Editor also a Flow (Design) and Tree (code) views. As indeed the old tree views is much more code oriented view and can give more insights to code oriented people. While the new Flow view will be a welcome addition to new users as well more visually oriented people.
13 Likes
I’m very relieved to know the tree view will be kept as well! 
4 Likes
And there will still be an option to actually see the code view of the server action files?
1 Like
Of course
1 Like
Hey there @george… thank you for really engaging with us on all the hot and sometimes emotional topics in the last few days!
I know I’ve been against the idea of using the Flow Designer, but I still want to be a part of putting forward ideas to make it helpful for power users as well as beginners!
Here are some thoughts…
Best wishes,
Antony.
On a per step basis…
-
Add a “Lightning bolt” icon on each step…. Clicking on it opens the normal window as a pop up… as wide as possible to accommodate complexity.
-
As I think you plan to do, allow a description area for each action step, and have an icon on the action step which you can click on to toggle its visibility. Give us an option not to have it visible by default.
-
Remove the text which is the Function of an action step (Set Value, Condition etc) and instead use the larger bolder font to show the details of what it does… as the icon is enough to show what the action step’s function is. Or if you feel it needs to be kept, give us an option to turn if off globally.
-
Remove the EXEC boxes, as I cannot see what they add… surely you will always execute what is inside an if or a repeat?
-
Add a “Container” to house sections of code, which serves as nothing more than a collapse for visual purposes.
-
Allow an include to be moved around (I can’t seem to move them in beta4).
In the overall interface…
-
Add a “Compress” function which puts the action steps closer together to enable more to be seen on the screen.
-
It would be great if nested areas had subtly different background colours so you can see visually which nested area you are in more easily, rather than just with a collection of vertical dotted lines… or if the dotted lines had different colours for different types of nesting such as a repeat or a condition.
-
At the end of a nested area, include some text to show what is being ended, like you would put in code
end repeat; //attendees.data -
I’d love it if you could make a couple of proposals for the two points above which are just images for us to see how it would look before you implement one of them…
Additional Features That Would Really Help…
-
Ability to turn a “Container” as listed above into a Library Item
-
Click on a Library Item and it opens in another window
A few more updates in Beta 6:
Wappler 6.0.0 Beta 6
Server Connect Editor
- Updated styling in the Flow view to be more compact
- Add new Alt+drag (left option on Mac) handler to be able to drag the whole canvas in Flow views
- Load actions now more in collapsed view so you can expand what you need
- Fixed selecting on actions on click
1 Like
Someone has probably already asked for it. but can the actions panel not also be available for the tree view and not only the Flow view? Would love to drag and drop using the tree view and not have to use the right click and + click but just drag 'em and drop 'em.
Or are these mutually exclusive?
Genius Mode - > Tree view vs. Dummy Mode - > Flow View 
2 Likes
Yes, someone already suggested that and we will make it available for the tree view as well.
2 Likes
For the tree view could the actions panel (if it’s going to be implemented) go on the right side instead of left? Unless someone disagrees in which case it’d be better to be selectable or hideable I guess
Wouldn’t right side be too far from the tree with the steps? Imagine working on a 27+ inch monitor and you have to drag it all way from the other side of the screen
Hm… For me personally the concern is I’m used to “real” programming, so the code is at the leftmost position on a code editor. Alternatively, would it be possible to toggle show/hide?
Maybe wait for other’s opinion
2 Likes
Maybe a toggle is the best solution here indeed.
1 Like
What about moving to a setup like Eclipse that allows you to place the windows in the panels of your choosing.
This video shows moving the windows between panels.
Multi-monitor Wappler support with separate windows is indeed the actual best solution that has been discussed many times in the community.
@Teodor Toggle would be the better solution for now.
Although, I would suggest to rather work on properties panel UI improvements so that it scales well with the dynamic width - and would apply to both existing tree view and the new flow view.
2 Likes