diff --git a/biz/src/main/resources/style/default-free-node-style-template.json b/biz/src/main/resources/style/default-free-node-style-template.json index d20a18c47445db1f2b17d0c8eb8ca25e20c9be53..eaa1b408cf6298506e95f16ee50b932f0b0a2827 100644 --- a/biz/src/main/resources/style/default-free-node-style-template.json +++ b/biz/src/main/resources/style/default-free-node-style-template.json @@ -2,7 +2,7 @@ "id": "${nodeId}", "shape": "ellipse", "width": 100, - "height": 40, + "height": 50, "attrs": { "body": { "fill": "#ffffff", diff --git a/graph/src/main/java/cn/icanci/loopstack/bic/graph/node/NodeAttrsBody.java b/graph/src/main/java/cn/icanci/loopstack/bic/graph/node/NodeAttrsBody.java index 5b182831a18ca53fc19df42841774447c40ff56b..d475d8480ddda1e29ae0c42245f0cc33c2bed767 100644 --- a/graph/src/main/java/cn/icanci/loopstack/bic/graph/node/NodeAttrsBody.java +++ b/graph/src/main/java/cn/icanci/loopstack/bic/graph/node/NodeAttrsBody.java @@ -12,4 +12,5 @@ public class NodeAttrsBody { private String stroke; private int rx; private int ry; + private String strokeDasharray; } diff --git a/views/src/main/resources/static/index.html b/views/src/main/resources/static/index.html index d8c8250f7540e75313bc3ba4780e91b8fae3bb2a..7a866572824e020682de1f640bf22c0b5877c75b 100644 --- a/views/src/main/resources/static/index.html +++ b/views/src/main/resources/static/index.html @@ -1 +1 @@ -

Last week atVue.js LondonI gave a brief sneak peek of what’s coming in the next major version of Vue. This post provides an in-depth overview of the plan.
\n
Vue 2.0 was releasedexactly two years ago(how time flies!). During this period, the core has remained backwards compatible with five minor releases. We’ve accumulated a number of ideas that would bring improvements, but they were held off because they would result in breaking changes. At the same time, the JavaScript ecosystem and the language itself has been evolving rapidly. There are greatly improved tools that could enhance our workflow, and many new language features that could unlock simpler, more complete, and more efficient solutions to the problems Vue is trying to solve. What’s more exciting is that we are seeing ES2015 support becoming a baseline for all major evergreen browsers. Vue 3.0 aims to leverage these new language features to make Vue core smaller, faster, and more powerful.
\nVue 3.0 is currently in prototyping phase, and we have already implemented a runtime close to feature-parity with 2.x.Many of the items listed below are either already implemented, or confirmed to be feasible. Ones that are not yet implemented or still in exploration phase are marked with a *.
\nTL;DR: Everything except render function API and scoped-slots syntax will either remain the same or can be made 2.x compatible via a compatibility build.\n
Since it’s a new major, there is going to be some breaking changes. However, we take backwards compatibility seriously, so we want to start communicating these changes as soon as possible. Here’s the currently planned public API changes:
\nTL;DR: better decoupled internal modules, TypeScript, and a codebase that is easier to contribute to.\n
We are re-writing 3.0 from the ground up for a cleaner and more maintainable architecture, in particular trying to make it easier to contribute to. We are breaking some internal functionalities into individual packages in order to isolate the scope of complexity. For example, the observer module will become its own package, with its own public API and tests. Note this does not affect framework-level API— you will not have to manually import individual bits from multiple packages in order to use Vue. Instead, the final Vue package is assembled using these internal packages.
\nThe codebase is also now written in TypeScript. Although this will make proficiency in TypeScript a pre-requisite for contributing to the new codebase, we believe the type information and IDE support will actually make it easier for a new contributor to make meaningful contributions.
\nDecoupling the observer and scheduler into separate packages also allows us to easily experiment with alternative implementations of these parts. For example, we can implement an IE11 compatible observer implementation with the same API, or an alternative scheduler that leveragesrequestIdleCallbackto yield to the browser during long updates.*

TL;DR: more complete, precise, efficient and debuggable reactivity tracking & API for creating observables.\n
3.0 will ship with a Proxy-based observer implementation that provides reactivity tracking with full language coverage. This eliminates a number of limitations of Vue 2’s current implementation based onObject.defineProperty:
The new observer also features the following:
\nEasily understand why a component is re-rendering
\n
TL;DR: smaller, faster, tree-shakable features, fragments & portals, custom renderer API.\n
TL;DR: tree-shaking friendly output, more AOT optimizations, parser with better error info and source map support.\n
TL;DR: it will be supported, but in a separate build with the same reactivity limitations of Vue 2.x.\n
The new codebase currently targets evergreen browsers only and assumes baseline native ES2015 support. But alas, we know a lot of our users still need to support IE11 for the foreseeable future. Most of the ES2015 features used can be transpiled / polyfilled for IE11, with the exception for Proxies. Our plan is to implement an alternative observer with the same API, but using the good old ES5Object.definePropertyAPI. A separate build of Vue 3.x will be distributed using this observer implementation. However, this build will be subject to the same change detection caveats of Vue 2.x and thus not fully compatible with the “modern” build of 3.x. We are aware that this imposes some inconvenience for library authors as they will need to be aware of compatibility for two different builds, but we will make sure to provide clear guidelines on this when we reach that stage.
First of all, although we are announcing it today, we do not have a definitive timeline yet. What we do know at the moment is the steps we will be taking to get there:
\nThis is the phase we are in right now. Currently, we already have a working runtime prototype that includes the new observer, Virtual DOM and component implementation. We have invited a group of authors of influential community projects to provide feedback for the internal changes, and would like to make sure they are comfortable with the changes before moving forward. We want to ensure that important libraries in the ecosystem will be ready at the same time when we release 3.0, so that users relying on those projects can upgrade easily.
\nOnce we gain a certain level of confidence in the new design, for each breaking change we will be opening a dedicated RFC issue which includes:
\nWe will anticipate public feedback from the wider community to help us consolidate these ideas.
\nWe are not forgetting about 2.x! In fact, we plan to use 2.x to progressively accustom users to the new changes. We will be gradually introducing confirmed API changes into 2.x via opt-in adaptors, and 2.x-next will allow users to try out the new Proxy-based observer.
\nThe last minor release in 2.x will become LTS and continue to receive bug and security fixes for 18 months when 3.0 is released.
\nNext, we will finish up the compiler and server-side rendering parts of 3.0 and start making alpha releases. These will mostly be for stability testing purposes in small greenfield apps.
\nDuring beta phase, our main goal is updating support libraries and tools like Vue Router, Vuex, Vue CLI, Vue DevTools and make sure they work smoothly with the new core. We will also be working with major library authors from the community to help them get ready for 3.0.
\nOnce we consider the API and codebase stable, we will enter RC phase with API freeze. During this phase we will also work on a “compat build”: a build of 3.0 that includes compatibility layers for 2.x API. This build will also ship with a flag you can turn on to emit deprecation warnings for 2.x API usage in your app. The compat build can be used as a guide to upgrade your app to 3.0.
\nThe last task before the final release will be the IE11 compatibility build as mentioned above.
\nIn all honesty, we don’t know when this will happen yet, but likely in 2019. Again, we care more about shipping something that is solid and stable rather than hitting specific dates. There is a lot of work to be done, but we are excited for what’s coming next!
',o={title:n,content:i};t["default"]=o},"99ea":function(e,t,a){},"9b8b":function(e,t,a){},"9bbf":function(e,t,a){"use strict";a.r(t);var n=a("e017"),i=a.n(n),o=a("21a1"),s=a.n(o),r=new i.a({id:"icon-drag",use:"icon-drag-usage",viewBox:"0 0 128 128",content:'I am testing data, I am testing data.