I’d like to force image capture on mobile devices. right now, the file input triggers a menu on mobile that allows the user to select between “Photo Library”. “Take Photo”, or “Choose File”.
I do not want to give the user a choice, I want to force the “Take Photo” option.
This is achievable via JS, but when attempting that route I encountered an incredibly difficult time passing the image capture data to a weweb variable using the wwLib.wwVariable.updateVariable function.
This was brought up in the latest Office Hours with Joyce and Flo. Submitting here to open the conversation to all
Hey, it’s a custom component, not a JS If you want I could sell it to you but after the amount of work that went into it I definitely won’t be “just sharing it”, sorry.
@Broberto
If it gets posted as is, I won’t be buying it. It’s an incomplete solution, at best a small time-saver but not super high value overall. Good luck with your sales buddy.
I’ll take it that you’re new to this type of web development, but respectfully, you have no idea the amount of work that @Broberto put into that component and you don’t actually understand what it takes to get that working well within WeWeb.
Maybe your user experience doesn’t require that level of quality, but calling it a ‘small time saver’ and ‘not super high value’ is absolutely wild.
Wow. My component will be released this week, please don’t buy it @cannible I don’t wanna deal with you. If you buy it you’ll get a refund. Thanks for understanding. Btw. with this attitude you’ll get nowhere in here.
I was considering giving this to you for free, thought you were broke or smth. after seeing you at the office hours, felt a little bad for you, but after this dick move, I think you’re done here. Good job of making a fool of yourself in front of the community.
@Micah and @Broberto are two of the most talented WeWeb developers and do a ton for the community.
I searched everywhere for a WebRTC camera solution to no avail, and ultimately commissioned @Broberto to build this for me. You will not find another camera component in or out of the WeWeb ecosystem with the feature set his has. The ability to switch the camera aspect ratio was an incredible feat in itself.
At the end of the day this is pretty simple: I gave Broberto honest feedback about his work, not about him personally as a dev. Micah came out of nowhere and made it personal, and so did Broberto when I defended myself. The community can read that for themselves. I will not be bullied.
This person tried to sell me something, that makes me a prospective customer. I don’t care if the developer and his internet buddies get hurt feelings if I have honest customer feedback.
trying to add some constructive feedback here:
the preview it’s actually nice. Building custom code components always requires more time and effort than what people not doing it may think.
some things I would add:
handle the rejection of getUserMedia
revoke unused object URLs. this one it’s a bit tricky because the user may be using them outside of the scope of the component. I would go for an autorevoke option to revoke all object URLs on component unmount and a revoke action for advanced cases where the user wants to disable autorevoke and handle that in a workflow
That’s great points : -) Thanks Mariano, as usually you come and bring your wisdom which is super on point and very appreciated. We both know it’s definitely a feat to make them work indeed.
You literally gave 0 constructive feedback and just belittled my work, without providing an answer.
I think everyone, buddies or not can agree that your feedback is nor honest, nor constructive, you just acted terribly towards the members.
If you want I could sell it to you but after the amount of work that went into it I definitely won’t be “just sharing it”, sorry.
