• Sign In
  1. Messages

Timing of new UI Changes?

LabKey Support Forum

View Message

view list print
Timing of new UI Changes? Ben Bimber  2017-09-12 14:40
Status: Closed
 
Hi guys - we're just started looking over the new UI and generally it looks great. However, we're going to have some custom code that we will need to adapt when you flip the switch and the new UI becomes default. Do you have a recommendation on when clients should be doing this? For example, while we're toying w/ the new UI on dev machines, our 17.2 production servers will be using the old UI.

If there is a situation where we need different behaviors on old- vs. new-UI, is there a recommended flag or anything that client-side code should use to figure out which UI is being used?

Thanks,
Ben
 
 
jeckels responded:  2017-09-12 15:04
Hi Ben,

17.3 will only support the new UI/UX. The trunk currently supports both, though new development is really only being tested with the new look. We're hoping to wrap up converting automated tests by the end of this month, and then we'll start ripping out the conditional code to support the old UI.

Server-side, you can call PageFlowUtil.useExperimentalCoreUI() to see which mode the server is running in.

Client side, you can check the LABKEY.experimental.useExperimentalCoreUI property.

Since there are continuing edits to the new UI happening now, it's fine to start playing with it for your code in 17.2, but you'll really have to wait for 17.3 to be able to finalize any changes.

Thanks,
Josh