Forum Discussion
_anomDiebolt_
8 years agoQrew Elite
So I played around with this feature using Chrome Canary and it is pretty sweet. It is like your own personal QuickBase Exploratorium where you can save a copy of any file QuickBase serves to your local disk and then edits to that local file are used in place of QuickBase's original file and the changes you make will persist over time until you turn off the Local Overfide feature with a checkbox.
Here is a simple screenshot of me altering the QuickBase file common.packed.js and putting an alert into the top of the file:
One nice feature is that you can use any IDE or Editor to edit your copy of QuickBase's file. You could even implement your own build tool chain as once the Local Override is setup Chrome creates a file watcher to incorporate the changed file whenever it detects a change.
The Local Override feature will only apply to your version of Chrome but it suggests a lot of use new cases we have never had before:
Here is a simple screenshot of me altering the QuickBase file common.packed.js and putting an alert into the top of the file:
One nice feature is that you can use any IDE or Editor to edit your copy of QuickBase's file. You could even implement your own build tool chain as once the Local Override is setup Chrome creates a file watcher to incorporate the changed file whenever it detects a change.
The Local Override feature will only apply to your version of Chrome but it suggests a lot of use new cases we have never had before:
- A user with only moderate CSS skills could explore styling changes to an application as feedback to QuickBase to correct a problem or suggest, demonstrate and share a new styling feature
- A user with only moderate JavaScript skills could explore new behavior without interfering with other users