wiki:BASE_RESOURCE_COMMONS_R0

Version 9 (modified by Tanya, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=BASE_RESOURCE_COMMONS_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

Resource is an object that can be persisted. Resources can be frame content. Resource can be used in the timeline.

Base resource model

  • UUID
  • target
    • data
    • URL
  • MetaInfo
  • comment

Resource Scope

  • Book
  • Local
  • Server

Types of resources

  • Text
    • Plain
    • RTF
    • HTML
  • Image
  • Audio
  • Movie
  • Book
  • Template
  • etc.

MetaInfo of the resource is:

  • info about the author of the resource
  • info about the date the resource was created
  • version of the resource
  • info when the resource was last modified
  • info who was the last that modified the resource
  • info about the dimensions of the image (if the target of the resource is an image)
  • etc.

Operations over a resource:

  • The resource can be created.
  • The resource can be modified (in a separate window - resource view).
  • The resource can be deleted.
  • The resource can be persisted.
  • The resource can be imported(exported) on a server.

Resource Manager manages:

  • Resource Versioning
  • Resource Security
  • Resource save/load

In the first revision of the task you should improve resource concept.

Task requirements

  • Resources should have a separate module.
  • The model of the resource should be defined.
  • It should be easily to add new kind of resource.
  • Check what we have for resources and modify where it is necessary. After this revision we are supposed to have the basic hierarchy of the resources.
  • Book should be made resource.
  • The metainfo problem
    • It should be easy to deal with the meta information of the resource. Think about an annotation @Meta("description").
    • You should provide that it is easily to add new meta information for a resource.

Task result

  • The result of this task should be source code.

Implementation idea

  • Create module org.sophie2.base.resources
  • @Meta("description") annotation for the meta info of the resource.

How to demo

  • Show the new module in eclipse.
  • Show the modified classes.
  • Run the application and demonstrate the usage of resources.
  • Ask if there are any questions.

Design

Implementation

(Implementation results should be described and linked here (from the wiki or the repository))

Testing

Comments

Log

Analysis:
Design:
Implementation:
Testing:
Comments: