3 ms·
This is very interesting. However I'm no iOS developer, so could you give me a cursory explanation on how it works? I mean, I can imagine creating a framework
by saganus 10y ago
This is very interesting.
However I'm no iOS developer, so could you give me a cursory explanation on how it works? I mean, I can imagine creating a framework that has "empty" screens, and then just loading data into them, but this seems like it can do much more.
So for example, if I want an app with say 4 screens, and GPS access (if supported) and a few buttons, do you have all those objects already in memory and just copy them and inject the data to show on screen?
Or maybe it's too early and I'm missing something. Very neat though!
- gliechtenstein 10y agoAlmost correct. To be precise, it doesn't have the objects in memory, it instantiates all the native components on demand based on the JSON recipe. And all of them of course go away once you close that view.
- mitchtbaum 10y ago>> how it works > it instantiates .. components on demand In general, to wrap your information engine around how information engines wrap around components, check out this marvelous design pattern: https://en.wikipedia.org/wiki/Visitor_pattern https://en.wikipedia.org/wiki/Visitor_pattern , like here https://github.com/Jasonette/JASONETTE-iOS/blob/develop/app/Jasonette/JasonComponentFactory.m#L54 https://github.com/Jasonette/JASONETTE-iOS/blob/develop/app/...
- saganus 10y agoAha! thanks to both of you for the answer. I've read about the Visitor pattern before, but did not link it to an engine like this.