You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by Gerhard Petracek <ge...@gmail.com> on 2012/11/02 17:09:36 UTC
[DISCUSS] DELTASPIKE-288
hi @ all,
i pushed a first draft for DELTASPIKE-288.
i started with the original api provided by codi and improved (+ prepared)
some parts based on a short discussion with brian and mark.
as soon as we have the final api and spi, i'll start with the final
integration with jsf.
right now we have the first steps for:
- type-safe config and navigation (+ event)
- folder support
- new meta-model which allows to change the meta-data during the
bootstrapping process. (it's the basis for the final (fixed) meta-data
representation.)
- @Page and @Folder are optional (they get added dynamically during the
bootstrapping process, if they aren't in place)
- no conceptual difference between meta-data provided by the framework and
custom meta-data
- no conceptual difference between callbacks provided by the framework and
custom callbacks
- view-config meta-data from codi (e.g.: @PageBean and @PageParameter)
- callbacks from codi (e.g.: @PreRenderView and @Secured)
- (optional) helpers from codi for manual/dynamic use-cases (e.g.:
ViewNavigationHandler and PageParameterContext)
there are still a lot of todos and some parts which aren't implemented.
since there are a lot of constellations we have to support, i'll start a
step-by-step discussion next week.
you are welcome to look at the current api + spi as well as the use-cases +
tests i've pushed (to see the basic direction).
regards,
gerhard
Re: [DISCUSS] DELTASPIKE-288
Posted by Thomas Andraschko <zo...@gmail.com>.
oh, you'r right. It's ok for me :)
2012/11/11 Gerhard Petracek <ge...@gmail.com>
> hi thomas,
>
> that's aligned with @PreRenderView which is also a term used by the jsf2+
> specification (see the javax.faces.event package - e.g.
> PreRenderViewEvent).
>
> regards,
> gerhard
>
>
>
> 2012/11/11 Thomas Andraschko <an...@gmail.com>
>
> > Hi,
> >
> > @PreViewAction sounds weird because of "preview". Maybe BeforeViewAction
> > would be better.
> >
> > The other classes/annotations sounds fine! :)
> >
> > Regards,
> > Thomas
> >
> > 2012/11/11 Gerhard Petracek <ge...@gmail.com>
> >
> > > hi @ all,
> > >
> > > it would be great to get feedback about the names (used in the api) we
> > have
> > > right now.
> > > as mentioned by thomas, we could align some of them - e.g.:
> > >
> > > @View -> @ViewRef
> > > @Page -> @View
> > > @PageBean -> @ViewControllerBean
> > > @PrePageAction -> PreViewAction
> > > @PageParameter -> @NavigationParameter
> > > PageParameterContext -> NavigationParameterContext
> > >
> > > while discussing the names, i'll start to write the documentation for
> the
> > > api and spi which allows us to get a shared perception for the next
> step
> > of
> > > the discussion.
> > >
> > > regards,
> > > gerhard
> > >
> > >
> > >
> > > 2012/11/2 Thomas Andraschko <an...@gmail.com>
> > >
> > > > ok, great :)
> > > >
> > > > 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> > > >
> > > > > hi thomas,
> > > > >
> > > > > that's one of the first topics i would like to discuss next week.
> > > > > (i just imported them with the same name to avoid confusion).
> > > > >
> > > > > we could rename @View e.g. to @ViewRef and @Page to @View (and
> > > > > @PageParameter e.g. to @ViewParameter)
> > > > > however, @ViewParameter might be a bit misleading.
> > > > >
> > > > > regards,
> > > > > gerhard
> > > > >
> > > > >
> > > > >
> > > > > 2012/11/2 Thomas Andraschko <an...@gmail.com>
> > > > >
> > > > > > Hi Gerhard,
> > > > > >
> > > > > > just one question.
> > > > > > The "View" name is currently used for all the functions but NOT
> for
> > > > > @Page,
> > > > > > @PageBean or @PageParameter.
> > > > > > Wouldn't it be better to call them @View... too?
> > > > > >
> > > > > > Regards,
> > > > > > Thomas
> > > > > >
> > > > > > 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> > > > > >
> > > > > > > hi @ all,
> > > > > > >
> > > > > > > i pushed a first draft for DELTASPIKE-288.
> > > > > > > i started with the original api provided by codi and improved
> (+
> > > > > > prepared)
> > > > > > > some parts based on a short discussion with brian and mark.
> > > > > > >
> > > > > > > as soon as we have the final api and spi, i'll start with the
> > final
> > > > > > > integration with jsf.
> > > > > > >
> > > > > > > right now we have the first steps for:
> > > > > > > - type-safe config and navigation (+ event)
> > > > > > > - folder support
> > > > > > > - new meta-model which allows to change the meta-data during
> the
> > > > > > > bootstrapping process. (it's the basis for the final (fixed)
> > > > meta-data
> > > > > > > representation.)
> > > > > > > - @Page and @Folder are optional (they get added dynamically
> > > during
> > > > > the
> > > > > > > bootstrapping process, if they aren't in place)
> > > > > > > - no conceptual difference between meta-data provided by the
> > > > framework
> > > > > > and
> > > > > > > custom meta-data
> > > > > > > - no conceptual difference between callbacks provided by the
> > > > framework
> > > > > > and
> > > > > > > custom callbacks
> > > > > > > - view-config meta-data from codi (e.g.: @PageBean and
> > > > @PageParameter)
> > > > > > > - callbacks from codi (e.g.: @PreRenderView and @Secured)
> > > > > > > - (optional) helpers from codi for manual/dynamic use-cases
> > (e.g.:
> > > > > > > ViewNavigationHandler and PageParameterContext)
> > > > > > >
> > > > > > > there are still a lot of todos and some parts which aren't
> > > > implemented.
> > > > > > > since there are a lot of constellations we have to support,
> i'll
> > > > start
> > > > > a
> > > > > > > step-by-step discussion next week.
> > > > > > > you are welcome to look at the current api + spi as well as the
> > > > > > use-cases +
> > > > > > > tests i've pushed (to see the basic direction).
> > > > > > >
> > > > > > > regards,
> > > > > > > gerhard
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] DELTASPIKE-288
Posted by Gerhard Petracek <ge...@gmail.com>.
hi thomas,
that's aligned with @PreRenderView which is also a term used by the jsf2+
specification (see the javax.faces.event package - e.g. PreRenderViewEvent).
regards,
gerhard
2012/11/11 Thomas Andraschko <an...@gmail.com>
> Hi,
>
> @PreViewAction sounds weird because of "preview". Maybe BeforeViewAction
> would be better.
>
> The other classes/annotations sounds fine! :)
>
> Regards,
> Thomas
>
> 2012/11/11 Gerhard Petracek <ge...@gmail.com>
>
> > hi @ all,
> >
> > it would be great to get feedback about the names (used in the api) we
> have
> > right now.
> > as mentioned by thomas, we could align some of them - e.g.:
> >
> > @View -> @ViewRef
> > @Page -> @View
> > @PageBean -> @ViewControllerBean
> > @PrePageAction -> PreViewAction
> > @PageParameter -> @NavigationParameter
> > PageParameterContext -> NavigationParameterContext
> >
> > while discussing the names, i'll start to write the documentation for the
> > api and spi which allows us to get a shared perception for the next step
> of
> > the discussion.
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2012/11/2 Thomas Andraschko <an...@gmail.com>
> >
> > > ok, great :)
> > >
> > > 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> > >
> > > > hi thomas,
> > > >
> > > > that's one of the first topics i would like to discuss next week.
> > > > (i just imported them with the same name to avoid confusion).
> > > >
> > > > we could rename @View e.g. to @ViewRef and @Page to @View (and
> > > > @PageParameter e.g. to @ViewParameter)
> > > > however, @ViewParameter might be a bit misleading.
> > > >
> > > > regards,
> > > > gerhard
> > > >
> > > >
> > > >
> > > > 2012/11/2 Thomas Andraschko <an...@gmail.com>
> > > >
> > > > > Hi Gerhard,
> > > > >
> > > > > just one question.
> > > > > The "View" name is currently used for all the functions but NOT for
> > > > @Page,
> > > > > @PageBean or @PageParameter.
> > > > > Wouldn't it be better to call them @View... too?
> > > > >
> > > > > Regards,
> > > > > Thomas
> > > > >
> > > > > 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> > > > >
> > > > > > hi @ all,
> > > > > >
> > > > > > i pushed a first draft for DELTASPIKE-288.
> > > > > > i started with the original api provided by codi and improved (+
> > > > > prepared)
> > > > > > some parts based on a short discussion with brian and mark.
> > > > > >
> > > > > > as soon as we have the final api and spi, i'll start with the
> final
> > > > > > integration with jsf.
> > > > > >
> > > > > > right now we have the first steps for:
> > > > > > - type-safe config and navigation (+ event)
> > > > > > - folder support
> > > > > > - new meta-model which allows to change the meta-data during the
> > > > > > bootstrapping process. (it's the basis for the final (fixed)
> > > meta-data
> > > > > > representation.)
> > > > > > - @Page and @Folder are optional (they get added dynamically
> > during
> > > > the
> > > > > > bootstrapping process, if they aren't in place)
> > > > > > - no conceptual difference between meta-data provided by the
> > > framework
> > > > > and
> > > > > > custom meta-data
> > > > > > - no conceptual difference between callbacks provided by the
> > > framework
> > > > > and
> > > > > > custom callbacks
> > > > > > - view-config meta-data from codi (e.g.: @PageBean and
> > > @PageParameter)
> > > > > > - callbacks from codi (e.g.: @PreRenderView and @Secured)
> > > > > > - (optional) helpers from codi for manual/dynamic use-cases
> (e.g.:
> > > > > > ViewNavigationHandler and PageParameterContext)
> > > > > >
> > > > > > there are still a lot of todos and some parts which aren't
> > > implemented.
> > > > > > since there are a lot of constellations we have to support, i'll
> > > start
> > > > a
> > > > > > step-by-step discussion next week.
> > > > > > you are welcome to look at the current api + spi as well as the
> > > > > use-cases +
> > > > > > tests i've pushed (to see the basic direction).
> > > > > >
> > > > > > regards,
> > > > > > gerhard
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] DELTASPIKE-288
Posted by Thomas Andraschko <an...@gmail.com>.
Hi,
@PreViewAction sounds weird because of "preview". Maybe BeforeViewAction
would be better.
The other classes/annotations sounds fine! :)
Regards,
Thomas
2012/11/11 Gerhard Petracek <ge...@gmail.com>
> hi @ all,
>
> it would be great to get feedback about the names (used in the api) we have
> right now.
> as mentioned by thomas, we could align some of them - e.g.:
>
> @View -> @ViewRef
> @Page -> @View
> @PageBean -> @ViewControllerBean
> @PrePageAction -> PreViewAction
> @PageParameter -> @NavigationParameter
> PageParameterContext -> NavigationParameterContext
>
> while discussing the names, i'll start to write the documentation for the
> api and spi which allows us to get a shared perception for the next step of
> the discussion.
>
> regards,
> gerhard
>
>
>
> 2012/11/2 Thomas Andraschko <an...@gmail.com>
>
> > ok, great :)
> >
> > 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> >
> > > hi thomas,
> > >
> > > that's one of the first topics i would like to discuss next week.
> > > (i just imported them with the same name to avoid confusion).
> > >
> > > we could rename @View e.g. to @ViewRef and @Page to @View (and
> > > @PageParameter e.g. to @ViewParameter)
> > > however, @ViewParameter might be a bit misleading.
> > >
> > > regards,
> > > gerhard
> > >
> > >
> > >
> > > 2012/11/2 Thomas Andraschko <an...@gmail.com>
> > >
> > > > Hi Gerhard,
> > > >
> > > > just one question.
> > > > The "View" name is currently used for all the functions but NOT for
> > > @Page,
> > > > @PageBean or @PageParameter.
> > > > Wouldn't it be better to call them @View... too?
> > > >
> > > > Regards,
> > > > Thomas
> > > >
> > > > 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> > > >
> > > > > hi @ all,
> > > > >
> > > > > i pushed a first draft for DELTASPIKE-288.
> > > > > i started with the original api provided by codi and improved (+
> > > > prepared)
> > > > > some parts based on a short discussion with brian and mark.
> > > > >
> > > > > as soon as we have the final api and spi, i'll start with the final
> > > > > integration with jsf.
> > > > >
> > > > > right now we have the first steps for:
> > > > > - type-safe config and navigation (+ event)
> > > > > - folder support
> > > > > - new meta-model which allows to change the meta-data during the
> > > > > bootstrapping process. (it's the basis for the final (fixed)
> > meta-data
> > > > > representation.)
> > > > > - @Page and @Folder are optional (they get added dynamically
> during
> > > the
> > > > > bootstrapping process, if they aren't in place)
> > > > > - no conceptual difference between meta-data provided by the
> > framework
> > > > and
> > > > > custom meta-data
> > > > > - no conceptual difference between callbacks provided by the
> > framework
> > > > and
> > > > > custom callbacks
> > > > > - view-config meta-data from codi (e.g.: @PageBean and
> > @PageParameter)
> > > > > - callbacks from codi (e.g.: @PreRenderView and @Secured)
> > > > > - (optional) helpers from codi for manual/dynamic use-cases (e.g.:
> > > > > ViewNavigationHandler and PageParameterContext)
> > > > >
> > > > > there are still a lot of todos and some parts which aren't
> > implemented.
> > > > > since there are a lot of constellations we have to support, i'll
> > start
> > > a
> > > > > step-by-step discussion next week.
> > > > > you are welcome to look at the current api + spi as well as the
> > > > use-cases +
> > > > > tests i've pushed (to see the basic direction).
> > > > >
> > > > > regards,
> > > > > gerhard
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] DELTASPIKE-288
Posted by Gerhard Petracek <ge...@gmail.com>.
hi thomas,
yes - i did it already in a local branch.
i planned to push it after a 2nd review of the new approach.
(we need the window-context from mark to finish the missing parts and i
would like to finish them before the 2nd review.)
regards,
gerhard
2013/2/14 Thomas Andraschko <an...@gmail.com>
> Hi Gerhard,
>
> any news about this?
> Will the names be changed for the 0.4 release?
>
> Regards,
> Thomas
>
> 2012/11/13 Brian Leathem <bl...@gmail.com>
>
> > +1 These name seem fine to me.
> >
> > Brian
> >
> >
> > On 12-11-11 06:56 AM, Gerhard Petracek wrote:
> >
> >> hi @ all,
> >>
> >> it would be great to get feedback about the names (used in the api) we
> >> have
> >> right now.
> >> as mentioned by thomas, we could align some of them - e.g.:
> >>
> >> @View -> @ViewRef
> >> @Page -> @View
> >> @PageBean -> @ViewControllerBean
> >> @PrePageAction -> PreViewAction
> >> @PageParameter -> @NavigationParameter
> >> PageParameterContext -> NavigationParameterContext
> >>
> >> while discussing the names, i'll start to write the documentation for
> the
> >> api and spi which allows us to get a shared perception for the next step
> >> of
> >> the discussion.
> >>
> >> regards,
> >> gerhard
> >>
> >>
> >>
> >> 2012/11/2 Thomas Andraschko <an...@gmail.com>
> >>
> >> ok, great :)
> >>>
> >>> 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> >>>
> >>> hi thomas,
> >>>>
> >>>> that's one of the first topics i would like to discuss next week.
> >>>> (i just imported them with the same name to avoid confusion).
> >>>>
> >>>> we could rename @View e.g. to @ViewRef and @Page to @View (and
> >>>> @PageParameter e.g. to @ViewParameter)
> >>>> however, @ViewParameter might be a bit misleading.
> >>>>
> >>>> regards,
> >>>> gerhard
> >>>>
> >>>>
> >>>>
> >>>> 2012/11/2 Thomas Andraschko <an...@gmail.com>
> >>>>
> >>>> Hi Gerhard,
> >>>>>
> >>>>> just one question.
> >>>>> The "View" name is currently used for all the functions but NOT for
> >>>>>
> >>>> @Page,
> >>>>
> >>>>> @PageBean or @PageParameter.
> >>>>> Wouldn't it be better to call them @View... too?
> >>>>>
> >>>>> Regards,
> >>>>> Thomas
> >>>>>
> >>>>> 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> >>>>>
> >>>>> hi @ all,
> >>>>>>
> >>>>>> i pushed a first draft for DELTASPIKE-288.
> >>>>>> i started with the original api provided by codi and improved (+
> >>>>>>
> >>>>> prepared)
> >>>>>
> >>>>>> some parts based on a short discussion with brian and mark.
> >>>>>>
> >>>>>> as soon as we have the final api and spi, i'll start with the final
> >>>>>> integration with jsf.
> >>>>>>
> >>>>>> right now we have the first steps for:
> >>>>>> - type-safe config and navigation (+ event)
> >>>>>> - folder support
> >>>>>> - new meta-model which allows to change the meta-data during the
> >>>>>> bootstrapping process. (it's the basis for the final (fixed)
> >>>>>>
> >>>>> meta-data
> >>>
> >>>> representation.)
> >>>>>> - @Page and @Folder are optional (they get added dynamically
> during
> >>>>>>
> >>>>> the
> >>>>
> >>>>> bootstrapping process, if they aren't in place)
> >>>>>> - no conceptual difference between meta-data provided by the
> >>>>>>
> >>>>> framework
> >>>
> >>>> and
> >>>>>
> >>>>>> custom meta-data
> >>>>>> - no conceptual difference between callbacks provided by the
> >>>>>>
> >>>>> framework
> >>>
> >>>> and
> >>>>>
> >>>>>> custom callbacks
> >>>>>> - view-config meta-data from codi (e.g.: @PageBean and
> >>>>>>
> >>>>> @PageParameter)
> >>>
> >>>> - callbacks from codi (e.g.: @PreRenderView and @Secured)
> >>>>>> - (optional) helpers from codi for manual/dynamic use-cases (e.g.:
> >>>>>> ViewNavigationHandler and PageParameterContext)
> >>>>>>
> >>>>>> there are still a lot of todos and some parts which aren't
> >>>>>>
> >>>>> implemented.
> >>>
> >>>> since there are a lot of constellations we have to support, i'll
> >>>>>>
> >>>>> start
> >>>
> >>>> a
> >>>>
> >>>>> step-by-step discussion next week.
> >>>>>> you are welcome to look at the current api + spi as well as the
> >>>>>>
> >>>>> use-cases +
> >>>>>
> >>>>>> tests i've pushed (to see the basic direction).
> >>>>>>
> >>>>>> regards,
> >>>>>> gerhard
> >>>>>>
> >>>>>>
> >
>
Re: [DISCUSS] DELTASPIKE-288
Posted by Thomas Andraschko <an...@gmail.com>.
Hi Gerhard,
any news about this?
Will the names be changed for the 0.4 release?
Regards,
Thomas
2012/11/13 Brian Leathem <bl...@gmail.com>
> +1 These name seem fine to me.
>
> Brian
>
>
> On 12-11-11 06:56 AM, Gerhard Petracek wrote:
>
>> hi @ all,
>>
>> it would be great to get feedback about the names (used in the api) we
>> have
>> right now.
>> as mentioned by thomas, we could align some of them - e.g.:
>>
>> @View -> @ViewRef
>> @Page -> @View
>> @PageBean -> @ViewControllerBean
>> @PrePageAction -> PreViewAction
>> @PageParameter -> @NavigationParameter
>> PageParameterContext -> NavigationParameterContext
>>
>> while discussing the names, i'll start to write the documentation for the
>> api and spi which allows us to get a shared perception for the next step
>> of
>> the discussion.
>>
>> regards,
>> gerhard
>>
>>
>>
>> 2012/11/2 Thomas Andraschko <an...@gmail.com>
>>
>> ok, great :)
>>>
>>> 2012/11/2 Gerhard Petracek <ge...@gmail.com>
>>>
>>> hi thomas,
>>>>
>>>> that's one of the first topics i would like to discuss next week.
>>>> (i just imported them with the same name to avoid confusion).
>>>>
>>>> we could rename @View e.g. to @ViewRef and @Page to @View (and
>>>> @PageParameter e.g. to @ViewParameter)
>>>> however, @ViewParameter might be a bit misleading.
>>>>
>>>> regards,
>>>> gerhard
>>>>
>>>>
>>>>
>>>> 2012/11/2 Thomas Andraschko <an...@gmail.com>
>>>>
>>>> Hi Gerhard,
>>>>>
>>>>> just one question.
>>>>> The "View" name is currently used for all the functions but NOT for
>>>>>
>>>> @Page,
>>>>
>>>>> @PageBean or @PageParameter.
>>>>> Wouldn't it be better to call them @View... too?
>>>>>
>>>>> Regards,
>>>>> Thomas
>>>>>
>>>>> 2012/11/2 Gerhard Petracek <ge...@gmail.com>
>>>>>
>>>>> hi @ all,
>>>>>>
>>>>>> i pushed a first draft for DELTASPIKE-288.
>>>>>> i started with the original api provided by codi and improved (+
>>>>>>
>>>>> prepared)
>>>>>
>>>>>> some parts based on a short discussion with brian and mark.
>>>>>>
>>>>>> as soon as we have the final api and spi, i'll start with the final
>>>>>> integration with jsf.
>>>>>>
>>>>>> right now we have the first steps for:
>>>>>> - type-safe config and navigation (+ event)
>>>>>> - folder support
>>>>>> - new meta-model which allows to change the meta-data during the
>>>>>> bootstrapping process. (it's the basis for the final (fixed)
>>>>>>
>>>>> meta-data
>>>
>>>> representation.)
>>>>>> - @Page and @Folder are optional (they get added dynamically during
>>>>>>
>>>>> the
>>>>
>>>>> bootstrapping process, if they aren't in place)
>>>>>> - no conceptual difference between meta-data provided by the
>>>>>>
>>>>> framework
>>>
>>>> and
>>>>>
>>>>>> custom meta-data
>>>>>> - no conceptual difference between callbacks provided by the
>>>>>>
>>>>> framework
>>>
>>>> and
>>>>>
>>>>>> custom callbacks
>>>>>> - view-config meta-data from codi (e.g.: @PageBean and
>>>>>>
>>>>> @PageParameter)
>>>
>>>> - callbacks from codi (e.g.: @PreRenderView and @Secured)
>>>>>> - (optional) helpers from codi for manual/dynamic use-cases (e.g.:
>>>>>> ViewNavigationHandler and PageParameterContext)
>>>>>>
>>>>>> there are still a lot of todos and some parts which aren't
>>>>>>
>>>>> implemented.
>>>
>>>> since there are a lot of constellations we have to support, i'll
>>>>>>
>>>>> start
>>>
>>>> a
>>>>
>>>>> step-by-step discussion next week.
>>>>>> you are welcome to look at the current api + spi as well as the
>>>>>>
>>>>> use-cases +
>>>>>
>>>>>> tests i've pushed (to see the basic direction).
>>>>>>
>>>>>> regards,
>>>>>> gerhard
>>>>>>
>>>>>>
>
Re: [DISCUSS] DELTASPIKE-288
Posted by Brian Leathem <bl...@gmail.com>.
+1 These name seem fine to me.
Brian
On 12-11-11 06:56 AM, Gerhard Petracek wrote:
> hi @ all,
>
> it would be great to get feedback about the names (used in the api) we have
> right now.
> as mentioned by thomas, we could align some of them - e.g.:
>
> @View -> @ViewRef
> @Page -> @View
> @PageBean -> @ViewControllerBean
> @PrePageAction -> PreViewAction
> @PageParameter -> @NavigationParameter
> PageParameterContext -> NavigationParameterContext
>
> while discussing the names, i'll start to write the documentation for the
> api and spi which allows us to get a shared perception for the next step of
> the discussion.
>
> regards,
> gerhard
>
>
>
> 2012/11/2 Thomas Andraschko <an...@gmail.com>
>
>> ok, great :)
>>
>> 2012/11/2 Gerhard Petracek <ge...@gmail.com>
>>
>>> hi thomas,
>>>
>>> that's one of the first topics i would like to discuss next week.
>>> (i just imported them with the same name to avoid confusion).
>>>
>>> we could rename @View e.g. to @ViewRef and @Page to @View (and
>>> @PageParameter e.g. to @ViewParameter)
>>> however, @ViewParameter might be a bit misleading.
>>>
>>> regards,
>>> gerhard
>>>
>>>
>>>
>>> 2012/11/2 Thomas Andraschko <an...@gmail.com>
>>>
>>>> Hi Gerhard,
>>>>
>>>> just one question.
>>>> The "View" name is currently used for all the functions but NOT for
>>> @Page,
>>>> @PageBean or @PageParameter.
>>>> Wouldn't it be better to call them @View... too?
>>>>
>>>> Regards,
>>>> Thomas
>>>>
>>>> 2012/11/2 Gerhard Petracek <ge...@gmail.com>
>>>>
>>>>> hi @ all,
>>>>>
>>>>> i pushed a first draft for DELTASPIKE-288.
>>>>> i started with the original api provided by codi and improved (+
>>>> prepared)
>>>>> some parts based on a short discussion with brian and mark.
>>>>>
>>>>> as soon as we have the final api and spi, i'll start with the final
>>>>> integration with jsf.
>>>>>
>>>>> right now we have the first steps for:
>>>>> - type-safe config and navigation (+ event)
>>>>> - folder support
>>>>> - new meta-model which allows to change the meta-data during the
>>>>> bootstrapping process. (it's the basis for the final (fixed)
>> meta-data
>>>>> representation.)
>>>>> - @Page and @Folder are optional (they get added dynamically during
>>> the
>>>>> bootstrapping process, if they aren't in place)
>>>>> - no conceptual difference between meta-data provided by the
>> framework
>>>> and
>>>>> custom meta-data
>>>>> - no conceptual difference between callbacks provided by the
>> framework
>>>> and
>>>>> custom callbacks
>>>>> - view-config meta-data from codi (e.g.: @PageBean and
>> @PageParameter)
>>>>> - callbacks from codi (e.g.: @PreRenderView and @Secured)
>>>>> - (optional) helpers from codi for manual/dynamic use-cases (e.g.:
>>>>> ViewNavigationHandler and PageParameterContext)
>>>>>
>>>>> there are still a lot of todos and some parts which aren't
>> implemented.
>>>>> since there are a lot of constellations we have to support, i'll
>> start
>>> a
>>>>> step-by-step discussion next week.
>>>>> you are welcome to look at the current api + spi as well as the
>>>> use-cases +
>>>>> tests i've pushed (to see the basic direction).
>>>>>
>>>>> regards,
>>>>> gerhard
>>>>>
Re: [DISCUSS] DELTASPIKE-288
Posted by Gerhard Petracek <ge...@gmail.com>.
hi @ all,
it would be great to get feedback about the names (used in the api) we have
right now.
as mentioned by thomas, we could align some of them - e.g.:
@View -> @ViewRef
@Page -> @View
@PageBean -> @ViewControllerBean
@PrePageAction -> PreViewAction
@PageParameter -> @NavigationParameter
PageParameterContext -> NavigationParameterContext
while discussing the names, i'll start to write the documentation for the
api and spi which allows us to get a shared perception for the next step of
the discussion.
regards,
gerhard
2012/11/2 Thomas Andraschko <an...@gmail.com>
> ok, great :)
>
> 2012/11/2 Gerhard Petracek <ge...@gmail.com>
>
> > hi thomas,
> >
> > that's one of the first topics i would like to discuss next week.
> > (i just imported them with the same name to avoid confusion).
> >
> > we could rename @View e.g. to @ViewRef and @Page to @View (and
> > @PageParameter e.g. to @ViewParameter)
> > however, @ViewParameter might be a bit misleading.
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2012/11/2 Thomas Andraschko <an...@gmail.com>
> >
> > > Hi Gerhard,
> > >
> > > just one question.
> > > The "View" name is currently used for all the functions but NOT for
> > @Page,
> > > @PageBean or @PageParameter.
> > > Wouldn't it be better to call them @View... too?
> > >
> > > Regards,
> > > Thomas
> > >
> > > 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> > >
> > > > hi @ all,
> > > >
> > > > i pushed a first draft for DELTASPIKE-288.
> > > > i started with the original api provided by codi and improved (+
> > > prepared)
> > > > some parts based on a short discussion with brian and mark.
> > > >
> > > > as soon as we have the final api and spi, i'll start with the final
> > > > integration with jsf.
> > > >
> > > > right now we have the first steps for:
> > > > - type-safe config and navigation (+ event)
> > > > - folder support
> > > > - new meta-model which allows to change the meta-data during the
> > > > bootstrapping process. (it's the basis for the final (fixed)
> meta-data
> > > > representation.)
> > > > - @Page and @Folder are optional (they get added dynamically during
> > the
> > > > bootstrapping process, if they aren't in place)
> > > > - no conceptual difference between meta-data provided by the
> framework
> > > and
> > > > custom meta-data
> > > > - no conceptual difference between callbacks provided by the
> framework
> > > and
> > > > custom callbacks
> > > > - view-config meta-data from codi (e.g.: @PageBean and
> @PageParameter)
> > > > - callbacks from codi (e.g.: @PreRenderView and @Secured)
> > > > - (optional) helpers from codi for manual/dynamic use-cases (e.g.:
> > > > ViewNavigationHandler and PageParameterContext)
> > > >
> > > > there are still a lot of todos and some parts which aren't
> implemented.
> > > > since there are a lot of constellations we have to support, i'll
> start
> > a
> > > > step-by-step discussion next week.
> > > > you are welcome to look at the current api + spi as well as the
> > > use-cases +
> > > > tests i've pushed (to see the basic direction).
> > > >
> > > > regards,
> > > > gerhard
> > > >
> > >
> >
>
Re: [DISCUSS] DELTASPIKE-288
Posted by Thomas Andraschko <an...@gmail.com>.
ok, great :)
2012/11/2 Gerhard Petracek <ge...@gmail.com>
> hi thomas,
>
> that's one of the first topics i would like to discuss next week.
> (i just imported them with the same name to avoid confusion).
>
> we could rename @View e.g. to @ViewRef and @Page to @View (and
> @PageParameter e.g. to @ViewParameter)
> however, @ViewParameter might be a bit misleading.
>
> regards,
> gerhard
>
>
>
> 2012/11/2 Thomas Andraschko <an...@gmail.com>
>
> > Hi Gerhard,
> >
> > just one question.
> > The "View" name is currently used for all the functions but NOT for
> @Page,
> > @PageBean or @PageParameter.
> > Wouldn't it be better to call them @View... too?
> >
> > Regards,
> > Thomas
> >
> > 2012/11/2 Gerhard Petracek <ge...@gmail.com>
> >
> > > hi @ all,
> > >
> > > i pushed a first draft for DELTASPIKE-288.
> > > i started with the original api provided by codi and improved (+
> > prepared)
> > > some parts based on a short discussion with brian and mark.
> > >
> > > as soon as we have the final api and spi, i'll start with the final
> > > integration with jsf.
> > >
> > > right now we have the first steps for:
> > > - type-safe config and navigation (+ event)
> > > - folder support
> > > - new meta-model which allows to change the meta-data during the
> > > bootstrapping process. (it's the basis for the final (fixed) meta-data
> > > representation.)
> > > - @Page and @Folder are optional (they get added dynamically during
> the
> > > bootstrapping process, if they aren't in place)
> > > - no conceptual difference between meta-data provided by the framework
> > and
> > > custom meta-data
> > > - no conceptual difference between callbacks provided by the framework
> > and
> > > custom callbacks
> > > - view-config meta-data from codi (e.g.: @PageBean and @PageParameter)
> > > - callbacks from codi (e.g.: @PreRenderView and @Secured)
> > > - (optional) helpers from codi for manual/dynamic use-cases (e.g.:
> > > ViewNavigationHandler and PageParameterContext)
> > >
> > > there are still a lot of todos and some parts which aren't implemented.
> > > since there are a lot of constellations we have to support, i'll start
> a
> > > step-by-step discussion next week.
> > > you are welcome to look at the current api + spi as well as the
> > use-cases +
> > > tests i've pushed (to see the basic direction).
> > >
> > > regards,
> > > gerhard
> > >
> >
>
Re: [DISCUSS] DELTASPIKE-288
Posted by Gerhard Petracek <ge...@gmail.com>.
hi thomas,
that's one of the first topics i would like to discuss next week.
(i just imported them with the same name to avoid confusion).
we could rename @View e.g. to @ViewRef and @Page to @View (and
@PageParameter e.g. to @ViewParameter)
however, @ViewParameter might be a bit misleading.
regards,
gerhard
2012/11/2 Thomas Andraschko <an...@gmail.com>
> Hi Gerhard,
>
> just one question.
> The "View" name is currently used for all the functions but NOT for @Page,
> @PageBean or @PageParameter.
> Wouldn't it be better to call them @View... too?
>
> Regards,
> Thomas
>
> 2012/11/2 Gerhard Petracek <ge...@gmail.com>
>
> > hi @ all,
> >
> > i pushed a first draft for DELTASPIKE-288.
> > i started with the original api provided by codi and improved (+
> prepared)
> > some parts based on a short discussion with brian and mark.
> >
> > as soon as we have the final api and spi, i'll start with the final
> > integration with jsf.
> >
> > right now we have the first steps for:
> > - type-safe config and navigation (+ event)
> > - folder support
> > - new meta-model which allows to change the meta-data during the
> > bootstrapping process. (it's the basis for the final (fixed) meta-data
> > representation.)
> > - @Page and @Folder are optional (they get added dynamically during the
> > bootstrapping process, if they aren't in place)
> > - no conceptual difference between meta-data provided by the framework
> and
> > custom meta-data
> > - no conceptual difference between callbacks provided by the framework
> and
> > custom callbacks
> > - view-config meta-data from codi (e.g.: @PageBean and @PageParameter)
> > - callbacks from codi (e.g.: @PreRenderView and @Secured)
> > - (optional) helpers from codi for manual/dynamic use-cases (e.g.:
> > ViewNavigationHandler and PageParameterContext)
> >
> > there are still a lot of todos and some parts which aren't implemented.
> > since there are a lot of constellations we have to support, i'll start a
> > step-by-step discussion next week.
> > you are welcome to look at the current api + spi as well as the
> use-cases +
> > tests i've pushed (to see the basic direction).
> >
> > regards,
> > gerhard
> >
>
Re: [DISCUSS] DELTASPIKE-288
Posted by Thomas Andraschko <an...@gmail.com>.
Hi Gerhard,
just one question.
The "View" name is currently used for all the functions but NOT for @Page,
@PageBean or @PageParameter.
Wouldn't it be better to call them @View... too?
Regards,
Thomas
2012/11/2 Gerhard Petracek <ge...@gmail.com>
> hi @ all,
>
> i pushed a first draft for DELTASPIKE-288.
> i started with the original api provided by codi and improved (+ prepared)
> some parts based on a short discussion with brian and mark.
>
> as soon as we have the final api and spi, i'll start with the final
> integration with jsf.
>
> right now we have the first steps for:
> - type-safe config and navigation (+ event)
> - folder support
> - new meta-model which allows to change the meta-data during the
> bootstrapping process. (it's the basis for the final (fixed) meta-data
> representation.)
> - @Page and @Folder are optional (they get added dynamically during the
> bootstrapping process, if they aren't in place)
> - no conceptual difference between meta-data provided by the framework and
> custom meta-data
> - no conceptual difference between callbacks provided by the framework and
> custom callbacks
> - view-config meta-data from codi (e.g.: @PageBean and @PageParameter)
> - callbacks from codi (e.g.: @PreRenderView and @Secured)
> - (optional) helpers from codi for manual/dynamic use-cases (e.g.:
> ViewNavigationHandler and PageParameterContext)
>
> there are still a lot of todos and some parts which aren't implemented.
> since there are a lot of constellations we have to support, i'll start a
> step-by-step discussion next week.
> you are welcome to look at the current api + spi as well as the use-cases +
> tests i've pushed (to see the basic direction).
>
> regards,
> gerhard
>