Well double click any server action and the preview tab opens. Selecting any another server action loads its contents there.
No blue dot for me ......
I'm totally lost. 
If double clicking on it opens a preview, how do I open the SC to work on it?
Ahhh lol now I understand the problem with the single click and double click 
Single click -> Open SC as if Wappler 3 was still a thing 
Double click -> Open SC in preview tab
Either you implement triple click(You better not!) or free Single Click from the burden of ancient UI.
So we can single click to open in tab preview and double click to change the preview tab into a fixed tab.
Told ya you were heading into a UX nightmareā¦
I actually like the ability to single click -> preview, or double click -> open in tab. Would be useful when split tabs are implemented.
A short gif displaying how to preview the server actions and how to edit any of them:
Iām still confused.
What does the italicized filename mean in the tab?
So you can only have one Server connect tab open?
Where is the indicator if the SC is saved or not?
Italic means that the tabs is a preview tab
So how do I get it out of preview so I can work on it? This has just gotten a lot more confusing than it needs to be?
Whats the purpose of the preview?
The file opened in the preview tab can be directly editedā¦
I think the split tabs is going to make this a polished solution. At the moment I canāt have a front-end page and a server script side by side which is crucial.
- But there is no indicator that the file is not saved?
- Can only have one SC open at a time defeating the whole purpose of tabs?
Just let's not be masochistic.
Better this way.
With the preview, this can be removed altogether.
1 Like
Just curious - in what cases do you need to work on the front end pages and back end (server actions) simultaneously?
Most of the time. Iāll work on the front-end page, need an API script to interact with it, create that on the left with my page open and just update either as needed or just have a good reference of variables, processes, etc. as I build the page.
Thatās why Iām missing the wider left column we had in v3 but hoping the split tabs will address that.
1 Like
In my case I usually don't but It can be convenient in large monitors to be able to quickly move from one to another on the same level(this is without an extra click on a tab)
But when working with global, library, API and scheduled actions side-by-side via splited tabs is a must.
After all the heat you guys gave me 
I'd now be in favour of the Tab method. But it certainly needs to be better implemented. Right now the tabs method is still a hot mess. I hope it is still at the very early alpha stage.
2 Likes
I agree, it looks strange and funny from the outside 
But Iāll explain. Iām not a fanatic. And neither is the person who wants to be always right. I always try to be open to new knowledge and rational suggestions. But that doesnāt mean I agree with everything. If something seems wrong to me, I will enter into a discussion. And I think a good argument is great. It is in the clash of different points of view that optimal solutions are born. When we discussed the beta 6 functionality, our points of view were supported by reasonable arguments and each had its own truth. In Beta 7, we got a new solution that brought us together, because we got something that meets our needs. In this regard, I see no reason not to support logical decisions on your part. And this does not contradict my motives, because I got everything I needed in beta 7.
1 Like
LOL yeah. It was just a simple comment on my side. I didnāt take anything personally. Healthy discussions are more than welcome because that makes people think harder for better and broader solutions.
1 Like