I am a beginner in extjs.I am doing a application which is having multiple page with one page presented at a time.From the intial page in a button click i want present the next page.I am able to do this in a card layout.How can this be done in other layouts.
Card layout helps you swap pages (make one page visible and all its siblings not). That means in other layouts you must do it manually.
Have you a reason use different layout?
Related
So I've started getting the hang on ReactJS and have built myself a basic Single Page Website (SPW?).
It currently is 1 "page" (really just an area which spans the whole screen) with the ability for the user to scroll down to the second "page" by clicking a button (or just scrolling).
Now what I need to do is give the user the ability to scroll up as well... to another "page".
Content Area 1
↑
LANDING AREA (user must be dumped here on initial load of the site)
↓
Content Area 2
I hope this makes sense?
EDIT: Apologies for the incorrect use of "SPA"... I've since learned the difference between that and a single page website.
A "single page app" doesn't mean you literally have all of the content on one page. You can have different "pages", however loading them won't cause a page refresh because they're not new html pages served up by the server. You should look into React Router if you want people to be able to navigate to different "pages" in your SPA, otherwise you can look into window scrolling so that you can move up and down.
According to my understanding you are trying to build one page website where each content section you linked with internal page linking & added button for the users to scroll top/bottom. It's not single page application. It's single page website. But, for learning curve it's good to start.
So, today i have the same issue as described here.
It happenes under Appearance - Menus when i try to add more pages to my custom menu. Search option works but when i hit View All to browse all pages, then i am able to browse first two pages, other pages return No pages. text.
What might be wrong?
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'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.
I'm working on a drupal site, and what I'm wondering is, I have a site that will have a main navigation menu-bar at the top of the page.
Then, other then the front page, each page will have it's own set of links. Now these links will be duplicated across pages that relate to each other. So, I know essentially what I need to do is to create individual blocks of navigation and then control those based on the page but I don't know how to do that.
Can anyone explain what I would need to do for this to work? Tutorials or videos would be helpful.
Why not create a taxonomy vocabulary containing all of the links.
Then add a term reference field to your page content type with checkboxes for the widget type.
Then when you edit the page you will be able to select any links that are needed for that page.
Control how these links are displayed on the page by looking at the manage display tab when editing the structure of the page content type.