can I use Vuetify in nativescript-vue? - nativescript

Vuetify seems to be an useful Framework. I was wondering if it's possible to use it inside our NativeScript apps with VUE.js
I have tried :
yarn add vuetify
<v-btn :href="source"
icon
large
target="_blank"
v-on="on"
>
<v-icon large>mdi-code-tags</v-icon>
</v-btn>
But Error says:
No known component for element v-btn.

NativeScript !== Cordova, so you can't. Vuetify is purely browser dependent / HTML DOM based components.

Though Manoj is right to point out that you can't use it like you intendet to do but you still can use a WebView in NativeScript to display your web application. Some apps in the appstores do just that - they use Nativescript for the Main-UI with device features and the webview to show the web application.

Related

Where to find Vuetify material icon list

Vuetify official doc says you can use the google material icon but some of them not working in is there is any reference online?
<v-icon >
mdi-layers
</v-icon>
the above works but the below one does't
From google material icon
<v-icon>
mdi-expand_more
</v-icon>
Here are the resources I personally use to get mdi icon names:
https://pictogrammers.github.io/#mdi/font/5.4.55/
https://material.io/resources/icons/?style=baseline
https://iconify.design/icon-sets/mdi/

MacOS HelpViewer navigation buttons don't work for web SPA content

Recently we had to migrate embedded help for Mac product to web and have referenced it from Mac HelpViewer.
As far as I know MacOs HelpViewer is a custom made webkit based applilcation that is used to display product help, which has to be presented in a specifis folder structure.
HelpViewer's nav and menu buttons aren't similiar to any browsers buttons, and for the rest browsers our web help works perfectly fine in SPA mode with
window.history.pushState
But once this SPA behaviour is applied to HelpViewer navigations buttons don't react (they are disabled) to changing url or adding state to window.history collection.
MacOS nativa applications also have web based help, e.g: calendar app. This help is based on Ember.js and has some SPA behaviour also, but this one trigger HelpViewer's buttons to react (they become enabled) and work once clicked.
The problem I try to solve is how to trigger HelpViewer to react on changing url or window.history. Maybe ember.js does some extra stuff except for adding state into window.history?

Nativescript and Angular 2 navigation transition

Could somebody tell me please how to use navigation transitions with nativescript and angular 2 application?
Currently, navigation transitions are not yet implemented for NativeScript + Angular-2.
This feature is considered among with options like clearHistory and backStackVisible. You can track its development from the nativescript/angular repo or directly here

Difficulty while writing custom renderer for navigation drawer(MasterDetailPage) xamarin.forms

I am using xamarin.forms mvvm light architecture and targeting Android & iOS.
I am currently writing custom renderer for navigation drawer(MasterDetailPage).
I am currently writing custom renderer for Android and i have tried many things.
Currently my MasterDetail Page renders according to OS's default behaviour i.e. in Android master page starts below the app bar but i wanted my master page to popover app bar or start above the app bar like gmail,stack exchange android app etc
use this theme Theme.AppCompat.Light.NoActionBar for the expected behaviour
There exists one already, as of this writing it is out of date though (not targeting Xamarin Forms 2): https://github.com/nativecode-dev/oss-xamarin. Perhaps you can use that?

React.js vs Auto-Layout

We are thinking about moving from Auto-Layout to React.js.
How does React.js build for multiple screen sizes: 3.5", 4.7", 5.5", iPad Mini, iPad Air ? and why is it easier in React.js ?
Has anyone made the transition? Please share your experience?
The purpose of the React.js framework is to help you create reusable components for your application. It doesn't enforce any structure of the html content, and it doesn't natively have support for things like auto-layout, since that's the role of CSS.
There is no direct auto-layout support in react, and there's no UI editor like interface builder where you can set the constraints for a particular html element. You can achieve similar results, but you'll need to write CSS rules for that.

Resources