What we want to express here is that while you can use Pinegrow Interactions in projects made with any tool, the license doesn’t allow you to integrate Pinegrow Interactions directly into another website builder’s core functionality. (Since you’re not the creator of this type of tool, you’re free to use it and sell your work as well.)
1 Like
It was not meant to be offensive, seemingly it will be an increasing slippery slope for all partakers. I’m glad you’re still master of your domain. 
@Pinegrow_User Oh, no offense, I just found the situation ironic considering the thoroughness of your messages and the always sophisticated vocabulary you use in your contributions.
Those same contributions remain rich and very informative, and they have often been helpful to everyone in their time, although - for some reason - they now often come with a bit of sharpness that seems to be your trademark for the past few years. 
Since our discussions and thoughts aren’t really helping anyone, I invite you to continue this privately if you’d like. I’m here and fully available for you.
It seems you’ve completely misconstrued what I’ve said entirely? So I will just leave that with you.
1 Like
If it is simply animations you are after, and you’re a Mac user, see if Tumult Hype would meet your needs.
1 Like
Now that the question about licensing for redistributing animations and interactions created with the Pinegrow add-on has been answered (and we have also clarified our licensing terms on the documentation site), I encourage you to continue the discussion on related topics in dedicated threads or in the appropriate section of the forum: Pinegrow Interactions Add-on - Pinegrow Community Forum
Thank you for your understanding.
Interesting points. As a Pinegrow user for a few years I’m going to give my opinion. I’m sure there are much more experienced devs who could weight in on this too. First of all, what I especially like about Pinegrow and the reason I’ve moved away from other website builders is because with Pinegrow I’m not locked into the builder’s solution which is often one-size-fits-all and may not be updated when newer methods arise. Take the example of a font manager. There are several ways to incorporate fonts. With Pinegrow I can use the design panel, or add font snippets by hand, I can even convert my local fonts to woof and woof2 using an online website that spits out a code snippet to add them to my site. I’m not sure if I’d prefer a preset solution to be honest. As for spell checking. I always run my text through multiple paid editing software before adding it to a website. I feel more comfortable with that than relying on my builder to implement spelling and grammar checking to my standards. Your optional “mass delete” and “mass rename” option for classes is a good idea. There might be cases when I would prefer to use search and replace so I can check each instance, but in general, that might be a useful feature. As for designing desktop first, that’s what I almost always do. I just write them myself in the code – it seems easier to me than the UI that Pinegrow offers, which I find overly complicated. If they would implement a system that automatically applies the css to a current selected breakpoint (responsive width) that’s open, either desktop first or mobile first, as some builders do, I would probably use it. I guess, in the end, if there’s something that doesn’t work for me in Pinegrow, I’m happy there are alternative ways to implement it. The workflow is flexible and open. By the way, I’m curious. What open source alternative even comes close to Pinegrow in terms of usability?
2 Likes
It’s worth clarifying right away that when I wrote that critique post, I was annoyed by the lack of a font manager, classes, and criticized Pinegrow in isolation from its positioning. All in all, I should have expressed myself in a more restrained manner. Now I feel silly for mentioning Pinegrow’s pricing and comparing it to a typical open-source project (that’s just my stereotypical perception of free products, don’t take it seriously).
I don’t know of any free open-source alternatives to Pinegrow. I wrote that pinegrow looks like a typical open-source product because the interface of pinegrow as mentioned by some users looks outdated, with not user-friendly UI/UX and in general Pinegrow feels unfinished due to lack of some basic features that users expect to see by default, but we have already realized that Pinegrow developers do not position it as a solution for all tasks in web development. But if you look at Pinegrow apart from the positioning, and imagine that Pinegrow is a tool that allows you to build websites/frontend in a visual editor, by a combination of factors, I can compare Pinegrow to the stereotypical underfunded raw open-source project. But considering their positioning, probably Pinegrow is a good tool for a narrow audience of users.
With regards to renaming or deleting classes or any content in our page, wouldn’t the code editor be a better option, as it provides finer control to find & replace these renamed classes/attribute/tags/text-content?
There are many benefits to this approach. Our monaco integration makes it easier to achieve it, use regex for finer control of what to find and replace, undo all the changes as required.
Also, project-wide updates might sometimes end up in unexpected results, unless all pages are open to visually double check the updates.
Say, I have a class called bg-primary-500, and I want to change to bg-brand-500. I duplicate the former in the styles panel, rename the new one to the latter. Now, as the user hasn’t deleted the former, we can’t assume the user’s intend here to apply automatic changes across the project, or should the user be given the benefit of doubt?
Rollback of mass transformation can always be very tricky with the user easily breaking the site, especially undo of the changes project-wide. Most users probably don’t always have their projects under a git repo to easily rollback between commits. There are lots to consider for such page/project-wide transformations.
Given Pinegrow nicely handles HTML - tags, attributes, classes, using the code editor to apply mass transformation might be the best approach. Is the ask really around applying such page/project-wide transformation as a separate action to when deleting or renaming classes, so that this way the user can opt into this transformation in addition to their delete/rename action? Thoughts from the community?
1 Like
2 Likes