Skip to content

Question regarding Views #19

@schuma7

Description

@schuma7

Hi, I have just started experimenting with StarlingMVC and I must say that I really like the framework so far. However, there are some things related to the handling of views that are not quite clear:

1st Question:
Currently I use the following package structure:

  • com.company.game.views
    • controls
      • Table
        • Table
        • Row
      • DropDown
        • DropDown
        • DropDownItem
    • screens
      • screenA
        • ViewA
        • ViewB
      • screenB
        • ViewC
        • ViewD

Does this mean that I actually have to add every sub-package under com.company.game.views to the viewPackages property of the configuration (no-recursive directory traversal)?
If I don't do this, it seems as mediators do not process the [ViewAdded] metatag.

2nd Question
The documentation states that "Dependency injection occurs on all beans and all Starling display objects.". However, it seems as I still need to create a BeanProvider for all my views,
otherwise they are not found when I try to inject them. Is that correct?

In case it's relevant, I'm using the current version of StarlingMVC together with Starling 1.3.

Thank you for shedding some light on this.

p.s. I also posted this question in the Starling forum. Unfortunately, I cannot delete it from the forum myself, so feel free to get it removed from there.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions