TheBigPlan

Peter Simmons sent in a very useful suggestion:

> I was wondering if you had put any thought into making iTrack based on
> ZPatterns? It seems after reading the future page that ZPatterns would help
> you do some of the wanted things. I haven't used them much just read the
> readme about them and they seem to allow you to do useful things like
> relate containers (ie folders) to content files in a peer way. That is to
> say you have some issue and then you have child issues contained in the
> parent issue's container. I am not too sure how this would work.
> 
> Perhaps you could use a rack to store the issues and have a sheet provider
> for each issue which (if there is child issues) states teh rack used to
> store them.
> 
> It would take a fair amount of time to work out how ZPatterns work but the
> other benefits I see from basing it on them is that issues would then also
> be Catalog aware.

I haven't yet put much thought into how exactly it would fit in but I do feel that the next version should be based on ZPatterns. I recently went through the RIPP Model Talk again and read the ZPatterns Readme, it seemed to be the way to go

Not that I have made the final decision in favour of ZPatterns yet, but I'm very close to it - I need to do some investigation before that.

-Shalabh 20-Apr-2000

On second thoughts, I feel I should delay integration with ZPatterns by another version or two. It would take time for ZPatterns to get stable (and documented) and for me to grok what it is all about.

-Shalabh 26-Apr-2000

ZPatterns is the eventual goal, no doubt. But not for now.

-Shalabh 2-Jun-2000