Ok, thank you again. You already saved me twice today.
2012/8/22 Christian Riedel
> That's up to your personal taste ;-)
>
> Am 23.08.2012 um 02:18 schrieb William Lopes:
>
> > Thank you so much again, it is solved.
> >
> > I put in util package, is a good practice?
> >
> > 2012/8/22 Christian R
That's up to your personal taste ;-)
Am 23.08.2012 um 02:18 schrieb William Lopes:
> Thank you so much again, it is solved.
>
> I put in util package, is a good practice?
>
> 2012/8/22 Christian Riedel
>
>> move br.cnt.aas.material.components.MaterialGridDataSource into another
>> package si
Thank you so much again, it is solved.
I put in util package, is a good practice?
2012/8/22 Christian Riedel
> move br.cnt.aas.material.components.MaterialGridDataSource into another
> package since it's obviously not a component class!
>
> Am 23.08.2012 um 02:03 schrieb William Lopes:
>
> > Th
move br.cnt.aas.material.components.MaterialGridDataSource into another package
since it's obviously not a component class!
Am 23.08.2012 um 02:03 schrieb William Lopes:
> Thanks.
>
> So, what do you advise?
>
> 2012/8/22 Christian Riedel
>
>> Before Tapestry 5.3 it was just a recommendation
Thanks.
So, what do you advise?
2012/8/22 Christian Riedel
> Before Tapestry 5.3 it was just a recommendation, now it's a requirement:
> NEVER put other classes than components, mixins or pages (except
> base-classes) into their corresponding packages!
> You know… Tapestry is doing MAGIC a.k.a.
Before Tapestry 5.3 it was just a recommendation, now it's a requirement: NEVER
put other classes than components, mixins or pages (except base-classes) into
their corresponding packages!
You know… Tapestry is doing MAGIC a.k.a. convention over configuration ;)
Am 23.08.2012 um 01:36 schrieb W
