[Sugar-devel] Unified bundles

[Wade Brainerd]

Good question.. My proposal is that activities which don't allow the
creation of brand new content (e.g. they require some initial content
to be used) become Content Viewers which is a special case of
Activity.

As it stands, I'm not sure whether they need to be merged into Sugar
or whether they can exist independently, with some sort of "This
bundle requires the Read Content Viewer".

My initial instinct was that they should be merged into Sugar.  But
now, given the inspiring "Unified objects" thread, I kind of think
they should be allowed to remain separate.

-Wade

On Wed, Apr 8, 2009 at 4:58 PM, James Simmons <jim.simmons at walgreens.com> wrote:
> Wade,
>
> Thanks for your response.  It clears up a lot now that I have a better idea
> of the purpose of Unified bundles.  There is still one question I have,
> which is what becomes of Activities in this scenario?  For instance, if you
> have a bundle containing a PDF, what happens to the Read activity to make
> that possible?  Does code from Read move out of the Activity and become part
> of Sugar?  What's left in Read if you do that?  Or does Read go away?
>
> James Simmons
>
>