You want me to create a one line file and include it because Pivot doesn't
support lifecycle notification? That's absurd. A one line bxml file.
Is there any conceivable use for a one line bxml file aside from working
around this problem? And I'm supposed to create these files every time I
want a notification?
I'm trying to think of another reason I would want to or need to litter my
source tree with one line files like
<NotifiedComponent label="Duh"/>
And the conclusion I'm drawing is that if the framework requires you to
create one line bxml files to implement certain functionality, the
framework is making your life harder than it needs to be.
Here's the thing. I have a component. It has a button for adding
children, but it has to know what wtkx file to include and it has to know
the value of one other property. I want it to create one child (like
pressing the 'add child' button) after its properties have been set (so it
knows how to do it) by the serializer so that one child item appears in
the UI when the user sees it. From there they can click the 'add child'
button to their heart's content.
Michael
On Mon, 26 Jul 2010, Greg Brown wrote:
There is. Use Pivot 2.0 and <bxml:include> the component you want to initialize.
On Jul 26, 2010, at 8:41 PM, Michael Allman wrote:
I don't know what @PostConstruct is. Does it do what I want? I just want to
know when the serializer has finished building my component. Jeeesh. You think
there'd be a way...
Michael
On Mon, 26 Jul 2010, aappddeevv wrote:
I think this is the @PostConstruct concept again. However, in a parent-child
tree you may have to bound the initialization process like in WPF
(BeginInit, EndInit) because a parent component is not really initialized
until its children are. You have to pick your semantics to figure out what's
right for you.
-----Original Message-----
From: Greg Brown (JIRA) [mailto:[email protected]]
Sent: Monday, July 26, 2010 8:13 PM
To: [email protected]
Subject: [jira] Commented: (PIVOT-580) Add a Lifecycle callback interface so
that components know when they've been initialized
[
https://issues.apache.org/jira/browse/PIVOT-580?page=com.atlassian.jira.plug
in.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892553#action_1
2892553 ]
Greg Brown commented on PIVOT-580:
----------------------------------
I understand. But keep in mind that BXML is just a shortcut to instantiating
and setting properties on Java objects "by hand". You wouldn't get any such
notifications in Java, so we don't provide them in BXML either. Your classes
should be able to function the same whether they are created by
BXMLSerializer or some other means (i.e. programmatically).
Add a Lifecycle callback interface so that components know when they've
been initialized
----------------------------------------------------------------------------
------------
Key: PIVOT-580
URL: https://issues.apache.org/jira/browse/PIVOT-580
Project: Pivot
Issue Type: New Feature
Components: wtk
Reporter: Michael Allman
I just created
public interface Lifecycle {
public void initialized();
}
because I want one of my custom components to know when it's been
initialized. The component takes a specific action after being initialized.
By "initialized", I mean "having all properties set".
The serializer calls this method after it has finished initializing the
component, basically at the end of the processEndElement method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
