Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: Idea for []...

From: greggirwin:mindspring at: 19-Mar-2004 12:18

Max, Robert, et al (pardon any disjointed-ness, this was composed in small pieces and spare moments) Sunanda and I are both very busy for the next few weeks, but we'll keep track of the suggestions made here regarding, so keep them coming. MOA> so far, it seems to me that rebolers don't play well together MOA> (code-wise) unless RT is giving its approval. My experience is that REBOLers play *very* well together. I've worked on a number of projects with people from this list and other channels. What I see as different about REBOL is that all the things we do remain external from the main distro (as I think it should be right now). Even if we come up with a great library, it won't ship with REBOL, so people still have to look for it. This is a big difference compared to other systems. To support the reusable/shared code approach in a general way, I think we need to have some other pieces in place (e.g. how to organize and define "projects", include other files, etc.). This is where RT comes into play. There are various INCLUDE mechanisms out there, but RT has their own (PREBOL); which one to support? We'd all like to see module support in REBOL (planned and rumored), but if we build our own it could be made obsolete when their native mechanism becomes available. So we wait...and build things for ourselves in the meantime. Package support is a great example. Should it be RIP, ZIP, RPM, doc'd, with metadata, allow 'includes, etc. We talked about a lot of things, and would still be talking if Sunanda hadn't taken the initiative to get *something* out there for comment and use. A library approach like Boost might help, and I think that's something can support, though maybe in a less formal manner. I looked at Boost (and CPAN, Parnassus, etc.) quite a bit when we set up We want to improve the guidelines we provide to submitters, without being overbearing in our formality about it.
>> Anyway, with we have a very good reference point. >> At the moment it's a portal to get access to scripts, someone owns >> and updates. Scripts are independent. The library people introduced >> the idea of packages, so now I can add collections of scripts that >> are related. But still it's only a one-person show.
People can collaborate via Scripts can be shared by multiple owners, though I don't know how many people are using that feature. I'm all for making things better and I think is the right place to get folks together to do it. Sunanda has made a huge difference in the community by taking the initiative and doing so much work at, giving us something to build on. We're looking now at making more attractive and useful, so let us know what you like (or don't), what you want to see in the future, and what you want to do to help! Thanks! -- Gregg