World: r3wp

this is a K-Meleon Windows browser gift  - maybe sometimes smaller/faster 
is not better ... KMeleon is writing to a USB ext drive and IE8 is 
writing to an internal HD ... sometimes KM is writing the larger 
VIEW exe intact, sometimes not.  This may account for some recent 
"bad" ZIP's from my x-plane Flightsim community.  Yuch.  Most of 
 those x-p guys always zip up all their Win indexing .Thumb or hidden 
Mac files - and sometimes they have accumulated both from working 
on a Win "airplane" on their Mac. So I am used to annoying ZIP's 
for that hobby ... but this is TOO annoying.

The request-to-authorize thing is managed by an extended attribute 
in one of the other forks of the file on NTFS, and not on FAT. Have 
you tried Chrome or Firefox?

Have you tried downloading the zip file containing the exe instead 
of the exe directly? http://www.rebol.com/downloads/v278/rebol-view-278-3-1.zip

Looks like we have OSX Intel and Linux Libc6 builds now.

Cool

Woohoo, also looks like the /View Linux libc6 builds (4-2) are no 
longer broken.

It would be good if 'ajoin were present

It has been since 2.7.7.

Ahh.. well, one of these days I shall upgrade from 2.7.6

2.7.8.2.5 seems to start a lot faster (than 2.7.7.2.5).

RobertS, yes, it's a good idea to check what filesystem is on your 
USB drive.

I find the technical arguments for leaving out /Library very hard 
to believe. I suspect this is a case of RT pulling a Microsoft, by 
making design decisions subordinate to business considerations

2.7.8 turned out to have to be a minimal release, due to outside 
constraints. That means it's time to talk about 2.7.9.

In this case, we're really still talking about 2.7.7

The code in R2 that implements those business constraints is still 
code, so changing stuff still takes work.

Pity that the 2.7.8 roadmap wasn't updated: http://www.rebol.com/docs/changes-2-7.html

2.7.7 also turned out to have to be a minimal release at the time. 
It's hard to budget time for major native changes in R2, partly due 
to business constraints (who is paying for this work? noone that 
I know of, and adding Library to Core removes a revenue source without 
replacing it with another), and partly due to the nature of the codebase 
itself.

Yes, Doc, I have been requesting that too. And Carl (belatedly) said 
to hold off on using or announcing the SDK (don't know why).

I repeat: I find the technical arguments very hard to believe

That's your perogative, since you haven't seen the code, and haven't 
discussed the code with Carl.

I'm not going to defend RT against trolls anymore, because they are 
proven right this way

I don't need to see the code, because it's very simple: there's Pro, 
and you only have to disable some parts of it

I agree.

rebview278 still fails when run in a non-X environment. So `Change 
"bad face in screen pane" issue on non-X env boot` was not done.

That seemed to be a business consideration a year ago, so I was hoping 
it carried some weight

Andreas, the changes doc wasn't updated yet. Most of the native changes 
that didn't have checkmarks next to them weren't done. This was a 
minimal release, so some stuff got put off to 2.7.9. Give me a moment 
and I will try to list the changes in that list that were in this 
release.

Nevermind. Prompted by Kaj mentioning it previously, I was just checking 
if this was fixed in 2.7.8 and found it it wasn't.

Instead of access-os there are also new natives list-env and set-env

BrianH: what are you talking about? Wasn't /shell and /library released 
for the /Core for free already?

talking any "revenue" in regards to RT and business, is quite funny 
imo ...

Not Library

yes, it was IIRC ...

No, it doesn't work on my systems, and I've discussed it extensively 
a year ago

or was it released for View?

Yes, View, which doesn't work on headless servers - game over

ah,now I finally understand, thanks ...

Isn't it just a cut&past of code then? Max few hours work?

I would think so

Kaj - still no option to switch to R3 + Extensions then? Or are we 
referring any existing product, which would need to be ported, e.g. 
Cheyenne itself?

Diffs from the old preliminary changes doc to the actual 2.7.8 release 
(that I know about):

- No installer changes yet (my bad, I didn't have time to do them)
- SINGLE? is LAST? instead
- RESOLVE is a (slow) mezzanine for now, not native

- Don't know about what the Command boot problem was or whether it 
was fixed
- No HTTP fixes yet
- No X fixes yet

- ASSERT and APPLY are still mezzanine, and ASSERT is still rather 
bad
- No FOREACH setword support yet
- SET-ENV native (with limits)
- Delay sound subtask creation (whatever that means)
- RUN function uses 'shell access in SECURE
- FIND and SELECT on objects
- FUNCT /extern option, SPEED? and DT

- Some fixes to bugs in RAMBO that I don't know since RAMBO is down

Petr, it's not even a concrete problem for me anymore if Cheyenne 
now works properly. What keeps getting to me are the broken promises 
that destroy my planning and my trust

There are likely also other changes I don't know about.

I hope that the "Command boot problem" will be fixed in 2.7.8, it 
was one of the biggest regression in 2.7.7 (IIRC, it was causing 
scripts encapped with a /Command kernel to crash on start).

Kaj - now you start being negative ... like I was several weeks ago. 
Well, don't even ask me, what I think about the situation - it is 
no more funny. No matter what, SCRUM or not, Carl is still not predictable, 
which has side effects on some of you ...

Yes, that's what bothers me most, that my limit has also been reached 
several times

I know I'm crazy, so if my limit is reached, most everyone else is 
long gone

Well, 14 years ago I said I am going to be the last one, turning 
off the lights :-) So once I find out I am the last one logging here 
for more than 3 months, I delete all rebol related stuff :-)

Doc, was that on Linux or on all platforms? If the problem arises 
on Windows, do you have an example script that I can test? Then again, 
this might be the reason for the SDK delay.

Carl was glad with the compliments on 2.7.8, but likewise, I seem 
to be the one who will have to promote R3 on OSNews in the time to 
come, and I can't do that if I don't believe in it

Well, we should probably move to advocacy, sooner than guys will 
kick-us off from here :-)