Greetings again, seems I am still not getting it.

I am trying to add the lifecycle transition buttons to the 
bootstrap-default table on the index page of one of my models (named 
DataCollection).

After trying for some time, I tried to simplify my problem case down to 
trying to just override what fields that table shows (since the 
documentation at 
http://hobocentral.net/tagdef/hobo_bootstrap/hobo_bootstrap/index-page says 
I should be able to do that), but my extend does not take effect:

<extend tag="index-page" for="DataCollection">
  <old-index-page merge>
    <content-body:>
      <collection: field="due_date"/>
    </content-body:>
  </old-index-page>
</extend>

What needs to be changed in this to effect the <collection>? And the 
actions-view within that? Or even state-view?

Thank you in advance.

2015. június 24., szerda 1:29:31 UTC+2 időpontban HuBandiT a következőt 
írta:
>
> But of course you are right sir! I did not read enough to realize the next 
> step in the hierarchy is the <input-many>.
>
> Below is the working solution:
>
> <extend tag="form" for="Dimension">
>   <old-form merge>
>     <field-list:>
>       <items-view:>
>         <input-many>
>           <field-list:>
>             <parent-view:>
>               <select-one include-none options="&@dimension.items"/>
>             </parent-view:>
>           </field-list:>
>         </input-many>
>       </items-view:>
>     </field-list:>
>   </old-form>
> </extend>
>
> Thanks again!
>
> PS: on a side note, I'm looking for a little more convenient tree-editing 
> UI than this simple nested form with the <select-one>s for the belong_to 
> association.
>
> 2015. június 22., hétfő 8:01:10 UTC+2 időpontban HuBandiT a következőt 
> írta:
>>
>> Greetings,
>>
>> Overview:
>>
>> I'm a beginner with Hobo, with some experience in Rails. I have a Hobo 
>> 2.1.1 app with the default bootstrap theme.
>>
>> I am facing this same problem: 
>> http://hobocentral.net/tutorials/42-customized-the-select-menus-in-a
>>
>> I am unsuccessful at adapting the suggested solution to my project 
>> however, and am seeking assistance.
>>
>> Details:
>>
>> I have two models in a has_many/belongs_to relationship. The 
>> AJAX-assisted nested edit form displays and functions correctly.
>>
>> However, I now need to customize the <select-one> for the belongs_to to 
>> raise the default 100 limit, and to add a custom query to limit the list of 
>> parents to the relevant ones.
>>
>> I was able to extend the "form" tag for the child to effect these 
>> changes, and those changes showed up on the form for the child. But the 
>> nested form of the parent did not change.
>>
>> I read through the DRYML tutorial, and then consulted the docs for 
>> <field-list> and <select-one> and <input-many> (including looking at their 
>> sources), but I'm hitting a wall and don't seem to be able to cross the 
>> line over into the nested form:
>>
>> <extend tag="form" for="Parent">
>>   <old-form merge>
>>     <field-list:>
>>       <items-view:>
>>           foobar
>>       </items-view:>
>>     </field-list:>
>>   </old-form>
>> </extend>
>>
>> this sucessfully replaces the series of nested forms with the diagnostic 
>> string "foobar" - but I am unable to go deeper.
>>
>> Question:
>>
>> What parameter chain do I use to get inside the nested forms?
>>
>> Thank you kindly in advance for any pointers.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/d/optout.

Reply via email to