Hello, Mircea

Even I am Romanian, I'll keep writing English here.

We both know what kind of database apps are delivered here. Mostly of them are in FPD26, some of them in FoxBase or even dBase III.

Another inherited thing in local programming is the 'code'. Article's code, written and maintained by the user. well... dbase stuff. Instead of article's name, let's remember some silly code.

This is for real: in a pizza store, that stupid programmer reserved 8 letters for the pizza's code. So, pepperoni pizza = X9D744F8. And when the waitress come to ask for pizza, she said 'Pepperoni Pizza'. The operator have a piece of paper, looks for the pizza's code and input that code. Question: how many different pizza's can be? 20? 50? 150? 1000? Romanian Police needs only 5 letters to register all the cars in the country! Isnt' that pizza thing stupid?

Also, the most seen interface is one with some buttons for every table: 'First record', 'Next record', 'Previous record', 'Last record', vertically aranged, etc. I am quite sure you know what I'm talking about.


--------------------------
Let's make the things clear: this is history. Dark age. Neolitic.
--------------------------


There is no reason to use ONLY the buttons. The application should be splitted in logical modules, every module should have it's own entry in the menu bar, etc. There exists multiple ways to organize the menus: data goal centric, user goal centric, etc. Have a look in MSDN (the one you got with VFP 7 or 6) and you'll find a book: Windows User Experience. Read it. Is just the beginning.

Hope this helps.

If you want to speak in Romanian, use the private messages area, please. Thank you.


>Hi all,
>
> How do you think about the ideea to develop an application based just on buttons and no menus ? Can be those interfaces more understandable because of better visibility of all option toghether? Whitch could be the main reason for doing all things from menus ?