Hi, Geoff, thanks for weighing in.

On Feb 25, 12:14 am, modius <[EMAIL PROTECTED]> wrote:
> This is a legacy issue that really needs to be fixed.  core should not
> have any dependencies on the presence of any plugin.

I suspected you would feel this way -- I will go ahead and raise a bug
on this.

> Perhaps we should be providing superDelete() by default on any core
> content type that could reasonably be expected to be extended?

I was actually going to suggest that it might not be a bad idea to
provide matching superXXX() methods in the core types for any method
that calls super.XXX() on the base class, as this would allow for the
choice of extending either the parent class or the "grandparent"
abstract class. That may very well be overkill, however, as it feels a
bit like an edge case that will not come up very often...

> Btw what are you extending delete for?  Is it something that might be
> an improvement to the default behaviour of an image object?

Well, I was mainly trying to work around the error I mentioned, but I
the course of doing so I decided to also add in some cross-checking
for deletion of images linked to my custom types.

I think that the most useful way the dmImage delete() method could be
enhanced would be to add an optional argument for a list of array
tables to query for references to the image object. For built-in
support of the system types, the value could default to:

"dmNavigation_aObjectIDs,dmHTML_aObjectIDs"

Then, if I wanted to add checking for image references from a custom
type, I could extend dmImage and call something like:

super.delete(stObj.objectID,
"dmNavigation_aObjectIDs,dmHTML_aObjectIDs,myCustomType_aRelatedIDs")

If you think this is a good idea I will go ahead and raise an
enhancement request for it. Thanks again,

--
Ezra Parker
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-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/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to