-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
🚀 Roadmap 🚀 #8316
Comments
List of TASKs that are more important than others for a beta release:
(those are items that came out from discussion during PRs and need to be properly captured in items) |
@asturur great work! do you and @ShaMan123 have some regular meetings to discuss the fabricjs product vision and roadmap, if yes, i would like to join the discussion if possible. |
Me too |
Regarding meetings: |
Am it for it too, Maybe a Discord, Slack whatever the approach |
@asturur I want to add refactoring ObjectGeometry, making sense out of coords, deciding in which plane they exist and make it accessible. I still can't understand what is going on there. And I am sure there are bugs with group that aren't known since they remain untested. |
I will add that we can use planeChange to redo most of geometry with ease I believe |
@ShaMan123 making oCoords/aCoords simpler has been a long standing issue, but i m afraid we can't do it now. |
I am shocked a year is about to pass |
when do you expect to release alpha v6? |
it is already in 6.0.0-beta19 and it is released, I have been using beta for a while now |
Yes, I'm aware of that. Currently, I'm using version 5.3.0 (RTL). However, I'm looking for stable release. |
I m doing an effort to create a project template that works as roadmap container. |
I would also like to use this pinned issue to announce and link new discussions and progress, so people have ONE issue to monitor, so let's avoid spam if possible or questions |
We want to use fabricjs to develop in new projects. Is V6 ready to release the stable release.? If we use the beta version now, will it have any impact on the future? |
Currently there is one large bug in v6 we want to fix and then should be released. All the rest will be bugfixes with no breaking changes. Other major versions could follow, maybe quickly maybe not, but we will try to have a single breaking change ( or feature) per major version, no large reworks like this |
Another small proposal #9737 |
From what I've been able to find out, there were once plans to add support for layers. The mechanism we know from Konva.js. Here one of the references on the subject #7692 Did this feature land in version 6? |
No. |
Roadmap 🚀
This Pinned list will contain an updated list of things that we want or we are working on.
Completed items will move in issue comments below. There isn't an ETA for any feature, and 1 or more developer may be working on them.
Those two feature are currently worked on and have priority above anything else:
The following list of feature are long standing items ( 2+ years each ) and in a perfect world we want to complete them before any other large refactor that could make them harder, or since introucing them later could make a refactor less effective.
Those listed feature are complex ( apart the filter one, that is easy) and touch many part of fabric codebase.
Improve/solve Sharpness of clipPaths WIP fix(fabric.Object): render clipPaths sharper #7186Done finallyIf you are a contributor and want to propose a new feature, do it, there is always space for:
The only issue is that if a new proposed feature could clash with something that is in the roadmap it needs to be discussed deeply or cut/changed, unless is a better indea than the roadmap and so it will take its place
The text was updated successfully, but these errors were encountered: