World: r3wp

uh, will look for some screenshot, but not sure I made one :-(

Not sure I have IOS developer's connection still active. I will look 
at my home's pc ...

found it ...

pekr, I find it highly necessary, because of the aforementioned lack 
of high level structure. It's not a luxury, but meant as a guideline 
to how to make your program look and act. I've changed the structure 
of my programs over the years too many times, because there was no 
real way to standardize this. Every REBOL programmer must come up 
with his own standard for this, which IMHO is a lot of unnecessary 
work.

You can see the whole menu datafile for Canvas RPaint by doing:

>> print decompress read/binary http://home.tiscali.dk/john.niclasen/canvas/modules/menu.dat

http://www.xidys.com/rebol-view/cyphre-menu1.jpg
http://www.xidys.com/rebol-view/cyphre-menu2.jpg

It is part of Cyphre's stylepack, which is freely available from 
rebol.cz somewhere :-)

well freely...the license is very confusing :)

Henrik - but I can imagine more than 10 such styles, how you build/divide 
canvas for your app :-( And last years, we have apps appearing, which 
simply don't adhere to some system rules anymore ...

Henrik - who not let it just be a style? Just like tab-view is container 
for other stuff? You could start the hierarchy with - view layout 
[app-window split-window 3 [list-box .......]]

This is also nice menu: 

do http://www.rebol.org/cgi-bin/cgiwrap/rebol/download-a-script.r?script-name=menu-system-demo.r

hey, that is cool ;-)

Pekr, it's highly likely that people will settle for a guide, if 
one is provided with REBOL and it's made in a reasonable way. There 
is a reason why most OS'es have interface guidelines, namely to encourage 
consistency. The good thing with a guide is that you are not forced 
to use it, and it's not meant to restrict you, but help you develop 
your software faster, since all those design decisions are already 
made for you. If you want to build a custom dialog, it would be very 
nice if you have the basic arrangement already available, so you 
can settle for creating content for the dialog.

pekr, it _is_ a style. maybe we are just naming them differently 
and we agree after all. :-)

Henrik - I just don't believe it will not push its usage style on 
me ...

but the truth is, that maybe we shold decide, if it is better to 
have them, or not ...

pekr, it probably depends on what type of UIs you develop. Is it 
large programs or just smaller scripts with a GUI slapped on? I see 
guides only as beneficial, when developing larger programs.

I think that kind of general split window with settable (resize yes 
or no) panes, auto-scrollers, could be suitable?

I do understand you properly, Henrik. My dilemma is different. Last 
4 or so years, I see BIG diversification in how companies aproach 
UI, even MS themselves!

Should I do a screenshot of MS Outlook? And then some other app, 
using their dev. tool? Those look different in that respect! So, 
what I just said is - the trend is towards moving away from traditional 
looks, more so with inclination to web based like apps ...

but I think we just want the same ;-) My intention is just to have 
it available as nested styles, no new concept, if we can make it 
that way. But some aspects of certain look & behavior could be rebol 
specific and cross platform imo.

Yes. And I don't agree with those design philosophies. :-) It may 
have something to do with those programs being so amazingly huge 
and have 2-digit sized development teams, so the program itself will 
reflect what the team is doing. MS is known to reinvent the wheel 
for each product. This is a bad trend.

Look at some of Office 2007 screenshots. I am still not used to it. 
There is NO menu - it is replaced by tabs plus big icons/configuration 
sections ...

I've seen it, and I hate it.

What I will accept - containers, where I can put whatever inside. 
I will not accept anything specific, which will be more than general 
pane box, because it will push certain usage scenario on me. I want 
to decide, if I place Cyphre's menu there, or yours toolbar ...

And when we talk about split-window (app-window), we can even talk 
about native VID windowing :-)

Do you remember the so called MDI or SDI app guidelines? I am not 
sure I agree with any of them :-)

that should be discussed in VID group probably :-)

