![]() Instead I’ll add the opinion of a Bubble rep that is far more knowledgeable about this than me. Other nocode platforms handle the plugin development much better and don’t have this kind of problem at all.Īlthough I find this conversation fascinating, it is so far over my head that I won’t even begin to have an opinion. It avoids to load the same dependencies many times because the same file loaded in bubble’s CDN with 2 plugins will have different urls. I can see it’s useful to use an external CDN if you have the same dependencies on multiple plugins that can be used toghether in the same app. Personally I prefer to do the work and host all the dependencies in bubble to reduce the exposed surface of the app and potential points of failure. Using an external CDN is a legitimate choice. It’s the plugin’s consumer responsibility to check if a new version is published, update, test that the app is working properly and then publish the updated app. Dependencies needs updates and it is the plugin’s author responsibility to do that, test that everything is working and then publish an update. there is no free lunch: software requires maintenance.most of the time you don’t need to build the library, it’s already distributed in its bundled version.You can choose to explicitly point unpkg to a specific file, otherwise it will follow the normal conventions. Unpkg automatically tries to published the library based on instructions in the package.json. most of the libraries do not choose to publiah on unpkg too.If it’s a major update or the mantainer doesn’t follow semantic versioning you can load a version with breaking changes and your plugin will stop working without any notice blindly load the latest library is bad practice, it “should” be ok if the library follows semver and the latest update is a patch or minor update.The are lots of different animations ready to use out of the box, but creating new ones is simple also.UNPKG allows content to always use the latest version Every aspect of animation is handled by CSS. Of course, in practice, it’s not always that easy, but the idea behind AOS is as simple as that. The idea behind AOS is straightforward: watch all elements and their positions based on settings you provide them. This allows you to add your own animations easily, and do things like change them according to the viewport. Have all the logic inside the JavaScript.I wanted to split the responsibilities with my new library: I decided to create a library that has a pure goal – detect position of elements and then add appropriate classes when they appear in viewport. Though, in some cases it’s ok to set them using JavaScript, it’s still much cleaner to just leave them where they belong and handle all CSS related things inside CSS file. ![]() In all of popular libraries, animations were completely handled by JavaScript by inserting inline CSS. For simple projects it was quite nice, but on larger sites we wanted to have more control over what’s actually happening. In my previous company we were using WOW.js (or other similar libraries) to animate elements on scroll. If you’d like to get right into it, the code is on GitHub. Have you ever seen those long web pages where different animations are being applied as you scroll down? I’d like to share with you a plugin I wrote that makes it really easy to handle all kinds of animations with full CSS control and no pain. Not to mention it’s proved itself by working well on a number of production sites. One of the things I like about it is that it leaves as much as it can to CSS for creating and controlling the animation themselves. Michał has created one of those “when you scroll to here, trigger this animation” libraries. The following is a guest post by Michał Sajnóg, a front end developer at Netguru. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |