<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Replies inline.</div><div><br>On May 31, 2016, at 11:19 PM, Andy Somogyi <<a href="mailto:somogyie@umail.iu.edu">somogyie@umail.iu.edu</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><span class="" style="font-family: Menlo-Regular; font-size: 11px;">Hi,</span><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><span class="" style="font-family: Menlo-Regular; font-size: 11px;">I’m a programming language researcher, and we are working on a new visual programming language. </span><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><span class="" style="font-family: Menlo-Regular; font-size: 11px;">I’m investigating using WebCore as the rendering component of our language editing/visualization system. </span><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><font face="Menlo-Regular" class=""><span class="" style="font-size: 11px;">Essentially what I’d like to be able to do is to programmatically (C++) generate 1: a DOM tree of a new family of Element derived object, 2: rendering tree, 3: layout the tree, 4: attach a GraphicsContext to an existing window or bitmapped resource, and 5: use WebCore’s GraphicsContext to render the custom rendering tree. I’d also like to create a family of custom Element derived objects that would be attached to the rendering tree and use the rendering tree. I’d also like to respond to the standard events, i.e. mouse, keyboard, etc…</span></font></div></blockquote><div><br></div><div>Generating a DOM is usually done in JavaScript. I'm curious about the problem you are trying to solve where JavaScript is not sufficient.</div><div><br></div><div>Drawing into an existing window is usually done by inserting a WebView into the view hierarchy of the window. Yet again, I'm interested in why this is not sufficient.</div><br><blockquote type="cite"><div><div class=""><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><span class="" style="font-family: Menlo-Regular; font-size: 11px;">Do you think this would be possible using WebCore as a library and have these custom render tree / dom tree derived objects live in my own library (this is really, really the way I’d prefer to do things), or do you think it would be better to add these objects directly into the WebCore library. </span><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><br class="" style="font-family: Menlo-Regular; font-size: 11px;"></div></div></blockquote><div><br></div><div>Are you planning on committing any changes to trunk?</div><div><br></div><div>Of course it is ::possible:: to do something like this - it's all software. Are you asking if it's easy to do it? Or the best way to do it?</div><br><blockquote type="cite"><div><div class=""><font face="Menlo-Regular" class=""><span class="" style="font-size: 11px;">I don’t think accessing any of the render tree objects in webcore would cause any issues on Mac/Unix, however, Windows sadly requires those EXPORT macros on each class def. If I added these, what would be the WebKit policy of accepting these changes? </span></font></div><div class=""><br class=""></div><div class="">What is the, for lack of a better word, the “viability” of WebKit on Windows? Our project fundamentally has to be cross-platform, and currently, I’m not aware of any webkit based browsers on Windows. I’m currently looking into using webkit, firefox or blink. I’ve essentially eliminated blink because their code is very hard to follow, much harder than webkit or firefox, and I think the webkit code is the easiest to understand and use. Webkit is currently my first choice, but my only hesitation is will webkit continued to be supported on Windows. </div></div></blockquote><div><br></div><div>Windows is an official port, just like iOS / Mac / EFL / GTK.</div><br><blockquote type="cite"><div><div class=""><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><span class="" style="font-family: Menlo-Regular; font-size: 11px;">thanks</span><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><span class="" style="font-family: Menlo-Regular; font-size: 11px;">-- Andy Somogyi PhD</span><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><span class="" style="font-family: Menlo-Regular; font-size: 11px;">School of Informatics and Computing</span><br class="" style="font-family: Menlo-Regular; font-size: 11px;"><span class="" style="font-family: Menlo-Regular; font-size: 11px;">Indiana University</span></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>webkit-dev mailing list</span><br><span><a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a></span><br><span><a href="https://lists.webkit.org/mailman/listinfo/webkit-dev">https://lists.webkit.org/mailman/listinfo/webkit-dev</a></span><br></div></blockquote></body></html>