My name is Nir and I have recently joined Editor X as Head of Product. I’m very excited to work with this amazing team to help build Editor X. Most of all, I am looking forward to connecting with this talented community of creators and designers, and listening to your feedback and inputs.
As you know, we are constantly working and releasing new features and capabilities for Editor X, but as
importantly, we are also hard at work to improve the product’s performance.
I am excited to share that today we are starting to rollout a new rendering technology which is expected to speed up the performance of the editor.
As always, our team is working hard to make sure this rollout goes as smooth as possible, but since this is a fundamental change to how we render the editor, we’d love to hear about your experience or if you encounter any issues.
On a personal note, please feel free to message me directly (@nirsadeh) for any topic related to Editor X, and even if you just want to get to know. I believe this community is an instrumental part of making this product great and I am excited by the opportunity to connect with you all.
Hi Nir, glad to hear you joined the team! I assume you’re going through the many posts of requests currently in this forum, so I won’t turn this into a request thread. Look forward to your leadership as Editor X becomes even more attractive and competitive. Cheers!
About performance Editor X is 10x better than classic Editor so far for me but I haven’t worked similar sites on Editor X (with tons of codes and pages) so I can’t say it’s fast but it’s enough fast for me.
I don’t know if it’s possible but why you don’t convert these editors (both classic and Editor X) to a software so maybe it can use more hardware power to render something. When we use the Editor inside browser I don’t think it’s using the ‘real’ power of CPU or GPU.
I have 16 core CPU and it’s overclocked with watercooler but there is no difference between old performance and new performance of editors (again both editor)
Beyond of performance I want to talk about features of Editor X.
It’s missing some key elements for users switching from classic editor to Editor X we can handle every single thing with custom elements using JS HTML CSS and Velo but this is not a reason and can’t be a reason to not release these small features.
What I meant by small but important features for users switching from classic to editor x:
Rich Content Element
Rating Inputs and Displays (must have for an ecommerce website and not exist on editor x right now)
Other Input Elements exist on classic but not on Editor X
Widgets of Wix Apps
these things are important for users who switch from classic editor to Editor X I want to switch but I can’t because of these missing features.
And again all of these features can be fixed by using third party apps or with JS and Velo but as I know this ad is created by Wix and published on official YT channel.
So plugins or code isn’t solution for everyone and it’s not the best solution every time.
The EditorX teams are working hard to make all of the features of the classic editor possible on EditorX.
Also, the post mentions that the new performance is in rollout, so you may not have it yet, hence the reason you may not be seeing any difference in performance.
@noahlovell I meant there was no difference between overclocked CPU and not overclocked CPU and I said if editor can use the power of CPU maybe it would be better to use the power of CPU maybe they need to create a downloadable software. IDK
I wonder if you might be able to update the post once the rollout has completed so we can keep up to date with where things are at. (It would give us confirmation to be able to compare if our editors feel better). Just a thought
I’m Kentin, Velo developer. I’m getting used to editorX and I’ve been doing some medium-size projects on it.
One feature request: better integration for the dev mode . Now that the editor is more stable, I would love to see a minor improvement: better integration on the code panel and vertical responsiveness. The code panel overlaps the edit panel and there is no scrolling available when the 2 overlap.
fixing a small UI glitch (see image) with the layers panel displaying elements’ id
last but not least I would love a true dark them for the editor
Hey Nir, I’m glad there’s a focus on improving the editor alongside all else going on.
My post here:
…highlights one of the major shortcomings and biggest frustrations for me, particularly when working with larger projects, pages management. If you’d like to take a closer look at my comments there.
