AltME groups: search

The thing is that they made software so complex, that it has become 
extremely hard to point your finger at where exactly it goes wrong. 
We had to build Syllable to get an idea of some of those things, 
and then nobody wants to believe you

Adrian, tablets with styluses are rare now; the iPad led the way 
toward finger-only interfaces. It's been announced that the Surface 
Pro will have a stylus, but it's a passive one. The Android tablets 
with styluses are passive too, just using the stylus for a sharper 
pointer. An active stylus is an expensive peice of electronics, while 
a passive stylus is just plastic with maybe some metal or rubber 
on it, so you can see why they're preferring passive now. Hover is 
going away for a lot of platforms, or was never there for some of 
the new ones.

I've just lost a long post I was typing here because my finger ripped 
on the small laptop keyboard from a CTRL-S to CTRL-Q...who the hell 
got the bright idea to put the app killing (no confirm prompt) key 
close to the post sending key?...Will have a few words with Carl 
about ergonomy in AltME. ;-)

Well i mean that when i start ALTME in i.e. 500x500 and then resize 
with mouse I dont see any screen stripes while resizing, but when 
I do this with a simple window under rebol I do see lots of screen-stripes 
during resize untill I loosen my finger from the mouse button...

Component: "REBOL Mezzanine Extensions" 1.2.0 (1-Aug-2004/22:34:12)

Component: "REBOL Internet Protocols" 1.71.0 (4-Nov-2004/21:08:24)
Finger protocol loaded
Whois protocol loaded
Daytime protocol loaded
SMTP protocol loaded
POP protocol loaded
IMAP protocol loaded
HTTP protocol loaded
FTP protocol loaded
NNTP protocol loaded
Component: "Command Shell Access" 1.9.0 (3-Jan-2005/21:08:57)
Component: "System Port" 1.4.0 (1-Aug-2004/18:58:28)

You might be thinking of one of these:
>> first system/schemes

== [self default Finger Whois Daytime SMTP ESMTP POP IMAP HTTP FTP 
NNTP HTTPS]

Oh man... to many typos (I cut my right finger):
- Let's say I have
- know = now

for some reason, using recursion...I just can't seem to put my finger 
on the right combo.

its not about the UI, its about how the fingers work.... people implementing 
gestures often don't even look at their hands to realize how each 
finger has its own specific optimized movements.

:-D

Gregg, you did a marvelous job with your multi-language intro at 
last DevCon. You tricked me for a second to think, you were fluent 
in all those languages. :-) I remember, I started to speak danish 
to you, and you raised your finger like saying: "I'm coming to that." 
hehe

About protocols: Carl says that the basic foundation is not going 
to change, so he wants to see some protocols written. He wants to 
start with something simple like Finger. Here's your chance to contribute!

Carl: "most of the scheme structure has been solid and unchanged 
for more than a year. The main disruption was Unicode, but that's 
been done for a while too. I think we should pick a few very simple 
protocols, maybe one like Finger, and j ust show how they are done... 
as an example."

I'm keeping finger crossed not to be too old to be able enjoy truly

How are things going on adding a few schemes?  


I mentioned that I would review the docs and add more examples; however, 
if someone has implemented a simple scheme example, like finger or 
such, then let's use that as the starting point, clean it up (if 
necessary), and put it on the wiki for others to learn from.

Me too, but it's times like these that differences with other people's 
brains pop up that I can't really put my finger on, either :-)

About crashes, I submitted 4267, 4238, 4167, 4137, all crashes, and 
I found them on my own. Besides I've bumped into recycle crashes, 
port crashes/hangs and also other crashes, that I can't put my finger 
on, when using Rugby with secure network transfers. I get a crash 
about 1-2 times a day.

Throw in a few example schemes like finger or whois.

For example, the primary multitouch I miss in VID on OS X is 2-finger 
scroll, but it can be packaged as a scroll event, so should map. 
 (The issues we face will also be faced by all web browsers, so we're 
in good company.)