Major rewrite: - Same script works with both R3 and Red - Block format has changed from flat (e.g. [a 1 b 2]) to blocked ([[a 1][b 2]]) - Single context with functions that can be selectively exported to global context - Functions simplified and non-core options split off (e.g. munge/list -> list, munge/save -> write-dsv) - General speed and efficiency improvements - Munge function supports 1st column binary search - OLEDB [Windows only] functions (e.g. load-excel) work with both 64bit R3 and 32bit Red - Some missing Red functions (e.g. delete, delete-dir) implemented via CALL [Windows only]
This is a preview release: - to-rebol-date and to-string-date do not work fully with Red (as it currently lacks date! support) - some functions have not yet been enhanced to work on non-Windows systems - write-excel requires 7-Zip to be installed and will only work on Windows - The now* function is available when run from Red and provides many [date related] options missing from now - Basic documentation is available at http://dobeash.com/files/munge3.html
I have claimed the name R3N on github and set it up as an organisation. The purpose of this 'organisation' is to overcome the status quo on the rebol/rebol repository this community has been put in. In r3n the github repo of the REN-C repository has been cloned. Graham Chiu and Giulio Lunati have been added as owners of the organisation. Work on collecting R3 stuff has begun. Making a start on https://github.com/r3n
Documenting the Red development project: https://github.com/reddoc/develop/wiki This project is to help interested developers to quickly get on speed in the codebase. All interested are invited to add to this project,so for example programmers with Linux background can help on the GTK3 branch.
Minor fixes: - added /preserve refinement for load-dsv - now support added for Red - removed dependency on 7zip - read-pdf now works on Mac / *nix - write-excel now works on Mac / *nix
I started a place to collect Red scripts that the community members might like to share with others, a bit like rebol.org it is https://github.com/freered/Code Together with it comes a place to collect valuable documentation for cooperating on the yet unexplored territories like 64 bit and GC. Also there is a fork to host cooperation of community members that want to work on these things without disturbing the official branch. https://github.com/freered All comes with a own gitter chat room https://gitter.im/free-red
Google gives new users on their cloud service USD300 credit which is enough to run a couple of VMs for a year. Here's a short HOWTO on how to setup CGI on a Google Compute instance. Any errors are my own and fixes/suggestions appreciated. https://github.com/r3n/renclib/wiki/CGI-on-Google-Compute
AWS is free for 1 year too.
I dont know if it s the right place but i m searching after any trial of a integrated voting machine based on the blockchaine (any type of : ethereum or bitcoin). Is there any open sourced code implemented in any version of Rebol ?
Not the right place .. this is announce. Use announce reply to anothe channel. and there is no blockchain code that is open for Rebol*
send email@example.com "Come back home, all is forgiven!"
After the recent outage at rebol.org and the subsequent postiing of the script library on github, I downloaded my own personal copy of the library out of fear of another disruption. I have that copy tucked away on my computer, but I also put it on my little web site in case such a backup would be useful to others. If that was improper in any way I would be happy to delete it, and would not be offended. The location is here: http://cobolrebol.com/pages/RebolOrgscripts/RebolOrgScript-index.html
Red release 0.6.3 is ready. Support of macOS. Next best in this release must be the test backend allowing automated testing of GUI!
Minor changes: - Simplified code now that Red 0.6.3 supports date! and delete - All test cases (200) now work with both R3 and Red 0.6.3 - Basic documentation available at http://www.dobeash.com/files/munge3.html
Minor changes: - Refactor to work with Rebol2 and Ren-C - All test cases (200+) now work with R2, R3, Ren-C and Red - Windows-specific features disabled on non-windows platforms - Updated http://www.dobeash.com/files/munge3.html to cover Excel, SQLCMD, SQLite, PDF dependencies
Implements a (largely) HTML5 compliant markup parser in Red and Ren-C and LOAD-MARKUP function using said parser. This is an experimental hybrid script and uses Red macros in a way that might conflict with other Red code--use with caution.
LOAD-MARKUP returns a block akin to Rebol 2's LOAD/MARKUP except that attributes are contained in a MAP! following the associated tag and self-closing tags are indicated by a </> closing tag following the tag or attributes (if present).
To do: tree-based model and DOM (likely similar to AltXML). Some work to be done here--the HTML5 rules for tree-building are labyrinthine.
I've added the tree constructor per the HTML5 spec and added a few more standard error codes (with source positions). There's a few kinks--while table nesting seems to be working and for the most part misnested formatting is resolved properly, there are still failures on the odd test or two*.
It's all still a bit slow for my liking--the parser is set up near exactly the way the spec suggests which in no way works to Rebol's (or Red's) parsing strength--pretty sure that's ripe for optimization**. Also still not sure about my choice of linked lists for trees either--there's a real gain in fidelity (good for editing when the time comes), but I'm not convinced there's not an insurmountable hit on navigation speed***.
Am still working in a Red/Ren-C compatible way (has it's challenges but is great for rooting out bugs!). In Red you can just DO the raw github url. In Ren-C, you can: import <markup>
LOAD-HTML will return a document node from a given string, MARKUP-AS-BLOCK will convert that into a more familiar block hierarchy. If you get an actual Rebol/Red error, let me know--shouldn't happen.
*I feel as if I've read the 'Adoption Agency' algorithm 30 times over and still don't understand how it's supposed to work **my only reservation here is while it does slow things down, it would work well with an incremental byte stream, say from a network source, where that might not be as noticeable ***if anyone has any thoughts on the efficacy of linked lists, would be interested to hear--have two versions: one with maps (no key/value clashes) and one with blocks (does seem faster)