I  think I must be missing something on how name-one works.

Below is what I have from my application.dryml for my product form:


<extend tag="form" for="Product">
    <old-form merge>
        <field-list: fields="category, customer, department, vendor, name, 
serial_number, date_ordered, date_received, date_invoiced,
        vendor_invoice, scc_invoice, quantity, dollar_amount, 
warranty_years, warranty_days, item, comments">
            
            <name-label:>Part Description</name-label:>
            
            <category-tag:><name-one/></category-tag:>
            <customer-tag:><name-one/></customer-tag:>
            <vendor-tag:><name-one/></vendor-tag:>
            
        </field-list:>
    </old-form>
</extend>

When I run it, I don't get anything different. I must have missed something 
on how to use name-one.

Jim

On Tuesday, May 1, 2012 2:48:51 PM UTC-6, kevinpfromnm wrote:
>
> You're not going to get something like that out of the box.  Something 
> like a lightbox or other modal dialog to hold the table.  The table will 
> need to be ajax updated based on filters.  Then you'll need a custom 
> javascript to pass the selection back to the form.
>
> Otherwise you'd need to store/pass along the form information for a 
> standard page load somehow, then repopulate the form when you get back.
>
> Seriously though, give the name-one a try.  It's probably 80-90% towards 
> what you're after functionality wise.
>
> On Tuesday, May 1, 2012 2:17:31 PM UTC-6, jhstephenson wrote:
>>
>> What I am looking for is something like this:
>>
>> I have am creating a new part purchased for a customer. It has the 
>> following fields:
>>
>> Name (part description): 
>> Date:
>> Customer:
>> Quantity:
>> etc....
>>
>> When I get to the customer field, right now it is a drop down box listing 
>> all of my customers (or at least as many as are allowed to be displayed). I 
>> actually have over 200 possible customers to chose from, which I believe is 
>> too many for a drop down box, even if it was allowed.
>>
>> I am not sure if this can be accomplished by what you are describing or 
>> not.
>>
>> What I would like is the following:
>>
>> Name (part description): 
>> Date:
>> Customer: _______________ |Select| (Button or Link)
>> Quantity:
>> etc....
>>
>> When the Select button is clicked I want to bring up a Table view with 
>> the folllowing on it:
>>
>> Search ____________________________
>>
>> Customer                     Address                       Contact
>>
>> ABC Customer              Any Address                 Some Contact     
>> |Select| (Button or Link)
>> .                                                                            
>>                     
>> |Select| (Button or Link)
>> .                                                                            
>>                     
>> |Select| (Button or Link)
>> .                                                                            
>>                     
>> |Select| (Button or Link)
>> XYZ Customer               Their Address               Their 
>> Contact       |Select| (Button or Link)
>>
>> When selected it would return the Customer ID just like it had been 
>> chosen from a Drop down list.
>>
>> I am not sure if that is what you are describing or not.
>>
>> Does that make sense?
>>
>> Jim
>>
>> On Tuesday, May 1, 2012 12:45:06 PM UTC-6, kevinpfromnm wrote:
>>>
>>> You're talking about a form input that instead of a plain select, you 
>>> can filter by name.  You're probably looking for the <name-one /> tag.  
>>> You'll need to setup an autocompleter to go along with it.
>>>
>>> On Tuesday, May 1, 2012 10:22:30 AM UTC-6, jhstephenson wrote:
>>>>
>>>> In another development tool I use, when I have a selection list that 
>>>> exceeds 20 or 30 items I usually create a button on the data entry form 
>>>> that takes me to a screen similar in form to Hobo's Index page. From there 
>>>> I can search for the record I am looking for and then click a button or 
>>>> link to select the record I want. The ID of the selected record is 
>>>> returned 
>>>> to the calling form and the link to the child is established.
>>>>
>>>> It looks to me like that should be possible with something like a 
>>>> Table-Plus based form, but I have no clue how to set that up. 
>>>>
>>>> Can someone point me to an example of how something like this might be 
>>>> done?
>>>>
>>>> Thanks,
>>>> Jim
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/hobousers/-/c2PjYX2U4XkJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/hobousers?hl=en.

Reply via email to