I would like to achieve IONIC application that allows a transition from right to left (and up to down, and others) between two pages, much like Snapchat. To switch from the main screen (the camera) in the center, to the list of snap on left and the list of stories on right.
Do you have an idea / solution to this problem?
PS: Snapchat is just one example, I do not wish to reproduce the application itself, but if you want me to examples in the basis for comparison, that's fine.
You may want to use ion-slides for transition from right to left http://ionicframework.com/docs/api/directive/ionSlides/
There should be other solutions for other type of transitions (for example https://github.com/driftyco/ionic-ion-tinder-cards) however mixing all type of transitions and in different directions might be confusing for the end user. I would suggest to stick with the standard UI controls and behavior which is clear and unambiguous for the end user.
Related
In the Codename One API, there are several methods that cointain the word "Tensile", such as isAlwaysTensile(), setAlwaysTensile(), getTensileLength(), etc.
I didn't find an explanation of the meaning of "Tensile" in the context of a mobile app. What are example of use of these methods?
Tensile is the rubber band effect you get when you drag the UI beyond the edge and it lets you. Then you release and the UI bounces back into the valid position.
This is the common behavior in iOS, on Android a highlight color effect is used to indicate the same behavior.
Generally these methods are best lest alone, they are set by the platform themes and modifying them can result in unexpected behavior.
I want to display a list of names on the screen and a vertical alphabet scroll bar on the right side of it...similar to the contact list application in Android.
So when I click a letter from alphabet scroll bar, all the names starting with that letter should appear at the top of the screen.
List of names
That is what fixed lead section mode does. It fixes the selection in one place so the rest of the list moves around it. This is quite common in non-touch UI's for mobile phones but not so much for newer devices so this feature isn't mentioned in the developer guide or used anywhere in our samples...
Furthermore, please notice that we no longer recommend using List as explained in the section covering it in the developer guide. It's an advanced and complex component that won't deliver advantages for most common use cases.
I am developing a little application to manage messages. Such application has two panels on big screens: a sidebar with the messages list and a panel with the message details: [ ][ ]. But in case the screen is small (smartphone) and just because we want it to be responsive, the sidebar is the only thing shown and when you click on a message the details are displayed hiding the sidebar.
With Angular, the last approach is quite easy doing some routing and it works very well. My problem comes when the screen is big enough to accept both panels together, as I want Angular to still control the flow but not hide/show any panel as I want both views visible.
Is there a way to go routing (one view at a time) with Angular when the screen is small but change the behavior when the screen is big to show the two views at a time?
By the way, I'm using Bootstrap to control the responsiveness and that's working quite well (the panels hide/show depending on screen size), I'm just worried about how am I going to handle this with Angular now.
Examples
Just to see if I can explain myself better, this is what I want it to be when screen is big enough: http://plnkr.co/edit/WuN08Q?p=preview (make sure you make the preview screen big enough to see it, click on a message, and then resize to smaller size to see how the details hide)
And this when it's small: http://plnkr.co/edit/UL1OpXjzEcCU9722lpA9?p=preview
First example has two panels visible and one of them is hidden when screen becomes small, second example uses two views and works as I want it when screen is small. Now what I want is to make it behave like first example when screen is big enough and like second when it's small.
Thank you Angular wizards!
Probably not the answer you're looking for, but one solution building upons Jonathan Hair's answer is contained in a fork of you original plunker:
http://plnkr.co/edit/chdn6XDpdnqaay3VfOqI?p=preview
This solution is not preferred because you end up having to refresh when you break across your sm / large barrier (in this case 768px width) in order to get the expected rendering behavior.
I think a better approach to this problem is to not use routing. (Which is precisely what I did for your "Big view.")
As an example, here is a unified scope that utilized the bootstrap responsive utility and builds off of Jonathan's size detection. As the screen is resized, it should follow the expected behavior. No routing necessary.
http://embed.plnkr.co/b7sSyDjRLSRrJF29l01d/preview
You could use a function in the templateUrl section for routing in you app config and change the templateUrl based on current window size. I dare say you would have the same functionality in the controllers so changes to just the templateUrl should suffice.
NOTE: In my example below I have just placed the window size logic where needed, you would put this somewhere else in your app like a helper file or a service instead.
Example
http://plnkr.co/edit/udDlJT?p=preview
Im developing an app for Microsoft Surface and Im trying to make the most of the libraries that are out there, the functionality Im after if to be able to flick a UI element.
The ScatterView control makes this easy, but I would like to restrict the UI element to only be able to be flicked along a set path. This is where Im having trouble.
So my questions are:
1) Can you restrict a ScatterViewItem to only be flicked along a path?
2) If not, how would you implement a flick gesture to flick a UI element along a set path?
Thanks!
Mark
1) Not that I know of, and this probably isn't the best way to approach it.
2) Assuming you have the object you want flicked and the path at design-time, I've previously implemented dragging and flicking along a path by creating a timeline animation that represents the movement across the entire path. At runtime, I capture contacts on that object, feed them to a Affine2DManipulationProcessor, and seek the animation based on the manipulation events.
So in my case I was creating a drawer. When the user touched the drawer, I start the animation and pause it immediately. If the user drags it open, I seek the animation the appropriate amount forward based on how far the manipulation processor tells me they've moved.
To get the flick behavior, you just hand off the manipulation to the Affine2DInertiaProcessor and continue handling the delta events.
This all works surprisingly well.
I know Windows Forms quite good but I'm new to WPF.
I'd like to create application similar to RSS reader - in main window every note will be displayed in Post-it like frame and all notes should be chained and scrollable up and down. I also want to include kind of fisheye view - single note will be displayed full size in the centre of the screen and will shrink and rotate on the edge.
I know custom control, transformation and databinding concepts but I'm not sure how to handle displaying and scrolling notes in the main window. The questions are:
what is the suggested way to arrange, display and scroll ordered chain of notes?
should single note discover own position on the screen or it should be notified by it's container?
how in such solution provide feature which will open related notes as a "multiple popups" notes connected by a line with original one? (like traversing correlated results in Google Wonder Wheel, adobe flash there)
are there any standard solutions for displaying and manipulating (moving, attaching, collapsing) such popup-widgets?
If there are any similarities in your proposal to other GUI frameworks (Forms, Swing, SWT), comparison are welcome too.
Thanks in advance!
It seems to me you are describing a "carousel control" or "element flow" or "cover flow". I've put some links at this answer.