is worth considering exposing "state" of projector?
i can see use case being able externally detect status of projector might able better schedule (or abandon) activities in larger frameworks.
currently, internally within projector, there scheduled , rendercompleted items. see simple isbusy(): boolean way externally signalling projector in process of doing render. way, in macro framework, transitory state changes, won't ever represented in dom, abandoned.
of course invariably leads desire have sort of notification when projector becomes "unbusy". of course, scheduling next animation frame "onunbusy" work should work without putting burden on maquette.
the dilemma here positioned maquette minimalistic library, , projector shipped maquette sufficient every-day use. macro frameworks implement own custom projector in 80 lines of code.
adding 1 isbusy(): boolean feature small addition (both in download size , learning curve), doubt end there. encourage experiment custom projector. if, in end, turns out isbusy feature addition needed, send pull request , happy integrate that.
Comments
Post a Comment