{"id":27061,"date":"2019-10-25T16:30:16","date_gmt":"2019-10-25T20:30:16","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=27061"},"modified":"2019-11-03T08:08:44","modified_gmt":"2019-11-03T13:08:44","slug":"direct-to-swiftui","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/10\/25\/direct-to-swiftui\/","title":{"rendered":"Direct to SwiftUI"},"content":{"rendered":"

Helge Heß<\/a>:<\/p>\n

\n

Direct to SwiftUI<\/a>\nis an adaption of an old \nWebObjects<\/a> \ntechnology called \nDirect to Web<\/a>.\nThis time for Apple’s new framework:\nSwiftUI<\/a>.\nInstant \nCRUD<\/a>\napps, configurable using \na declarative rule system<\/a>,\nyet fully integrated with SwiftUI.<\/p>\n

[…]<\/p>\n

Without applying any rules, you’ll essentially get a simple database browser and editor, for all SwiftUI targets. When using Direct to SwiftUI, this is what you start with, a complete CRUD frontend. You then use rules to tweak the frontend, and potentially replace whole generic D2S Views. Or mix & match.<\/p>\n

[…]<\/p>\n

D2S uses a rule engine called \nSwiftUI Rules<\/a>\nwhich we introduced in another\nblog entry<\/a>. You might want to read that now, or later.<\/p>\n<\/blockquote>\n\n

Marcel Weiher<\/a>:<\/p>\n

\n

Definitely cool. Should remember, however, that Direct2Web applications were not just quick\/instantaneous to build, but also utterly incomprehensible and impossible to maintain.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n