Its not that its that a quick search often reveals all the answers to the questions asked. Many have been answered dozens or more times. Its not personal, and sometimes users are overwhelmed with their own responsibilities, deadlines, etc. Frustration unfortunately does boil over, and its not fair, but it does happen. I apologise for my part in this, I've been guilty of it before. Its just that answering the same questions multiple times becomes tedious. Its so easy to search the community for answers but very few do. Its just hard work some days keeping up.
1 Like
This is just my opinion, but Wappler has so many parts to it that it is actually pretty difficult to write tutorials for all the things it can do, even though there is a written tutorial for login procedures which you may need to adjust to suit your needs.
Unlike some low code tools which give you blocks of predeveloped content, where you can just pull in a login form and configure the options it hands you.
Wappler is different because it can do almost anything, which means there are too many variables, which is what makes it such a powerful tool but at the same time makes it difficult.
A login form as an example has so many ways you do it, depending on what you want as an end result.
I think of Wappler more like learning php was for me as an example, it will show you how to do an if/else condition or set a variable etc. but you need to know about 20 of those procedures and put them all together if you wanted to create a working end result.
I think Wappler took that logic as such as a base and worked on automating and simplifying as much of that as they could, while at the same time keeping in mind they had to leave the customisation and power in the end users hands.
1 Like
If it has been answered dozen of times why itās not part of a āhow toā / ādocumentationā? I know and understand that for you Wappler is āfingers in the noiseā and people who express their issues to build even simple things with the tool are just lazy people that ādo not understand how easy is Wapplerā (ie. we are morons and what we express is BS). Up to date documentation / how to / education ecosystem and focus on learning is key in most SaaS and even more in low code / no code apps. I know some here are against because they want more features every week, but on the long run new users / ecosystem and low churn is the key (except if the team is full of cash and does not plan to expand and make money with Wappler).
Check bubble and even 10% of their documentation and ecosystem would be a miracle and paradise here.
Iām not a staff member nor paid or sponsored by Wappler in any capacity. Neither are the Ambassadors or Moderators. Iāve written guides and tutorials but they always lead to dozens of questions I covered in said guides and tutorials. I think Iāll just put together examples in the future and package them up for a few Euros (to cover the time spent making them, not for profit, I work so my time is money). Very difficult balance. You can see on the Community how many questions have been answered by myself by looking at my Profile Summary, and the others that answer on a regular basis, again remember none of us are paid and we all have jobs and families too. Hundreds of users have been helped this way, and many then go on to help others. Yes documentation could be increased, and admittedly the team acknowledge that fact, but there are other things that get in the way sometimes. Be it what may.
1 Like
Agree on your points. Community is important but forum should be last action.
My opinion is that things has to go this way :
- Education and strong documentation from Team
- Less support in the forum
- More users
- Opportunity for people like you to create content. In order to build an ecosystem a SaaS needs to get a certain number of users in order to make it worth for people creating content.
- More users coming from courses / workshop
- More revenue for team : money to hire dev and people for education
- Repeat.
4 Likes
Exactly the type of reply that helps @GlobaticoLabs
The team are 100% committed and are really and truly second to none for being direct to the user. We all have room for improvement and every bit of feedback is read. Am sure this is being read right now. They always do what they can, and are still young in their existence, ie Wappler is still a baby. Things will all come together. We just all need to work with each-other and support one and other. Everyone tries their best and sometimes, for some, its not good enough, I donāt mean that disrespectfully. Maybe they just donāt have the time spare for the learning curve. BUT if they stick with it the rewards are fruitful. It has to be like any form of education. Canāt just go to school one day a week and think youāll end up with a degree at the end of the month, no different learning Wappler or any other piece of software for that matter. The user has to aid in the process. Would be great if we could hold each new users hands and walk them through it one to one but just not feasible or a reality.
2 Likes
I donāt want to see you or your screen. I want you to hear me talking, see/control my screen, and show me how to get it done.
Started with Macromedia DW and just recently with Wappler. I chose this path because of the āsimilaritiesā to DW. Each application is different. Iām finding the learning curb is my issue - impatience. I know what I want, but translating the Wappler terms to my old brain - eh - itās a learning curve. Most all of my questions are quickly answered with the documentation, YouTube or community response. Iām finding all the answers I want and hope you end with the same results.
3 Likes
I bought Wapler so I could stop subscribing to the DMXZone extensions every year but have found I may still need to have both.
I work with web developers and add functionality to their sites that they canāt add (not technocal but very good at design). A simple example is a form to email with a message on successful completion - not Bootstrap. I create the form in standard html and the server connect to send the email. On success in Dreamweaver I would create a static event to hide the form and show the response message. In Wappler the static event can be set but there are no actions for static events. So the codeless Wappler requires me to create JQuery function to hide the form and show the response. This was codeless in Dreamweaver with extensions.
I work both with Bootstrap and standard html and sometimes hybrid where I need a modal or similar on a site that already exists in html but I donāt want to handcode. Wappler with custom bootstrap 5 lets me do this without the bootstrap css completing changing the design. It is tricky but works.
The static actions like Dreamweaver would be great if it can be provided as I can then throw my Dreamweaver extensions away.
1 Like
So why using static events for this? Static events are meant to be used for calling javascript functions.
With dynamic events you can use all of the available dynamic events in Wappler.
1 Like
Explain please how when the server connect is successful that I can hide the form and show a DIV with success message using dynamic events. I know how to do this with DMXZone extensions in Dreamweaver but not with Wappler. Remember - not Bootstrap. I am keen to learn and canāt find any resources for this.
You can use a variable and toggle its value on success. So for example - set the var value to 1, then toggle the visibility of your elements using the dynamic attributes show/hide depending on the variable value. I.e. - hide the form when your_var.value == 1 and show the div when your_var.value == 1
2 Likes
Thanks Teodor, I will give that a go.
I am enjoying using Wappler so far. The program is much more stable than Dreamweaver which is a big plus.
3 Likes