If I try to make a MacOSX program in Cocoa, I'm actually pretty restricted 
in what I can do in terms of UI guidelines. I have to follow their 
menu system and structure. I have to follow their windowing system 
behaviour. I have to have an icon in the dock and I can do certain 
specific things with the icon. If I choose to, I can even let MacOSX 
handle loading and saving of data and preferences for me and handle 
the aspect of multiple documents for me.

I could probably code my own stuff, but since Apple have spent years 
designing these UI elements and guidelines, I see no reason to do 
that, since it provides a high amount of consistency. It's actually 
pretty hard to make something that looks shoddy or amateurish, unless 
you start drawing up your own graphics elements and ignore existing 
guidelines, which would be a huge waste of time. MacOSX is exactly 
being touted as being a fast environment to develop in, because many 
of the tough design decisions have already been made.

moving to VID...

Henrik, the link above state exaclty what you say: The NIB (stands 
for NeXTStep Interface Builder) file is a loosely coupled, standalone, 
user interface definition. It wouldn't make sense to double-click 
a button and immediately be taken to a code-behind. Instead, you 
have to create a controller class, and then ctrl-drag from the button 
to the controller and then pick the outlet you're going to use (something 
like click: or calculate:). To me, as a huge fan of the MVC pattern, 
this makes perfect sense. And it seems so elegant in its simplicity, 
and so incredibly cool in the fact that it is truly enforcing good 
design simply by the way the IDE works.

yes, the guidelines are in fact inherent to Cocoa itself. I didn't 
think of it that way :-)

well, listening to raising requests to be tight to os-native widgets 
(not only windows behavior), I start to think that it would be better 
to scrap View altogether, and to go with some other UI toolkits, 
as gtk, qt, or simply to wrap OS ones ;-)

why? it's simply adding a layer above VID to guide how to handle 
certain dialogs and multiple groups of widgets. it doesn't have to 
be more than a few kb's of code in total.

think of it as a layer above VID as VID is a layer above View. imagine 
how it would be to code layouts without having VID in REBOL...

layer about VID ... maybe the thing is, I can't imagine it. Kind 
of 'View function dialect? e.g. view/custom, or view/specific custom 
block configuration?

no, just advanced styles with many single faces grouped into one. 
just like you said yourself.

ok then ...

so, now what? We wait for Gabriele to come out with some prototype?

yes, I think we should see how that works out. if it will be as extensible 
as it's claimed to be, then this can easily be done.

I wonder about one thing - will layout be changed to grid model?

.... and ... not sure it is possible or if it would be vital, but 
Chris requested future VID being CSS like, simply put that widgets 
would be separate from styling. But not sure it is possible. The 
trouble is, that once layout is decomposed into view objects, there 
is no way back. There is nothing like DOM ....

so - would anyone else find the ability to get back to layout usable? 
I don't remember, what exactly Chris had in mind with that ...

well, I wouldn't mind seeing a way to store UI skins centrally, so 
there would be a way for the user to customize it, like you can with 
MUI on a per application basis.

Between Cyphre, Geomol, and Christian, we have three solid menuing 
systems to analyze as prototypes. If someone wants to write an interface 
to native OS menus, that can probably be written as an extension 
to R3. The only critical thing would seem to be the ability to attach 
an OS menu to a REBOL window.

Four
do http://anton.wildit.net.au/rebol/gui/demo-menu.r

Christian's menu-system-demo is showing some interesting memory-eating 
behaviour on my system. I'll try to isolate that tomorrow.

Petr, just to be clear, system menus are OS neutral.  Every platform 
that View runs on has a menu system that is essentially the same. 
 The mode of access may be different platform to platform, but how 
different in function is a Windows menu to an OS X menu to an Amiga 
menu?  All I would like is a standard way to utilise them.

Sorry, forgot yours Anton; so much chat here lately.

Let's specify menus with a dialect that does not assume where they 
will be put, and then implement that dialect in a platform-specific 
way, with a cross-platform REBOL native fallback.