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

Notes on my intentions #11

Closed
prepare opened this issue Feb 6, 2018 · 13 comments
Closed

Notes on my intentions #11

prepare opened this issue Feb 6, 2018 · 13 comments

Comments

@prepare
Copy link
Member

prepare commented Feb 6, 2018

Hello
@bjorn-ali-goransson,
and those who come from AngleSharp/AngleSharp.Css#2

If your code meet these ...

  1. No copyleft code
  2. Support .Net framework >=2.0
  3. No Linq

It makes me easier to integrate your code back to my repo.


I also try to figure out
How to support more that 1 Html-Css Dom/Parser frameworks.

eg.

  1. HtmlKit - that is used in this repo.
  2. Pasta - my unfinished port of Google's Gumbo.
  3. Radius - attempt the bring AngelSharp to the HtmlRenderer, not finish.

so lets create some abstraction.

Please don't throw other frameworks away :)


Feel free to create issues about the HtmlRenderer here.

@bjorn-ali-goransson
Copy link

bjorn-ali-goransson commented Feb 6, 2018 via email

@prepare
Copy link
Member Author

prepare commented Feb 6, 2018

Why support more than 1 ?

I want other C# developers who have their framework can
use the HtmlRenderer too.

I don't want them to throw their work away.

eg.

HtmlKit code help this repo come true => I continue to support it.

or Pasta => I want to study the Google code too ;)

@prepare
Copy link
Member Author

prepare commented Feb 6, 2018

And that is another way to ensure that the code has low dependency on others

@bjorn-ali-goransson
Copy link

HtmlKit almost looks like a SAX parser. Is it anything like traversing the DOM?

@prepare
Copy link
Member Author

prepare commented Feb 6, 2018

You can simply access each node by traveling through their DOM.

but no sophisticated traversing code now.

@bjorn-ali-goransson
Copy link

It sounds like an abstraction on top of the parsers should be simple.

@bjorn-ali-goransson
Copy link

I find the solution to be a bit strangely organized (if not unorganized 😅)

How does one get Deps ? Why not use NuGet?....

@bjorn-ali-goransson
Copy link

For example, I now have an empty HtmlRenderer\Source\Deps\BurningMineCurve\CurveUtils, dunno how it got created.

And it gives hundreds of errors when opening the solution (of course since Deps only contains empty dirs)

[Failure] Could not find file '... HtmlRenderer\Source\Deps\BurningMineCurve\CurveUtils\VectorHelper.cs'.

@prepare
Copy link
Member Author

prepare commented Feb 6, 2018

@prepare
Copy link
Member Author

prepare commented Feb 6, 2018

The Rendering Part ((https://github.com/PaintLab/PixelFarm) is a huge part,
quite complex and yes not well-organized :'(

since It is planned to support real-time HtmlRendering.
(esp. UI application / software/hardware rendering).

but once you get the PixelFarm code => all the code are there.

@prepare prepare closed this as completed Feb 6, 2018
@prepare prepare reopened this Feb 6, 2018
@prepare
Copy link
Member Author

prepare commented Feb 6, 2018

At this development stage,
you may need to see all the PixelFarm code (helping organize them too is welcome).


I cheer you, Don't give up with that complex part!

@prepare prepare closed this as completed Feb 6, 2018
@prepare
Copy link
Member Author

prepare commented May 24, 2018

I am investigating / developing more on Radius (https://github.com/prepare/Radius)

:)

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

No branches or pull requests

2 participants