ENGAGE-332: Exhibtion View and About share the same component code, but they offer very different presentations. They should be factored out as separate components.

Metadata

Source
ENGAGE-332
Type
Bug
Priority
Major
Status
Closed
Resolution
Won't Fix
Assignee
N/A
Reporter
Colin Clark
Created
2010-02-05T17:34:40.000-0500
Updated
2017-12-22T09:44:26.582-0500
Versions
  1. 0.3b
Fixed Versions
  1. 0.5
Component
  1. Exhibitions

Description

At the moment, the Exhibtion View and About pages are implemented using the same component, called ExhibitionView.js. However, they have very different templates which show very different views on the data.

They should be separate components--if there's shared logic between the two, it should be factored out into an object that they both use. This should enable us to deliver much smaller and less bug-prone versions of each component.

An example of this issue is how we handle catalogue information. Exhibtion About doesn't display any catalog information at all, yet ExhibitionView.js fundamentally concerned with this sort of information.

Comments

  • y z commented 2010-03-10T17:10:27.000-0500

    This issue causes an error in the stand alone where about and view both use the same demo data. About will try to initialize navigation list that it doesn't have the container for in html nor it has the resource in place (since there's no screenNavigator shared resources).

  • Justin Obara commented 2017-12-22T09:44:26.581-0500

    The repository has been archived.