Re: Need Input- Mike

From contact method Todd's Email Contact Method
Item Re: Need Input- Mike
Item version number 1
Mike, the advantages are:

* One item type instead of two (project, recursively defined)
* Avoids duplication of fields across two item types - Project and Task
both seem to need the same set of fields
* Allows progressive refinement into subprojects, whereas refining a Task
would require changing it to a Project (deleting and creating a new item
or changing its type) so it could hold other tasks
* Allows easy creation of a project without need to specify any tasks, but
later refinable into subprojects

With multiple inheritance we can treat Project as both a Collection and
an HTMLDocument, so it's DRY because you can embed both viewers in a
Project viewer.

Todd

Todd Davies *** email: davies@stanford.edu
Symbolic Systems Program *** phone: 1-650-723-4091
Stanford University *** fax: 1-650-723-5666
Stanford, CA, 94305-2150 *** web: www.stanford.edu/~davies
USA *** office: 460-040C

On Wed, 20 Jul 2011, Mike Mintz wrote:

> [Mike Mintz][1] commented on [Project Model Proposal][2]
> Comment title: [Re: Need Input- Mike][3]
>
> * * *
>
> Seems like it would work, but I'm not sure what the benefit is over
> the current proposal. Django has some bugs with multiple inheritance
> which have made things a bit harder for TextComment, but other than
> that it's technically feasible.
>
> On Wed, Jul 20, 2011 at 2:56 PM, Noam Ben-Avi <nbenavi@stanford.edu>; wrote:
>> Noam Ben-Avi commented on Project Model Proposal
>> Comment title: Need Input- Mike
>>
>> ________________________________
>>
>> Should we combine task and project into one super item that multiply
>> inherits html document and collection? Are there any intricacies of the Deme
>
>> architecture that would prevent this from happening?
>
>
> [1]: http://deme.stanford.edu/viewing/person/7
> [2]: http://deme.stanford.edu/viewing/htmldocument/207
> [3]: http://deme.stanford.edu/viewing/textcomment/403
>
>

For Internet Explorer users: Click on the Tools menu, located at the top of your browser window. When the drop-down menu appears, select the option labeled Full Screen.

For Chrome users:Click on the Chrome "wrench" icon, located in the upper right hand corner of your browser window. When the drop-down menu appears, select the choice labeled Full Screen.

For Firefox user:Click on the View menu, located at the top of your browser window. When the drop-down menu appears, select the option labeled Full Screen.

For Safari users: Safari currently does not support the ability to go fullscreen.