Exercise 5

A.




[PROGRAMMER A]




[PROGRAMMER B]



B. On my own understanding to the context diagram, the Programmer A required a hard coding to give satisfactory of the process while Programmer B can use a simple code looping.

A.Sketch out the general structure of each program.




B. Highlight any potential interface problems you expect from each programmer and how they could attempt to correct them.

In programmer A, it uses the simple programming algorithm that waits for and dispatches events or messages in a program. It works by polling some internal or external "event provider", which generally blocks until an event has arrived, and then calls the relevant event handler. While in programmer B, it uses a long term of coding where the reader cannot trace or map out the codes easily.

B.
Based from the two approaches made in creating the event, I prefer to understand the loop-style programming of programmer a. It is much easier to understand than the callback structure that the programmer b used. Callbacks style of programming are more complex than the other one. Consequently, both programmers do good in the sense that they uses event handlers for less complexity.

a)




b) Maybe a problem may occur if a user misinterprets the buttons displayed in the interface. The programmer may attempt to change the interface if ever they have identified these problems.

The program of Programmer A loops and stops when it encounter an event. This style uses short-length of codes thus said to be manageable but causes more errors during runtime.
The program of Programmer B waits for an event to happen. And since it is possible to have two events happen at the same time, runtime errors are inevitable.

a.)

Programmer A: Get Event --> Checks events from queue for event identification and Execute event handler --> Save (Confirmation) or Open List

Programmer B: Get Event --> Process events to identify proper event handler --> Save (Confirmation) or Open List

b.)

Programmer A: uses the event-loop style which is very easy to manage and understand and this styles has short-length of codes.

Programmer B:uses the long-length coding which is hard to trace and manage.

a. Programmer A: Get Event --> Checks events from queue for event identification and Execute event handler --> Save (Confirmation) or Open List
Programmer B: Get Event --> Process events to identify proper event handler --> Save (Confirmation) or Open List

b. Programmer A used simplified coding by using the event-loop style of program where this style is coded shorter and easy to manage while Programmer B used a style that is longer to code and harder to read but has the ability to manage events better.

a.





b. i guess, it is very advantage for the programmer A, for he uses a short coding process than programmer B. Programmer A uses event loop style to shorten or even restore the process.

a.)
- Programmer A
https://2img.net/r/ihimizer/i/programmera.jpg/

-Programmer B
https://2img.net/r/ihimizer/i/programmerb.jpg/

b.)
Programmer A- He used a short coding style or event loop style which is very advantageous to his part. Because the codes are simplified.
Programmer B- Used a long method in coding.

A designer described the following interface for a save operation.
The users initially see a screen with a box where they can type the file name. The screen also has 'list' button that they can use to obtain a listing of all the files in the current directory (folder). This list appears in a different window. When the user clicks the 'save' button the system presents a dialogue box to ask the user to confirm the save.
Two programmers independently coded the interface using two different window managers. Programmer A used an event-loop style of program whereas programmer B used a notifier (callback) style.

(a) Sketch out the general structure of each program.
(b) Highlight any potential interface problems you expect from each programmer and how they could attempt to correct them.


A:
a.) Get Event > Checks events from queue for event identification and Execute event handler > Save Confirmation or Open List
b.) Get Event > Process events to identify proper event handler --> Save Confirmation or Open List

B:
Programmer A had chosen event loop style, which is as all we know is structured and short. The problems is that it always loop until it found something like an event which would certainly cause more runtime resources as it takes its process.
Programmer B on the other hand, had chosen to code it to a more complex style of coding. Now, because of it, it becomes more complicated and unlike the first style of coding, it is harder to trace. On the kind of coding for Programmer B, it waits for something to happen. Two synchronous events might happen and might cause runtime problems. Comparing it to the first style of coding, the error is much more awful.

Exercise 5 A designer described the following interface for a save operation.
The users initially see a screen with a box where they can type the file name. The screen also has 'list' button that they can use to obtain a listing of all the files in the current directory (folder). This list appears in a different window. When the user clicks the 'save' button the system presents a dialogue box to ask the user to confirm the save.

A said dialogue box is indicating an overview of what the user may want occur in the system by the interaction. Once this has been detected and presented to the user in the dialogue box, the only action that the system allows the user is to acknowledge the message and dismiss the dialogue box with yes, no, and cancel. The system prompts the user dialogue, with good reason. The preemptive nature of the dialogue box is to ensure that the user actually notices that there was an occurrence or happening. Presumably, the only event that will be produced in such manner are ones which the user must know about before proceeding, so the preemption is warranted. But sometimes dialogue boxes are not used to indicate errors and they still prevent the user from performing some actions that they might otherwise wish to perform but sometimes asks for verification and authentication of the event that is being process. The dialogue box might be asking the user to fill in some information to specify parameters for a command. If the user does not know what to provide, then they are stuck. A lot of the time, the user can find out the information by browsing through some other part of the system, but in order to do that they must exit the dialogue box (and forfeit any of the settings that they might have already entered), find out the missing information and begin again.

