r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[!REBOL3-OLD1]

Geomol
29-Jul-2007
[3759]
Does SWITCH need a /case refinement like we have in FIND and SELECT?
Pekr
29-Jul-2007
[3760]
Gabriele - has anyone tried new View on multi-monitor display? It 
is imo good to keep that in mind, as R2 was not much friendly here 
....
Gregg
29-Jul-2007
[3761]
Under R2 it would just need to propagate the refinement to SELECT 
(which is a bit of a pain of course). Worth asking for R3 though.
btiffin
29-Jul-2007
[3762]
John;  I'd vote yes for a case sensitive refinement for switch.
Pekr
30-Jul-2007
[3763]
... as for multiple screen, my experience is as follows. Under Windows, 
multimonitor set-up is an ilusion. You can find it out, once you 
use e.g. VNC and connect to such a remote desktop - you can easily 
see one big screen. The interesting part is - even if one of your 
displays is moved 90%, it is still one big box of x*y size.


So, in regards to REBOL, I think it would be vital to being able 
to identify multi-monitor set-up, and not one big screen face. My 
expectation is to have screen-face having two (or more, according 
to active monitors) or more subfaces - desktop windows ....


It would be good to get correct behavior in that regard from the 
very beginning ....
Geomol
30-Jul-2007
[3764]
Sound like a complicated thing to support on all platforms.
Pekr
30-Jul-2007
[3765x2]
hmm ... maybe we should at least have some strategy. Simply we should 
be prepared that screen-face is not screen face, but kind of desktop-face 
.... it should be indexed [1 [screen here] 2 [screen here]], it would 
be on pair with how driver identifies primary and secondary monitors. 
Not sure all drivers do it the same though, I mostly use nVidias 
.....
so my suggestion is, that screen-face should be a holding block, 
container, not face itself ...
Gabriele
30-Jul-2007
[3767x2]
Petr, I have two monitors here, one 1600x1050 and one 1280x1024. 
screen-gob size only reports the first, but I hope we can add support 
for things like these soon enough (not for beta).
about it being i single big box - it is so on linux too, and i'd 
assume it would be so in all OSes that have legacy to maintain, but 
it depends on the desktop mode too.
Pekr
30-Jul-2007
[3769x2]
hmm, if you have two monitors, maybe you could try "a trick" :-) 
try to place your window "off-screen" and watch, if it appears on 
secondary monitor? :-)
btw - will there be release this week, or is it going to be postponed?
Gabriele
30-Jul-2007
[3771x2]
petr, is ok if screen gob is just one when it is one for the OS too, 
we just need some way to know the size of the monitors.
yes, i can move windows around the two monitors. i have this altme 
window in one monitor and other two on the other monitor.
Pekr
30-Jul-2007
[3773]
... and if so, could we at least get some preliminary (one week before 
release) access to docs, to read some things and being prepared to 
jump on R3 more quickly?
Gabriele
30-Jul-2007
[3774x2]
i can have windows "in between" and so on. it's just one big framebuffer. 
if i do a screeshot, i get a big 3000x1000 image.
access to docs.... i can ask Carl...
Pekr
30-Jul-2007
[3776]
really? (re screenshot) ... moving windows by accelerator keys was 
fine. I think that we will need to map win32 api, which will tell 
us about particular monitor set-ups ...
btiffin
30-Jul-2007
[3777]
Add a meetoo for access to docs, even if it's a subset.
Gabriele
30-Jul-2007
[3778x3]
this is how linux sees my display:
SZ:    Pixels          Physical       Refresh
*0   3360 x 1050   ( 948mm x 303mm )  *60
 1   1680 x 1050   ( 948mm x 303mm )   60
 2   1280 x 1024   ( 948mm x 303mm )   75   70   60
 3   1280 x 720    ( 948mm x 303mm )   60   50
 4   1152 x 864    ( 948mm x 303mm )   75   70   60
 5   1024 x 768    ( 948mm x 303mm )   75   72   70   60
 6    800 x 600    ( 948mm x 303mm )   75   72   70   60   56
 7    720 x 480    ( 948mm x 303mm )   60
 8    640 x 480    ( 948mm x 303mm )   75   72   60
 9    640 x 432    ( 948mm x 303mm )   60
 10   640 x 400    ( 948mm x 303mm )   75   60
 11   512 x 384    ( 948mm x 303mm )   75   60
 12   400 x 300    ( 948mm x 303mm )   75   60
 13   320 x 240    ( 948mm x 303mm )   75   60
 14   320 x 200    ( 948mm x 303mm )   75   60
