Tobias Uhlig
Tobias Uhlig
![Screenshot 2024-06-25 at 16 30 18](https://github.com/neomjs/neo/assets/1177434/65f106b9-8516-4d3a-bd6f-67e99cc3ee7f)
![Screenshot 2024-06-25 at 15 45 38](https://github.com/neomjs/neo/assets/1177434/83f2ec52-0d9b-4751-9b9e-32d7a6422bdc)
right now, the amount of `getConfigInstanceByNtype()` calls got huge. it would help to store the closest first found controller and model instance inside a symbol to reduce the amount of...
![Screenshot 2024-06-23 at 21 22 52](https://github.com/neomjs/neo/assets/1177434/178a3c41-2bc4-4d95-8a82-85d2456e5196) this one needs brainstorming. while we could further polish the edge-cases, the fine grained major updates version would resolve it out of the box:...
reducing the overhead for windows which e.g. don't need AmCharts. @maxrahder
@maxrahder @ExtAnimal if i recall it correctly, we already had something similar with the helix inside the covid app. ![Screenshot 2024-06-23 at 19 35 23](https://github.com/neomjs/neo/assets/1177434/b1e2b158-f90b-427d-aed7-de81089ab67a) inside the LivePreview, the DOM...
without doing a deep dive, using `Neo.Responsive` feels like a namespace pollution. in case we want to share data across all instances of the plugin, we can either use a...
we need to move the resize listener logic outside of `construct()`. rationale: moving a component into the viewport of a different window => we still want it to be responsive.
`Neo.first()` is only meant for debugging. Custom apps can have custom Viewport ntypes and especially inside the multi-window scope it is crucial to match the right Viewport.