newspaperTable merge with dataTable

[Dave <ja...@yahoo.com>]

  newspaperTable should be merged with dataTable. It should be a property of dataTable.
   
  <t:dataTable ....
            newspaperColumns="8"/>
   
  if the property is 0 or not defined, it is a normal table, otherwise render as newspaper.
   
  This way it can leverage all features of dataTable such as sorting and dynamic column model, etc.
  what do you think?
   
  Dave




		
---------------------------------
 Yahoo! Personals
 Skip the bars and set-ups and start using Yahoo! Personals for free

Re: newspaperTable merge with dataTable

[Mike Kienenberger <mk...@gmail.com>]

I don't think so, but you could create a trivial subclass of
t:dataTable called t:newspaperTable, and change the renderer.   Then
you'd inherit all of the non-rendering behavior of t:dataTable.

As I said, this is just a workaround until someone did the work to
combine the two rendering classes properly.   But it seems like doing
so might provide a partial quick-fix.

On 12/5/05, Jesse Wilson <li...@gmail.com> wrote:
> It's just a separate renderer, but it's a renderer that requires some
> parameters - the number of newspaper columns, and the gap
> between newspaper columns.
>
> Does JSF support multiple renderers for the same component
> simultaneously? In effect, could you render a dataTable with
> its regular renderer and a newspaper renderer in the same page?
> As far as I know this isn't supported.
>
>
>
> On 12/5/05, Mike Kienenberger <mk...@gmail.com> wrote:
> > Is the only difference in rendering?
> >
> > Perhaps someone could create a patch that provided an alternate
> > renderer for t:dataTable that performed the newspaper column layout.
> > That'd be a simpler intermediate step than trying to combine both
> > components.
> >
> > If nothing else, it'd make sense to open a JIRA improvement issue on this.
> >
> > On 12/2/05, Jesse Wilson <li...@gmail.com> wrote:
> > > I wrote newspaperTable a long time ago and
> > > I think this is a great idea. When I wrote the
> > > class I didn't extend dataTable as to make it
> > > much more attractive to the MyFaces admins -
> > > it would be quite controversial to add an attribute
> > > to one of the most popular components.
> > >
> > > But newspaperTable and dataTable are 99%
> > > the same code, and making this change makes
> > > a lot of sense. Unfortunately I won't be able to
> > > implement it due to lack of time and familiarity.
> > >
> > > Cheers,
> > > Jesse
> > >
> > >
> > > On 12/2/05, Dave <ja...@yahoo.com> wrote:
> > > >
> > > > newspaperTable should be merged with dataTable. It should be a property of
> > > > dataTable.
> > > >
> > > > <t:dataTable ....
> > > >           newspaperColumns="8"/>
> > > >
> > > > if the property is 0 or not defined, it is a normal table, otherwise render
> > > > as newspaper.
> > > >
> > > > This way it can leverage all features of dataTable such as sorting and
> > > > dynamic column model, etc.
> > > > what do you think?
> > > >
> > > > Dave
> > > >
> > > >
> > > >
> > > >  ________________________________
> > > >  Yahoo! Personals
> > > >  Skip the bars and set-ups and start using Yahoo! Personals for free
> > > >
> > > >
> > >
> >
>

Re: newspaperTable merge with dataTable

[Jesse Wilson <li...@gmail.com>]

It's just a separate renderer, but it's a renderer that requires some
parameters - the number of newspaper columns, and the gap
between newspaper columns.

Does JSF support multiple renderers for the same component
simultaneously? In effect, could you render a dataTable with
its regular renderer and a newspaper renderer in the same page?
As far as I know this isn't supported.



