World: r3wp

The look of R2 View is one of its smaller problems.

 => OK, but we are in 2011 (already for some, in a couple of hours 
 for the others).

An look is important. Apple and Steve Jobs show how it is important.

A good look will be possible for R3 to do. It's simply a waste of 
time for R2 and you can't produce anything that resembles Aqua anyway 
in R2. In R3 that is possible. But focusing on look alone is a big 
mistake, which too many developers using GUI systems are suffering 
under.

nve - what is Henrik trying to point out imo, is the fact, that it 
is not that easy to change look of R2 VID and stay consistent. I 
think that with VID3 it is going to be easier, as the system is more 
and better abstracted. It might be easier to do the job for R3, than 
to R2. I believe R3 is going into beta sometimes ... when Carl re-appears 
 + 2-3 months :-)

Rebol2 is quite a closed project. It needs only maintaining and updating 
activity. No more core changes.

We will not be delaying 2.7.8 to update the appearance of View :)

Some of what is coming in 2.7.8:

- Bug fixes and enhancements to improve Cheyenne, and other apps 
that have to do similar stuff.

- Some native fixes for non-Windows platforms, particularly Linux.

- Environment variable stuff: GET-ENV expansion on Windows, SET-ENV, 
LIST-ENV

- Function fixes: RUN enabled, LIST-REG/values, possibly TO-LOCAL-FILE

- R2/Forward: FUNCT/extern, LAST?, COLLECT-WORDS, EXTRACT fixes, 
ASCII? fixes, LATIN1? fixes, INVALID-UTF?, CD, LS, MORE, PWD, RM

- (Still pending) Natives: ASSERT, APPLY, RESOLVE, FOREACH set-word 
support

wow, worth waiting for updating UltraEdit Wordfile

Some of the registry stuff is broken on R2/command .. hope they are 
fixed and not just enabled

One of the things we would like to do is easily detect all installed 
fonts in windows, and install new fonts

Have the registry bugs been reported? If not, do so here or in RAMBO. 
(I am a bit new to the RAMBO admin process.)

I have reported them ... just checking to see where

Ok, it wasn't rambo

This is from August in the SDK group


Trying to see if .net is installed but this gives me an empty block 


 foreach key keys: list-reg/HKLM "SOFTWARE\Microsoft\Windows\CurrentVersion\Internet 
 Settings\5.0\User Agent\Post Platform" [
                print key
 ]

even though I can see it full of keys in the registry ...

And from View in Sept 26

and ...


keys: list-reg/HKLM "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts"
    probe keys


    keys: get-reg/HKLM "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" 
    "URW Palladio L Italic (TrueType)"
    probe keys


    keys: exists-reg?/HKLM "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts\URW 
    Palladio L Italic (TrueType)" 
    probe keys

produces this

[]
URWPA32_0.TTF
false

Those are not keys, those are values. LIST-REG/values will get those.

Btw, the registry functions are still not made available in regular 
/View, for the same security reasons as before.

2.7.8 released! http://www.rebol.com/article/0502.htmlHappy New 
Year!

At least for Windows so far. Things that didn't make it in this version:
- The TO-LOCAL-FILE fix for Windows UNC paths
- FOREACH set-word support
- ASSERT, APPLY and RESOLVE are still mezzanine

But as a bonus, we got SELECT and FIND on objects, and that is better 
than any of those others :)

Congrats

where's the fix log?

Hasn't been updated yet.

Give us a bone

and for linux ?????

What is the plan for next release ?
Do we need to post bug/request on RAMBO ?

I think so. RAMBO is still the only offical bug report for R2

OK. Thx

I miss a detailed change-log, as we can see it for R3 ....

I can find this one, but not sure what got implemented in the end 
- http://www.rebol.com/docs/changes-2-7.html

I understand Brian's answer that it will be available, but it's simply 
not done yet.

Btw.. it would be nice to port the bugs from old tired Rambo to the 
CureCode hospital, where it's pretty visible which bug is fixed and 
if the fix is tested as well.

Is the download page for 2.7.8 easy to find?

as usualy http://www.rebol.com/download-view.html

So far win only

Thanks.... curious that this link does not yet show it http://www.rebol.com/download.html

Yes... the blog was released too early I think.

January 1 deadline

What found new : unbind, resolve, list-env, cd, ls, more, pwd, rm

I listed most of the changes above, except for the details of the 
Linux changes (which I don't know much about).

What we got in 2.7.8, that I know of:

- Bug fixes and enhancements to improve Cheyenne, and other apps 
that have to do similar stuff.

- Some native fixes for non-Windows platforms, particularly Linux. 
See ACCESS-OS.

- Environment variable stuff: GET-ENV expansion on Windows, SET-ENV, 
LIST-ENV

- Function fixes: SELECT object!, FIND object!, RUN enabled, LIST-REG/values

- R2/Forward: FUNCT/extern, LAST?, COLLECT-WORDS, RESOLVE, APPLY 
fixes, EXTRACT fixes, ASCII? fixes, LATIN1? fixes, INVALID-UTF?, 
CD, LS, MORE, PWD, RM

no ODBC fix ?

where more than one date is passed as a parameter?

We really need to make a roadmap for a 2.8 version of R2 !

I don't know, but Carl didn't mention it. We won't have as long a 
wait until the next release - Carl is multitasking.

2.7.8 was due early last year

Nve, we will have 2.7.10, etc. We don't plan a 2.8 yet.

Past performance is not predictor of future development practices 
in the REBOL world, you should know that by now. Think about how 
different last year was from the year before.

Past predictions of future development are consistently wrong .. 
you should now that by now

Yup, that too. Especially when they are based on what happened in 
the past.

As R3 has no official release still in alpha mode and because there's 
a big shift between R2 and R3, professionnals user's of REBOL really 
need to have a plan for R2 support, R2 bug fixes, R2 enhancement...

Is there's something to migrate script written in R2 to script in 
R3 ?

Not yet, as R3 is a bit of a moving target. Most R2 code will run 
in R3 if it doesn't use any GUI or port code. Part of the migration 
strategy has been the R2/Forward stuff, which allows you to write 
code in a more R3-like way in R2. Plus, we are backporting some of 
the native enhancements that are additive rather than changing, like 
SELECT on objects.