Features + Package dependency + new GitHub organization + new packages

Hi Folks,

I've just done a first commit to
https://github.com/Cuis-Smalltalk/Development . This includes the cool
Features work by Ken Dickey, integrated and tweaked by yours truly. Now
packages can specify dependence on some Features, optionally including a
Version or a Version.Revision number. Dependency loading is automatic!
Just load the package you want (interactively or by Smalltalk code as in
the Feature class comment), and requirements will be automatically
loaded in proper order.

This new repo includes all the change sets since the release of Cuis 4.1
in April. ChangeSet 1749 includes Ken's Features code verbatim.
Subsequent change sets integrate, and modify it (some subtle bug fixes,
some style changes, lots of changes for integration). Ken, thanks for
this important contribution. Please feel free to review my later
changes, and challenge those you don't agree with. There is more work
needed to make package dependency work smoothly, especially on
integration with Package List and other tools...

I also included StyledTextEditor and a new SignalProcessing package with
stuff from PhotoSqueak, etc. The idea is to include there all packages
that are currently maintained. To contribute code, please use an image
with all these packages already loaded, and include new versions of
affected packages. This will ensure we don't break them while we evolve
Cuis.

The old repo is now obsolete.

Please test, complain if appropriate, report bugs or annoyances, and if
possible, enjoy.

Cheers,
Juan Vuletich

_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org

On Wed, 17 Jul 2013 22:55:28 -0300
Juan Vuletich <[hidden email]> wrote:

> Hi Folks,
>
> I've just done a first commit to
> https://github.com/Cuis-Smalltalk/Development .
...
> The old repo is now obsolete.

I just added the provides/requires text to my local copy of Morphic-Games-Solitaire.pck.st and everything came in smoooothh.  Cooooool !!

Note that previous images will break on trying to load this as they don't understand provide/require.

I would like to update the solitaire release in GitHub but the question arises what to do about the breakage for people who are/have picking/picked up the older images?

We can
  -- Add a note to all ReadMe's about requiring the image [4.1 1762]
  -- Clone projects with a different name [ugly!]
  -- Increment the version number of Pharo (4.2 ? 5.1 ?)
  -- ...

For the base image I was thinking that the "save number" would be the base revision (1762) and 4.1 might be version 41.

Any thoughts on this?

Juan, thanks for doing this.   It is sooooo coooool!!

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

_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org

I could think of updating the version no. to 4.2 to avoid confusion.

--Hannes

On 7/19/13, Ken Dickey <[hidden email]> wrote:
_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org

_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org

Yes, good idea. Will do it right now.

Cheers,
Juan Vuletich

On 7/19/2013 4:34 PM, H. Hirzel wrote:

_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org