2022/06/23/event-object as output container: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{nav/codeblog}} | {{nav/codeblog}} | ||
[[category:ferreteria]] | |||
__NOTOC__ | __NOTOC__ | ||
''originally rubberducked [https://discord.com/channels/469887577311150080/508798205505306628/989645884935508028 on Discord]'' | ''originally rubberducked [https://discord.com/channels/469887577311150080/508798205505306628/989645884935508028 on Discord]'' | ||
| Line 5: | Line 6: | ||
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? [[2022/06/24/event-object as output container|Stay tuned...]] | ||
==17:51== | ==17:51== | ||
This could be... such a huge mess. | 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. | If it in fact turns out to be just that, then I will have some intensive documentation to do. | ||
Latest revision as of 00:01, 2 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.