On 12/5/05, Mike Kienenberger <mk...@gmail.com> wrote:
> Is the only difference in rendering?
>
> Perhaps someone could create a patch that provided an alternate
> renderer for t:dataTable that performed the newspaper column layout.
> That'd be a simpler intermediate step than trying to combine both
> components.
>
> If nothing else, it'd make sense to open a JIRA improvement issue on this.
>
> On 12/2/05, Jesse Wilson <li...@gmail.com> wrote:
> > I wrote newspaperTable a long time ago and
> > I think this is a great idea. When I wrote the
> > class I didn't extend dataTable as to make it
> > much more attractive to the MyFaces admins -
> > it would be quite controversial to add an attribute
> > to one of the most popular components.
> >
> > But newspaperTable and dataTable are 99%
> > the same code, and making this change makes
> > a lot of sense. Unfortunately I won't be able to
> > implement it due to lack of time and familiarity.
> >
> > Cheers,
> > Jesse
> >
> >
> > On 12/2/05, Dave <ja...@yahoo.com> wrote:
> > >
> > > newspaperTable should be merged with dataTable. It should be a property of
> > > dataTable.
> > >
> > > <t:dataTable ....
> > >           newspaperColumns="8"/>
> > >
> > > if the property is 0 or not defined, it is a normal table, otherwise render
> > > as newspaper.
> > >
> > > This way it can leverage all features of dataTable such as sorting and
> > > dynamic column model, etc.
> > > what do you think?
> > >
> > > Dave
> > >
> > >
> > >
> > >  ________________________________
> > >  Yahoo! Personals
> > >  Skip the bars and set-ups and start using Yahoo! Personals for free
> > >
> > >
> >
>

Re: newspaperTable merge with dataTable

[Mike Kienenberger <mk...@gmail.com>]

Is the only difference in rendering?

Perhaps someone could create a patch that provided an alternate
renderer for t:dataTable that performed the newspaper column layout.  
That'd be a simpler intermediate step than trying to combine both
components.

If nothing else, it'd make sense to open a JIRA improvement issue on this.

On 12/2/05, Jesse Wilson <li...@gmail.com> wrote:
> I wrote newspaperTable a long time ago and
> I think this is a great idea. When I wrote the
> class I didn't extend dataTable as to make it
> much more attractive to the MyFaces admins -
> it would be quite controversial to add an attribute
> to one of the most popular components.
>
> But newspaperTable and dataTable are 99%
> the same code, and making this change makes
> a lot of sense. Unfortunately I won't be able to
> implement it due to lack of time and familiarity.
>
> Cheers,
> Jesse
>
>
> On 12/2/05, Dave <ja...@yahoo.com> wrote:
> >
> > newspaperTable should be merged with dataTable. It should be a property of
> > dataTable.
> >
> > <t:dataTable ....
> >           newspaperColumns="8"/>
> >
> > if the property is 0 or not defined, it is a normal table, otherwise render
> > as newspaper.
> >
> > This way it can leverage all features of dataTable such as sorting and
> > dynamic column model, etc.
> > what do you think?
> >
> > Dave
> >
> >
> >
> >  ________________________________
> >  Yahoo! Personals
> >  Skip the bars and set-ups and start using Yahoo! Personals for free
> >
> >
>

Re: newspaperTable merge with dataTable

[Jesse Wilson <li...@gmail.com>]

I wrote newspaperTable a long time ago and
I think this is a great idea. When I wrote the
class I didn't extend dataTable as to make it
much more attractive to the MyFaces admins -
it would be quite controversial to add an attribute
to one of the most popular components.

But newspaperTable and dataTable are 99%
the same code, and making this change makes
a lot of sense. Unfortunately I won't be able to
implement it due to lack of time and familiarity.

Cheers,
Jesse


On 12/2/05, Dave <ja...@yahoo.com> wrote:
>
> newspaperTable should be merged with dataTable. It should be a property of
> dataTable.
>
> <t:dataTable ....
>           newspaperColumns="8"/>
>
> if the property is 0 or not defined, it is a normal table, otherwise render
> as newspaper.
>
> This way it can leverage all features of dataTable such as sorting and
> dynamic column model, etc.
> what do you think?
>
> Dave
>
>
>
>  ________________________________
>  Yahoo! Personals
>  Skip the bars and set-ups and start using Yahoo! Personals for free
>
>