menu
announcement

Spectrum is now read-only. Learn more about the decision in our official announcement.

Grapedrop

Grapedrop is an easy to use builder for designing your website projects and publish them instantly online

Channels
Team

Why is open source version functioning correctly, while paid version is not?

February 18, 2021 at 4:21am

Why is open source version functioning correctly, while paid version is not?

February 18, 2021 at 4:21am (Edited 8 months ago)
No flex assigned when adding from these built-in blocks?

In grapedrop, layouts are not correctly set for any blocks...

  • app intro
  • all blocks in features
  • pricing
  • all blocks in teams
  • all blocks in testimonials
  • all blocks in footers
  • all blocks in forms
No blocks have set flex like in the previews, or open source editor. In fact, none of the elements have an option to set flex layout at all in grapedrop, even manually. It doesn't exist in the grapedrop editor.

Additionally:

  • Bootstrap is not applied to any of the forms in any of the blocks in any sections, including the bootstrap selection from the drop-down.
  • There is no way to clear the canvas.
  • CSS Console is full of errors related to dropped declarations.
  • Not only is flex missing, there is no grid! And you call this a web editor?
I was considering paying for the use of grapedrop because of the additional blocks, but after realizing that the opensource editor is far superior, and free. I can't justify even using grapedrop at all, not even for free.
I'm testing in Chrome, Edge, Firefox, and Firefox Dev.

February 19, 2021 at 12:59pm
Hi thank you very much for such feedback. Well, I can't argue against Built-in blocks. Unfortunately, we didn't update them for a while and they never followed Basic blocks, which leads to a huge inconsistency from the UX point of view. The idea is to rebuild them all by using Basic blocks (which what we'll do soon). What about the flex options you're mentioning, we've decided to use a dedicated block for that, the Grid block (from the basic library), that because having those options available on all blocks could have a lot of undesired effects. Indeed for all the layout purposes, the Grid block is all you need. You can learn a bit more in detail about it here: https://grapedrop.com/docs/getting-started.html#using-the-editor
Bootstrap is not applied to any of the forms in any of the blocks in any sections, including the bootstrap selection from the drop-down.
What do you mean exactly? Bootstrap is included when you drop in the canvas one of the blocks from its library. If there is actually an issue about those blocks, I'd be glad to help, just let me know how to reproduce it.
There is no way to clear the canvas.
Honestly, I don't think it's worth adding, you can easily clear the canvas from Layers. Open the body layer, click on its first children, then press the SHIFT and click the last one, now with all blocks selected you can simply delete them with a CANC/DELETE.
CSS Console is full of errors related to dropped declarations.
What CSS Console are you talking about? Are you referring to any particular block?

February 20, 2021 at 9:52pm
When I add bootstrap to my server on a fresh test site, I get rounded corners on all form elements, buttons, etc.. In grapedrop all corners are square, so it's not apply all bootstrap rules, or these CSS errors need to addressed to fix it maybe.
All I know is that using the open source grapejs editor is more efficient and the blocks actually work correctly and in grapedrop none of the blocks get layout correctly.
Why would you take away the ability to use flex, and also force grid into a block? How is that freedom of creativity for UI designers? That's debilitating. I wouldn't pay money to be debilitated. You need to keep the features of the original grapejs editor and add even more if you're trying to justify getting paid. Or just make the original the paid service and close the source.
You're directly competing with webflow which makes grapedrop look like a school IT class project. If I was going to pay for a service like that I'd pay for the best service, not some alpha that was released as a finished product. This grapedrop thing feels very alpha stage to me. The only feature that works well in grapedrop is the feature that stops me from doing anything productive.
Edited
> Honestly, I don't think it's worth adding, you can easily clear the canvas from Layers. > Well, then I don't think it's worth paying for. You didn't even need to add it, it already existed, you removed it. That's the exact opposite of making something better as a paid service. A digital canvas needs a reset button. Sometime I just want to drag a bunch of blocks on the screen to see if they look right, then clear canvas to add the one that fits best to my design idea.
Front end is easier to write by hand than to try and use grapedrop right now. I literally got more layout structure faster by writing <style>.flex {display: flex;}</style> and <div class="flex"></div> than I did by dragging one of the built-in blocks onto the canvas, then copying the source, then fixing the source locally, then uploading the source. Why do I need to even fix the source locally? Why does the actual block layout look different than the graphic? Why can't I just use the block editor at the right like in grapejs to set flex on the parent and make it look like the graphic? How would keeping flex capability in the block/element settings panel cause a problem for the designer? How is taking away layout control helpful?
It doesn't work yet, don't release it. I suggest you watch some product development lectures and learn what customers expect from a paid product vs a free product, think about the direction you're currently headed, carefully inspect your competitors' products, and decide if you want to actually compete or not.
You were closer with the original grapejs to having something worth paying for than you are now with grapedrop. In webflow I can set grid and flex, or remove them from any block/element in the settings panel. Both grid and flex in the settings panel are requirements, not options.
Honestly, my opinion is that you are not fully invested in making grapedrop a serious competitor to webflow or wix, and you're just floating out some lazily built alpha junk hoping you might make some money off people who don't know the difference between a good and bad WYSIWYG. I think you're taking the lower road and targeting the uneducated, not actual UI developers. That's the only reason you would take away design control from the end user, because you think they're too stupid to use it properly.