World: r3wp

The point is that previous experience with Wine shows it is not a 
stable platform to test on. That's why there is a discussion.

There's no Linux port of R3.

As I said, previous experience shows Windows is not a stable platform. 
What´s the point of any software development at all?

Kaj, you're missing the point completely. Do you blame id Software 
if Wine doesn't run Quake 4 properly?

If it´s this difficult to report a bug, then I will refrain from 
it

Curecode is the appropriate channel to report bugs

Stable platform = API stable = no change in underlying behavior. 
For Wine, it means it should behave identically to Windows. It seems 
not to be the case.

Henrik, what were the earlier wine issues that were fixed?

Kaj - you are just angry, that is all. Gee, so ppl complain, that 
there is no thing to test, and once there is an ALPHA, we hear things 
like "Isn't the point of REBOL to be usable?". And I thought, that 
you are SW developer. Beucase as such, how can you post any such 
sentence to Alpha SW?

Graham, an issue with 100% CPU usage every time a GUI was invoked.

Yes, but I´m not angry about the bugs, I just got angry about the 
reception

Besides that - who said, that bugs are not being fixed? Just go to 
release page and see what bugs were fixed for what particular release. 
We are finally getting there, but not there. Post your finding to 
CureCode, mark it, and let's see how critical it is or if it could 
be fixed with some higher priority. What is point here?

Graham: Carl found that some Wine libraries were of the incorrect 
version in the public builds.

So,it was a wine issue?

Graham, yes.

uh, on Vista and R2 I get:

>> dir? %work
== true
>> dir? %work/
== true
>> file? %work
== true
>> file? %work/
== true


Is that correct? :-) There is a work directory on my system, so how 
is that "file? %work/ reports true?

Isn't a directory also a file?

file? looks at the datatype

Kaj, I understand it's very frustrating only to be able to do limited 
testing. Being on OSX, I have to waste a lot of resources running 
WinXP in VMWare to test R3. I think it's a good idea to keep some 
talks going with the Wine people to make sure and verify that it's 
a Wine bug rather than an R3 bug. This is in order to keep Wine out 
of Carl's hair, so to speak, so he can continue development of R3 
as rapidly as possible. I deeply respect the daunting task it is 
to emulate the Windows API and I would not like to be in their shoes.

If you reread the above, you´ll see that I reported more bugs than 
this issue on WINE

I´ve been muddling through bugs all night

In any case, by your own admission, you´re the wrong people to talk 
to

that's correct.

BTW, this is probably not common knowledge, but R3 does not officially 
support Win95/98/ME, even if it may run there. I don't know if that 
may have any effect on Wine behavior.

I like the current dir? function in R3.  I think it works well.

We just need to understand how it operates in R3.  It's more of an 
adjustment in our thinking than a problem.

Is it normal in R3 to get a bunch of output in the console when saving 
a file?  save %blah "test"

yes, that is for two reasons. when saving a file, a port is returned, 
which was not the case before. the other reason is that objects are 
now returned to the console.

Ok, just wanted to make sure.  That helps.  Thanks Henrik.

Switching from AltME to RebDev chat has been very hard for me and 
since I am not a core developer I will be in read only mode until 
the GUI version will be released.

However I am not negative about how things are going. We finally 
have a pubblic alpha. an upgrade mechanism, an internal chat system. 
GUI is going to be developed and also documentation reviewed.

We already have GUI in R3 but you gotta load it first via load-gui. 
 I know it is still in development though.

Yes Paul I know but it is not complete and Henrik will be back to 
work on it in march.

It will be the foundation for the RebDev GUI side.
Everyone seems now in the same cavern where Carl retired himself.

Oh, I didn't know he was the only one working on it.

I'm not a fan of rebdev either but I view it as the catalyst for 
the GUI side of it.

I suppose both Carl and Henrik ar working on it while Cyphre will 
be back soon to fix some lower level issues.

Well the good thing is that I see lots of activity on R3.

Let's count our blessings here.   At least it is active.

However we are in the middle of a big change. Once the new messaging 
system and the GUI will be complete the whole speed of REBOL3 will 
shift up again.

I think Carl is very excited about things right now and motivated 
towards getting R3 fixed, stable, enhanced, and released.

Expect a 2 months where everyone involved will work in the cavern 
with Carl and then we will finally have something to start with seriously.

March is fine for me.  About that time I really expect my project 
to be in a mature state via 2.7.6 and can then hopefully begin porting 
at that time.

By now, we could only try to test REBOL3 and report bugs in CureCode. 
It is still a big thing.

For discussion with the development team we need to use the chat 
system as everything else (AltME) seems abandoned.

My project still have everything they need in REBOL2. SQLLite, REBGUI 
and REBOL Itself.
When things will be mature I'll start to port my projects to R3.

Lets not forget it is a complete new beginning. While R2 is a mature 
man R3 is still an infant.

It is nice to see lot of interest around it. This mean that the child 
will be well supported by an extended family of relatives ;-)

Kaj, please report bugs in CureCode. And here if you like, but the 
important place to report them is in CureCode. If you have problems 
making an account on CureCode say so here or in the !CureCode group. 
Please mention that you are running on WINE in the bug, in case your 
bug is WINE-specific. We have no problems with supporting REBOL properly 
on WINE, but at least I can't test it since I am running Windows.

It is easy to report bugs in CureCode, and they get reviewed, tested, 
discussed and eventually fixed. It is much easier to report bugs 
in CureCode than it is to do so here. Please don't complain about 
the need to report bugs - that is what alpha means.

It doesn't matter that WINE is not a stable platform to test on - 
it's fixable, whereas Windows is not. We will try to make things 
work.

However, native support for R3 on Linux and other WINE platforms 
will continue to be a higher priority than WINE support.