notice there is an invisible area under the second monitor (1280x26 
pixels).
Pekr
30-Jul-2007
[3781]
interesting part is, when you rotate one of your monitors, the actual 
bix size is max of respective x or y axis ....
Gabriele
30-Jul-2007
[3782]
mainstream OSes do not support multiple monitors very well - they're 
mainly hacks. the way R2 and R3 work now, you only "see" the first 
monitor, but you can still move windows to the second one. this is 
not too bad, because windows get centered to the first monitor if 
you use center-face instead of being between the two monitors (which 
is bad, and some apps do that). so altme always opens on the first 
monitor, because it thinks the offset it saved in the prefs is offscreen 
if it was on second monitor.
Pekr
30-Jul-2007
[3783]
not sure, but IIRC I was able to get Altme started on second monitor 
too. At new work I don't have two monitor set-up, so can't confirm. 
nVidia drivers offer you an option to save the proferences for particular 
apps/windows. But often even known apps as Adobe Reader did not switch 
properly between two monitors (ignoring orientation for e.g.), so 
icons on windows showed the window is maxed, yet it was not ...
Gabriele
30-Jul-2007
[3784]
nvidia drivers were maybe overriding the setting from altme itself 
about position.
Pekr
30-Jul-2007
[3785]
yes, I used and a bit extended Gregg's keys dialect. I was able to 
shape and move windows by calling win32 api functions. I tried to 
wrapp also the monitor stuff, but if was upon my capabilities ....
btiffin
30-Jul-2007
[3786]
Unless there is an R3 Window Manager is this not an issue completely 
under the control of the desktop window manager?  Wouldn't any attempt 
by REBOL to effect this just break the desktop control?
Pekr
30-Jul-2007
[3787]
btiffin - I am not sure I want R3 to break anything :-) But it would 
be nice, if programmer would have easy option to investigate state 
of monitor set-up, and eventually decide where to send the window 
to.
btiffin
30-Jul-2007
[3788]
So aside from being coded to be "friendly" to any exisiting multi-montor 
display managers, there isn't much REBOL could do...at least not 
cross-platform...in my humble and zero experience opinion.
Gabriele
30-Jul-2007
[3789]
i think the current behavior is better than many other apps. but 
it can be improved a bit. we'll see...
Pekr
30-Jul-2007
[3790x2]
it could detect monitors ... they are often numbered 1, 2, 3 ... 
and their orientation, resolution :-) Then we could have 1, 2, 3 
etc panes to post our apps to :-) That is my very unexperienced opinion 
too :-)
Gabriele - you mentioned "skinning". Will basic VID3 design be vector 
based, or still bitmap based? And will it be upon "skin" just to 
skin existing element, or will skin include also code of how to draw 
the element?
Gabriele
30-Jul-2007
[3792x4]
well, then where is a window which is between two monitors?
it can't be in two panes at the same time.
i think, where windows go should be left to the user. what's important 
is that rebol does not try to center windows incorrectly, or to clip 
them to the first monitor and so on.
skinning is completely abstracted and you can have whatever look 
for the styles. currently we only use draw, not images, but some 
styles may require images. anyway it depends on the skin, vid does 
not care at all what you do.
Pekr
30-Jul-2007
[3796]
ah, valid point, I do remember some Delphi app incorrectly centered 
itself between two monitors ...
btiffin
30-Jul-2007
[3797]
I'd leave this up to a display manager.  That is until there is an 
R3wm  :)
Pekr
30-Jul-2007
[3798]
re skinning - sounds well abstracted. The same goes for your mention 
of layout no caring about actualy rendering anything too ....
Gabriele
30-Jul-2007
[3799]
source of layout function is like 4 lines ;)
btiffin
30-Jul-2007
[3800]
Taunting the bears again huh?  :)
Pekr
30-Jul-2007
[3801x2]
Gabriele - one of your past discussion was also so called two-ways 
functionality. I mean - after you do layout in R2, from the "live" 
state, e.g. by moving UI element, get it back to layout. So once 
you relayout you loose that info. Could that be solved?
ah, so why is there layout at all? :-) Could Rebol code 4 lines be 
any usefull? Scary question with REBOL :-)
Gabriele
30-Jul-2007
[3803x2]
hmm, what do you mean exactly?
layout it is useful. you would probably not guess those four lines. 
:)
Pekr
30-Jul-2007
[3805x2]
hmm, not sure - I just remember one discussion ... you have layout 
[button 100x200 "ok" [print ok]] ... then you e.g. programatically 
move or resize the button .... layout simply is here like a template, 
which generates faces. The reverse aproach is not here ... maybe 
it even can't ....
is one of those lines - "; comment - for compatibility reasons ...." 
:-)
Gabriele
30-Jul-2007
[3807]
so basically, given win: layout [something here]  you want to get 
back the dialect block from win?
Pekr
30-Jul-2007
[3808]
not sure I want, not sure it would be usefull. It is just that I 
remember one product which claimed to do something like that ....