[Etoys-notify] [JIRA] Updated: (SQ-141) Policy about screen scaling and project dimensions

[jira at immuexa.com]

     [ http://tracker.immuexa.com/browse/SQ-141?page=all ]

Scott Wallace updated SQ-141:
-----------------------------

    Priority: Critical  (was: Normal)

Yoshiki's recommendations from ticket SQ-219:

1) With the screen scaling feature, the actual screen size is not the real decisive factor. For a 600 high display, 900 high virtual screen is a "ok".
2) On the other hand, scaling adds performance penalty, and scaling down does add some visual artifact. One may want to avoid it.
3) With 800x600, yes it fits within a web browser running in a XGA screen.
4) When running Etoys as an application, the initial size of window can be set by us (in a typical case; where the actual display has enough room for the size we specify).
5) It is hard to show viewers and menu bar "outside" of the Etoys project extent.
6) Showing the grid wouldn't really help. The positions in scripts will be different once it is exported and loaded onto a different sized computer (without scaling). If we want the content creators not to exceed the boundary, scaling or just making the etoys image in that size would do it.
7) We care about the "initial experience". People may be able to set their Etoys size afterwards, but there can be a standard size. So, "toggling back to the standard size" is less important.

So, finally, here is my suggestion #1:
a) We set the standard size to 1200x900 (, which is bigger than the actual screen for many computers).
b) For Windows/Mac/non-XO Linux, we make the application window size is 800x600 and always scale to 1200x900.
c) in the browser, we set the embedded object size to 800x600 and always scale to 1200x900.
d) For those who want to use different size, we provide a way out (but not necessarily get in).

My suggestion #2:
a) We set the standard size to 800x600 (, and basically we say we don't support any smaller screen than that).
b) For Windows/Mac/non-XO Linux, if the actual screen size is bigger than that, we start in a window that holds the 800x600 pixels Etoys screen. If the actual vertical pixel size is 600 and cannot accommodate window embelishment, we just get into the full-screen mode. with "Centered Virtual Extent" (if necessary).
c) on XO, we run it in "Centered Virtual Extent"; i.e., have 800x600 pixels at the screen center, and surround it with gray border. (We can optimize it so that Centered Virtual Extent doesn't involve WarpBlt.)
d) For those who want to use different size, we provide a way out (but not necessarily get in). 

> Policy about screen scaling and project dimensions
> --------------------------------------------------
>
>          Key: SQ-141
>          URL: http://tracker.immuexa.com/browse/SQ-141
>      Project: squeakland
>         Type: Improvement
>   Components: etoys
>     Reporter: Scott Wallace
>     Priority: Critical
>      Fix For: dormant, residual, historical
>  Attachments: browserGrid.003.pr
>
>
> Project authors typically would like their projects to be usable across a broad range of screen resolutions, OS's, browsers, etc.
> To this end, we should articulate a clear set of guidelines concerning screen-scaling and project dimensions when authoring projects.
> The set of cases to be dealt with is something like the cross-product of:
> (1)  Whether running in browser vs. running standalone
> (2)  Whether resolution in which project was authored is less than, equal to, or greater than resolution in which project is viewed.
> (3)  Whether operating "full screen" or within a window.
> We should decide:
> - What resolution do we recommend that authors use for creating projects intended to be used on screens of many different sizes.
> - When squeak opens a project, in-browser or not, what setting should be adopted for screen scaling?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://tracker.immuexa.com/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira