Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out a way to export to lambdasoup #100

Open
Drup opened this issue Mar 29, 2016 · 2 comments · May be fixed by #223
Open

Figure out a way to export to lambdasoup #100

Drup opened this issue Mar 29, 2016 · 2 comments · May be fixed by #223
Milestone

Comments

@Drup
Copy link
Member

Drup commented Mar 29, 2016

Currently, Xml_iter is very crude and not very used. I would like to both improve the functionality and deprecate the current interface.

We can do that by providing a way to export to lambdasoup. I would prefer to do it while not actually depending on lambdasoup, so some structural thing would be nice.
This would also potentially provide us with a good streaming printer, when one is added to lambdasoup.

@Drup Drup added this to the later milestone Mar 29, 2016
@aantron
Copy link
Contributor

aantron commented Mar 29, 2016

@Drup, Markup.ml has a streaming printer – so Lambda Soup does too, it's the Soup.to_string function. It can also be done with soup |> Soup.signals |> Markup.write_html |> Markup.to_something_other_than_string.... I am not sure what the purpose or use case of Xml_iter is, but depending on what it actually is, can it be achieved by functorizing Lambda Soup over its tree representation somehow?

@Drup
Copy link
Member Author

Drup commented Mar 30, 2016

can it be achieved by functorizing Lambda Soup over its tree representation somehow?

Either that, or expecting a tree walker (see Xml_sigs.Iterable).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants