Summary: | [Qt] unify resources used in WebKit/qt/tests/ | ||
---|---|---|---|
Product: | WebKit | Reporter: | Antonio Gomes <tonikitoo> |
Component: | WebKit Qt | Assignee: | Antonio Gomes <tonikitoo> |
Status: | RESOLVED WONTFIX | ||
Severity: | Normal | CC: | benjamin, hausmann |
Priority: | P2 | Keywords: | Qt |
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | All | ||
Bug Depends on: | |||
Bug Blocks: | 32216 |
Description
Antonio Gomes
2009-11-17 08:19:38 PST
i can look at that. Does it really make sense to group them? If there is not any resource that is a copy from another test, I would keep the resource close the where they are used. (In reply to comment #2) > Does it really make sense to group them? > If there is not any resource that is a copy from another test, I would keep the > resource close the where they are used. in fact, idea would be get the resources currently used more organized. i do not know if just unifying them all is the plan here, but as you said, avoiding duplication, among others ... @simon, benjamin: do you thing there is room for improvements here ? (In reply to comment #3) > i do not know if just unifying them all is the plan here, but as you said, > avoiding duplication, among others ... > > @simon, benjamin: do you thing there is room for improvements here ? I think that make sense for the image and the swf, but I would not change the .html. Otherwise, when someone updates the html to extend a test, that could break another test. > I think that make sense for the image and the swf, but I would not change the
> .html.
>
> Otherwise, when someone updates the html to extend a test, that could break
> another test.
right. so there is no much gain from doing that, i believe.
|