Repository Restructuring #51
breautek
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Coming soon I'll be archiving modular repos and moving the content to a mono repo structure.
We will still have modular packages but using a mono-repo will make it easier to temporary link against dev builds for development for plugin modules and alike.
It will also be easier to build the documentation which need access to all repos to build the JavaDocs and DocC.
Consequentially it will also put all issues and discussions under the btfuse/fuse repository.
In other news I've added 3 new items to the Roadmap of features that I believe should be part of the core framework.
Extendable Loading Splash
Most hybrid frameworks has an issue where the "native" view is considered ready long before the webview is actually showing content. The intent here is to make it configurable (including disabling the splash altogether), or make it extendable enough that applications can implement their own views to act as the loading splash. The default behaviour will transition to the loading view from the splashscreen. The loading view will feature the application icon and a progress bar. The core framework will keep track of loading progress accordingly for anything internal.
Plugins will have an API exposed so that they can keep track of their own loading progress as well.
The webview will not be considered loaded until the webview performs an API call to native indicating that is ready. Application developers can implement logic to delay this signal if they need to do further asynchronous actions before they are ready to render the view.
Core StatusBar API
An API to control the state and styling of the StatusBar.
Instance Data Store API
A native-side memory data store which can be used to store and read state from. This data store can be useful to store view state, and can be recovered if the application's activity or UI is destroyed when it's in the background. When the user returns back to the app, the UI/activity must be reconstructed, and the instance store can be retrieved, allowing app developers to return and rebuild their view.
I'm a one-man army with lots of work ahead of me, that is only able to work after hours at this time so I can't create any kind of timeline, but these three new road map items I think is important for MVP.
Beta Was this translation helpful? Give feedback.
All reactions