@munsterlander The other day I started the docs for Onsen UI on SOF. Looks like it already got enough commiters. We’d like to have information there but it is meant to be community driven, so I’m not sure if we will put much effort on it other than reviewing
Thanks for the first contribution, by the way
@munsterlander That was the way to extend animatinos in v1, but unfortunately it won’t work for v2.
@davidfherrerar For Onsen UI 2 right now extending and modifying animators is not an easy task. We still need to make this easier. I’ve made an example with the simple slide animation here.
Basically I made a new animator using simple slide’s pop method in the new push method and changing some minor stuff.
The problem is that the core animators are written in ES6, but here you would need to write ES5 for the browser, and also right now we can only extend the very basic animator, not an already implemented one.
If you really want a pop animation I think right now it would be easier to just delete the pages you don’t need from myNavigator.children HTMLCollection and perform a normal myNavigator.popPage() afterwards.
Anyway, just for the record, this is the code for the custom animator:
@yuyaogawa If the splitter is going to be common to multiple pages I guess you can use it as the parent/root component. Then maybe you can add a navigator in the content. Check this tut if you think this could help you.
If an element has position: fixed and it’s parent is scrolled with a momentum scroll (a single swipe up/down instead of a drag) - then instead of retaining its position on the screen it would scroll together with the other content and then returns to its proper position only after the scroll finishes.
In the suggested case the element which is scrolled is .page__content which is a sibling of ons-toolbar instead of a parent so the problem should not occur.
Hi. Well you could always make a splashscreen and hide it when everything is loaded. I suspect the splashscreen which you see the first time might be something more OS/App related - you can make a second one (you can prob make it look the same as the first one), however this one will be from the app code itself.
In FB App you have to assign an IP Site/ App Domain.
Facebook matches this url with the url of the request where it came from.
You can not assign localhost or 127.0.0.1
You have to enter the IP address your server. Also if it is rails then call the site with your-ip:3000 instead of localhost:3000; I use 192.168.1.154:3000
Enter the same IP address in IP of the site and APP Domain in your FB APP Settings.
Thank you very much for your quick response.
I fully understand your business priorities, and this is normal.
The big problem is that right now everything is in beta!
Regarding your TS templates for VS, for example: Onsen UI Splitter.
I’m not saying it does not work but:
Index.ts is generated for a standard Cordova project.
I would have preferred a TS page with the use of onsenui.d.ts.
But do not worry everything about typescript is like that
Thanks for the answer. No the carousel and the image also i do not want to cover the whole of screen but cover the screen that is the height of the image. For example if the image height is 200px i want the carousel cover only 200px of the screen and the image show 100% of the size in all different size of device screen.