2.3 is imminent, I don’t think a hefty amount is gonna make it now concerning new features.
I would agree concerning the asset manager, possibly needing some further thought or advancements.
If you have lots of images it can get confusing. Maybe it’s just me, but also the previews could be bigger to fill their transparent cells, or even have a larger magnified popover with the name as you roll over them or a corner area. I just noticed today also that animated gifs are animated in the asset manager and seem to perhaps have impact on the app - unless it’s just me, could be.
What would be nice is if the application kept all relative assets in an app support folder on the users system and used a getFileType to load the assets instead of being hard coded in the app bundle. I personally don’t need any pictures by default and would prefer to define my own defaults. This type of file system gathered by the app via a public folder would allow users to externally manage - comp assets, favicon, preloaders, patterns, logos, etc., either app wide or defined per project via a referenced project folder and structure. This seems like it would also work well with the missing asset feature.
Lastly it might be nice to allow CSS and JS assets, libraries to be dragged on the app and by doing so automatically reference these assets in the page settings, head, body, create the links, etc.,
Using CDN on export as an option would be nice also for the libraries that Blocs uses, Bootstrap, JQuery, Animate.css, FontAwesome, etc., to lessen server load calls and use instead user cache for these common libraries when available.
Sorry @norm, just dreaming and thinking aloud there a little, just some random thoughts, not sure any are applicable.
Blocs_User