HTML Rendering in C# : Anole

[Bruce Shankle]

All,

I am making an alpha release of Anole (C# HTML renderer) available for
download at http://home.nc.rr.com/bshankle/cfhtml/

I have asked Neil Cowburn to review Anole in hopes that it might be
picked up by the OpenNetCF organization. So far I haven't heard back
from him.

A few people have been asking about the status of the project.

I have the go-ahead to open source the code. It is a relatively decent
renderer for simple things. Table support is in progress but I recently
started a new job and haven't had much time to allocate to it.

I suggest you download and try it out and if you want to contribute let
me know.

-Bruce

 

[Chris Tacke, eMVP]

Bruce,

Does this provide more/different functionality than our current HTMLViewer
control? If so, you could always roll your stuff into what we've already
got. We're not likely to just take it as-is for a couple reasons:

1. It duplicates functionality of an existing OpenNETCF library
2. It doesn't follow the OpenNETCF Guidelines

See these links for more info
http://www.opennetcf.org/guidelines.asp
http://www.opennetcf.org/forms.asp

 

[Neil Cowburn [MVP]]

Firstly, I apologise for not getting back to you about this sooner, but as I
have explained, my activity level goes off the chart so you will just have
to bear with me. Secondly, I don't appreciate you bringing this into a
public forum as it has nothing to do with anyone else, and is a petty
attempt to soil the name of OpenNETCF.org and myself.

Since a large portion of websites use tables for layout control, I really
don't think a HTML renderer without table support would be of much value.

--Neil

 

[Chris Tacke, eMVP]

I beleive you're correct that the HTMLControl wraps the CE HTML control
(I've not used it yet), but its purpose is to parse and display HTML
formatted text.

If your renderer provides the ability to parse and display HTML formatted
text, then I would consider it a functionality overlap. Now if yours
provides more, better or different functionality, then great - we're all for
improving our library functionality.