[Grok-dev] How to use auto-forms to quickly handle nested objects

[Sebastian Ware]

I have tried the Object(schema=xxx) approach but failed because I  
needed invariants and they seemed to be broken for the related object.  
Anyway take a look at this thread:

   [Grok-dev] How do I use schema.Object?

You need to use a CustomWidgetFactory.

Mvh Sebastian

26 mar 2009 kl. 17.32 skrev Tim Cook:

> Hi Steve,
>
> I haven't replied to this because you stated the problem slightly
> differently than I did.  I also had some other errors in my code and
> everyone was very helpful in helping me fix those.  BUT....they didn't
> solve the Object(schema==xxxx) issue.  In fact I have multiple  
> layers of
> these.  I was told that someone was working on an Object() widget  
> but I
> do not think it is a high priority.  I chased this for a couple of
> months, no solution.
>
> I think that my approach at this point is going to be to convert all  
> the
> Object()s to Fields() and then see if I can test to  see if the
> attribute implements the desired interface(s).
>
>
> Good Luck,
> Tim
>
>
>
> On Thu, 2009-03-26 at 09:22 -0700, Steve Schmechel wrote:
>> Sorry for replying to my own post, but I am still in the dark as to  
>> whether autoforms (grok.formlib) can be employed to automatically
>> navigate a hierarchical model structure using schema directives in  
>> the model object interfaces.
>>
>> It looks like they might, but I can't find any examples.
>>
>> Does anyone have a definitive answer?
>> Is this approach just "wrong" in the Zope/Grok world?
>> Should I ask on the Zope mailing list regarding zope.formlib?
>>
>> I want to keep working on my tutorial, and I want to present the  
>> simplest approach to viewing/adding content objects in a web  
>> browser as the first step.  I'd rather work on "multiple model  
>> object views" and "custom widgets" later, but if that is the only  
>> way to make this happen, I will have to change my plans.
>>
>> Thanks,
>> Steve
>>
>> --- On Mon, 3/23/09, Steve Schmechel <steveschmechel at yahoo.com>  
>> wrote:
>>>
>>> Auto-forms (or at least really fast templating) of a
>>> hierarchical object model would be the key to creating a
>>> rapid, web-based prototype of this type of application.
>>>
>>> I am not really having a problem with modeling the
>>> relationships or storing the object data in the ZODB, but
>>> with doing it in a way that it is easy to publish the
>>> contents to the web (the "ope" in "zope"
>>> :-)
>>
>>
>>
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> http://mail.zope.org/mailman/listinfo/grok-dev
> -- 
> Timothy Cook, MSc
> Health Informatics Research & Development Services
> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
> Skype ID == timothy.cook
> **************************************************************
> *You may get my Public GPG key from  popular keyservers or   *
> *from this link http://timothywayne.cook.googlepages.com/home*
> **************************************************************
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev