MatthewScammel1
Qrew Trainee
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Upcoming Changes to JavaScript in Quickbase
@Evan Martinez Has there been any considerations for moving this date? We the developers/users for your platform have our own roadmaps, and projects that we are either currently working on, or will be shortly. April is really really soon to make such a major change. When we started our development we were under the terms that we had these tools available to us. As I've already expressed, I don't agree at all with these changes, but I hope you can reconsider giving us and our companies more time to figure out how to more forward.2Views0likes0CommentsRe: Upcoming Changes to JavaScript in Quickbase
Hey @Evan Martinez thanks for your response. A question I have for you: is there going to be any native way of custom DOM manipulation? The reason I ask is because most of the time, users/clients have a specific workflow that they want to achieve. Especially when they are moving to Quickbase from another system. We as developers, need a way to do this or our answers will be either no, we can't do this, or those of us who were Software Engineers prior to this will say yes, but it's going to take more time (also cost them more $), because we'll have to build the flow in a code page. I have a bunch of scenarios in which we would need improvements to the platform in order for our users to get their desired workflow- if your solution is to remove js insertion. If there is a place I could provide this information, or someone to speak to about this I would be more than happy to do so.1View0likes0CommentsRe: Upcoming Changes to JavaScript in Quickbase
Big fan of the platform, but this is a MAJOR loss for many of us. I've been to dev conferences in NYC and I didn't meet a single person who wasn't using IOL. For us personally, this is really going to slow down development time. Inserting IOL to do something as simple as make the Save button run an extra function before it saves the record is the reason we use Quickbase. We don't want to have to create our own forms (code pages) each time we need small extended functionality. This is essentially why we chose to use Quickbase. I hope you can all reconsider. I completely agree with eventually having to remove this for testing/security purposes, but the platform's feature set is not there yet.10Views0likes0CommentsRe: Quick Base Release Notes for February 2019
I agree with you, it would be perfect if it was optional because it works really well for us when there's only a couple on the form. But, on forms where we have 4 or more we're seeing some issues. Otherwise, this is a great step in the right direction!2Views0likes0Comments