2011/6/8 Daniel Danilatos <[email protected]>: > It must be said that this is a bit of a gotcha - it's got me twice, > far enough apart that I forgot what the fix was and I had to figure it > out again. > > Perhaps can we have two modules - a default one that defines user > agent, etc, and a fancy one that doesn't, so for more special needs > such as yours you could depend on the fancy one? (the "default" one > would simply depend on the fancy one and then add the definitions)
Good idea, but given the number of modules in WiaB that directly or indirectly inherits from ….common.util.useragents, you'd probably have to choose only a few ones you'd like to make "reusable as independent components without bothering with user.agent override". It also introduces a risk that some module added/modified later inherits from the "default" module rather than the "fancy" one and therefore break another "fancy" module that depends on the new/modified one. IMO, documentation (could be in the README, or a README.gwtmodules) would be far easier to maintain, and not necessarily "harder" for users (they'd have to find some documentation on which modules they can use, and why there are 2 gwt.xml files for the same "logical" module, etc.)
