2022/06/23/event-object as output container: Difference between revisions
Jump to navigation
Jump to search
(Created page with "{{nav/codeblog}} __NOTOC__ ''originally rubberducked [https://discord.com/channels/469887577311150080/508798205505306628/989645884935508028 on Discord]'' ---- ug, more design...") |
No edit summary |
||
| Line 2: | Line 2: | ||
__NOTOC__ | __NOTOC__ | ||
''originally rubberducked [https://discord.com/channels/469887577311150080/508798205505306628/989645884935508028 on Discord]'' | ''originally rubberducked [https://discord.com/channels/469887577311150080/508798205505306628/989645884935508028 on Discord]'' | ||
==17:39== | |||
ug, more design decisions... | ug, more design decisions... | ||
* '''old tree-rendering system''': Render() returns a string; each Node sums up the strings from the Nodes underneath | * '''old tree-rendering system''': Render() returns a string; each Node sums up the strings from the Nodes underneath | ||
* '''new tree-rendering system''': OnRender() is dispatched from OnEvent(), which receives an object of any of (currently) 3 different event-classes. Each class specifies the method to call when it is received. (This way we only have to implement *one* dispatch hierarchy.) The Render Event has a string property which is the result of the rendering, and each Node adds its output to that property. ...but there are tendrils of the old system still remaining; my instinct is to convert them and tidy up, but how much will I end up regretting this? Stay tuned... | * '''new tree-rendering system''': OnRender() is dispatched from OnEvent(), which receives an object of any of (currently) 3 different event-classes. Each class specifies the method to call when it is received. (This way we only have to implement *one* dispatch hierarchy.) The Render Event has a string property which is the result of the rendering, and each Node adds its output to that property. ...but there are tendrils of the old system still remaining; my instinct is to convert them and tidy up, but how much will I end up regretting this? Stay tuned... | ||
==17:51== | |||
This could be... such a huge mess. | |||
If it in fact turns out to be just that, then I will have some intensive documentation to do. | |||
Revision as of 17:02, 1 July 2022
originally rubberducked on Discord
17:39
ug, more design decisions...
- old tree-rendering system: Render() returns a string; each Node sums up the strings from the Nodes underneath
- new tree-rendering system: OnRender() is dispatched from OnEvent(), which receives an object of any of (currently) 3 different event-classes. Each class specifies the method to call when it is received. (This way we only have to implement *one* dispatch hierarchy.) The Render Event has a string property which is the result of the rendering, and each Node adds its output to that property. ...but there are tendrils of the old system still remaining; my instinct is to convert them and tidy up, but how much will I end up regretting this? Stay tuned...
17:51
This could be... such a huge mess.
If it in fact turns out to be just that, then I will have some intensive documentation to do.