Hi,
Well the <contact-tag> suggestion doesn't seem to do anything. From
more googling and searching for other examples (there are very few!),
I think I need to include the field-list too correct?
And the examples seem to use <contact-view:> rather than <contact-
tag:>.

Using <contact-view:> will change the control to an input text control
but typing in it does a GET (I think) and displays a sub-window with
"The page you were looking for could not be found" . Do I have to use
ajax "part" logic? I am assuming that the "page" it cannot find is
related to the autocompletion. I read the tag reference for name-one
and find its examples confusing.

My extend looks like:

<extend tag="form" for="Sale">
  <old-form merge>
  <field-list:>
   <contact-view:><name-one /></contact-view:>
  </field-list:>
  </old-form>
</extend>

To further complicate things, the item I am trying to do the lookup on
has a "def name" function to return the name - it is not a simple
column in the table. Is this a problem?

Thanks,
 Mike


On Jun 24, 12:46 pm, oldlibmike <[email protected]> wrote:
> Thanks for the clarification on the "old-form". I don't get any errors
> now but unfortunately I still get a selection list on the form for
> contacts.
> It doesn't appear that the override is doing anything. I'll experiment
> some more. I'll certainly give the dryml manual another look!
>
>  - Mike
>
> On Jun 23, 3:27 pm, kevinpfromnm <[email protected]> wrote:
>
> > You need to include the old form when extending otherwise hobo has no
> > idea what you mean by <contact:> (btw it should be contact-tag)
>
> > <extend tag="form" for="Sale">
> >   <old-form merge>
> >     <contact-tag:><name-one /> ...
>
> > You might want to read through the dryml 
> > guidehttp://cookbook.hobocentral.net/manual/dryml-guide.  it helped me get
> > a handle on parameters and attributes.
>
> > On Jun 23, 1:12 pm, oldlibmike <[email protected]> wrote:
>
> > > Thanks for the reply. I still don't quite understand it though.
> > > I have a sales table that :belongs_to contact.
> > > In the fields list for sales, there is "contact" which currently
> > > brings up a picklist of contacts - which doesn't work because there
> > > are over 10,000 of them.
>
> > > I tried overriding the contact field in application.dryml as:
>
> > > <extend tag="form" for="Sale">
> > >   <contact:><name-one /></contact:
> > > </extend>
>
> > > For some reason, this causes my index page for sales to throw errors
> > > that method "contact" does not exist. I don't know why the form would
> > > impact the index page at all.
>
> > > I'm sure I'm missing some basic hobo concepts here. I'm rereading
> > > Kerouac for additional inspiration!
>
> > > Best Regards,
> > >  Mike
>
> > > On Jun 23, 2:11 pm, kevinpfromnm <[email protected]> wrote:
>
> > > > From the cookbook taglib docs (http://cookbook.hobocentral.net/
> > > > api_tag_defs/field-list) the param name for each input tag is #
> > > > {this_field.to_s.sub('?', '')}-tag, so you'd use something like <owner-
> > > > tag:><name-one />... in your override.  I think you also need to setup
> > > > the controller ajax response as well.
>
> > > > On Jun 23, 11:53 am, oldlibmike <[email protected]> wrote:
>
> > > > > I am getting further into my application and now find that I need to
> > > > > change some of my "pick lists" for owners to "name-one" due to the
> > > > > many possible entries.
>
> > > > > I cannot find any clear examples in the tutorials or documentation on
> > > > > exactly where and how I do form overrides.
>
> > > > > Do I create a "<extend tag="form" for "MyTable"> in application.dryml?
> > > > > How do I just change the input type for a "belongs-to" owner? The form
> > > > > defaults just use a field-list. Where and how do I control the type of
> > > > > input used for each field?
>
> > > > > Do I need to create an entire form from scratch if I don't want the
> > > > > default?
>
> > > > > I'd appreciate any guidance or examples!
>
> > > > > Thanks,
> > > > >  Mike
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
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