• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Classes used to render webview content (tags)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Classes used to render webview content (tags)


  • Subject: Re: Classes used to render webview content (tags)
  • From: Andre <email@hidden>
  • Date: Fri, 11 Nov 2005 13:13:00 -0800

Thanks for the response.

Well, basically I am investigating the possibility of integrating NSView with a layout engine.
Since one already exists in the form of Webview, I am looking at the easiest possible entry-point
for integrating the layout capabilities of KHTML with the flexibility custom NSview.


Basically, CSS 2 + </canvas> offers just about everything I could think of in terms drawing a custom
piece of content in a custom view and having automatic layout of those items.


So, in short, I'm investigating how to pipe events (say to NSCell) from a custom element in a webview to handle events in
cocoa, and from there also have the drawing of those elements in either CG/Cocoa or the automatic
drawing done in CSS and <canvas>. Also, I'm wondering how bindings can be integrated at this level as well.
All without having to explicitly generate HTML or deal with the DOM directly in code.


As an example, I have custom data in an Array controller, and I want to print this out in either a custom view for printing
or custom visualization. If I did it the standard way, I have to layout everything in code, handle redraw (unless using subviews)
etc. This is a lot of code to write over and over again and is almost analogous to writing glue code before bindings and model
code before coredata. Its just a lot of functionality that is repeated over and over again.


In the ideal way, I have a template (XHTML?), and fill in the missing data at runtime through bindings, and repeat the items (for maybe a list)
and be done with it. This is something that is very valuable in Webobjects and allows very very rapid development of interfaces.
The only problem is that typical HTML (outside of maybe ajax) is not very smart and doesn't interact with the same "flash" possible
with desktop apps.


Hope that wasn't too much for one post.

In any case, any help is appreciated.

Andre

Eric Seidel wrote:

khtml/rendering/render_canvasimage.*

May I ask what sort of customizations you'd like to make? Are there changes we might like to pick up long term?

best of luck.

-eric

On Nov 10, 2005, at 9:18 PM, email@hidden wrote:

Hi,

I'm currently looking at the webkit source, and am wondering what are the classes used for drawing
each item, specifically, the <canvas> tag introduced for use in dashboard. And also how it is called
to draw by the layout engine. (I've gone to the webcore site, but a lot is "still to be written")


I'm looking to introduce some custom behavior...

Thanks in advance.

Andre
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webkitsdk-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com


This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Prev by Date: Re: NSPersistentDocument SQL Save As
  • Next by Date: Predicate oddness
  • Previous by thread: Re: Self-Updating Bundle
  • Next by thread: Predicate oddness
  • Index(es):
    • Date
    • Thread