I am looking for a control similar to the one used in FeedDemon 2.7. it's a ListView with paging capabilities. it divides contents into pages. at the bottom of the control, you can see Page 1 of 3 and so on. you can see what I mean at the bottom of the attached picture : Page 1 of 3 .
I hope you understand what I mean.
Thanks.alt text http://img193.imageshack.us/img193/133/listview.jpg
I suppose the "pager" at the bottom of the screen is a different control than the list itself...
Have a look here for a starting point. HTH
Related
I am looking for how you can build a link in draw io, so that when you click first, it hides a layer and then opens a different page of the same draw io document.
so far i tried this:
data:action/json,{"actions":[{"toggle": {"cells": ["SvuciECQg7tZUCU10AH1-3"]}},{"open": "data:page/id,IZEQzf0yfGXm-2QJ5-Q8"}]}
But it seems that the Toggle is executed after the Open, and I need the Toggle to be first and then the Open.
I even tried to do an Open of the same page I'm on, do the Toggle, and then do the Open of page 2, but it didn't work. I would appreciate if anyone knows how to do this, thank you very much.
This is pretty old, you've probably figured it out or given up by now. In case you haven't:
If you want to Hide a layer, just Hide the layer. This did exactly what you're describing: (I've inserted your IDs)
data:action/json,{"actions":[{"hide":{"cells":["SvuciECQg7tZUCU10AH1-3"]}},{"open":"data:page/id,IZEQzf0yfGXm-2QJ5-Q8"}]}
If you need to toggle the layer back on, you'll need to Show it again. The code you have works, it's kindof unexpected not knowing if the layer is showing or hidden at the start.
Unless the layer you want to show/hide is on the different page.
You won't be able to interact with objects on a page that's not in scope. In that case, you probably want to hide the layer by default. That way, when you Open the second page, the layer is already hidden.
I am working on this app where many pages (8+) are linking to the same page. Every page needs to show correct breadcrumb. Since many pages are linking to the same page, the target page (p5) has a number of breadcrumbs and each breadcrumb has a condition that an application item needs to have a specific value for the parent page.
For example pages 1,2,3,4,6,7 link to page 5. So page 5 has 6 separate breadcrumbs on it where the condition is when parent_page = x where x is the parent page number. So if the user comes from page 1, a correct breadcrumb is selected.
I feel that this is excessive and creates a mess. Also the number of pages that link to page 5 seems to grow. I could create new breadcrumbs for each parent page but I feel that this is wrong and want to find a better way. Can anyone point me in the right direction? how have you handled something like this in the past?
I haven't actually done it, but I remember wanting to at one time. I think you would need to "roll your own" breadcrumbs. You could use an APEX collection to keep track of the user's navigation by "pushing" and "popping" pages on to and off of the APEX collection. Then create a SQL-based list region to display these. You may need to create a bespoke list template to make this list look like breadcrumbs.
Had a similar requirement. Many paths to a single location and keeping the breadcrumbs in sync with the users path was a coding horror story. Finally we decided on not going down that road. The breadcrumb now shows the main path back to the main screen, which might not be the exact path the user followed. So, just a single breadcrumb per page. If you want to go back to the previous page then a "back" or "cancel" button could still do that, but not the breadcrumb.
Is there a way in Ionic 2 to be able to transition between pages as if we were in a Slides component? Meaning that as soon as I start swiping a little left or right I start seeing a piece of the next or previous page? If I continue swiping then I transition to the next/previous page, else I go back to seeing only my current page.
It's like having a dynamic slides component, where ion-slide are automatically added. A little bit like the way the infinite scroll works, we could have 2 to 3 ion-slide in the DOM and they'd be reused as we move forward/backward.
This feature will be available in beta 7 (we are in beta 6) for tabs in material design. The option to swipe back in the pages stack is already available but you must be running on a device to see it in action. Check out the Ionic2 road map to see whats up and coming: https://docs.google.com/document/d/1Qlc5X2eJyOB0izkFlH7KJ5BmMi0MeXUZRHJHt3hS6Wo/edit
I created a custom section named Created/Updated in Sitecore 7 just below the default “Quick info” section as shown below:
Recently we migrated our project from Sitecore 7 to Sitecore 8 but “Created/Updated” section developed by us is no more looking like quick info of Sitecore 7.
The code is similar to Quick info default code used in Sitecore.Shell.Applications.ContentEditor.Pipelines.RenderContentEditor namespace in Sitecore.Client.dll
As shown above the fields present in “Created/Updated” are not looking like “Quick info” section. Instead, we can see a distinct table and rows for fields and width of these fields is less because of which entire time in Created Time field is not visible at the moment and it is getting cropped. I am not sure how it changed in Sitecore8 and how it can be switched back to the correct view like Quick info of Sitecore 7.
Instead of outputting <input> HTML in your second column, just do straight values.
You will need to change CSS for your custom component.
First of all, make sure first column has fixed width and second column has nowrap style set:
td:nth-of-type(1) { width: 110px; }
td { white-space: nowrap; }
This will make second column that contains info to occupy whole rest of space after first column.
Important: CSS order does matter; also you would prefix td from example above with selector of your parent container element for your custom panel (not to mess with rest of tables on a page).
Also, you'd probably want to remove borders, to have look and feel like Quick View section has, but from your post it is unclear which element makes borders, likely to be the same TD.
Hope this helps!
I am having trouble stopping the first scrolling once the page loads. You can see it here http://foundation.zurb.com/docs/components/joyride.html . After loading the website, joyride window scrolls automatically page littlebit lower
See it better in the old demo http://zurb.com/playground/jquery-joyride-feature-tour-plugin
I need the website to load normally (with top bar) and then activate scrolling after "next" button is clicked.
I am using latest version of Foundation 4 and foundation.min
Currently I am trying the docs page and it does not scroll, so either they fixed it or it was not a problem at all initially.
http://foundation.zurb.com/docs/components/joyride.html
Either ways, I see the best solution for you is to have the first step way above in the page, so that even when it takes focus, there's no page scrolling needed.