I wrote an ExtJS application like this:
the sub menu is dynamic added by clicking the button on the left.
The question is :
as the sub panel is created dynamically, so if I refresh the whole page, the panel will go away.
What I expected is it could still display the same content before refresh pages.
So, my question is how to handle this in ExtJS?
Do I need to record the current panel information into Ext.App?
ExtJS is a framework to build Web Applications that run inside the browser.
With Web Applications, just like normal applications, you don't close the program and start it anew (like a browser refresh does) just because someone wants to switch to a different toolbar or look at different data. You work with multiple panels, switch between them, and/or open windows.
You could for instance generate multiple panels inside a container with card layout, and bring to front the panel that you want to show right now.
If you have a license that allows you to use Sencha Architect, there is a nice "navigation" sample available in Architect from where you can start and look at how it's done.
Related
I'm using the Ionic Framework to build a hybrid app and its heavily dependant on drag and drop features. Using the 'sidemenu' template I have created one main view, and two side menus.
The main view will use the Ionic Calendar to display data. The two side menus will be used as views where data will initial be stored in list form. I need to be able to drag elements from side menu and into the main screen, where they can then be dropped on the calendar.
All the events work perfect when in calendar view (ie. onClickItem, onClickTime, etc). The drag and drop call backs work fine too, when remaining in the side menu display area. However, when I try to drag the element out of the side menu area and into the calendar, only the onDragStop event is recognized and not the onClickTime event from the calendar.
I realize I'm trying to fuse a few things together here in a not so usual way. I can't even find anyone else making posts about the same thing. Maybe I'm making the wrong searches.
Any help, advice, or direction would be appreciated.
I'm building my first Angular.js + Bootstrap web site.
As far as user interface is concerned, I use a classical top navbar approach, with 7/8 items in navbar linking to the relative views. This is a first version of the site. When you click on "weather", you go to the weather page. When You click on "services", you go to the services page. That's ok.
But, I would like, for a better mobile user experience, when scrolling down, all views to be shown, in sequence... This is an example of what I mean, to be clearer...
Is it possible, preserving the angular.js "routing" logic?
UPDATE: I did change the page contents in the first link, adding two links in navbar, because of Ronni Skansing comment...
UPDATE2: I try to better reformulate the question:
Is it possible, with angular.js (+bootstrap), to design an UI with all views reachable without any click, but continuously, vertical scrolling the page, the way a typical mobile web app user is used to?
I don't think you can really have a single page unless you design your website to be a single page.
Anyway, I found a solution which is very similar to what you would like: simply add a transition on ng-view change. The user won't be able to scroll, it will still have to click on the navbar items. But the sensation will be similar to scrolling. See here the example. (remember to choose the slidedown effect)
I am trying to write a WPF application. The general outline of the application is as follows: There is a main window(Note that the main window is a full screen application) and there are several pages(Possibly 25) and I want to navigate from one page to another with a button click event on each page. What will be the best way to achieve this?
I have tried creating a Frame on the MainWindow and then use the frame to display pages, but my problem is that I can not navigate from one page to another from a button click on the pages. I am new to this and I would appreciate any help.
You could of at least tried a Google mate, this information is abundant, but because you thought typing a paragraph here was easier, I shall save you the trouble.... http://paulstovell.com/blog/wpf-navigation
I am building a WPF Standalone application. It consists of a menu on the left of the window and when a menu option is selected I want a page showing content related to the option selected shown on the right hand side of the window.
If a user selects a different menu option then the new view will be loaded.
If the user selects a previously selected menu option then that view will be shown but it will have held it's state. So if has a result set for customers with "bob" as a first name then when I view it again the result set will still be showing.
My questions is what is the best way to implement this.
Pages are not suitable as the app will not be viewed in a browser.
I could not see a Master Page -> content layout approach.
So is it a case of loading custom controls?
I am using the MVVM pattern.
Any help would be appreciated.
You could use TabControl with TabStripPlacement value set to "Left" - is that what you are looking for?
I managed to implement something similar detailed here using "workspaces". http://msdn.microsoft.com/en-us/magazine/dd419663.aspx
I'm running a dotnetnuke project (v7.0) with 2 portals.
I need to remove the default DDR menu from one page only.
The menu works great now with multiple pages and sub-pages, however on 1 specific page , ie landing page, I don't want to show the menu.
Right now I can think of 2 methods for achieving this:
Create a new skin template, remove menu, apply template to that one page
Use jquery to detect URL, for that page hide menu.
I'd rather just code the logic inside the template file, but I'm not strong in .net/c# and I'm new to DNN.
It's just one page today.
However, if you are using it for a landing page design I would recommend you just create another skin and exclude it from that and tailor that skin for that need.
That way when your non-technical editors need to work on the site and make a page that might only be used when linking from Google Adwords or whatever they can pick a template without that navigation and you as the developer/designer don't need to edit the skin to put in another exception based on the URL.