HomeExercise 5
+54
tiffanycarabuena
ikoymaster
padibergonia
Chad Festejo
Jake Darren T. Colina
Dianne Jean Dumdum
Calvin John Dalino
Mark Bryan B. Gonzales
Sherwin_Elioreg
Michael Anthony Jandayan
rowellpines
Marlie E. Sisneros
Russel John L. Serrano
arnulfotaghoy
florenzie_palma
Julie Ann R. Monteroso
Godofredo C. Pisngot Jr.
vinceilagan
Xaviery Dwight Noval
Genne Fernandez
rancisolanobero
Nesscel Ann Marie Calara
irwin rod adesna
irelene cosicol
exzellrobelo
oberorancismichael
merafehangad
jezrelle larubes
cherilyn lagare
kevin.cris.ramos
willypedroso
Jovanne Nick L. Cacayan
jennifer conta
Marybert V. Lee
Jevelyn C. Labor
Mhel Sheryll Jala
KatrinaAnirtak
April Kaye Bestre Bigonte
Phoebe Angelie Gallardo
Cariza Joy Ensoy
Allan Gregor Gepulla
Mary Claire P. Avila
dudzcomz
Alaina Simbal
Ma. Monique Asuque
Ruchan Alangilan
juvilyn consejo
jonalyn sanchez
ericpapasit
Gwapong_Tao_Edward_Baylon
Frenzess-Joy H. Elman
abigail_duhaylungsod
george101_2007
Admin
58 posters
Page 3 of 3
Page 3 of 3 • 
1, 2, 3
Excercise 5
Jake Darren T. Colina Thu Apr 07, 2011 12:47 pm
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.
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.
Jake Darren T. Colina- Posts : 5
Join date : 2011-04-07
Age : 33
Location : davao city
Re: Exercise 5
Chad Festejo Thu Apr 07, 2011 1:03 pm
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 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.
Programmer B: Get Event --> Process events to identify proper event handler --> Save (Confirmation) or Open List
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.
Chad Festejo- Posts : 7
Join date : 2011-03-10
Re: Exercise 5
padibergonia Thu Apr 07, 2011 1:14 pm
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.)
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.
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.)
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.
padibergonia- Posts : 5
Join date : 2011-04-07
exercise 5
ikoymaster Thu Apr 07, 2011 1:21 pm
A.) programmer A....Start Event--->(if list.clicked) display all files from current directory, (else if file name entered and save clicked) Confirm save---> save file.
programmer b....Start Event--->Process events to identify proper event handler---> Confirm save---> save file.
B.)programmer A. makes use of a loop that makes code tracing easy.
programmer B. uses call back which makes a a source code for a program very long.
programmer b....Start Event--->Process events to identify proper event handler---> Confirm save---> save file.
B.)programmer A. makes use of a loop that makes code tracing easy.
programmer B. uses call back which makes a a source code for a program very long.
ikoymaster- Posts : 5
Join date : 2011-03-12
tiffanycarabuena- Posts : 5
Join date : 2011-01-14
Re: Exercise 5
axel ros e. campaña Thu Apr 07, 2011 1:31 pm
a.
1.) Get Event -->
Checks events from queue for event identification and Execute event handler -->
Save (Confirmation)
2.) Get Event -->
Process events to identify proper event handler -->
Save (Confirmation)
b. Programmer A used the event-loop style of program and since this style has short-length of codes and can be easily managed, Programmer A used practical coding. While, 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.
1.) Get Event -->
Checks events from queue for event identification and Execute event handler -->
Save (Confirmation)
2.) Get Event -->
Process events to identify proper event handler -->
Save (Confirmation)
b. Programmer A used the event-loop style of program and since this style has short-length of codes and can be easily managed, Programmer A used practical coding. While, 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.
axel ros e. campaña- Posts : 5
Join date : 2011-03-10
Re: Exercise 5
frozenfreak7 Thu Apr 07, 2011 1:40 pm
Ralph Gideon B. Doron
a. GetFilenameEvent------>notify----> confirm email
b. GetFilenameEvent------>notify----> confirm email
a. GetFilenameEvent------>notify----> confirm email
b. GetFilenameEvent------>notify----> confirm email
frozenfreak7- Posts : 5
Join date : 2011-03-11
JEanette R. Vale
chamz_perez Thu Apr 07, 2011 3:34 pm
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.
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.
chamz_perez- Posts : 10
Join date : 2011-03-11
Charry Mariz Perez
chamz_perez Thu Apr 07, 2011 3:49 pm
Programmer A needs more programs or codes in order to satisfy the required process thus, the event-loop is at the highest level of control within the program while Programmer B is just easy to load and to use.
chamz_perez- Posts : 10
Join date : 2011-03-11
Exercise 5
boogie Tue Apr 12, 2011 2:54 pm
Melchor S. Inte Jr.
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 the simple and practical event-loop style while Programmer B used the complicated set of style in coding the program.
(sir, sorry kau nagkaproblem lng internet connections k2ng ngsend q sa exercise 5. Krn lng nq nbantayan.)
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 the simple and practical event-loop style while Programmer B used the complicated set of style in coding the program.
(sir, sorry kau nagkaproblem lng internet connections k2ng ngsend q sa exercise 5. Krn lng nq nbantayan.)
boogie- Posts : 5
Join date : 2011-03-11
Age : 33
Location : Davao City
Page 3 of 3 • 1, 2, 3
Page 3 of 3
Permissions in this forum:
You cannot reply to topics in this forum|
|
|