smartweb-devel

[smartweb-devel] Introducing a Web Entity Search Component

[Gaetano P. <gpe...@sm...>]

I'm thinking about introducing a standard web entity search  component.
Think about a form mask with customer field to valorize with the customer
id. Actually we do this opening a popup and managing manually all the
interaction between the opener and the opened window.
In my opinion a standard generalized ajax complient component ( :-) ) could
resolve this common web developing problem.
Waiting for opinions...
-- 
View this message in context: http://www.nabble.com/Introducing-a-Web-Entity-Search-Component-tf4961136s17546.html#a14209483
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Introducing a Web Entity Search Component

[Roberto Lo G. <rlo...@us...>]

I like the idea, but I've few questions for you:

- do you intend a component that doesn't need to be customized on a per
entity basis?
- in case the previous answer is yes, how do you intend to choose fields
that should be considered searchable?


Gaetano Perrone wrote:
> 
> I'm thinking about introducing a standard web entity search  component.
> Think about a form mask with customer field to valorize with the customer
> id. Actually we do this opening a popup and managing manually all the
> interaction between the opener and the opened window.
> In my opinion a standard generalized ajax complient component ( :-) )
> could
> resolve this common web developing problem.
> Waiting for opinions...
> 

-- 
View this message in context: http://www.nabble.com/Introducing-a-Web-Entity-Search-Component-tp14209483s17546p14335866.html
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Introducing a Web Entity Search Component

[Gaetano P. <gpe...@sm...>]

Truly I haven't yet got the time to think about how to implement but only to
what to implement.
Otherwise I think 2 approches are possibile:
1. Standard component to customize (by configuration: xml / properties)
2. Standard component that supports standard features: we could introduce a
tag library for doing it receiving the entity (the mapped class or a
property we can resolve with the mapped class at configuration time) the
criteria to filter. Mapped classes that are "searchable" could implement a
Searchable interface.
The previous sentence are just ideas at this time, but suggestion are
appreciated.



Roberto Lo Giacco wrote:
> 
> I like the idea, but I've few questions for you:
> 
> - do you intend a component that doesn't need to be customized on a per
> entity basis?
> - in case the previous answer is yes, how do you intend to choose fields
> that should be considered searchable?
> 
> 
> Gaetano Perrone wrote:
>> 
>> I'm thinking about introducing a standard web entity search  component.
>> Think about a form mask with customer field to valorize with the customer
>> id. Actually we do this opening a popup and managing manually all the
>> interaction between the opener and the opened window.
>> In my opinion a standard generalized ajax complient component ( :-) )
>> could
>> resolve this common web developing problem.
>> Waiting for opinions...
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Introducing-a-Web-Entity-Search-Component-tp14209483s17546p14336619.html
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Introducing a Web Entity Search Component

[Gaetano P. <gpe...@sm...>]

I'm thinking about a customized per entity component and a
a basic for name / description implementation to be customized.
Tipically a lot of search are for name...


Roberto Lo Giacco wrote:
> 
> I like the idea, but I've few questions for you:
> 
> - do you intend a component that doesn't need to be customized on a per
> entity basis?
> - in case the previous answer is yes, how do you intend to choose fields
> that should be considered searchable?
> 
> 
> Gaetano Perrone wrote:
>> 
>> I'm thinking about introducing a standard web entity search  component.
>> Think about a form mask with customer field to valorize with the customer
>> id. Actually we do this opening a popup and managing manually all the
>> interaction between the opener and the opened window.
>> In my opinion a standard generalized ajax complient component ( :-) )
>> could
>> resolve this common web developing problem.
>> Waiting for opinions...
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Introducing-a-Web-Entity-Search-Component-tp14209483s17546p15085405.html
Sent from the SmartWeb Developers mailing list archive at Nabble.com.

Re: [smartweb-devel] Introducing a Web Entity Search Component

[Roberto Lo G. <rlo...@sm...>]

Can you be more specific about your idea?

2008/1/25, Gaetano Perrone <gpe...@sm...>:
>
> I'm thinking about a customized per entity component and a
> a basic for name / description implementation to be customized.
> Tipically a lot of search are for name...

-- 
   Roberto Lo Giacco

Re: [smartweb-devel] Introducing a Web Entity Search Component

[Pino C. <gco...@gm...>]

It's a really good idea but It's not so simple as it seems..
In a simplest view of case you can consider to obtain ,from an input
parameter, a list of "BusinessObject"  described  by a String value.=20
1=C2=B0 question: Where? where do you want to visualize them?
2=C2=B0 question: What ? What do you intend to fill with tou search result =
? A
label ? an input text with a value?
3=C2=B0 question: how many items?Your search must be paginable ?=20
4=C2=B0 question: who ? Who can see this informations .We must filter them =
by an
auth property.
And so on..

I've an idea , and I'm studing to resolve all these questions in a very
elegant way ...
I think I'll post it in this days ...for the moment I'm curious to know you=
r
consideration..as well

:)


Third=20
But =20

Gaetano Perrone wrote:
>=20
> I'm thinking about introducing a standard web entity search  component.
> Think about a form mask with customer field to valorize with the customer
> id. Actually we do this opening a popup and managing manually all the
> interaction between the opener and the opened window.
> In my opinion a standard generalized ajax complient component ( :-) )
> could
> resolve this common web developing problem.
> Waiting for opinions...
>=20

--=20
View this message in context: http://www.nabble.com/Introducing-a-Web-Entit=
y-Search-Component-tp14209483s17546p15119029.html
Sent from the SmartWeb Developers mailing list archive at Nabble.com.