+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 <[email protected]>
ok, great :)
2012/11/2 Gerhard Petracek <[email protected]>
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 <[email protected]>
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 <[email protected]>
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