A:
a.) Get Event > Checks events from queue for event identification and Execute event handler > Save Confirmation or Open List
b.) Get Event > Process events to identify proper event handler --> Save Confirmation or Open List

B:
Programmer A had chosen event loop style, which is as all we know is structured and short. The problems is that it always loop until it found something like an event which would certainly cause more runtime resources as it takes its process.
Programmer B on the other hand, had chosen to code it to a more complex style of coding. Now, because of it, it becomes more complicated and unlike the first style of coding, it is harder to trace. On the kind of coding for Programmer B, it waits for something to happen.

b.) Programmer A used a short coding style that processes in a short way which is called the event loop style and is better than the style used by the programmer 2- something that is complicated.

Programmer A has an effective flow of controls and has a determined flow of events while Programmer B has made the program more complex and unorganized.

* cenxa sir, lahi ang account na akung gigamit, di man gud ku kasulud.. wew..

A designer described the following interface for a save operation.
The users initially see a screen with a box where they can type the file name. The screen also has 'list' button that they can use to obtain a listing of all the files in the current directory (folder). This list appears in a different window. When the user clicks the 'save' button the system presents a dialogue box to ask the user to confirm the save.

In typing the file name in the prompt box, there will be a save button underneath it, and if you’ve input the chosen file name and click on save, the data that you want to save will be redirected to the path which will be the new location of the data that you want to save. There will also be the ‘list’ buttons where you can access the datum stored in the hard drive; once you’ve clicked on save, there will be a prompt box where the user will be asked to confirm the saving status of the data.

a.) Programmer



b.) Programmer A code it self is smooth and easy to manage and understand, while the Programmer B has a complex code it may cause a hard to manage specially when there is a problem comes.

a.)



b.)
Programmer A - in terms of Coding the program is easy to understand and nice but it has a bit of complexity in terms of the flow of the structure.

Programmer B - in terms of Coding the program is hard and complex specially when there is an error comes it is hard to trace and manage but in terms of the flow of the structure it is smooth and easy.

A.
https://www.facebook.com/album.php?aid=44263&id=100000054516576#!/photo.php?fbid=209078452437304&set=a.178466598831823.44263.100000054516576&theater" alt="" />

Programmer A: After the user has confirmed to save his/her file, the program informs the user that the file has been saved and then it goes back to the save interface once again.

Programmer B: After the user has confirmed to save his/her file, the program informs the user that the file has been saved and then it exits the save interface.

a. Programmer A: Get Event --> Checks events from queue for event identification and Execute event handler --> Save (Confirmation) or Open List
Programmer B: Get Event --> Process events to identify proper event handler --> Save (Confirmation) or Open List

b. Programmer's A style of coding is much more complicated compared to programmer's B style of coding. Programmers A style can give ease and comfort to the user because it can be manage easily but the only problem is that it will be prone to errors because it has no notifiers unlike programmers B style, whenever the programs detects an error/s it will alert and notify the user that there is something wrong...

Admin wrote:A designer described the following interface for a save operation.
The users initially see a screen with a box where they can type the file name. The screen also has 'list' button that they can use to obtain a listing of all the files in the current directory (folder). This list appears in a different window. When the user clicks the 'save' button the system presents a dialogue box to ask the user to confirm the save.




Two programmers independently coded the interface using two different window managers. Programmer A used an event-loop style of program whereas programmer B used a notifier (callback) style.

(a) Sketch out the general structure of each program.
(b) Highlight any potential interface problems you expect from each programmer and how they could attempt to correct them.

answer:

(a) 1.) Get Event --> Checks events from queue for event identification and Execute event handler --> Save (Confirmation) or Open List
2.) Get Event --> Process events to identify proper event handler --> Save (Confirmation) or Open List

program A





(b) I think Programmer A used the practical coding by using the event-loop style of program, since this style has short-length of codes and can be easily managed, whereas the Programmer B used the lengthy-style of coding and is very difficult to manage and trace. There could also be problems when it comes to callback functions.

program B

(a) First, when you enter your name the program reads it and save it in the saving area. When the user chose to search the name the program reads and search the database if the name is their and if found it will give all the information.

(b) I think Programmer A used the practical coding by using the event-loop style of program, since this style has short-length of codes and can be easily managed, whereas the Programmer B used the lengthy-style of coding and is very difficult to manage and trace. There could also be problems when it comes to callback functions.

a. When an event occurs, the event loop takes care of dispatching that event to the relevant code in order to handle the event. While there may be some layers of library or framework between your application code and the low-level event handler, ultimately it will usually be some part of your application code that gets invoked in response to the event.

Please follow the link below for diagram/sketch

https://2img.net/r/ihimizer/i/hci1.jpg/


b. Programmer A uses a better kind of programming algorithm using event loops since it is easier to do and understand "for me". Event Loop provides more detailed, fine grained approach because it read events from an event queue, interpret an "event control string" to identify the event needed and it provides ability to run event handler. On the other hand, programmer B using a callback style uses the more composite one but Callbacks provide structured environment since it can build a table linking event with event handlers. Callbacks simplified the even processing.

Please follow the link for the diagram or sketch.

https://2img.net/r/ihimizer/i/hci2.jpg/