Hi mike,

>>I'm not sure what core function you talk about, but normally my applications contain only a very few core functions. In size it is hardly an argument to bother about functions you might not need in a certain project. I would agree if such PRG exceeds a one or few hundred K, but else I don't bother. The size difference is insignificant on a few MB project.

>Core may be the wrong word. I'm referring to functions that are atomic, like ISARRAY. It doesn't really belong anywhere, because it could be used in so many places.

Theoretically I think you're right. However practically it seems more of a hassle as you'll end up with many, many prgs in your project cluttering up your PM (given the fact we cannot classify functions and classes in the PM). Let's be honest, if you were to design a prg with the most common atomic functions in there how many KB will that take?

>>Interesting idea. I think this would be extremely usefull in large project with lots of resources.

>Actually, such a feature could be useful even in small projects.

but is extremely usefull in large projects.

>>I think this is about actual implementation which might be very different from the logical workings. In all honesty I don't think it should be stored in seperate classlibs but rather all resource in one big repository database from which the PM pulls only the neccesary resources from in order to build an executable.

>>All applications hook into this repository. Of course it must be possible to import and export repository items (using something like GUIIDs to make them unique world wide).

>>However, I'm aware we're talking about features that VFP never would have, but we can dream, can't we ?

>I don't think we should just dream. We can make it happen. That is your signature after all.

Well, you could subclass the project manager which copies the resource from a repository into a subdir of the application and build the application from there. However, I'm not sure how to copy changes of any item in the PM into the repository again.

I think this need a lot of thoughts before implementing. But you might be right, this beeing possible.

Walter,