21–30 of 30 posts
What kind of applications do you want to be able to build with such a tool?
I was thinking about basic CRUD applications to start. I think it would be valuable for a business to be able to build a small, basic CRUD application to manage certain processes like QA, or any other basic data-keeping that's needed - in situations where ready-made products just don't fit the bill.
What kind of applications do you want to be able to build with such a tool?
I was thinking about basic CRUD applications to start. I think it would be valuable for a business to be able to build a small, basic CRUD application to manage certain processes like QA, or any other basic data-keeping that's needed - in situations where ready-made products just don't fit the bill.
Also, I recommend trying out a hosted wiki and Google Docs. Having a shared Google Docs spreadsheet will probably be more functional than anything you can build without actually programming.
Earlier quoted context omitted.
Yeah Access was the closest think I could think of. But for what I'm picturing, that's too complicated - I don't want the end-user to see or think about the database at all. The end-user should basically drop and drag things, then click a button that says "create application" and it spits out your app.
The name for the activity you describe is programming . Just because you've not typing lines of code doesn't mean you're not programming. Meanwhile, you need to think about why people like spreadsheets. Yes, they show you all your data on a big stupid sheet and force you to look at it, but that's a feature, not a bug. People don't collect data because pressing buttons is fun. They want to see their data again. Indeed…
Earlier quoted context omitted.
The name for the activity you describe is programming . Just because you've not typing lines of code doesn't mean you're not programming. Meanwhile, you need to think about why people like spreadsheets. Yes, they show you all your data on a big stupid sheet and force you to look at it, but that's a feature, not a bug. People don't collect data because pressing buttons is fun. They want to see their data again. Indeed…
The reason I would not choose a spreadsheet for this idea is for a cleaner layout. I think a basic form with boxes and labels, where the other data is hidden, would be more user-friendly. A spreadsheet has data all over, and that can be distracting to see and navigate around - for me, anyway. That's my preference.
1) The main body of the data should fit on one page. In many cases, it can be made to fit, you just need to reorganize some of it and tweak sizes of boxes, use some reasonable abbreviations, etc.
2) Try to keep it to 7 colors (though this rule can be bent a smidgeon by going one shade darker for emphasis without really introducing a totally new color).
3) "Whiting out" (though beige, gray or taupe can be better choices than white) the background boxes can go a long way towards making a spreadsheet less torturous to look at.
4) Going one font size up and adding bolding can be plenty of emphasis. You really don't need anything of size 72 lettering just because it's a title or some such.
(I'm sure you don't personally care. And I'm not trying to change your mind. Maybe I just needed to say it for myself.)
HyperCard was the gold standard for this kind of thing. http://en.wikipedia.org/wiki/HyperCard#Applications
Requires nothing more than a Google/Google-Apps user account to get going.
You can define Entities ("table"/"sheets") and Attributes ("columns"/"fields") to get working with your database app within a few minutes.
Integrates with Google Contacts (import/upload), Google Docs (attach docs to database records), Google Maps (mark and search for records based on geographic location). Google Calendar (export events/tasks-like data) and email integration are coming up later.
The web-app can be mapped to your own domain like http://app.yourdomain.com (using Google Apps).
Other features include :
- Authorization Profiles for fine grain access control up to field level.
- Custom Views to filter data matching your criteria.
- Custom Actions for single click edits.
- Automated Audit of all write operations
- Bulk Export & Import of data as CSV files.
- Support for drop-down choices,
look-up fields (references) and
image fields (with auto thumbnails for list view)
..and more.
We're working on a framework we hope to expose to our customers for just this purpose. It'll be made up of modules you can add and a GUI for field/form customisation. A bit like Microsoft Access but web based, is that what you had in mind?
Somewhat, but easier to use than Access. I was thinking that after learning the tool, the end-user should be able to create a basic CRUD application with one or more workflows/screens in a few hours, tops. Do you have any information about your framework? I'm interested to know more.
I think the desire to program without programming is somewhat misguided. It's great to avoid churning out boilerplate code, and it's great not to need to remember lots of arcane interfaces, but programming, even in the most WYSIWYG DWIM system, still requires the ability to mentally model how the machine interprets its instructions and to write (click, draw, gesture, vocalize) instructions that solve the right problem.
HyperCard was the gold standard for this kind of thing. http://en.wikipedia.org/wiki/HyperCard#Applications
Something that I've played with that is obviously inspired by HyperCard is RunRev.com's LiveCode: http://runrev.com/home/