-
FieldModel Design
FieldModel design thoughts:- FieldModel is a part of the MVC triangle for any field. For now InputController is designated to control UI widgets
- FieldModel holds the object value.
- FieldModel value may sometimes differ from what is displayed by the View (view may display invalid data)
- FieldModel value may sometimes differ from what is stored in the ( Read more... )
-
Parse, Format, and Validate
The following 3 services are critical for data processing- Formatting (process of converting of Objects of any type to String)
- Parsing (process of parsing of a String to create a new instance of the Object)
- Validation (process of validating an Object against certain criteria)
For convenience, suggested design is to combine provision of all three ( Read more... ) -
TextInputController design
Text-based input controller high-level design:- Custom FormatterControlled document
- Control insertString by passing it through Formatter
- Control removeString by passing it through Formatter
- Register a CaretListener
- Control UI caret movement by passing it through Formatter
-
Binding
I am returning back to the implementation of binding. It was a long detour to implement the MD and formatter infrastructures. It will take some time to regain the clarity of thought and refresh all of the issues related to binding. I really wish I had the journal entries for the period when I started. I will try to add to this entry all the ( Read more... ) -
RuntimeException woes
Many operations on the low level of the framework perform rigorous tests of passed parameters and throw appropriate exceptions when faced with incorrect parameters or in other exceptional cases. Question at hand is whether these exceptions should extend RunTimeException or Exception.
( Read more... ) -
Why ParameterProvider chain of responsibility does not work for FieldInfo
Some more thoughts regarding the example in the previous post. The premise of the example was that the Form where the MD is used wants to override certain properties of the MD. By supplying a parameter provider for the form and by adding it to the top of the chain, one can ask the MD to re-initialize itself, which would guarnatee that the MD used ( Read more... ) -
ParameterProvider chain of responsibility
Chain of responsibility is a natural pattern for providing an entity with the most appropriate value for the context. Let's analyze the need by carefully considering the following example:- Subordinate descriptors for the MD entity have default parameter values
- The class where the MD is defined (most often the MD will point to the element of the ( Read more... )
-
FieldInfo etc ...
I need to go back to FieldInfo and see how MD infrastructure fits in. The following is just to refresh my memory.
MD is short for Meta-Data which can be described as a container for all meta-data information which is associated with a particular element of a data structure ( Read more... ) -
Pluggable Descriptor Infrastructure ready
Pluggable Descriptor infrastructure in laregely ready. First generation of Swing_UID and Parameter_PD is finished.
The only complication was desire to pull off Descriptor configuration by means of using MD infrastructure. Even though it might be equated to an attempt to create the clay out of bricks, which are supposed to be made out of clay, I ( Read more... ) -
Entity Domain Management
Domain management should be delegated to the manager class (e.g. DomainManager). This way we will no longer have to organize domain infrastructure in each descendant of the BaseEntity class
DomainManager services:
getDomain(Class clazz);
/**
This method either:
- populates the domain from an external source v
- or (if v == null) ( Read more... )