[IDEA] [CRAZY] [WIP] A Smart Resource idea

*more info coming soon*
Looking at this I'd actually like to see a further level of abstraction. In what we have here, we assume that the create, update and delete functions differ. Actually As I'm typing this I'm thinking that what I'm proposing is probably more or less what we have right now. I'm not against this at all, but I wonder if perhaps it could be better for us to more rigorously enforce what a create method does. Does it navigate? From what level? Does it flash check? I can see what you're doing here, but splitting some of it apart even more giving more granularity and more files to look through. I dunno, I'm not sure I can say I'm 100% for it. I like idea of the object knowing it's locations in a predefined place for sure. and perhaps we should have a class that all "objects" inherit like this. I don't know if I wholly agree with the separation of the create to fit into a mold that has a pre/main/post structure. I guess that part I perhaps don't like is having a go_to_create......and a create function, there's a part of me that wants to register _actions_ so that this can be extended, for example, if go_to_create and go_to_update are so similar, why can't we have a go_to_location_for(action) function, (name is not important btw) whether this is access by passing a param, or whether we do fancy getattr work on it, I don't really mind. I guess what I'm trying to say is, it looks like we're trying to make things generic, but this isn't looking generic enough yet. Just my humble opinion and I love the direction. What a ramble. /me shuts up now. :facepunch: