-
Notifications
You must be signed in to change notification settings - Fork 1.5k
⚠️ Vis.js - End of Live #4259
Comments
hi @mojoaxel |
The timeline has been separated to my fork here: It is maintained actively every week. |
It would be cool to be able to leave this last version as operational as possible as @mojoaxel suggested on #4197 In fact and to take an example, if someone can make graph2d work properly from the latest version or even on the branch develop, good deal... Otherwise and in general if we can't fix this type of bugs, wouldn't it be better down to an earlier version when the currently broken functionality was still working properly... until 4.20.1 for example? I'm just wondering... and what do you think about that ? |
The network module lives on in our community fork here: It is actively maintained, with multiple contributors from the visjs community ☺ We also publish regularly to npm https://www.npmjs.com/package/visjs-network you can start using the latest visjs-network features & bug fixes today with the command:
or
|
like @yotamberk says, I do think it would be nice to have https://github.com/yotamberk/timeline-plus and https://github.com/visjs-community/visjs-network under a common github org, to make it easier visjs users to discover the projects and collaborate. |
@yotamberk @micahstubbs Feel free to move your projects to the visjs community account whenever you want! |
@mojoaxel I think that could make sense once vis itself migrates to https://github.com/visjs github org. Do you know if there are plans to do that? |
The plan is not to migrate the whole project. Instead I'm planning of splitting it up into its modules (network, timeline..) and find a team of maintainers for each modules. (Looks good already!) I'm planning to do this Mar/Apr 2019 as soon as I find the time. To anybody who wants to support/speed-up the migration: please consider funding the development using our opencollective: https://opencollective.com/vis |
https://github.com/almende/vis This fragmentation is tough to sort through. |
Yes, it is! 😞 |
Time to merge/move guys! How can i help? |
You have to archive the project as soon as possible. Hope is not a solution. |
Finding time is not easy but I have scheduled the transfomation fom the |
Well i'm sad this awesome plugin is going to end...i have been using mainly because of timeline. Btw i made a 5 dolar contribution https://opencollective.com/vis#budget |
The previous location wasn't available anymore so it had to be updated. More details about it here: almende/vis#4259
I'm starting the process of moving alemde/vis to the visjs community NOW. |
Here i'm going to track the progress of the transformation and document what I did (for future maintainers maybe!?)
|
Any news on the merge? ;) |
I'm happy to say that I managed to leap a giant step forward yesterday: I removed gulp/webpack in favor of rollup and can now start to split the vis-charts library in separated projects - saving the git commit history :-) If everything works out like I planned it I can release the new libraries this weekend or next week. After that this repository finally gets archived and the new libraries can be used... After I delivered what I promised I hope that @yotamberk and the others will (again) join the visjs community 🙏 |
Help? I just discovered vis.js and graph3d over the weekend (after googling "javascript 3d data point visualization") and was quickly able to do almost what I needed -- to make a 3d scatter plot -- but still need to (learn how to) make a few changes.. I've read the How to help post, but then when I go over to visjs community I don't see graph3d on the list, and when I go inside vis_original there's some graph3d stuff but there's no Issues or Pull Requests tabs. For now I've started my own fork but...not sure how/where to ask questions when I get stuck. Can someone advise, re. which account or repository I should be looking at? Literally, all I want to do is plot a bunch of points in 3D, except make some the markers different shapes (e.g. make some of them squares or crosses ), or perhaps still all circles, but allow them to be both different colors and different sizes, not just color or size.). Thanks! |
@drscotthawley You have every reason to be confused! There is a very good chance that a
This is probably not the best thing to do...already so much confusion. |
Hey guys. |
I see a big conflict rise here! vis.js is a very big project with a long history. Starting with professional almende contributions and later maintained my me, yotamberg and may others. Later we had no more time to maintain the whole library, answer the countless beginner questions or feature-requests. It leaves behind the whole community and more important the whole project history. While this approach is fully legal due to the open licenses, I still think it is not how we should act as a open-source community! Forking Yes! Copying code without attribution: No! This is why I took the (already existing) visjs community account from AlexDM0 and created a new home for vis.js to flourish as a whole. Than I invidet everybody to joun the new community. The idea of this community is to provide each library (timeline, network ...) as its own module with its own maintainer team, while saving the projects history, website and community spirit. With the help of @Thomaash I already separated the module vis-util (common helpers) and vis-data (DataSet, DataView, Queue) during the last days. I honestly hope is that after doing the split each project can find a team of maintainers. Ideally the pull-requests from timeline-plus and other private implementations can be transferred also to the newly created libraries! The visjs community will also continue to support the opencollective "vis" and the homepage "visjs.org". "You got to be free |
@drscotthawley I just publishes vis-graph3d. Feel free to use try it. |
I understand what you're saying. To be fair, there were many legitimate reasons why I copied the project and not forked it in the first place, mainly due to having a real hard time trying to advance timeline without a lot of noise and restrictions of the project, whilst disagreement of the owners to separate the modules in the first place. I did said I will be willing to work on re-merging the work done in my copy starting on Saturday. I'm also willing to continue as the main maintainer of this module as long as I have full access and ownership on it. |
I'm really happy that you understand. Also I'm sorry that this took me so long! I'm looking forward working with you again!
👍 Great! I'll help if I can.
This sounds reasonable! I also hope to get some of the funds for doing the separation into modules. I'm sure we will figure this out!! I really hope that some people here read what we are saying and consider becoming a sponsor to support further development! We think we have proven that we are willing to keep this project going, but we need funds to finance all this work. 🙏
I just released the new vis-network module. The timeline is the only one still missing. I'll finish the separation this week and and than we can try to update it together. As soon as the repository exists I'll give you full access (of course!) |
Glad to see that the new https://github.com/visjs/vis-network has been released. Works great as a replacement for almende vis. Are there any plans to merge the pull requests left behind on almende vis into the new community vis? |
hi @richardeaxon, we've already done this 😄 We have merged all of the active, working network-related PRs from almende/vis - you can see the list here https://github.com/visjs-community/visjs-network/pulls?q=is%3Apr+is%3Aclosed Install via yarn:
Install via npm:
|
I'm not sure what the status of @mojoaxel's fork is with regard to to including open PRs from almende/vis. He probably knows more about that. |
Thanks! It was a peace of work! But I'm olso happy that we are finally getting somewhere..
I'll contact the original contributors and ask them if are willing to reopen theirs pull request at the new repository. If they don't we will properly move them one by one. But to be honest I would prefer the original contributors to provide their code. This way they get attribution an maybe feel more responsible to fix bugs in "their" code and maybe even get more involved. |
one question: What do you think about merging my angular-integration to vis org? I would still maintain it there. |
ngx-vis Looks very promising! I think the best way would be to open an issue at vis-network and discuss the best way to approach this over there. |
I'm happy to announce that vis.js is now fully managed by the community:
Please feel free to contribute to the new repositories and/or sponsor further development. |
I'm thinking about opening this issues for many month now. Today the time has come:
This is the beginning of the end of vis as we know it - and hopefully a new beginning.
Current status
This project can not go on like this!
Future steps
This is propably going to happen in March 2019.
vis.js is dead, long like visjs!
The text was updated successfully, but these errors were encountered: