ENGAGE-284 | Language selection

[Andrea Leutgoeb .]

Hi Colin,> I've been doing some code review today and realized that I haven't taken a look at your latest version of the Language Selection screen.Sorry for the confusion, I just uploaded the latest patch:http://issues.fluidproject.org/browse/ENGAGE-284?focusedCommentId=17001&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_17001Language selection 0.2- Integration of user component (core & kettle).  CouchDB: User record created in table "users":  http://unistud.asteasolutions.net:11929/users/  TO-DO: Store language preference of user in CouchDB  - List of languages generated dynamically based on the museum document.  Museum document for McCord:{   "_id": "mccord",   "_rev": "1-b7cf5fa17688439515f77a9c14b2275f",   "type": "fluid.engage.docs.museum",   "name": "McCord Museum",   "languages": [       "en",       "fr"   ],   "lat": 43.662424,   "long": -79.441134}    Currently the museum document for McCord is stored locally.  TO-DO: Info needs to be stored in CouchDB & for all museums.- Minor html/js changes Currently the language preferences are fetched based on the museum document for McCord only. I am wondering how the museum identifier is stored in order to retrieve it and fetch the corresponding museum document?It would be great if you could have a look at the patch. Thanks in advance!Andrea
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100201/e891d45b/attachment.html>