Open Multiple Windows in Server Studio

Open Multiple Windows in Server Studio

  

I'd like to be able to open multiple windows or multiple tabs within Server Studio so I can see two Screen Actions side by side to compare them to each other. Or for whatever reason. I takes so much time to switch between windows and then redrill into the tree structures to get back to something.

It'd be nicer if I could keep multiple windows open at the same time.

Not quite what you are asking but you can actually have two copies of Service Studio running at once. I do this often and have one on monitor 1 and the other on monitor 2.

@PJ M

Can't quite figure what you're trying to do... Either way you can always merge two modules to see what's different.

https://success.outsystems.com/Documentation/10/Developing_an_Application/Merge_the_Work/Compare_and_Merge_Module_Versions

Regards,

João Heleno


@PJ M

If comparing versions of modules is what you want, João Heleno provided the answer.

If you want to have multiple windows of your app in Service Studio side-by-side you can follow these steps:

  • Open you app in service studio as many times as you want to have it in a seperate window, as in this example I haved opened the SafetyApp 3 times:

  • Now click one of the Tabs open and drag it outside the window of service studio. This will automatically open up a new Service Studio window.
  • I repeated this step 2 times resulting in the following windows:

Hopes this answers your question.

Regards,

Daniel

Hi PJ,

This is not possible in Service Studio. As a workaround, you could open the eSpace twice, each in a seperate instance of Service Studio.

Opening two instances of studio does work, however there is a significant downside, because they can get out of sync if a change is made while both are running.

What I'm asking for is useful when there are two server actions or preparations that are very similar. Perhaps one works and the other doesn't. If you open them both up at the same time is two tabs and then tile them vertically, you can quickly see that one might be missing an IF or a condition is incorrect and you can quickly fix it.

This is a very common feature of almost ALL development environments, so coming from something like Visual Studio that makes things like this intuitively simple gives a new user of OutSystems a very claustrophobic feeling being constrained to seeing only one window at a time. 

Imagine another scenario where you want to see the web form and the preparation open at the same time. This is broadly general and very useful behavior.

I actually tried to submit this as an idea rather than a forum topic. Perhaps this should be over there in Ideas.

Yes put it in as an idea and if it gets enough votes or the attention of Outsystems then you will have a better chance of getting it implemented than through a forum post.

I agree that the two copies is just a workaround although the "getting out of sync" issues isn't that bad or hard to deal with. Outsystems will automatically trigger a version check and a compare/merge if you publish from both the environments, also you can get either of them back in sync with the currently published version by doing a "Compare and merge with Published Version"

PJ M wrote:

Opening two instances of studio does work, however there is a significant downside, because they can get out of sync if a change is made while both are running.

Still can't figure out the way you want to develop... In OutSystems you develop in one environment and then you MERGE your code into another target environment (or the same).

Why would you want to replicate the same actions or whatever side by side? You do it once and then merge it...

If you want to see differences MERGE your version with another one! 



João Heleno wrote:

PJ M wrote:

Opening two instances of studio does work, however there is a significant downside, because they can get out of sync if a change is made while both are running.

Still can't figure out the way you want to develop... In OutSystems you develop in one environment and then you MERGE your code into another target environment (or the same).

Why would you want to replicate the same actions or whatever side by side? You do it once and then merge it...

If you want to see differences MERGE your version with another one! 



If I understand it correctly, he wants to compare 2 screens/actions/whatever in same environment.

João, he might have two actions made by diferent people in same environment/module that have the same logic but one works and the other doesn't.


Regards,

Abílio Matos

Abilio Matos wrote:

If I understand it correctly, he wants to compare 2 screens/actions/whatever in same environment.

João, he might have two actions made by diferent people in same environment/module that have the same logic but one works and the other doesn't.


Regards,

Abílio Matos

Sure thing... that's what merge is for. 

Regards,

João Heleno


Seems to be confusion for some reason. The OP is trying to compare two DIFFERENT actions. For example the preparation of Screen A with the preparation of Screen B. Merging will handle two different people working on the SAME action but not two completely different actions no matter how similar they are. 

Aside comparing screen actions, there's many use case for multiple window.

Sometimes, when working on a screen action or preparation logic, I want to see the screen layout side by side.

Agreed with most of the comments, but this discussion is better handled as an Idea, so it can be picked up by OS.

I think I found (and liked) an idea that would give me what I'm after here.

https://www.outsystems.com/ideas/1250/Multiple+tabs+for+Actions%2fScreens%2fetc

Thank you everyone!