Tag Info

Hot answers tagged

128

There is little need even to explain the idea of interface to users of the program. To them, the program is the interface. Don't say "the GUI of the program does X". Just say "the program does X". Don't say "the GUI has a red self-destruct button". Say "the program has a red self-destruct button". To you, the programmer, it is very important to think ...


25

What about "the visual part of the application, i.e. its buttons, text boxes and other visual elements"? In a more detailed form, you would also include that it handles: The process of displaying the elements to the user through a screen, The interaction of the user with those elements (most commonly known as events, but it's not limited to events). ...


7

The terms I commonly mention with the users are interface and database. Most users know the term User Interface (UI) and even if they don't I find it more immediate than front end. With database I mean both the DBMS and the server side code. Most users know or understand this (they realize there must be some server side code) but they don't care. For the ...


2

If you want to separate the program from the GUI, then you can use 'Basic interface' vs 'Advanced interface'. If you merge the concerns (program & interface) then you can do what the calculator application on mac and windows does, have multiple views, 'basic', 'advanced' and more if need be. You can also link it with functionality and say, 'basic ...


2

You could offer a tiny downloader app like the ones you get when you download apps from a website such as softonic or google (chrome installer) that essentially pulls rest of the stuff from the Internet. My University provides a huge amount of materials online and there is this small application that downloads all those updates and feeds from their servers. ...


1

Since they are all PDF's I would combine the PDF's on the server and have them download one PDF. Any other way you go is just going to have some layer of complexity, which seems to be what you are trying to avoid. Sure, there are some valid reasons why putting them all in one isn't a good idea, but there is no best answer.


1

There are a few options. Individual files You can have a guide explaining how to download an HTML file from the browser which includes images and all related files. Basically a manual for the "save as HTML" option of the browser. You can offer them in word 2007 using, for instance PHP. You can offer them in odt using, for instance, PHP. If you have a ...


1

Here are a few usability concerns (not problems) associated with masonry grids. If there is not a fair amount of padding between photos, things can get distracting and messy very quickly. Due to the nature of the layout photo's with certain dimensions can end up becoming the centers of attention, there is nothing wrong with this -- however it all depends ...


1

In Dutch we have the word 'digibeet', in analogy with 'analfabeet', e.g. the English analphabetic. I guess 'digibetic' would be the English version, and would perhaps be a good word for this. However, for now computer illiterate as mentioned in the other answers would be the best term.


1

|You can just progress to the next state automatically in application, with a notification in addition to that. Avoid 'prompts' (alerts) whenever possible. The best notification system I can think of is Facebook (apart from the emails). Show a red number on a meaningful icon. When a user clicks on the icon, show a list of all notifications and clear the red ...



Only top voted, non community-wiki answers of a minimum length are eligible