World: r3wp

From time to time I watch http://haxe.org/doc

Pekr: "...author's ignorance to co-work with the community..." - 
this time you are wrong. It is your ignorance, Pekr.

The big problem with it is that anything else becomes painful to 
work with.


That is so true. Once you realize, how easy development can be, it's 
a pain to work with just about any other language. The difference 
is like when humans moved from carving letters into stone to using 
a printing press a la Gutenberg.


If you're forced to use other languages, it's maybe not a good idea 
to learn REBOL!? :) Jokes aside, learning REBOL was the largest change 
for me in my programming career.

SFarber, regarding gui toolkits, maybe Qt is worth a look. Was created 
by norwegian Trolltech and acquired by Nokia:
http://qt.nokia.com/products/

I remember, it looked promising, when it came out. I don't know, 
if it still holds.

Qt is very popular, but it is written in C++, which from our perspective 
means that it is much harder to write bindings to other languages 
for than for toolkits written in C

Isn't it possible to make a C wrapper for Qt? Maybe it is done already?

Yes, but that's the thing: before you can write a binding to your 
language, you must write a binding to C in C++. So it's double work 
and you must be fluent in C++ as well

I'm not sure, but I don't think the bindings are usually written 
with that one intermediate level in C. They're usually meshes of 
C++ and the target language in some tool such as SWIG

And as always, writing it once is not enough. You also have to maintain 
it when Qt changes

Too bad. :/

Maybe it is possible in an easy way, as I read this on the wiki:

Qt can also be used in several other programming languages via language 
bindings.
From: http://en.wikipedia.org/wiki/Qt_%28framework%29

Sure, that's after the hard work is done

If you evaluate toolkits, you'll see a sharp distinction in available 
bindings between C and C++ subsystems, and in how current the bindings 
are

Ladislav - I don't mind you thinking I am wrong, as I might be easily 
misunderstood. This time though, I insist. You either know what has 
to be done to support your effort, or you don't, which is often the 
case of good engineers ...

I wonder what happens with Qt. Is that open-sourced? Because there 
is no place for Qt at Nokia now, after they became MS HW house?

And Intel seems to be closing MeeGo down too :-( Meego, as a mobile 
OS, was not tied to JAVA, like Android is. You could run Python, 
PHP - it would be probably a good target for R3 without much effort 
...

probably a good target for R3 without much effort
 ... are you volunteering then? ;)

For Meego? If the person informing me about the architecture was 
correct, then it is "normal" Linux, so we would need ARM kernel port 
(which can be done by Carl only), and Hostkit port. What's here to 
volunteer for? And would you support dying platform?

I was just trying to state, that we are not lucky in the mobile area, 
as to support iOS, Android, WP, all require special aproach, not 
just "normal" OS port ....

R3 probably runs on x86 MeeGo already. Someone interested in MeeGo 
should just try.

Did not know x86 was supported by Meego ....

Does anybody know situation on BlackBerries? OS8 should be QNX based. 
QNX has C inteface. IIRC, there was some veeeery old port of R2. 
Hopefully there's not some special API to support, I mean, in JAVA, 
etc.

http://www.osnews.com/story/25125/Samsung_Denies_webOS_Plans_Intel_Denies_it_s_Dropping_MeeGo

Ah, should not read Czech "news" servers :-) They reported on Digitimes 
article just yesterday :-)

It was just flame bait

I wonder, if following info might be important for the Meego - https://meego.com/community/blogs/rudolfstreif/2011/meego-ivi-achieves-genivi-compliance

If you're targeting cars :-)

No, I just think, that as a platform (OS), it might find its niche 
market, not necessarily dying. Then WebOS might be in worse condition. 
Samsung has BADA, so they don't need it, and I am not sure anyone 
else will buy it ... We will see - it seems that in mobile market, 
there are just following player - iOS, Android, WP7, then BB (QNX), 
Bada (Samsung), Symbian (Nokia)

You either know what has to be done to support your effort, or you 
don't, which is often the case of good engineers ...

 - that is typical for you, an unrelated thing. You ignored Karl Robillard's 
 effort, so it is your ignorance. I did not.

P.S. you still are ignoring his effort, attributing your own ignorance 
to Karl.

Ah, sorry for being off topic in this group

>> a/weekday: 2
** Script error: cannot set weekday in path a/weekday:

>> a/day: 12
== 12

IMO the first one should work too.

Weekday is a function of day, month, and year - if it's being set, 
which of those should change, and in which direction?

Don't get what you mean. If I have a date and I set the weekday, 
it should just set the day part to the given weekday.

So, keep the date, just set: monday, tuesday, ...

Izkata makes sense. You can't keep the date while changing the day

Sure, I don't want to keep the date. I want to change it.

I guess, that what Izkata wanted to mention was, that it is not obvious 
in what direction should such a change be?

Ah... Since it's weekday, it's the same week. So, when current day 
is Sunday, we move backward. And if it's Monday we move forward.

There are countries that let the week start on Sunday...

ISO8601 supports the notion of Monday being Day 1 of the week, so 
Robert's suggested behavior would be ISO compliant.

But ... not sure this is an essential native. It would be a fun mezzanine 
to write, though.

Agreed

Besides bugs to be fixed and Carl's missing, what keeps R3 from going 
to Beta? Any new features?

Some functions still need to be finished compared to R2, such as 
SORT

And of course, there was this strategy that R3 can't be released 
before the GUI is finished

The licence is also still undecided

SORT is totally unnecessary for R3 to become beta, IMO (you can use 
any algorithm written in REBOL, e.g.

http://www.fm.tul.cz/~ladislav/rebol/msort.r

, etc.

It's in there, and it's incomplete and buggy. That's no state for 
beta

There are important issues, but surely not this one

Tell that to Carl