World: r3wp

i do after if a load %my-copy-db.r

the function db-create is ok then !-) ............but need much more 
to be good for us

In general you would be very lucky if a fairly large R2 product works 
directly under R3.

i thing it is important for every body who use rebdb !!!!

or perhaps R3 guru would give us a better way to do this ;-)

is the same for rebgui............il would like to see a R3

a R3 demo that do all rebgui do

The table name you supply to db-create should be a word! not a string!

>> ? db-create

USAGE:

	DB-CREATE 'table columns

DESCRIPTION:

	Creates a table.

	DB-CREATE is a function value
.

ARGUMENTS:

	table (word!)
	
	columns -- Column names (block!)

But when you correct that you get a real R3 compatability error:

>> db-create my-table [id date norm]

 ** Script error: write does not allow string! for its value argument

** Where: db-create

** Near: db-create my-table [id date norm]

R3 will not be very compatible with R2. You will almost always need 
some kind of porting process, so this is up to the authors of rebdb 
and rebgui, if they want to do that.

Claude and Peter, as I reported here one or two weeks ago, I ported 
my CMS of around two thousand lines

It took a full week to compensate for the changes and bugs. I think 
about half of that could be prevented after fixes and more attention 
to compatibility

The other half is due to planned changes to the design of R3

Anything but the smallest scripts will be affected

ok seem we must do a real port effot from R2 script to R3 !!!!!

Sure.!

That's what R2-Forward is for.

Demo is crashing instantly after fetching in a34, anybody has experienced 
the same?

new alpha?

Henrik: yes. But I've got problems too here on Windows.

Pavel:  Having same problem with r3-a34.exe

In fact, it's not the demo. Doing a "load-gui" from the console crashes 
all.

confirmed

I'm running r3-a35 and load-gui is working for me.

view [image %/path-to-img/img.jpg] 

doesn't work for me.

make image! 88x88 => Crash is marked as fixed. that's interesting.

Hrm...  I suppose this might have something to do with it.

>> img: load %/t/1.jpg
** Script error: load-jpeg has no value
** Where: case load
** Near: case [
    string? source [to-binary source]
    binary? sou...

** Note: use WHY? for more about this error

ammon, image loading is not available at this time.

there used to be a jpeg loader, but it has been removed for now due 
to changes in LOAD and we're awaiting mediatypes, which would handle 
image loading.

I guess I'll just have to keep waiting... 

Any idea when that might be done?

Not yet. I believe there are other things that need to be done first.

After upgrading to r3-a35.exe, the TextView demo keeps crashing for 
me.

looks like changes in the GUI dialect

Henrik: this demo never worked before for me.

I haven't tried it in a while, so it may be an older bug, but it 
has been working for me in the past.

Ok. I've read that it was crashing somewhere here, but don't remember 
in wich group.

looking at the code, it appears to be correct, so I don't know what 
change has occurred.

I can see now that it tries to load main.r, but that will fail. This 
gives a dialect error instead of a file error. Interesting.

submitted as bug 653.

Henrik: thanks. Also, I wonder what's new in r3-a35 ?

kib2, go to http://curecode.org/rebol3/view-tickets.rsp

and filte by "Recent changes". The gray entries are the changes.

Nice!

There's an even better way if you are logged in to CureCode:


Select "Change Log" from the menu bar and it lists the tickets fixed 
in the release.


You can look at previous release by using a drop down version selecter.

For changelog - bewary - the list is empty unless you select concrete 
product at the top right section of the screen ...

at R3-alpha world Carl stated that he found a bug in rich-text gamma 
correction.

Carl says that rebol.net will go down for a bit, due to moving it 
to a new server.

Is there any 'Challenge' channel for submitting a problem ?

sorry : wrong channel

alpha 36 released.

Seems like Text View has not been fixed yet.