Document viewer app with extras
Posted: Wed Jul 13, 2016 10:59 pm
I’ve been given a task of creating an app to help couples where one person has had an early diagnosis of dementia. The details are sketchy at present but a large part of the app will be a text guide. I’ve been given the chapters and sub-headings https://goo.gl/7UFbDL. I believe amongst other things the sponsors also want some kind of user interactivity like questions and answers which can be answered by typing or by recording speech. They do have videos they want to include and have also talked vaguely about some kind of games.
Anyhow, for the text side of it I did think of converting the whole document to PDF and just displaying in a LiveCode browser. However a colleague seems to think that the app needs to be more bespoke and the sponsor was talking about breaking up the guide into multiple windows with a section of the guide per window. To format the text I guess I could use the htmlText property of a field.
How could I produce a card with a clickable table of contents which opens the relevant card containing the text for that section of the guide? I know one way would be to have each section on a button but is there any way to use hypertext to link to a card or any other better way?
Does anyone have any thoughts or experiences they could share on that specific question or on the app design in general?
Many thanks,
Jim
Anyhow, for the text side of it I did think of converting the whole document to PDF and just displaying in a LiveCode browser. However a colleague seems to think that the app needs to be more bespoke and the sponsor was talking about breaking up the guide into multiple windows with a section of the guide per window. To format the text I guess I could use the htmlText property of a field.
How could I produce a card with a clickable table of contents which opens the relevant card containing the text for that section of the guide? I know one way would be to have each section on a button but is there any way to use hypertext to link to a card or any other better way?
Does anyone have any thoughts or experiences they could share on that specific question or on the app design in general?
Many thanks,
Jim