Group Details Private

guest-publishers

Guest publishers are allowed to write in the articles category and link to their blogs.

  • RE: Please is angular 4 perfectly compartible with Onsen UI?

    @mykoman ngx-onsenui is compatible with Angular v4 at least. Not sure about v5.

    posted in Onsen UI
  • RE: How to change tabbar in page components ?

    @丶JavaScript said:

    <component :is=“page” :set-page="() => showPage(…)"></component>

    <component :is=“page” @page=“showPage(…)”></component>

    You pass props or event handler to the page components so you can communicate with them.

    posted in Onsen UI
  • RE: Scroll to element / to top with animation

    @Aden23q The scrollable element is not the list, but the page’s content (.page__content). You can learn about that wrapper here.

    posted in Onsen UI
  • RE: How to change tabbar in page components ?

    @丶JavaScript Do you mean changing the current page from a button inside pages? You’ll need to pass a prop function to modify your page variable or emit an event to do it.

    posted in Onsen UI
  • RE: Splitter and navigator

    @Michael-Redwine You can see all the “navigation” components (ons-navigator, ons-splitter, ons-tabbar) as some kind of frames that can change their content. As a content wrapper, they offer certain unique features: ons-navigator provides page stack and animations; ons-splitter provides a responsive side menu; etc. But they are just that, frames. If your frame A is the parent of frame B (i.e. frame B is part of the content of frame A), whenever you change frame A’s content you’ll be removing frame B and all its features.

    Therefore, if you have a splitter inside the first page of a navigator and you push a new page to the stack… the new page will be on top of the splitter and you won’t be able to see it. This means you only get a side menu for specific pages (the first one in this case). Otherwise, if you put the splitter as the parent of the navigator and push pages to the navigator’s stack, the splitter still remains in the same position and will be visible in every page of the stack. Components are not magically global, they only affect specific portions of the screen and as such you need to think about their order, position, etc.

    Hope this clarifies it a bit!

    posted in Onsen UI
  • RE: ons-tabbar lift animation

    @CsLaci Perhaps you can use a <ons-modal animation="lift"> for your use case.

    posted in Onsen UI
  • RE: Browser and Android back button

    @Michael-Redwine The Android back button in Cordova apps should work well. For browsers back button, we are not modifying the history stack since this framework was originally meant for Cordova apps. Perhaps we should add it for PWAs. In any case, I think you can use navigator’s postpush event to run history.pushState and then use window.onpopstate to call myNavigator.popPage. I think that should work :+1:

    posted in Onsen UI
  • RE: ons-tabbar lift animation

    @CsLaci Hi! I think ‘lift’ animation in tabbar is quite uncommon :confused:
    Ours is a swiping tabbar so it doesn’t support other animations. However, if you really want it, you can remove swipeable attribute, place a ons-navigator inside a tabbar page and then overwrite the click behavior of the tabs to load pages in the navigator. Something like this. This is not “official” behavior but it should work fairly well.

    posted in Onsen UI
  • RE: Using $ons.GestureDetector in Vue

    @JiProchazka Hi! $ons.GestureDetector for Vue is the same than for any other bindings or the core itself. It is just the internal Hammer.js (1.x) that Onsen UI uses and we expose, so you can check Hammer.js docs.

    posted in Onsen UI
  • RE: How to navigate within pages

    @amco So can’t you do something like this?

    function buttonClick() {
      document.querySelector('ons-navigator')
        .pushPage('nextPage', {
          data: {
            value: document.querySelector('ons-select').value
          }
        });
    }
    

    Actually, the page with the ons-select remains in the DOM so you can even access it with document.querySelector when you are in the next page already…

    posted in Onsen UI