[MTOS-dev] attaching vs. embedding assets to entries patch

[Byrne Reese]

Ok - now I just got confused. If this patch doesn't do much, then what
specifically does it do? Does it add a field to the UI? Does it simply make
the necessary database schema changes to allow for these types of
associations?

What specifically does it do and how is the user's experience inside of the
app affected?

Byrne


On 3/20/08 2:51 PM, "Timothy Appnel" <tim at appnel.com> wrote:

> Also the intent of this patch was to make it possible for things like
> attached assets. It does not implement that functionality.
> 
> Just to clarify this patch isn't going to do much -- in fact its
> missing a thing or two. Should a patch that needs the MT database
> schema incremented do so? What is the policy? Also since upgrade
> functions have always been a painful affair I wanted some feedback
> before attempting one. The routine should be pretty straight forward.
> It's the registry of the function and testing part that has always
> dogged me.
> 
> So I should have been more specific in the thoughts I was looking for.
> Does heading down this path (asset attachments in entries and pages)
> make sense for MT and is my approach to implementing those acceptable?
> 
> <tim/>