How do we access the examples now? The links are broken.

@pelikhan

The quality of the splines/lines when using the webgl rendering is very poor compared to the svg renderen.

WebGL:

SVG:

Seems anti-aliassing is missing. Using Edge on Windows.

Hello. Just found this library and is awesome. I'm using it in an angular project and I receive the following warnings:

Warning: D:\work\htdocs\hubtalk2-dashboard\node_modules\@msagl\core\dist\layout\layered\layerEdge.js depends on 'typescript-string-operations'. CommonJS or AMD dependencies can cause optimization bailouts.
Warning: D:\work\htdocs\hubtalk2-dashboard\node_modules\@msagl\core\dist\math\geometry\RTree\rectangleNode.js depends on 'stack-typescript'. CommonJS or AMD dependencies can cause optimization bailouts.
Warning: D:\work\htdocs\hubtalk2-dashboard\node_modules\@msagl\core\dist\structs\graph.js depends on 'queue-typescript'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

I know I can add exceptions for those libraries in angular.json, just wanted to notice this in case you want to move to other libraries that support es6 modules.

Provide option to generate SVG with mouse/keyboard interaction.

To be consistent with the other packages, msagl-js1 should be part of the @msagl org.

I want to use this library in my React.js app and would like to render my own React components as edges.
Even custom HTML or SVG could work.

Or If it's possible to praise the coordinates of edges, I can use that to draw the graph.

Is either of this possible?

I'm trying to use @msagl/core for layout, and then render the node graph myself, but the edges are always routed from the top left of the nodes. Is is possible to specify an offset or something for the start and end of the edges before layout is calculated?

Thanks a lot for any help.

I have a build problem, which I do not know how to solve:
Could you please help me
Thank you
Giatgen

PS C:\Temp\Autolayout\msagljs-main> npm run build

[email protected] build C:\Temp\Autolayout\msagljs-main
rm -f modules//.tsbuildinfo && rm -rf moduls/*/dist && lerna run build

'rm' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: rm -f modules/*/*.tsbuildinfo && rm -rf moduls/*/dist && lerna run build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

and with "npm run publish" I get this error:

lerna ERR! yarn run build stderr:
error Command failed with exit code 1.
lerna ERR! yarn run build exited 1 in 'msagl-js'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] publish: lerna run build && lerna publish
npm ERR! Exit status 1

The packages somehow defeat Webpack when trying to compile msagljs into a MDX component in Docusaurus.

This might be due to some deckgl dependency.

SSR: server side rendering

Good day

I was playing around with this lib and stuck with error that on this line

if (t.containsPoint(this.poly.end)) {

t is undefined It's because method private getSleeve(sourceTriangle: Tr) gets sourceTriangle === undefined. Looking in code I found that this method used only ones

    const sleeve: FrontEdge[] = this.getSleeve(this.findSourceTriangle(localCdt))
    if (sleeve == null) {

so result of this method could be null or undefined and I decided to add check for sourceTriangle like

  private getSleeve(sourceTriangle: Tr): FrontEdge[] {
    if (!sourceTriangle) return;

and error gone

Why this.findSourceTriangle(localCdt) returns undefined I don't know, but I can give you my graph in json and code how I use it.

Separate svg vs deckgl packages so that a svg user does not get all the deckgl dependencies.

I found node related events

certainly need to emit some mouse events here

If a user needs a border, it can be added through CSS outside the SVG.

The docs are quite sparse so not sure if this is bug or just something that is not finished yet or maybe I am doing something wrong with the configuration.

When using VerticalConstraintsForSugiyama the layout code calls getFeedbackSetExternal on the constraints object:

As that call just throws

Before node move ( splines ):

After a node move (straight lines) :

FYI

In the repo there are at least 4 files that cannot be created on windows (and ruin the git use of the repo as they can't be checked out or in) due to a : (Colon) in the filename. They seem to be checked in accidently.

Example is:
msagljs\website\static\img\undraw_start_building_re_xani.svg:Zone.Identifier

How can i set the color and other atributes of Nodes and Edges (I'm trying to use msagl directly from html/javascript) and is there a list of implemented attributes?

Not a bug/issue, but it might be useful info for others trying to get up & running with msagl.js usign VSCode on Windows. Maybe it's useful for an FAQ entry.

I found that with some modifications the main scripts and examples can be build on Windows using VSCode.

After installing Node.js on Windows you should be able to run the following commands to install the build tools globally:

npm install -g yarn
npm install -g lerna
npm install -g esbuild

In the various package.json files split the "build" command into a separate clean (the linux rm/rmdir command that won't work on Windows) and build command.

After this you can either run commands as 'npm run build' or (if present) use the VSCode npm command window. Note that some of the examples end up in the website folder instead of the examples folder.

PS 1) the clean commands use wildcards that are not compatible with Windows so one would need a batch file (and call in in the clean command) to clean the repo from previous output.

PS 2) if you want to disable minifiying the scripts (for debugging purposes), modify the 'esbuild.js' file and change all '.min.js' extensions in build scrips to just '.js'.

Is there a theming strategy for generated chats?

Could there be a builtin dark mode?