-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FCOSE demo & misc. docs fixes for 3.31.0 #3303
Conversation
- While Cola is a good layout, FCOSE is faster and provides better compound support. It's our default recommendation in the blog (https://blog.js.cytoscape.org/2020/05/11/layouts/). - The Cola demo used to be the first one at the top of the demos. It gives the impression that it's our top/default pick. - People end up complaining, "Why can't I do X with Cola?" If they were to use FCOSE first, they'd get a better result most of the time.
@ugurdogrusoz: Here's a video of the FCOSE demo that replaces the Cola demo (https://js.cytoscape.org/demos/colajs-graph/). Let us know if you notice anything that should be improved in the new FCOSE demo. Thanks fcose.mp4 |
Demo looks really good. One question: what does the play button do? Every time I click it the nodes just shift slightly. |
It just iterates the layout a bit, the iterative mode. If you drag a node out of place it would be more noticeable. We could remove that button. I added it because it looked a bit off to only have one. |
Its fine. Maybe just add tooltips to the buttons? |
The demo looks good but of course, it doesn't illustrate the compound support... |
Great thanks @maxkfranz |
Cross-references to related issues. If there is no existing issue that describes your bug or feature request, then create an issue before making your pull request.
Associated issues:
N/A
Notes re. the content of the pull request. Give context to reviewers or serve as a general record of the changes made. Add a screenshot or video to demonstrate your new feature, if possible.
Checklist
Author:
unstable
. Bug-fix patches can go on eitherunstable
ormaster
.Reviewers:
master
branch and theunstable
branch. Normally, this just requires cherry-picking the corresponding merge commit frommaster
tounstable
-- or vice versa.