On Tue, 27 Jul 2010, Greg Brown wrote:
Call me naive or maybe just a newb but I didn't know that the order in which
attributes appear on an element in bxml mattered. I mean, in XML
element attr1=d24 attr2=hahth/
and
element attr2=hahth attr1=d24/
are the same when considering each
Michael Allman wrote:
On Tue, 27 Jul 2010, Greg Brown wrote:
Call me naive or maybe just a newb but I didn't know that the order in
which attributes appear on an element in bxml
mattered. I mean, in XML
element attr1=d24 attr2=hahth/
and
element attr2=hahth attr1=d24/
are the same
in the DOM order has relevance. Attributes are stored as a list, not a map.
Pivot's org.apache.pivot.xml.Element class provides both keyed and indexed
access to attributes.
Huh? What language/implementation of the DOM are you referencing? I'm
looking at Java's org.w3c.dom.Node, in
A crazy idea: and try to use existing Swing components with Pivot
wrappers (Scala Swing seems to do something like this ... Ok, complex
but powerful, and with the benefit to have the original LF) ...
That's certainly possible too. A Pivot theme could (theoretically) be created
that uses Swing
One of the most important things for my choice for java GUI work is richness
of the components/widgets. Pivot has a good selection, but there are a
number of JIRA tickets suggesting improvements which I would like to see.
The creation of a brand new component would probably be a fairly daunting
Hi Chris
What components in particular, are you missing?
-- Noel
Chris Bartlett wrote:
One of the most important things for my choice for java GUI work is richness
of the components/widgets. Pivot has a good selection, but there are a
number of JIRA tickets suggesting improvements which I
I appreciate the benefits making Pivot more accessible to Swing developers,
but don't have the experience with the theme/LF side of Pivot to be
understand the effort involved. If you feel it is doable without adding a
lot of additional complexity or maintenance issues, then I don't see the
I would actually consider an exception thrown because of attribute ordering
to be a bug prior to getRoot or readObject in the serializer.
It's not a bug. It is by design. BXML is processed like a script, and order of
execution is relevant. If you need different behavior, then BXML may not be
Since there has been some continued discussion about it, I want to clarify what
BXML is and what it is not:
- BXML is an XML-based markup language for simplifying the construction of an
object hierarchy (often a WTK component hierarchy).
- Unlike some other similar markup langauges (e.g. MXML
Add parent to TreeNode/TreeBranch
-
Key: PIVOT-583
URL: https://issues.apache.org/jira/browse/PIVOT-583
Project: Pivot
Issue Type: Improvement
Components: wtk
Reporter: Greg Brown
[
https://issues.apache.org/jira/browse/PIVOT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12894951#action_12894951
]
Todd Volkert commented on PIVOT-583:
Heads up, we used to have this feature way back
Nice write up! Can that go on the web site?
I can only provide these personal thoughts:
I think the discussions around BXML here really are just saying, hey, there
is an original BXML use-case that it satisfies fair enough to your point.
But it could do more and that may make pivot have a
[
https://issues.apache.org/jira/browse/PIVOT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12894959#action_12894959
]
Greg Brown commented on PIVOT-583:
--
I don't remember the reason either, but I don't see any
Nice write up! Can that go on the web site?
Yes - it will most likely be incorporated into the BXML Primer when 2.0 is
released.
Create adapters for Swing model classes
---
Key: PIVOT-585
URL: https://issues.apache.org/jira/browse/PIVOT-585
Project: Pivot
Issue Type: New Feature
Components: wtk
Reporter: Greg
Update BXMLSerializer extensibility
---
Key: PIVOT-584
URL: https://issues.apache.org/jira/browse/PIVOT-584
Project: Pivot
Issue Type: Improvement
Components: core-beans
Reporter: Todd
[
https://issues.apache.org/jira/browse/PIVOT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12894970#action_12894970
]
Todd Volkert commented on PIVOT-583:
I can't think of a good reason not to do it, so
[
https://issues.apache.org/jira/browse/PIVOT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12894971#action_12894971
]
Roger Whitcomb commented on PIVOT-583:
--
FWIW -- every time I've implemented my own Tree
I think its been well proven that intercepting (even a
little) the creation and initialization of an object hierarchy (the wiring)
can be a huge complexity reducer
FYI, this has recently been revisited - check out the changes in revision
#981995. Todd can provide more detail.
personally maintain are small enough that its not worth it at this point. A
BXML compiler is not out of the question given aspectj and ITDs actually
although it is unclear what the performance benefit would be.
FYI, I prototyped one back in the day, got it working, and the
performance benefit
[
https://issues.apache.org/jira/browse/PIVOT-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-583.
--
Assignee: Greg Brown
Resolution: Fixed
Add parent to TreeNode/TreeBranch
Alt+A in Polish locale incorrectly selects all text
---
Key: PIVOT-586
URL: https://issues.apache.org/jira/browse/PIVOT-586
Project: Pivot
Issue Type: Bug
Components: wtk
That's consistent with my thoughts then. If I look at BXML use generally in
pivot, the BXML trees are not large or complex. I think they are more
complex in XAML where because of their design decision to push as much as
possible into XAML e.g. templates, data binding, triggers, xml extensions
23 matches
Mail list logo
