Mo' notes.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@373 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
@@ -115,3 +115,10 @@ particular game and participating in the game on the client side.
|
|||||||
* Notes
|
* Notes
|
||||||
Where does the panel/view, controller stuff fit in? Should it be in its
|
Where does the panel/view, controller stuff fit in? Should it be in its
|
||||||
own package and used by the Parlor services or provided directly?
|
own package and used by the Parlor services or provided directly?
|
||||||
|
|
||||||
|
Update ParlorManager to check access control related things before
|
||||||
|
accepting and delivering an invitation.
|
||||||
|
|
||||||
|
How to prune stale invitations since invitations are not set up to be tied
|
||||||
|
to a location (in which case we could use occupant added/removed to
|
||||||
|
trigger invite cleanup)?
|
||||||
|
|||||||
@@ -46,3 +46,7 @@ configure the scene managers when they are initialized.
|
|||||||
|
|
||||||
Add code to flush scenes from the client scene manager cache.
|
Add code to flush scenes from the client scene manager cache.
|
||||||
|
|
||||||
|
We need some mechanism for the scene registry to know which SceneManager
|
||||||
|
derived class to instantiate. Probably something like
|
||||||
|
Scene.getManagerClassName() which can be implemented by an application
|
||||||
|
when it creates its Scene implementation.
|
||||||
|
|||||||
Reference in New Issue
Block a user