Hi, I would love the ability to directly edit the BT_config.txt file that is stored on the buzztouch servers. I know this is somewhat dangerous, and would be a power user feature, but in my particular situation, it would be invaluable. I currently have 1000+ screens in my app, and several hundred that I want to exclude from Search because they are similar. To do this now, since I'm having to go back and do it, means going through each screen properties and turning off the search inclusion. This is obviously very time consuming. The ability to make the changes via an edit of BT_config.txt would be extremely helpful. Another instance...if I were to host my own BT_config.txt file on my server, and make changes to it, there is no way to sync it with the one on the buzztouch server. So, adding that ability via editing or possibly upload and replace would be cool as well! Thanks, Mark

Without too much thinking... maybe this as solution... Updating the file itself is a bad idea while also using the control panel. In other words, doing it plain-text and parking it somewhere is fine. Or, using the control panel is fine. Both is tough. It's hard because I can imagine it getting very out-of-sync with the control panel and it could get confusing when the control panel settings don't match the actual file. I'm thinking ... a setting in your control panel like 'use live data' or 'use file data' If you selected 'use live data' mode the app would query the database like it does now when creating the config data for the app, changes in control panel would propogate to the app LIVE. If you selected 'use file data' you could use the control panel to create the file, download it, change it, then re-upload it. Changes in the control panel would not affect the app, only the config data that you would download. When you uploaded it it would be FIXED until you uploaded another copy. Not sure if this makes sense. Just need to figure out ways to make it easy on you without making it confusing?

I hadn't thought about the problem of somebody tweaking the config file while somebody else was updating in the control panel...and shame on me, because I test software/hardware for a living! I was only thinking from my perspective as a user, where I would be doing one or another, but not both. I like your idea. A way to freeze changes on the database while other changes are made offline then uploaded to the database, at which point the freeze would be taken off and the database would again feed live data. I think that would work for me. The only thing I'm looking for here is the ability to make large scale changes in the file without having to go screen by screen. And, by the way, this is not an urgent issue...would rather see Android availability in v1.5 before this was implemented! ;-) Thanks! Mark

David, I believe your solution would be a great solution for those of us trying to manage lots of data...

See above...