Hey Guys,
Although I am new to Wappler (and Web apps in general), I would like to explore things and get organized as I go forward.
My question is, how do you guys organize your scripts (successful coding or ways of making tasks work)?
I know this is a very “general” question, but as a matter of fact I am just asking how do you reuse coding parts that took you long time developing the first time.
I hope you understand what I mean.
It would be very helpful to hear from experienced users how they handle a kind of “template/library” system on their creations.
Thanks in advance!
Library actions are a great way to start within a single project. You can then copy paste those library files to other projects and modify as needed. This usually means having a common data schema so try to keep that consistent across projects.
Now with one mobile application I developed, we utilize a single code base for half a dozen separate Wappler projects by aliasing a folder back to a common source. This particular use case deals with common front end code, but I’d imagine you could do the same for library actions. This way you could code in one place and have it reflected on other projects. Haven’t tried this but seems doable.
Having a base project in GitHub is another way to reuse. I did this for a while, but given my desire to constantly improve and simplify things, I found I was always having to go back to the source project and update with my latest method of accomplishing a task—a not so rare event given how quickly Wappler evolves. So now. I tend to copy paste the files I need.
You also have extensions that you can “install” in each project to provide functionally and formatters you use often.
2 Likes
Thanks Ken for your input!
The main key is to be productive (time saving).
I have no experience on GitHub yet and Mobile apps are too advanced for me at the moment.
So, I keep the “Library actions” and “extensions” from your suggestions and try to learn more about them (how to).
Really appreciated!
2 Likes