11–20 of 82 posts
And now there's 201!
I don’t know what the opposite of “Not Invented Here Syndrome” is. But these days I swear all anyone wants to do is MacGyver together three dozens layers and frameworks and pray the spit holds it together.
If you know what you want, and no tools does it, then just roll your own. Inventing Things Here is criminally underrated.
Earlier quoted context omitted.
I mean custom HTML by the creator. You create a form rule to set the value of an HTML input, and then you can embed the values of inputs in the form into that html. I've used a lot of hidden inputs to determine values like even css classes to change how stuff gets displayed. You can even append to an HTML value so you can use multiple rules to build up HTML content.
Do you do some cleaning to avoid interference of the code of the creator and your code?
I tried out the demo and was dissapointed that for number inputs a regular ` ` is used. This removes any option to add numbers by using the arrow up keys on a keyboard. Another thing I noticed is that your blog loads very slow, but that might be because this article is rather popular now.
> None of them can do dynamic HTML. Does it mean custom HTML written by the creator of the form or just a few precanned options?
I mean custom HTML by the creator. You create a form rule to set the value of an HTML input, and then you can embed the values of inputs in the form into that html. I've used a lot of hidden inputs to determine values like even css classes to change how stuff gets displayed. You can even append to an HTML value so you can use multiple rules to build up HTML content.
I tried out the demo and was dissapointed that for number inputs a regular ` ` is used. This removes any option to add numbers by using the arrow up keys on a keyboard. Another thing I noticed is that your blog loads very slow, but that might be because this article is rather popular now.
so there is a good reason for this - I've learned the hard way that you cannot trust the number input, it has some very strange behavior. I could write a blog post just about that issue. I plan to create my own custom number input that has its own increment/decrement buttons. The thing was built with react and the number input has some unanticipated side effects.
I've been building a form builder with a no code rules engine. Hoping to relaunch in the next couple of months. Have been redesigning the homepage and creating content to explain how it works. Here's a video of a tutorial; https://www.youtube.com/watch?v=lDlKtyYf5Kc
And now there's 201!
And it still doesn't do what I need it to... Guess I'll just write my own! :)
Right now it does not have a date picker because the difficult of writing a rules engine that handles date conditions. I hope to change that down the road, this is more than an MVP but I have so much more I hope to do.
Earlier quoted context omitted.
so there is a good reason for this - I've learned the hard way that you cannot trust the number input, it has some very strange behavior. I could write a blog post just about that issue. I plan to create my own custom number input that has its own increment/decrement buttons. The thing was built with react and the number input has some unanticipated side effects.
It may be worth mentioning in a future blog post because you lose a lot of the built in behavior of browser input when you make everything a "text" input. It hurts accessibility and inclusiveness as well by ignoring these common browser behaviors.
I tried out the demo and was dissapointed that for number inputs a regular ` ` is used. This removes any option to add numbers by using the arrow up keys on a keyboard. Another thing I noticed is that your blog loads very slow, but that might be because this article is rather popular now.
so there is a good reason for this - I've learned the hard way that you cannot trust the number input, it has some very strange behavior. I could write a blog post just about that issue. I plan to create my own custom number input that has its own increment/decrement buttons. The thing was built with react and the number input has some unanticipated side effects.
How will you handle users who have javascript disabled?
Why reinvent the wheel? Why not fix whatever problem you have with numeric input?