-
Notifications
You must be signed in to change notification settings - Fork 871
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
Upgrading yarn editor to the newest version #6460
Comments
Might give this one higher priority than upgrading bondagejs, seeing as to how its getting more hearts. I did some work on yarn editor to trim down its bundle size while keeping as many of the new features as possible over the weekend. There was some badly optimised stuff. Like typing to search for a node was very slow, panning was slow, loading the file was slow. There is always room to improve it still. It should be able to scale to bigger documents I still want to try tackling this one first |
I think the implementation of the new yarn editor + being able to handle tons of nodes will be incredibly useful for my upcoming via move, would contribute if i really understood js, ts & such much more but sadly can't, still tho keep up the great work 🗣️📢🔥 |
yup I understand the demand. The good news is that I managed to trim down the newest version of yarn to almost the same size as it is now in gdevelop's old version, while retaining all the new the features. I remember when I initially did the bundle pr - the deploy size being small was a very important point. I want to sort out my vn actor pr before doing the yarn editor upgrade though so in the mean time I am just working on yarn itself. |
Description
I am wondering if its worth making a pr to upgrade yarn editor to a newer version.
There are some missing bits and fixed bugs/ improvement of life features in the newest version. Is this something that would be welcome as a Pr?
Improvements over the old one:
Solution suggested
Before doing a PR I think I will do some work on yarn editor to trim it down - to reduce its size. It has grown in size due to bundling of an inkjs compiler and some word library files - to enable previewing ink stories directly inside yarn + suggestion of related words to selected word.
I am planning to trim it down and speed up its start time, so the ink playtesting feature might be reworked or removed, but the optional ink import/export/syntax support will stay
Alternatives considered
I really want gdevelop's web version to be able to open yarn editor the way it can now do piskel. Can anyone point me to any tips as to what needs doing to enable this for yarn editor?
The text was updated successfully, but these errors were encountered: