You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that previously we have avoided to add a header on the webapp because it might be the interruption when we want to import the app in the other applications such as Starrydata.
However, it is now possible to display the header only on the StarryDigitizer page by not loading the component from StarryDigitizer.vue (which is exported as a library), but only from App.vue.
I guess the version, copyrights and maybe release notes are OK to be staying in the footer, but it should be better if the document is on the header because it is assumed that many users will want to refer to the documentation.
@t29mato
I want to hear your opinion, but not urgent☕️
The text was updated successfully, but these errors were encountered:
@yu-smc
Thanks for your suggestion. While adding a header could work without impacting the component, I'm not sure if it's necessary just for the documentation, as it might reduce screen space. Like with games, not everyone may read the manual.
Sorry, some part of my thoughts was lacking from the message above.
I was also thinking about adding menu for some operations such as exporting data, and also settings icon on the header (Still, the header space will be very narrow)
I understand that previously we have avoided to add a header on the webapp because it might be the interruption when we want to import the app in the other applications such as Starrydata.
However, it is now possible to display the header only on the StarryDigitizer page by not loading the component from StarryDigitizer.vue (which is exported as a library), but only from App.vue.
I guess the version, copyrights and maybe release notes are OK to be staying in the footer, but it should be better if the document is on the header because it is assumed that many users will want to refer to the documentation.
@t29mato
I want to hear your opinion, but not urgent☕️
The text was updated successfully, but these errors were encountered: