(FIXED) BOARD 10.3 Adaptive Web Page Sizing - How is this Optimised?
I am having some trouble optimising the Web Page sizing options. Prior to BOARD 10.3,
- All of my models are manually optimised to resolve fully on a common laptop 1366x768.
- All screens and masks are locked using 'Lock Size'
My interpretation of the release notes was that the screen would dynamically fit a web browser screen dependant on USER selection during their session and that I would not need to use SCREEN LOCK any more when developing screens and masks. My experience has been that this feature leaves a very large amount of screen blank and unusable whilst the image is rendered too small to be workable. Furthermore, screen settings do not remain from screen to screen, requiring user to constantly set them for each screen and for each session.
After upgrading to BOARD 10.3, I removed all screen locks, in the hope of having dynamic screen sizing, as stated in the release notes. Whilst there is an effect when selecting the 3 options, it is not the behaviour that I had expected.
I appreciate that I may have interpreted the release notes wrongly and so, if anyone can help in advising how to use this really needed feature, I'd be very grateful.
Below are the effects of the three options on a LAPTOP screen of 1366x768.
SETUP
- All screens and masks were created within the LAPTOP pixel range and the first ACTUAL SIZE image demonstrates a perfect match of web page and BOARD model sizing.
- Screen Lock was taken off all screens and masks.
- The browser used was CHROME with Zoom was set at 100% and bookmarks bar active.
- All screen shots have been pixellated to obscure the data being shown.
EXPECTED BEHAVIOUR
As all screens were optimised for Laptop use with a browser, the expected behaviour I was hoping to see in all settings was that the screen would remain exactly the same as for the image in ACTUAL SIZE.
Screen setting is held from session to session.
BOARD 10.3 OUTCOMES
1. ACTUAL SIZE
The first option is ACTUAL SIZE and, as expected, the model fits the complete browser page. If I make the browser screen smaller, scroll bars will immediately appear.
2. FIT TO PAGE
The next option - FIT TO PAGE - reduces the image to almost a quarter of its size and leaves a massive section of screen below and to the right blank and unusable.
3. FIT WIDTH
The last option - FIT WIDTH - expands the image a little but still leaves the massive white area and so the image is, again too small and not optimised for width. There is a very large amount of screen below and to the right of the image that is blank and unusable.
Answers
-
Hi,
do you have a mask on the screen? Does it also occur after disabling the mask
regards
Björn
0 -
Hi Bjorn,
Thanks for the suggestion. I've removed the mask and there is no screen lock on. The outcomes for all three settings are the same. Unless I use the Actual Size setting, I cannot get a workable screen. I would have expected 'Fit to page' to make no difference but it actually shrinks the screen to a totally unworkable size, as can be seen below with web screen zoom at 100%
Image: Chrome settings with screen zoom set to 100%
Image: BOARD 10.3 WEB screen without mask and Optimisation set to Fit to page - yellow area is amount of usable screen lost.
. 0 -
Hi,
never seen something like this. Maybe the best approach would be to contact your local support and create a TK
Regards
Björn
1 -
Thanks for your help Bjorn. I will now raise it with the support desk.
Can I take it from your reply that the screen sizing feature is working as expected for you?
For completeness, I created a brand new capsule with a different database
- One screen only.
- No masks
- No screen setup in any way
Same outcome when selecting 'Fit to page':
Image: Yellow area indicates the amount of screen lost when selecting 'Fit to page'
1 -
0
-
No, not yet but it is summer and I only asked eight days ago, and they're only questions, not issues, and... there was the Perseid Meteor Shower the previous night, visible from Greece!
2 -
0
-
I am experiencing similar behaviour with all of my screens. Lock size turned of for screen and mask. The screens fit perfectly on my laptop screen or monitor in chrome and "fit size" just makes it smaller which is unnecessary. They do not end up as small as Paul Wyatt screens, but still a lot smaller than they have to be. They also end up too small for users where the screen originally was too big. They can see the whole screen now but there is a lot of unused space around it. The setting also gets disabled all the time, which means I have to keep pressing the button. I have tried a few things like taking of the mask and playing around with the screen size, nothing seems to change the behaviour. I was quite looking forward to this feature and I must say I am bit disappointed with the current status. I am sure it will be improved in the future but it was supposed to be one of the main improvements of this version.
1 -
We are experiencing the same issue. We are developing screens, which look fine when saved by the Admin user, however when a different user opens the screen it is unusable as the screen is not displaying all the field headings / data...the sizing has all changed.
We have reached out to our external developers with no response as yet...1 week.
0 -
Wir haben auch genau das selbe Problem. Wäre echt super wenn es im Board dann mal möglich wäre, dass sich da Bild automatisch perfekt an die Bildschirmgröße anpasst und die Charts auch noch schön angezeigt werden. Wir entwickeln zur Zeit immer für einen 24" Bildschirm mit Locksize 1920x1080. Wenn jemand ein kleines Laptop hat oder die Äuflösung anders ist sieht es gleich ziemlich schlecht aus. Das ist ja nicht mehr zeitgemäß.
Wir haben auch auf die Funktion im 10.3 gehofft, aber so ist sie für uns auch unbrauchbar :-(
1 -
Hi together,
first of all I would ask you to only answer in english, cause some of the colleagues can't speak german (or italian, or spanish, or whatever).
Just made some tests on my local machine with a new generated screen (without LockSize, without a mask). Screen was devoleped with 1650*1050 on Windows client (I used background colors to show the area of each element):
Now I open the screen on same monitor (resolution in chrome) with options "fit width" [so i only have a horizontal Scroll bar]:
I'm also able to change the size of the window (to approx 1/4 of the orignal size) [win client on orignal monitor for scal]:
As you can see all objects are displayed according to the size.
If I know switch to "actual size" the screen is displayed "as is was created":
So from my point of view the adaptive scalling is working as designed.
If there are are screen whcih are displayed not in a good way please get in touch with your local partner who helps with implementation or with BOARD Support.
Cause it might be (due the fact that it's a new technology) that there is still some possible enhancements. Cause there are allways many other options, whcih can also affect the rendering (for example Mask, Background picture, etc)
Philipp Schraml can you please give us some hints what you mean with " showing the charts in a good way" [die Charts auch noch schön angezeigt werden. ]? Cause as you can see in my example I (as a developer) decided for the chart in the top right corner that I want to display it per month and not to use a label interval. So when I display the same chart on a smaller area the chart can't be displayed in the best way, cause otherwise my settings (which I have choosen) would be overwritten by the system. And for sure if board would adapt this automaticaly, we would have a similar discussion with other people, why the software is changing settings, which were made by the Developer
regards
Björn
3 -
Thanks Bjorn, it's very interesting that you are getting the desired results with this feature but others are most definitely not. I hear you when you advise users get in touch with their respective support networks; I did on 14 August 2018, see image below, and am awaiting a response which I will post to the community the moment I find out anything.
In the meantime, I'm using the BOARD Community which is beginning to clarify the issue and reveal the potential extent of the problem, if not solving it.
0 -
Hi,
Furthermore I forgot to say, if you save the screen with "Lock size" it should be opened (by default) with Actual size, otherwise with fit width
regards
Björn
0 -
Hi Paul,
sorry I haven't got access to the local UK tickets (as the local uk support has no access to the german ones). For 1st level its seperated by country.
regards
Björn
0 -
Paul Wyatt - GVA wrote:
Thanks Bjorn, it's very interesting that you are getting the desired results with this feature but others are most definitely not.
the problem is allways (as I said in the other post) due to complexity.
Do you have maybe a hidden object (Label), or a special setting for mask. can it be that you're using an image, etc.
So from my point of view, If I would start to analyze the screen, I would start to disable the mask, than I would look for not necessary objects till the root case can be isolated.
regards
Björn
0 -
Thanks Bjorn, I know. I just posted the image to demonstrate that I'd raised it with my local support here in UK.
0 -
Bjorn. The issue here is that I created a completely new capsule with only one dataview, no mask and no screen lock.
When opening on a UHD 27" monitor, this 'vanilla' model defaults to the [Fit Width] setting, occupying approx 1 quarter of the screen. When selecting either of the other screen settings, the image gets much smaller.
If using [SCREEN LOCK] in the model and saving, the model opens in [Fit to Page] on web as default. Selecting another setting makes the model smaller but not by as much as saving without screenlock.
0 -
it is also far too small for me from the width.
In addition, the chart of the font size and other objects are not scaled even with smaller.
0 -
If Björn Reuber is getting a successful outcome with this feature but other users are able to document adverse outcomes, it should be understood under what conditions the features operate as designed. This can only be described by BOARD Intl.
There are functional issues with this and a number of the new features of BOARD 10.3, features that were presented at BOARDville promising that developers needed only to wait for the release and not waste time fixing or mitigating functionality that has become native.
For test script purposes, the release notes describe the expected behaviour of the new features and so it is very simple to evaluate this and the other new features.
As I cannot switch off these features, I cannot recommend that GVA upgrade to BOARD 10.3 as we have external customers to whom we would have to explain the issues, and admit where we did not know the solutions to such platform features.
1 -
Hi,
now I understand, and for me this isn't a bug:
Just created a a new screen (on big resolution as in your example):
If you know export the Capsule Meta Data you can see, that the screen has a resolution from (in my example) ScreenResolution="1600,900", so board will adjust this screen to the web Size.
so in my case the DV got a size of Width="300" Height="200" and it's starting at Top="30" Left="50".
So from pixel 50 to pixel 350 this DV is displayed. So it's starting it's starting at 3% of the whole width and it's going up to 22%.
So if I use fit witdht the whole screen (was 1600) is placed on the whole widht and the DV is allways using the are from 3%-22%.
Cause BOARD isn't use fit widht according to the object, instead it's using about the scren size:
Hope I understand your case correctly and my explanation was helpful
regards
Björn
1 -
please see my answer above to Paul Wyatt - Avison Young UK question, cause it might be the same key issue.
If not, please open ask your partner for help or open a TK on local support.
regards
Björn
1 -
Hi Paul,
due to the fact that you posted a lot screenshot, how the Screen is displayed in Web, can you please also Post a screenshot, how its displayed on the same Monitor in Win client (Without lock size).
Maybe this would help to see if there is a slightly difference
regards
Björn
0 -
how can i change the capsule resolution?
0 -
Hi,
as far as I know, just open the screen on a monitor with new resolution and save the screen.
regards
Björn
0 -
oh it looks good :-).
But it would be better if you could set the resolution fixed and not just the last saved screen size
1 -
if I remember correctly from a 10.5 beta/alpha version (i have seen once) their might be a setting in html5 Screen designer.
And can I assume from your
oh it looks good :-).
that it's now workingin a better/expected way?
regards
Björn
0 -
ok thanks, it is very good.
but in future the fonts must be auto size for better charts view
0 -
(EDIT: blue italic text added)
(Ha ha,with replies to replies, this thread is becoming quite difficult to read.)
Björn Reuber is thanked for providing a technical explanation as to what the new web page sizing feature is doing. In summary, on my servers, several of which are hosted on azure using iis and one local network server, the new BOARD 10.3 page sizing features scale down a screen. A point to note is that it scales down all screens, regardless of whether they already fit the current resolution or not.
Also, the setting is non-persistent, in that it requires setting each time a specific setting is desired, contrary to the release notes.
The practical impact of this new feature for me is twofold. Firstly, I will continue to develop for a standard Laptop resolution of 1366x768 and use the Lock Screen function. The second point is that, if I were to upgrade our production servers to BOARD 10.3, I would need to advise all users and our external clients that they should disregard the page-sizing feature. I could make use of a scale up feature to any screen, as Microsoft Office365 Word does.
By way of illustrating the main feature above, using two capsules on two display devices and resolutions, I have compared the three settings and displayed the outputs below in a table. Both capsules were tested first on ACTUAL SIZE. Each was then set to FIT WIDTH and FIT TO PAGE to observe how the capsule was effected by each setting. The comments are my own subjective view.
I do acknowledge that other users may have a different experience with this feature. It is for this reason that I have also raised a Service Ticket.
Capsules:
- BOARD db Log - a small screen size below 1366x768. Whilst this is a very old BOARD capsule, it was optimised for BOARD 10.3 by saving after opening in order to make it BOARD 10.3 compatible.
- GVA test capsule - A large screen optimised for the HD resolution of 2560x1440. NB: figures have been pixelated.
Display devices:
- Laptop at 1366x768
- Monitor at 2560x1440
DEVICE ACTUAL SIZE FIT WIDTH FIT TO PAGE Capsule 1 with Device 1:
LAPTOP with small screen model
Comment WORKABLE - Readable but with unused screen area, as expected. Difficult to read and large unused screen area Very difficult to read and use and very large unused area Capsule 1 with Device 2:
HD Monitor
with small screen model
Comment Readable but with large unused area Readable but large unused area Readable but with larger unused area Capsule 2 with Device 1:
Laptop with large screen model
Comment WORKABLE - Readable but user must scroll to see all of screen Almost unreadable but most of model seen Unreadable and wasted screen area to the right and below Capsule 2 with Device 2:HD Monitor
with large screen model
Comment WORKABLE - Whole model optimised for large screen resolution WORKABLE - No change, as expected. Screen almost unreadable as model has reduced in size for an unexpected reason and leaving wasted screen right and below. 2 -
Hi Paul Wyatt - Avison Young UK
it's not easy to say if the behavior is correct or not, without seesing the same CPSX directly in Win Client. Furthermore, without having access to the CPSX for further analysis it's very hard to help you. So as said before, due to the fact that it seems to be a misbehavior in some cases, the best way is to create TKs (as you already have done) and follow the standard support process.
regards
Björn
1 -
Hi,
did some tests on DB Log appllication [used Screenresolution: 1650*1050)
updated the original DB Log CPSX to b10 format (cpsx is using lock size) and added a label to show, which area is used:
Win Client:
HTML5 Actual Size :
HTML5 fit to page:
fit width
So from my point of view, everything is working correctly.
Paul Wyatt - Avison Young UK find also attached my test- capsule, maybe you can also add yours (for log application)
2
