[
https://issues.apache.org/jira/browse/PIVOT-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884981#action_12884981
]
Michael Allman commented on PIVOT-560:
--------------------------------------
So I think I've figured out what I want to argue.
To make another analogy, think of this feature as a tool. A tool can be
dangerous. For example, you can literally shoot yourself in the foot with a
nail gun. And yet nail guns exist, because when they're used properly they're
very valuable. They save a lot of work.
Similarly, this feature can be "dangerous" or "confusing". It can also be very
valuable and save a lot of work if it's used wisely. The wisdom of its usage
is up to the user. Given that rejecting this feature basically shuts out its
use even in helpful cases, I respectfully request you reconsider your position.
Yes, dummies will mess it up. They'll also mess up everything else. Who's
dumb enough to abuse this capability but smart enough to write clean code
everywhere else?
Cheers.
> Permit WTKX namespace declarations to declare more than one in-scope package
> ----------------------------------------------------------------------------
>
> Key: PIVOT-560
> URL: https://issues.apache.org/jira/browse/PIVOT-560
> Project: Pivot
> Issue Type: New Feature
> Components: wtk-wtkx
> Affects Versions: 1.5.1
> Reporter: Michael Allman
> Fix For: 1.5
>
> Attachments: multiple_packages_in_one_namespace_uri.patch.gz
>
>
> The attached patch allows this:
> <Frame xmlns="org.apache.pivot.wtk,my.custom.component.package"
> xmlns:wtkx="http://pivot.apache.org/wtkx";>
> <content>
> <BoxPane/>
> <MyCustomComponent/>
> </content>
> </Frame>
> The obvious benefit of this patch is to (almost) eliminate the need for
> alternate namespace prefixes for other packages. If a type name exists in
> more than one package, the system throws a SerializationException complaining
> that the type name is ambiguous.
> To make an analogy, the way things currently are would be like restricting
> imports in a Java source file to a single package. Any type from another
> package would have to be qualified. This patch allows the Pivot developer to
> bring multiple packages into the default (or other) XML namespace. This is a
> huuuuuge time (and finger) saver when working with custom components.
> Cheers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
