From 10ad9a332e6596bb8da465f4d5c453fe9059ec65 Mon Sep 17 00:00:00 2001 From: Sebastien Jourdain Date: Fri, 12 May 2023 14:38:13 -0600 Subject: [PATCH] docs(website): Add roadmap and v2-3 mention --- docs/content/docs/trame_v2-3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/docs/trame_v2-3.md b/docs/content/docs/trame_v2-3.md index d24a3f44..5c552bd7 100644 --- a/docs/content/docs/trame_v2-3.md +++ b/docs/content/docs/trame_v2-3.md @@ -4,7 +4,7 @@ Trame v3 is right around the corner. The main driver for the version 3 is to sup On top of making vue3 the new default, we want to shrink the default dependency list by only bundling by default the client and the server. And if the user needs vuetify and/or vtk they will need to list them as dependency of their project (trame-vtk, trame-vuetify). This will allow a leaner core package while still offering the same capabilities as before. -So far we don't have a release date, but while vuetify, vtk and more are already vue2 and 3 compatible. Not everything is available (router, plotly) or will be ported. So until we fill we have a great offering in vue3, we will hold off for the V3 release. +So far we don't have a release date, but while vuetify, vtk and more are already vue2 and 3 compatible. Not everything is available (router, plotly) or will be ported. So until we feel we have a great offering in vue3, we will hold off for the V3 release. ## New defaults @@ -17,4 +17,4 @@ server.client_type = "vue3" # instead of 'vue2' ## API change -Trame in itself won't have API change but it is possible that vue3 widget will have a different API than in V2. See vuetify2 vs vuetify3. But ideally the rest will remain the same. +Trame in itself won't have API change but it is possible that vue3 widget will have a different API like you can see between vuetify2 and vuetify3, but in general we'll try to maintain full API compatibility. \ No newline at end of file