WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
74691
[Qt] Eliminate dependency to QUndoStack
https://bugs.webkit.org/show_bug.cgi?id=74691
Summary
[Qt] Eliminate dependency to QUndoStack
Simon Hausmann
Reported
2011-12-16 00:09:43 PST
[Qt] Eliminate dependency to QUndoStack
Attachments
Patch
(5.20 KB, patch)
2011-12-16 00:12 PST
,
Simon Hausmann
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Simon Hausmann
Comment 1
2011-12-16 00:12:02 PST
Created
attachment 119577
[details]
Patch
Simon Hausmann
Comment 2
2011-12-16 00:12:59 PST
Once this is in, the next step is to get rid of the class entirely and just fold the few lines of code straight to the page client, if that's okay with you folks :)
Caio Marcelo de Oliveira Filho
Comment 3
2011-12-16 05:51:08 PST
Looks good to me. I don't think we are getting any benefit from using QUndoStack. Regarding moving this to QtPageClient, I like the fact that QtPageClient is super-thin and just forward things to the proper object handling them. I'm afraid folding even this small chunk of code will put page client in another route... but that could be me just being a bit over-cautious ;-)
Alexis Menard (darktears)
Comment 4
2011-12-16 06:49:27 PST
(In reply to
comment #3
)
> Looks good to me. I don't think we are getting any benefit from using QUndoStack. > > Regarding moving this to QtPageClient, I like the fact that QtPageClient is super-thin and just forward things to the proper object handling them. I'm afraid folding even this small chunk of code will put page client in another route... but that could be me just being a bit over-cautious ;-)
+1 tend to agree with that. This is exactly how we ended up with QtWebPageProxy.
Simon Hausmann
Comment 5
2011-12-16 12:06:37 PST
(In reply to
comment #3
)
> Looks good to me. I don't think we are getting any benefit from using QUndoStack. > > Regarding moving this to QtPageClient, I like the fact that QtPageClient is super-thin and just forward things to the proper object handling them. I'm afraid folding even this small chunk of code will put page client in another route... but that could be me just being a bit over-cautious ;-)
I understand your fear, but I'm not sure if it is really another classes responsibility to handle the undo command storage. It is the _intend_ of the C API that the page ui client handles it, so why should we delegate it even further? The QtWebPageProxy became big because it implemented multiple client APIs in one shot. Anyway, I'll try to convince you with code :) - in the meantime we need to get this patch reviewed :)
Kenneth Rohde Christiansen
Comment 6
2011-12-16 12:12:53 PST
Comment on
attachment 119577
[details]
Patch im fine with it.
Simon Hausmann
Comment 7
2011-12-16 12:40:48 PST
Comment on
attachment 119577
[details]
Patch Thanks Kenneth :)
WebKit Review Bot
Comment 8
2011-12-16 12:55:26 PST
Comment on
attachment 119577
[details]
Patch Clearing flags on attachment: 119577 Committed
r103097
: <
http://trac.webkit.org/changeset/103097
>
WebKit Review Bot
Comment 9
2011-12-16 12:55:31 PST
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug