The current behavior of the sidemenu in Codename One is that the sidemenu pushes the current form aside as it comes out. I need to have the sidemenu slide over the form without displacing it instead.
It appears that the only options are to modify the underlying code for the sidemenu or to utilize some other component in a way that would mimic sidemenu behavior. From a conversation I had with CN1 support, modifying the underlying code sounds problematic and I haven't been happy with the results thus far of layering other components on top of the form.
Has anyone else been able to successfully implement this functionality? if so, can you please share how it was done?
Thanks!
I would hope we can do that for you but scheduling is making this really challenging. If all else fails try avoiding the sidemenu altogether and using a Container in the layered pane or alternatively a full blown InteractionDialog to simulate a sidemenu.
Related
Background:
Since build v2.10.0, Desktop Support has been introduced into Flutter Stable Channel.
I am trying to develop a Desktop Application with it, achieving an adaptive split-view
Situation
As it is illustrated above,I'd like a customized(Arbitary,Drawer-Like) sidemenu widget to be FIXED (Undismissable) in adjacent to the root navigator of MaterialApp.When a new route has been pushed into the route stack,I need the hero animation only covers the content part and leave the SideMenu untouched.
Since MaterialApp hold the entire navigator (Have not find out a way to replace the root navigator or wrap it with any other container), I cannot customize the MaterialApp Layout.
The main consideration why I don't want to put SideMenu out of MaterialApp is that I want to use the whole material things for SideMenu building which requires context information such us MediaQuery, Directionality,Locale etc... And I want there only one entry to setup Material-relationed configurations to keep the style consistancy of the whole design.
In Short
Split Layout
Customizable Persistant SideMenu
No Hero for Side
Official-Styled Code Pattern
Question
If it's possible, I do not prefer modifying any source code of official packages.
How to achieve this in a Flutter/Material way?
Maybe MaterialApp.build could be helpful?
I'm new to Navigator 2.0 in Flutter, and now I'm trying to achieve BottomSheet behavior using declarative approach. Unfortunately, I only managed to come up with quite a cumbersome way to do that so I'm wondering if there's an easier way.
I'm building a shopping app and I want to show the item details card that slides out from the bottom of the screen, dimming the previous page (as shown in picture), when user taps on item in a list. I also want to allow url support, so that /item/id opens home page and then shows the details card over it.
So how I think this could be done is to push (or to add to Navigator's pages array in case of Navigator 2.0) custom non-opaque page with no transition animation using TransitionDelegate and PageRouteBuilder, and then animate dimming and sliding by hand using animation controllers. But this approach seems unnatural (and genuinely scares me to be honest) and it's still not clear to me how to handle back button in this case (Do I need to somehow notify the page to play closing animation from Navigator's onPopPage, is this the way to do this?).
If anyone has an experience of implementing similar feature, I would really appreciate sharing it! Or maybe you have come up with more elegant solution, then tell me about it and I'll give it a try! Thanks!
I followed this link http://www.wintellect.com/devcenter/jprosise/handling-the-back-button-in-windows-10-uwp-apps and "successfully" make my button work. I mean I can make my backbutton work between pages. However, if I navigate to a control which is inside this page and will cover the whole screen, then it would not allow me to back to the page. I will stuck in that control.
I'm wondering how to solve this problem. Currently I can think two possible ways (0) Override OnBackRequested() inside the control's code behind or viewmodel? (1) Override OnHardwareButtonsBackPressed() inside the control's code behind or viewmodel?. I don't know if these are correct way to do it or there is some better way to do it. Another reason for me to override is that I need to make some changes to the page navigation behavior.
As you have guessed, you simply need to hide the control again when the back button is pressed or back is requested in some other way. I would listen for the BackRequested event (not the HardwareButtons.BackPressed event) in the page's code-behind, and in the handling method you can check to see if the control is currently shown. The reason I recommend the BackRequested event is because it is universal, while HardwareButtons.BackPressed only works on a phone. Anyway, if the control is visible, then hide it, and set the Handled property of the event arguments to true. If the control is already hidden, don't do anything special to handle the event (because in that case you will want the navigation system to handle it by navigating to the previous page, if there is one). There are many aspects to navigation in Windows 10 -- please see these pages on Navigation and the SystemNavigationManager.
basically I want this splitview from MainPageView to load the departmentView which contains its own ViewModel that has an Observablecollection
<SplitView.Pane>
<Frame>
<local:DepartmentsView/>
</Frame>
</SplitView.Pane>
but it has to be in sync with the navigation service. because I am relying on the template10's OnNavigatedToAsync to load my data
This is interesting. Nobody has ever asked for this before. I am not 100% sure you want the Template 10 hamburger menu in this circumstance. Why? Because the T10 HamMenu is really built around the idea of managed buttons in the Pane. There is NOTHING stopping you from simply adding your own SplitView control to your app and doing what you are wanting. The more I think about it the more I think that might be the best thing for you to do. If you think otherwise, please explain. Otherwise, just adding a SPlitView might not have been an option you thought of until now. The HamMenu in T10 uses the SplitView control.
I am creating a new footer sublayout in sitecore for use in multiple sites (we run a multi site environment). Currently a sublayout called StandardLayout is used, but I would like to change this across several of our sites to a new layout GlobalFooter.
The problem is that child items of the Home Page have overridden layout components, so what I would like to know is if there is an easy way to change the layout without losing all of the overridden components (as I expect that I may need to reset the layout in order for the flow down to occur)?
I am hoping to be able to just change the top level element (Home) and then have this flow down to the child elements, otherwise this task will become very long and tedious if I need to go through each item and change the presentation to use the new footer.
The icon circled in red in the image above indicates that the presentation has been overridden for that particular sitecore item.
To answer your question, directly, there is no way to apply an update of the presentation details of a template to templates that inherit from it that have had their presentation details changed without losing the changes.
The solution described in the blog post you linked to is the best solution for updating inherited presentation details in this manner. IMHO, I believe that this functionality should have been built into Sitecore long ago as a separate button on the ribbon, and you may choose to add one if you are so inclined. If you do not have the time to do so however, creating an admin page that you later delete from the site after using is a perfectly viable solution as well.
This post appears to detail a way that I can achieve my goal, basically I would create a admin page that does not publish and put the code in the blog into it to update the layout via a button trigger.
https://www.sitecore.net/Learn/Blogs/Technical-Blogs/John-West-Sitecore-Blog/Posts/2011/09/Programmatically-Update-Layout-Details-with-the-Sitecore-ASPNET-CMS.aspx