[REBOL] Re: [REBOL.org] [ANN] Packages: the next generation
From: SunandaDH:aol at: 4-May-2004 5:04
> Great work guys! I think these are a good solid steps forward for a REBOL
Let me reply to the bits I can affect, and leave others to respond to other
> *The descriptions, "package file", "linked script", "package script",
> "script from Library" look like they could be useful, but to me I'm not
> what they actually mean. Perhaps a link to a glossary of terms or help page
> would be good.
I'll update the documentation, and try to make it a bit clearer.
-- is a file in the package that the package owner has
uploaded. It may be a REBOL script, binary image or anything else
all the other terms (I think!) refer to scripts from the Library -- Example:
I may have uploaded a package that needs Andrew's values.r to work properly. I
don't need to upload a copy of values.r to the package. All I do when
defining the package is flag values.r as part of it. Repack.r will download the
latest copy of values.r when you download the package. Means there is only ever
one copy of values.r in the Library -- not dozens of copies in different
Comprehensive (though maybe not comprehensible) help about packages starts
> *It was not obvious to me that clicking on an item in the package pane
> invoke network activity. This could be important for someone on a slow
> The subtle psychological consequence is that a user could become worried
> that they don't know when and where to click to be most efficient.
More visual feedback on what is happening is on the list of things to do.
I agree that on slow links no one wants a program to start unexpectedly to
start long-running network operations (I got only a 56K modem link most of the
But total data transfer is very small -- well under 2K in most cases, unless
you actually click the download button.