On Nov 22, 10:20 am, "Mark Mandel" <[EMAIL PROTECTED]> wrote:
> Gavin,
>
> It looks like you really need to
> read:http://docs.transfer-orm.com/wiki/Managing_Relationships_and_Composit...
>
> And I would highly recommend looking at the tBlog example
> app:http://docs.transfer-orm.com/wiki/Example_Code.cfm#tBlog
>
> Which outlines all the different composition types, and how to utilise them.
>
> If you also read:http://docs.transfer-orm.com/wiki/Generated_Methods.cfm
>
> You will see that the arguments required for the methods generated do
> not match up to what you are passing in.
>
> Mark
Just for the record I have read the docs at least two dozen times.
I have read through the tBlog application almost as many.
I'm certainly not stupid, by any means... it just simply isn't sinking
in.
Perhaps it is simply that I have no real-world OO experience.
So trying to think (learn) objects and Transfer at the same time ...
For an example of something that I don't get is;
In the tBlog application there is the following code at the beginning
of a lot of the templates (I.e listPost, listUser etc)
transfer = application.transferFactory.getTransfer();
Is this necessary?
Could I not just do this?
application.transfer = application.transferFactory.getTransfer();
and store it once in the application scope?
Is there any value in doing it in the instance scope as opposed to a
persistent one? (I know application / session aren't (literally)
persisted - but you know what I mean!)
I can;t even remember where I "got" the code to put it nto the
appliation scope.
Perhaps it was from Bob Silverberg's tutorials... but I can't even
find it in there at the moment...
Then again - maybe there-in lies the problem - trying to take the
examples of different people / architectures and trying to
Though it did make sense to me at the time, that if I was going to the
effort of doing things OO, then I should also be doing things with an
appropriate framework / methodology from the get-go... as opposed to
doing it "simply" and then having to refactor it later.
I agree there is no reason to assume that Bob's way is the right way,
or the only way...
But the theory in his posts made sense to me (even if the code
didn't).
I am the kind of guy who likes rules / design standards. - it helps to
keep me inline - not just my code.
Anyway - looks like I'll go and read the examples apps again and the
docs - again... tough to be honest ... I really feel like I am a
flogging a dead horse at the moment.
--~--~---------~--~----~------------~-------~--~----~
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer
You received this message because you are subscribed to the Google Groups
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/transfer-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
