By tabs I mean something like this (the navigation bar on the left):
I haven't found anything on the internet that demonstrates the proper use of tabs in a fyne application. Anyone knows?
The bar on the left is the List widget https://developer.fyne.io/api/v2.0/widget/list.html.
There is also the AppTabs container that is designed for areas of an application https://developer.fyne.io/api/v2.0/container/apptabs.html.
Remember that all of the source code to fyne_demo is at https://github.com/fyne-io/fyne/tree/master/cmd/fyne_demo.
Related
I'm trying to find a tutorial or book, that explain who to make a menu application, like the iPod/iPad menu, with images as buttons, and pages. What i'm trying to do, is a menu, with a Popover window, when an option from the popover is selected, then the menu is filled (with code) with the buttons/images, that can be located in more then a page.
Thanks you in advance
Okay there are two things you can use here:
The Three20 library , which has several extra components you can use as well: repository here
If you want just a view similar to that and nothing else, you can go with myLauncher: repository here
I know there are probably more, but these were the main two I looked at when I went looking for a similar view.
I have been able to disable tabs in a tab bar using the following helpful tutorial.
http://blog.flexexamples.com/2007/08/25/enabling-and-disabling-specific-tabs-in-a-tabbar-control/
This only works for mx tabbar. Does anyone know how to do this for a spark tabbar? I prefer the lnf of the spark one. When I try it with a spark tab bar it just disables the viewstack of the tab and not the actual tab.
An alternative solution may just be to make the mx tab bar look like a spark toolbar with the rounded edges. Any ideas on this?
Many thanks in advance
Based on this post in the Adobe Forums, How to Disable a tab in a spark tab bar, your best solution seems to be a custom skin. There is also a 'hack' mentioned at the end, that was posted last month.
Give the control you have with the new structure I think the custom skin makes the most sense.
I'm joining an Eiffel project that has a horribly outdated GUI design. The GUI is built with EiffelVision2 and the application is Windows platform only.
how can I change the look/design of the widgets, like defining shape and color of scrollbars, buttons, window borders and so on?
thank you!
I think this can be done using manifest file.
For instance, https://svn.eiffel.com/eiffelstudio/trunk/Src/Eiffel/Ace/ec.exe.manifest allows EiffelStudio to have nicer look than default classic theme.
You can check similar question/answers from http://tech.groups.yahoo.com/group/eiffel_software/message/8791
So I have a PRISM v2 (M-V-VM) application up and running. It's 4 modules that load into a tab control. Great.
Now my question is - where to go from here? Most tutorials seem to stop at this point.
Maybe I'm overthinking this, but it almost seems like I'd need each module to be its own PRISM application, but that can't be right.
Please help a PRISM n00b figure out where to go from here.
What I'm looking to do next: Each tab (module) has its own toolbar with buttons, etc. Clicking a button should change the content (view) below the toolbar.
How to achieve this (correctly) with PRISM? Each module (tab) should have control over its content, however, clicking cetain buttons in one tab may trigger an event in another tab (hence the use of PRISM).
So what's the correct-PRISM way to change views within a module?
I think you are thinking about this a bit hard. I'll explain.
What is commonly referred to as the "Shell" should contain all of your navigation controls. For example, if I wanted a tabbed UI, my Shell would contain a tab control (usually you'd decorate that TabControl with a RegionName, like "ShellTabs").
Your Modules will contribute views to these shell elements. So let's say you have the email module, it will contribute an inbox view to your collection of tabs. It could contribute these views by registering them with the RegionManager for the app (like registering your view with the Region called "ShellTabs").
Modules don't have to contribute anything visual. I have one module in our app that takes care of logging and other background processes.
Hopefully this clears up some of the nomenclature and helps you know what the responsibility of each part is.
I'm making a Cocoa application, and I would like a panel like the 'Attributes Inspector' in Interface Builder. So with big tabs on the top and collapsable/expandable groups. Does anyone know how I can do this?
This is an image of the Attributes Inspector:
Attributes Inspector http://developer.apple.com/documentation/DeveloperTools/Conceptual/XcodeQuickTour/Art/hello_win_attributes.jpg
So I actually want to make a window like the one shown in the image above.
InspectorKit is FOSS on github.
There's no built-in Cocoa controls to do this. You're going to have to write some custom views which replicate the functionality.
There some good advice for creating custom controls in the answers to this question: Looking for info on custom drawing of interface components (Cocoa)
If you need additional help, I recommend you ask smaller, more specific questions explaining what you've tried and what hasn't worked.
I've written some custom classes to do this- it ended up being less work than I expected. I broke it down into two separate components which can be used independently- the first handles the icons at the top and performs the view switching and the second handles the expandable panes:
My code is available at github and is under the BSD 2-clause license.