[REBOL] Re: Bugs, patches and distributed systems
From: jason:cunliffe:verizon at: 25-Mar-2002 7:46
> Here's a suggestion that works at least for mezzanine-level system functions.
>
> There should be something like Patches.r in my application directory. I can
> download the most recent Patches.r from RT as often as I like.
>
> Patches.r Isn't just the latest source for each function. It's cleverer than
> that. If a function has been modified three times since the major release,
> patches.r contains all three versions. Rebol has some start-up magic that
> lets me accept or reject the patches I need, e.g.
>
> rebol -p [layout 1.2.1 view 1.2.2 make-face original]
RVS - rebol versioning system
great idea!
Recently I have been reading up on CVS [concurrent versioning system] and
wondering how to base a rebol/vanilla dynasnip extension on the idea. I have
been interested in how it might work for media content, sequences, collections,
metadata and associations.
..Kind of general purpose VCR for media-oriented metadata. The reason I
especially like to do this in rebol is because it seems to encourage a very
granular approach. Simplexity system where each little piece of rebol is just
smart enough. But a powerful whole system set of behaviors can emerge. The way
rebol treats everything as data makes this seem more 'natural'.
A fascinating article for inspiration is the new[ly] [named] science of
'Proteomics'. Check out the April issue of Scientific American Magazine for an
clear introduction.
./Jason
