ENGAGE-297: Ensure all the Engage component work locally from the file system.

Description

Some of the components seem to no longer work when looked at locally from the file system. It's best for components to be able to be worked on without a web server present.

Attachments

• ENGAGE-297.patch
• ENGAGE-297b.patch
• ENGAGE-297oce.patch

Comments

• Michelle D'Souza commented 2010-03-10T18:25:34.000-0500

  The one change in this patch that seems a little odd is the format of the json data files and therefore the expectation of initComponentWithLocalData. The data files now contain an options block rather then just a model. Yura explained that the reason he made that change was because the exhibition view requires a model for the guestbook sub component. This model needs to be specified as part of the exhibition view options not as part of the exhibition view model. If we don't change the expectations of initComponentWithLocalData then we would need to put demo data into the options we pass to it. This defeats the purpose of separating out the demo data from the html file.

• Michelle D'Souza commented 2010-03-10T18:32:10.000-0500

  I would like to see two changes to this patch before I commit it:

  1. format the json data files so that they are human readable. I'd like to see this because I believe they are the only good documentation that we have at the moment of what the model for a particular component looks like.
  2. merge the options passed into initComponentWithLocalData with the options returned from the json data files and update the API docs accordingly

• y z commented 2010-03-10T18:58:12.000-0500

  Change to handle user cookies when dealing with guestbook is made inside fluid.engage.user.currentUser. And not in fluid.engage.user.createNewUser where the call to couch is made. This is because fluid.engage.user.currentUser will try to call fluid.engage.user.fetchUser and fail because local guestbook will set/have the user cookie.

• y z commented 2010-03-10T19:31:33.000-0500

  1. JSON demo data is now readable
  2. Options for the component are now merged with the data from the ajax call
  3. updated nav list html to include all style dependencies (fix the position of media badge)

• Michelle D'Souza commented 2010-03-12T12:47:52.000-0500

  All the components except for code entry now work when loaded from the file system. Let's keep them working! 🙂