Changes between Version 44 and Version 45 of PRO_LIB_CORE_TUTORIAL

Timestamp:

07/14/09 15:55:28 (16 years ago)

Author:

peko

Comment:

--

PRO_LIB_CORE_TUTORIAL

@@ -785 +785 @@
 }}}
 
+ ==== Depending on a non-final property inside a "create()" method of a ResourceProperty ====
+ * Using an non-final property inside a the create method will eventually work if that property is not null or is already initialized. Changing that property however will not affect the value of the resource property since its create method is invoked only once...
+{{{
+        public RwProp<Icon> icon() {
+                return getBean().makeValueProp("icon", Icon.class);
+        }
+        
+        public RwProp<String> toolTip() {
+                return getBean().makeValueProp("toolTip", String.class);
+        }
+        
+        public Prop<JButton> button() {
+                class button extends ResourceProperty<JButton> {
+
+                        @Override
+                        protected JButton create() {
+                                JButton res = new JButton();
+                                res.setIcon(icon().get());
+                                return res;
+                        }
+
+                        @Override
+                        protected void destroy(JButton res) {
+                                //nothing.
+                        }
+
+                        @Override
+                        protected void setup(JButton res) {
+                                res.setToolTipText(toolTip().get());
+                        }
+                }
+                return getBean().makeProp(button.class);
+        }
+}}}
+
+ * In this case the icon will be set (if initialized by the time the create method is invoked). Besides, the tool-tip will be set, no matter what because the setUp method will be invoked after the initialization of the toolTip()'s property. If we change the tool-tip the setUp method will be re-setUp-ed. '''However if we change the icon property, the icon of the button will not be set to the new one.''' Be careful about such scenarios, because it will probably remain silent.
+
+
 == Debugging ProLib ==
 Some advice:
@@ -796 +834 @@
  * Keep the ProLib and with high quality, because everything else will depend on it.
  * Be careful not to create cyclic dependencies (like a = b + 1, b = a + 1). No library can solve them.
+ ==== More sophisticated scenarios ====
+ * Suppose you have several non-ProObject, non-Immutable objects that you need to keep in sync. Imagine you have three 
 
 == TODO ==