Here's some thoughts I had on chunks of Frame / MacFrame (the former
KHTMLPart and KWQKHTMLPart) that could be factored out into a
separate class.
Drag and drop code --> DragController (probably needs to be Mac-
specific for now)
Selection related code --> move to the existing khtml/editing/
SelectionControler.cpp
Code to convert to NSAttributedString --> free function in a separate
file (Mac-specific)
editing-related code (not selection) --> some new editing-related
file, maybe call it Editor?
page cache related code --> some new class, not sure what to call it
off-hand
code relating to toolbar visibility, JS alerts, etc --> Chrome,
UIController, something like that
event handling --> FrameEventHandler (may require a Mac-specific
subclass for now)
marked text handling --> MarkedTextController (or maybe just
MarkedText?)
JS related stuff --> push down to ScriptInterpreter
copy/paste stuff --> Clipboard or ClipboardController or something
like that
focus related things --> FocusController (or maybe just Focus?)
_______________________________________________
webkit-dev mailing list
[email protected]
http://www.opendarwin.org/mailman/listinfo/webkit-dev
