Posted by Dale Henrichs on Sep 19, 2012; 12:05am
URL: https://forum.world.st/Smalltalk-X-port-of-Metacello-tp4647981p4648021.html

Jan,

I decided to take a quick look and then put together a little guide for you[1]. I thought I'd end up with more method links than I did ... it actually looks like getting the load order for your packages will be pretty straight forward ... When I moved the methods up from the MC packages to Core I pushed most of the stuff that you need except a couple of methods that you need for your own package spec and a couple of methods for your version spec ... the rest of the stuff will be occupied by your customizations for your loader ...

Dale

[1] https://gist.github.com/3746823

----- Original Message -----
| From: "Jan Vrany" <[hidden email]>
| To: [hidden email]
| Sent: Tuesday, September 18, 2012 4:47:46 PM
| Subject: Re: [Metacello] Smalltalk/X port of Metacello
|
| Dale,
|
| > | >
| > | > At ESUG when I said that I didn't like the split that I had ...
| > | > The
| > | > package spec is one of the areas that may or may not have some
| > | > commonality ... I found quite a bit that could be moved from MC
| > | > to
| > | > Core for projects, but not being familiar with your needs for
| > | > packages, I wasn't able to see much commonality ... off the bat
| > | > ... looking at your implementation of packages may reveal some
| > | > common code ...
| > |
| > | Ok, that means I have to bake this cake completely myself :-)
| >
| > Nope, I think that we can extract out big hunks of code that you
| > can leverage.
| >
| > |
| > | What I basically need is to "resolve" whole project spec into
| > | flat
| > | (ideally topologically ordered) list of package thingies
| > | (say MetacelloStXPackage) with all the properties.
| >
| > Yes, this bit can be extracted out ... I can take a stab at
| > extracting out the code that you need ... it will be a combination
| > of package code and some loader code ... you will be rolling your
| > own loader, but I can certainly tease out the important bits ...
| > I'm kinda busy this week tho.
|
| That would be great. Once I get the list, my "loader" will do the
| rest.
|
| >
| > |
| > | While I can imagine how and where to hook in my
| > | MetacelloStXPackage
| > | and MetacelloStXPackageSpec, I've got lost how and where to get
| > | the list (or something from which I can easily construct such a
| > | list)
| > |
| > | Maybe you can give me some pointers - classnames where to start
| > | reading should be enough...
| >
| > Okay...I can do that ... I'll put together a method/class reading
| > list with the important bits about producing the ordered list of
| > packages ... should be able to have it for you tomorrow morning.
|
| No rush! I'll hardly have a time for Metacello next week, so no need
| for
| that tomorrow! I guess you have better things to do...
|
| Jan
|