[Cuis] Cuis-Features

[Ken Dickey]

On Fri, 5 Jul 2013 17:46:34 -0700
Casey Ransberger <casey.obrien.r at gmail.com> wrote:

> So if I had a feature B that depended on the presence of a feature A, would
> sending #require to B automatically load A as well?

Right.  Specifically,

 (Feature name: #'Morphic-Games-Solitaire' version: 1 revision: 0) require.

Loads
  Compression
  Graphics-Files-Additional
  Morphic-Games-Solitaire

If after this I invoke:

 (Feature name: #Sound version: 1 revision: 0) require.
  
This only loads
   Sound
because the other requirements are satisfied.

> Next question: have you guys thought about a UI for this?

What about the Code Browser?

How about "converting" a Category Name into a package? 

Select the category, right-click to bring up the context menu, select "Make into Package" and get a version 1 revision 0 <category-name>.pck.st file.

The Package Manager could show a Provides version.revision column.  Select the package to increment a version number or add one or more requirements.  Alternately, one might multi-select packages to create a requirements set, then select the package which needs them.

Just a thought.  Juan is the guy here.


> Ken, this is really cool.

Hey, Cuis is really cool.  I'm just trying to keep the breeze blowing in the right direction.  ;^)

-- 
Ken [dot] Dickey [at] whidbey [dot] com