http://lest.iluminat.cz/ has been updated with conditions. Everything can be replaced with condition now. Few examples: either why-not? div span "content" div either [now/time < 12:00] .am .pm "Hello" etc...
Maxim
An Update on StoneDB. --------- I am FINALLY delivering the first prototype for review tomorrow. Its taken quite some time but its improved a lot, it now even has an API layer, which is the basis for the forthcomming query functionality. :-)
right now, I'm building it as a DLL, linking to it in R2 and am using memory buffers with parse for i/o with the DB. almost every part of the system is aimed at maximizing resources and reducing or practically eliminating memory fragmentation. Not all of the design is implemented, but what is done is extremely robust with a full stack error reporting mechanism, optional db function tracing log file (for very detailed support debugging, without debugger mode compilation).
Although only about 10% of the Server is implemented (in terms of having a robust multi-threaded multi-client "server") the storage and low-level api are already at v2. its all been re-implemented at least twice, sometimes even reviewed again.
I still can't say when I'll be opening up the source publicly. right now, I've got no time to handle any type of request or discussions on it, so there really is no point in wasting precious time on this.
this week and the next I will be adding the set theory query engine called AQUA . AQUA is an acronym for Accumulate & Qualify. basically a system which scrubs the relationships and data of any item, qualified by various properties where each phase can either accumulate more data or reduce it by qualifying it against many generic properties.
by supplying a simple chain of operations, you can traverse any dataset (in fact, several superimposed/remodeled versions of datasets) and try to find arbitrary and generic patterns within.
if you read through these you'll see that from an information system point of view they are closely related. I am not trying to support and describe my system using all of the (relatively strict) theory and some of the rather complex math lingo involved, but I am definitely reading this stuff over and over and it is influencing the design and philosophy of the entire system. for example, datasets are called domains, queries are perfomed using set operations, there will be possibility for some domains to be functional, so given an node ID, instead of storing a value, it calculates it on the fly, and you'll be able to build directed graphs of information even when using these computed datasets!
and the fun part of this is that your datasets need not be symmetric, but any sufficiently defined related sets of data will return a result. for example, any sales without a related date are automatically rejected from the above query. we could still get other data from those sales, if criteria is not related to dates.
all of this without knowing anything of the DB or how its supposed to be setup. If data is there, it browses it and extract datasets without requiring you to "search" thru gigabytes of information... it uses item associations directly for extremely fast navigation/extraction.
Kaj
I've updated my binary downloads with the latest Red changes:
In particular, I added FreeBSD binaries. It's likely that some of the names and versions of shared libraries used by my bindings need to be adapted for FreeBSD, so I'm interested in reports of success or failure, and in updates to the names or versions of the library files on FreeBSD.
I tried to replace my simple CALL implementation by Bruno Anselme's new one, but his includes an incomplete copy of my C library binding, so they conflict and I can't use it in its current form.
FYI, I have upgraded my server to a safe openssl version, so CureCode and other web apps I am operating are protected for the infamous heartbleed vulnerability.
Maxim
Concerning Heartbleed:
If you are running commercial apps and have used OpenSSL for the last two years, you should force people to use new SSL certificates if the site contains sensitive information, even if you have patched your server. the keys it contains may have already been breached and no one would know.
Version 0 of Rebol3 interpreter for SL4A is out http://giuliolunati.altervista.org/Rebol3/Rebol3ForAndroid.apk courtesy of Giulio Lunati. Once you install it from the apk, you start up SL4a and there will be a demo.reb script. If you don't have sl4a, you'll need to install it first.
I have the StackOverflow chat client now able to grab your StackExchange cookies if you provide the credentials. Windows only as linux/https not working it seems. See https://github.com/gchiu/RSOChat
Thanks to Barry Walsh (draegtun), Github now should have significantly improved detection of Rebol code when using the .r suffix. For example, red/red is now more correctly identified to consist of ~99% Rebol code.
Further, the .reb suffix is now also supported to unambiguously identify (and thus: syntax highlight) Rebol code. For example:
Finally, some changes I pushed to Pygments a while ago seem to now be live on Github as well. That means that most Rebol files were syntax highlighting was previously somewhat broken should now be more properly highlighted. One case I can remember which was previously broken is prot-http.r from the R3 sources:
Just as Nenad's original, this is a pure-Rebol implementation of the MySQL protocol.
Together with Andrea G's mysql binding written as a R3 extension (mentioned by Graham above), there are now have at least two MySQL drivers publically available for Rebol 3.