Replies: 1 comment 1 reply
-
Hi Pavlo, there are quite a few classes that implement the IComponent interface, that can be parsed, which are not actually inheriting from Scryber.Components.Component (styles, data classes etc). Along with any custom components others may have implemented. A static method that returns a cast concrete instance should be fairly trivial to implement for anyone using the library. I have also posted a solution to your previous, excellent, discussion on binding SVG content, and I hope this provides a solution that alleviates this option as a request. What do you think? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
For composing a complex document we have to use Component instances (which implement IComponent interface) because Page.Contents property requires exactly Component instances .
Together with that Document.ParseHtml returns IComponent and that is not suitable for Page.Contents
So, I can't implement some components as html templates because have a problem to attache those to the Page.
Have a suggestion to change the result type of the method Document.ParseHtml from IComponent to Component. That should not brake code that already exist and will allow to mix different approaches for building document.
Beta Was this translation helpful? Give feedback.
All reactions