09-27-2024, 02:06 PM
(This post was last modified: 09-27-2024, 02:11 PM by PurpleStudio.)
I'm developing a couple different apps right now for Haiku.
One of the applications I am developing - I think - will turn out best (from a user experience) if I use Stackview to change views depending on how the user interacts with the main application.
Example: I want to have several buttons on the main window that lead to other sections "inside" of the application. Instead of having a button open a whole new window (which doesn't look good if there are window's all over the desktop) I figured, why not just use Stackview to generate a view with the exact same dimensions as the main window's view, allow the user to use buttons, lists, etc and then if they click a "Back" button, it will take them back to the original window (or view).
That being said, Yab-Documentation doesn't really go very "in-depth" with their synopsis or explanation of Stackview. I guess it's not impossible to have a whole bunch of things going on inside different views.
This all being said, this leads me to my final point: how much input/output/widgets can I have going on inside different Stackviews? Can I treat each Stackview like a window in terms of the content that's drawn on said view? Can I have a view with a BoxView, a field that takes input from the user, buttons, &etc? Or is there a better way of doing this? Initially I thought I'd just open a window directly on top of the main window, that way it looks like one application, but if the user accidentally bumped or moved the window, then it would reveal the original one below it, and that doesn't make for a nice, clean, user-experience.
If this post seems "a bit of a ramble", my apologies. Just learning Yab and the breadth and widths of its capabilities.
Cheers.
EDIT: I did visit Besly's site for more info on "Stackview" but it looks like all their links on different resources and information are all broken. If you visit this LINK, and stroll down to Stackview, there's a hyperlink that is broken/leads nowhere.
One of the applications I am developing - I think - will turn out best (from a user experience) if I use Stackview to change views depending on how the user interacts with the main application.
Example: I want to have several buttons on the main window that lead to other sections "inside" of the application. Instead of having a button open a whole new window (which doesn't look good if there are window's all over the desktop) I figured, why not just use Stackview to generate a view with the exact same dimensions as the main window's view, allow the user to use buttons, lists, etc and then if they click a "Back" button, it will take them back to the original window (or view).
That being said, Yab-Documentation doesn't really go very "in-depth" with their synopsis or explanation of Stackview. I guess it's not impossible to have a whole bunch of things going on inside different views.
This all being said, this leads me to my final point: how much input/output/widgets can I have going on inside different Stackviews? Can I treat each Stackview like a window in terms of the content that's drawn on said view? Can I have a view with a BoxView, a field that takes input from the user, buttons, &etc? Or is there a better way of doing this? Initially I thought I'd just open a window directly on top of the main window, that way it looks like one application, but if the user accidentally bumped or moved the window, then it would reveal the original one below it, and that doesn't make for a nice, clean, user-experience.
If this post seems "a bit of a ramble", my apologies. Just learning Yab and the breadth and widths of its capabilities.
Cheers.
EDIT: I did visit Besly's site for more info on "Stackview" but it looks like all their links on different resources and information are all broken. If you visit this LINK, and stroll down to Stackview, there's a hyperlink that is broken/leads nowhere.
