Timeline for Choose your own adventure - choices stack
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2016 at 19:05 | answer | added | JBiggs | timeline score: 0 | |
| Jul 24, 2016 at 12:04 | comment | added | Philipp | @uliwitness There are different kinds of UML diagrams. The closest to a dialog tree is an activity diagram. I experimented with various tools to generate code from UML diagrams once and was quite disappointed. You usually get some quite messy code which isn't even functional yet and needs some manual filling out of stub methods. | |
| Jul 24, 2016 at 11:17 | answer | added | uliwitness | timeline score: 1 | |
| Jul 24, 2016 at 11:04 | comment | added | uliwitness | @Philipp Isn't a UML diagram exactly what an object graph is? You could probably look into object graph serialization approaches to find good ways of representing a graph of objects in a linearized fashion. | |
| Jul 20, 2016 at 23:36 | history | tweeted | twitter.com/StackGameDev/status/755909350066094081 | ||
| Jul 20, 2016 at 17:08 | answer | added | Jesse Williams | timeline score: 0 | |
| Jul 20, 2016 at 16:39 | answer | added | Pikalek | timeline score: 2 | |
| Jul 20, 2016 at 13:28 | vote | accept | TommyBs | ||
| Jul 20, 2016 at 9:35 | comment | added | Philipp |
The underlying problem is that there is simply no elegant way to represent non-linear narrative with a linear medium like sourcecode. The ideal method would IMO be to have an UML-like visual editor where story-points are represented as boxes and the possible narrative flows as arrows. But for most smaller projects it would likely be more work to implement such an editor than to just hand-write a mess of spaghetti code full of if's, else's, switch's and case's hoping you will be finished before losing your sanity.
|
|
| Jul 20, 2016 at 6:58 | answer | added | Felsir | timeline score: 13 | |
| Jul 20, 2016 at 6:01 | comment | added | TommyBs | @JoshPetrie updated with some more info | |
| Jul 20, 2016 at 6:00 | history | edited | TommyBs | CC BY-SA 3.0 |
added 537 characters in body
|
| Jul 20, 2016 at 5:42 | comment | added | user1430 | How do you currently representing each "page" of your adventure? Are they all just hard coded functions in Swift? Are you reading the text/images and choices available for each page from a data file? If so, what's the file look like? | |
| Jul 20, 2016 at 5:10 | history | asked | TommyBs | CC BY-SA 3.0 |