Bug 28228

Summary: Add WebkitDOMObject header files
Product: WebKit Reporter: Gour <gour>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: andersca, sascha.dewald, xan.lopez
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   
Bug Depends on: 27428    
Bug Blocks: 16401    
Attachments:
Description Flags
uploadded none

Gour
Reported 2009-08-12 14:12:29 PDT
Adds header files for WebkitDOMObject.cpp https://bugs.webkit.org/show_bug.cgi?id=27428 Is part of gobject.
Attachments
uploadded (4.47 KB, patch)
2009-08-12 14:14 PDT, Gour
no flags
Gour
Comment 1 2009-08-12 14:14:28 PDT
Created attachment 34688 [details] uploadded
Gour
Comment 2 2009-08-12 14:17:05 PDT
Comment on attachment 34688 [details] uploadded I am cancelling the review because it has the same problem as #27428.
Mark Rowe (bdash)
Comment 3 2009-08-12 15:30:23 PDT
Gour, rather than continuing along with the same problematic approach that Luke took can you please do as requested and discuss a more productive approach with the maintainers of the GTK port.
Gour
Comment 4 2009-08-13 03:12:11 PDT
(In reply to comment #3) > Gour, rather than continuing along with the same problematic approach that Luke > took can you please do as requested and discuss a more productive approach with > the maintainers of the GTK port. OK. I'm just trying to take over from where Luke was blocked to contribute...
Gour
Comment 5 2009-08-13 03:18:15 PDT
(In reply to comment #4) > (In reply to comment #3) > > Gour, rather than continuing along with the same problematic approach that Luke > > took can you please do as requested and discuss a more productive approach with > > the maintainers of the GTK port. OK. What should i do? I am not as experienced as lkcl but i am willing to learn, please do advise me what I should do, and where should i contact the gtk developers?
Xan Lopez
Comment 6 2009-08-13 03:52:26 PDT
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > Gour, rather than continuing along with the same problematic approach that Luke > > > took can you please do as requested and discuss a more productive approach with > > > the maintainers of the GTK port. > > OK. What should i do? > > I am not as experienced as lkcl but i am willing to learn, please do advise me > what I should do, and where should i contact the gtk developers? First read https://bugs.webkit.org/show_bug.cgi?id=16401. Yes, it's long, but hopefully when you are done you'll see how important is to avoid to keep falling into this abyss over and over again. After that, I (and I think I talk for all GTK maintainers here) still think that the way to go was already stated clearly in comment #194 (https://bugs.webkit.org/show_bug.cgi?id=16401#c194) in that bug: "I concur with Mark's review, this is not ready to be landed. I have gone through the CodeGenerator and picked out a bunch of issues that really stick out, but in general, I can't really review this as is. I believe the best way forward is for you to pick one file (say Node.idl) and get code generation working for it or a subset of it. The stripped down version of the code generator that can generate this one file will be a great jumping off point. I know this seems like a step backwards, but the current state of the patch is really not reviewable as is due to a lack of clarity in the code." So if you want to get into this, I suggest you try to start doing something like that, and see where we get from there.
sascha.dewald
Comment 7 2009-12-12 08:00:28 PST
hello, my english is not the best... so i didn't know whats wrong with this patch? how can i help, to bring bug #16401 forward? greetings
Anders Carlsson
Comment 8 2014-01-31 19:02:27 PST
This doesn't need to be open.
Note You need to log in before you can comment on or make changes to this bug.