World: r3wp

Graham, yes.

I think yes.

And I guess you change them for whatever language you use ...

Anyway I hope R3G has robust keyboard handling .. for speed a mouse 
driven gui sucks

I hope so too, but we haven't gotten to that part yet.

alert "New Acronym in use"

shortcuts, and language need to be unified and solved...

Javascript does a pretty decent job of creating GUIs ... I don't 
think one should be criticized for looking there for inspiration

regardless of its age.

The JS GUI is pretty much the de-facto standard GUI

Yes, reserve your criticism for attempts to replicate its flaws.

I like the easy way you can easily chain callbacks

to give smooth GUI changes

Javascript *plus extensive frameworks and bug fixes* does a pretty 
decent job of creating GUIs.

and the way you can stop a current animation

Yes, I was actually talking about jQuery

Graham - what JS gui? Is there actually any JS GUI? Or are you talking 
about web gui in general, hence HTML, CSS, JS?

the latter

Graham - I think noone criticised you.  But honestly - you started 
your description like if R3 GUI plan would need any inspiration in 
JS.  There were many many discussions about it, and also from some 
docs it starts to be apparent, how R3 GUI is flexible ...

... besides that, there also were some talks of R3 GUI generating 
some output to web .... we will see, where all this leads ...

I started by saying that I was reading about ujs ... and picked on 
aspect of it knowing full well that most of ujs did not apply

on => one

I know my own screens are horribly complex with all the code attached 
to buttons

And then I looked for R3G examples and did not see any separation 
there either. So, I asked ...

No need to reopen the discussion, but the thing you wanted was to 
separate gui description (elements and its placing, look) from the 
action code?

yes.

So, one person could design the gui, and another could design the 
functionality

I don't know any other system than web, which does it.

Which does what?

Separation of form from action.

form = presentation

are you saying that it's not necessary?

because noone else does it?

Absolutly not. I am just saying, that looking into Delphi, SAP, or 
other tools, which are used to build apps, it is not simply common 
methodology. Web came from presentations. Remember - some 5 - 7 years 
ago, some companies don't even allowed JS to be run. "Nowadays there 
is no web without JS" - remember that statement, as it is proof, 
the web is patched beast, not something very well thought out from 
the beginning ...

There is surely still time to talk about those things for R3 gui.

That's what we're doing :)

While basic concepts are in place, there still might be room to allow 
many things. R3 gui is really very flexible ...

And unfinished

Every thing in development is - unfinished ...

I merely offer my observation for discussion :)

I realize that Carl doesn't read this group ...

You will be able to post some notes via chat system. Dunno when we 
will be back to GUI though. RebDev aka DevBase is still not finished 
...

The R3 GUI does the separation of form and function better than Delphi 
(or even HTML/CSS/Javascript).

the chat system is too hard on my eyes :(

And Carl is currently busy generating R3 documentation.

When do new-users will be accepted inside the chat app in R3 ?

Carl is doing very good and needed infrastructure thing. I always 
support such things. Both DevBase and Docs are needed.

Kib2, likely when the chat server is finished being ported to R3 
on Linux. We were running into problems with Unicode user names on 
R2, since R2 can't do case-insensitive comparisons of Unicode strings, 
even when encoded in UTF-8.

BrianH: ok, thanks. What about  allowing ASCII chars in user names 
until it's really finished?

Nowadays there is no web without JS
 - I take it you are not:
- Blind
- Using a text-mode browser (similar constraints to blind)

- Running a safe browser (similar constraints to Firefox with the 
NoScript extension)

Of course there is the web without JS - otherwise "Unobtrusive Javascript" 
wouldn't be needed.