ipyvuetify
ipyvuetify copied to clipboard
is there plan to make ipyvuetify's interface the same as ipywidgets?
Hi,
For example, in the slider3 in notebook example, v_model is used to link two widgets.
This is quite new to me since I am not familiar with vuetify itself. Any plan to make ipyvuetify's interface the same as ipywidgets's one?
cheers
The linking of two widgets is functionality of ipywidgets. The only difference is that v_model is used for the slider value instead of value in ipywidgets.
There are no concrete plans to supply an ipywidgets compatible API layer. This will be a very nice feature to ease adoption of ipyvuetify though, but we will probably not have time to implement this any time soon.
We are thinking of removing v_model which in many cases would be replaced by value right?
(from mobile phone)
On Wed, 14 Aug 2019, 20:08 Mario Buikhuizen, [email protected] wrote:
The linking of two widgets is functionality of ipywidgets. The only difference is that v_model is used for the slider value instead of value in ipywidgets.
There are no concrete plans to supply an ipywidgets compatible API layer. This will be a very nice feature to ease adoption of ipyvuetify though, but we will probably not have time to implement this any time soon.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mariobuikhuizen/ipyvuetify/issues/31?email_source=notifications&email_token=AANPEPNG4FUYDBW4KCP7CNLQERC3TA5CNFSM4ILXA3QKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4JUHOY#issuecomment-521356219, or mute the thread https://github.com/notifications/unsubscribe-auth/AANPEPKRVCXJFTDF7KUXPATQERC3TANCNFSM4ILXA3QA .
uhm, I think this issue is related to #10. It seems like using v_model is confusing for ipywidgets' ecosystem :D.
Sure, but we wrap an existing library, we're not aming for compatibility. however, if we make a small change it will feel more compatible.
(from mobile phone)
On Wed, 14 Aug 2019, 21:21 Hai Nguyen, [email protected] wrote:
uhm, I think this issue is related to #10 https://github.com/mariobuikhuizen/ipyvuetify/issues/10. It seems like using v_model is confusing for ipywidgets' ecosystem :D.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mariobuikhuizen/ipyvuetify/issues/31?email_source=notifications&email_token=AANPEPO5Z2OBBCQQ3OMMFK3QERLNHA5CNFSM4ILXA3QKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4J2XEQ#issuecomment-521382802, or mute the thread https://github.com/notifications/unsubscribe-auth/AANPEPLMBD7SJQWKLNZZIV3QERLNHANCNFSM4ILXA3QA .
Sure, but we wrap an existing library, we're not aming for compatibility.
yeah, I agree.
however, if we make a small change it will feel more compatible.
and agree too.