Re: WODisplayGroup bindings aren't complete for selectedObject or masterObject

From: David Holt (programmingos..ac.com)
Date: Thu Jun 12 2008 - 18:53:43 EDT

  • Next message: David Avendasora: "Re: Apple Maven Support: First Impression (Take 2)"

    On 12-Jun-08, at 3:23 PM, Chuck Hill wrote:

    >
    > On Jun 12, 2008, at 3:16 PM, David Holt wrote:
    >
    >> I have discovered that all of my page components that were created
    >> with the DisplayGroupComponent wizard in Xcode are broken. The key
    >> path convention that is used by the wizard throws errors in
    >> component editor.
    >>
    >> For example, the wizard inserts a button that inserts an entity
    >> (entityDisplayGroup.insert(), which then becomes the display
    >> group's selected entity) and then wires the selected entity to the
    >> editing form fields by using a key path for the value such as
    >> "entityDisplayGroup.selectedEntity.name". This key path is not
    >> recognized. Is this a bug? Or was Xcode doing something
    >> inadvisable and I should be changing all these pages to create
    >> variables when an item in the display group is selected? The issue
    >> seems related to my previous message in this thread.
    >
    > It is just a validation "error".
    >
    > It can't validate it as it does not know the type of object
    > returned by selectedObject. Go to the WOLips binding validation
    > rules preferences and tell it to not validate key paths with
    > displayGroup.selectedObject in them

    If anyone else wants to add these to their rules I used:

    .*.DisplayGroup\.selectedObject\..*
    .*.DisplayGroup\.masterObject\..*

    >
    >
    > Chuck
    >
    >
    >> On 5-Jun-08, at 3:25 PM, David Holt wrote:
    >>
    >>> In converting a project to WOLips I have discovered that the
    >>> bindings for someDisplayGroup.masterObject or
    >>> someDisplayGroup.selectedObject don't map to the EOs that are
    >>> specified in the DisplayGroup configuration. In WOBuilder if you
    >>> bound to selectedObject() it would expose the variables and
    >>> methods available for that object.
    >>>
    >>> See screenshots for details.
    >>>
    >>> Is this expected behaviour?
    >>>
    >>> <037.jpg>
    >>>
    >>> <038.jpg>
    >>
    >>
    >
    > --
    >
    > Practical WebObjects - for developers who want to increase their
    > overall knowledge of WebObjects or who are trying to solve specific
    > problems.
    > http://www.global-village.net/products/practical_webobjects
    >
    >
    >
    >
    >



    This archive was generated by hypermail 2.0.0 : Thu Jun 12 2008 - 18:54:29 EDT