[ic] special_search component feedback (better late than never)

[Brendan Crosser-McGay]

> -----Original Message-----
> From: interchange-users-admin@interchange.redhat.com
> [mailto:interchange-users-admin@interchange.redhat.com]On Behalf Of
> Julia Jacobs
> Sent: Friday, February 22, 2002 1:01 PM
> To: interchange-users@interchange.redhat.com
> Subject: [ic] special_search component feedback (better late
> than never)
>
>
> Mr. Brendan Crosser-McGay,
>
> Developer of the great special_search component!
>
> A while back you asked for feedback on your component and I
> guess I could
> make up a creative excuse like I was caught up in a freaky
> time machine
> accident, but the truth is I only noticed these issues recently.
>
> So I hope its not too late to give you some feedback
> regarding your killer
> component.
>
> I used it on my results.html page and deleted the content so
> I would not get
> doubling search results.  I noticed that if there were more
> than 50 items in
> a category, only the 50 would show with your component and the content
> deleted out of the results.html page.  Whereas with the
> regular content in
> the results page, over 50 items would create multiple pages
> to click and
> view more items.  I tried to figure out how to add this
> feature to your
> component or leave this feature in the content but I'm too much of an
> Interchange newbie.  I'm hoping you can help me.
>
> Another feature that would be soooooo awesome (if its not to
> much of a pain
> in the butt to add) would be a drop down menu labelled:
> Layout Type and the
> menu choices: boxes, rows.  Boxes would put the item thumb, SKU,
> description, etc all in a single cell <td> as opposed to
> spreading it out
> among 6 columns and 6 <td>s.  If Boxes is chosen you can put
> a number to see
> how many items you want in a row.  The radial buttons the
> special_search
> component currently has can stay the same for both layout types.
> --
> Julia Jacobs
> Currant Media
> 407-977-4523
> Fax 407-261-0176
> http://www.currantmedia.com
> Members of The Better Business Bureau
> * Multimedia Producers
> * Web Design & Development
> * 2D/3D Graphics/Animation
> * Hosting, domain and e-mail
> * E-Commerce ­ check, credit card validation


No its not too late :)

I'm just glad someone found it useful, I haven't tested it much, I just
knew that it worked when I used it, so I'm glad someone else can find
some use for it.  The purpose I had in mind was for multiple stores
using a component that would let them choose what was displayed and
what was not displayed, I was tired of having to customize that results
page, so I just made that up.  I am thinking of making a customized
shopping cart page, but I kindof want to find a efficient method of
linking all of the fields being displayed in the catalog together.

Inotherwords, if the catalog doesn't use the SKU field on many places,
or if the in stock feature isn't being used, etc. you understand, the
user can change it without having to dig in the interchange too much.

As far as the changes you suggest, I don't know why you would want all
the results in one cell, but if you want to, its very easy, just take
the special_search component and you might need to make another
conditional infront of each row to see if its using multiple td's or
just one.  I'll see what I can do.

It only displays 50?  Hmmm, I guess I never really tried using it with
 more then 10 or 15 items, so that would explain why it does that, I'm
sure the default search returnitems is something like 50, its a search
parameter, just put the searchmax on whatever, and then "OF COURSE" add
the [more-list][more][/more-list] tag between the [search-region] and
[search-list], or between [/search-list] and [/search-region].

----------------------------
Brendan Crosser-McGay
brendan@paymentonline.com
----------------------------