[yast-devel] WebYaST developers: check return values of YaST::ServiceResource.proxy_for
Hi, as we have a distributed application with WebYaST, the frontend part actually has to check if the backend part is complete and behaves correctly. So whenever you request a backend resource, check if it actually exists ! Klaus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Klaus Kaempf wrote:
Hi,
as we have a distributed application with WebYaST, the frontend part actually has to check if the backend part is complete and behaves correctly.
So whenever you request a backend resource, check if it actually exists !
Klaus
Hi, I don't know if you want it, but now doesn't work proxies in webyast, but it is ideal for testing. I find that almost all modules use same functionality and to simplify and ensure same behavior for modules I add in http://git.opensuse.org/?p=projects/yast/web-client.git;a=commit;h=904de56ce... shared functionlity which load proxy, handle errors and return result of proxy.find. In same commit you can see example usage. Welcome any idea -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Josef Reidinger <jreidinger@suse.cz> [Jul 14. 2009 09:46]:
Klaus Kaempf wrote:
Hi,
as we have a distributed application with WebYaST, the frontend part actually has to check if the backend part is complete and behaves correctly.
So whenever you request a backend resource, check if it actually exists !
Klaus
Hi, I don't know if you want it, but now doesn't work proxies in webyast, but it is ideal for testing. I find that almost all modules use same functionality and to simplify and ensure same behavior for modules I add in http://git.opensuse.org/?p=projects/yast/web-client.git;a=commit;h=904de56ce...
Yes, having common functionality for all plugins to share is very helpful. Whats needed then is good documentation and examples. Btw., common functionality should go to lib/. Then it can be tested standalone and doesn't bloat the ApplicationController. Klaus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Klaus Kaempf wrote:
* Josef Reidinger <jreidinger@suse.cz> [Jul 14. 2009 09:46]:
Klaus Kaempf wrote:
Hi,
as we have a distributed application with WebYaST, the frontend part actually has to check if the backend part is complete and behaves correctly.
So whenever you request a backend resource, check if it actually exists !
Klaus Hi, I don't know if you want it, but now doesn't work proxies in webyast, but it is ideal for testing. I find that almost all modules use same functionality and to simplify and ensure same behavior for modules I add in http://git.opensuse.org/?p=projects/yast/web-client.git;a=commit;h=904de56ce...
Yes, having common functionality for all plugins to share is very helpful. Whats needed then is good documentation and examples.
Btw., common functionality should go to lib/. Then it can be tested standalone and doesn't bloat the ApplicationController.
Klaus
As it set some fields of controller and uses logger from controller I think that this is good place for it. If I move it to library, then it must be some module, which is include to controller and at least need two more lines of code to include this functionality. On documentation I plan work after demo release, as now I prefer good functionality. (I also plan edit skeletons to reflect current state) -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Josef Reidinger <jreidinger@suse.cz> [Jul 14. 2009 10:12]:
As it set some fields of controller and uses logger from controller I think that this is good place for it. If I move it to library, then it must be some module, which is include to controller and at least need two more lines of code to include this functionality.
Those two lines are fine as they make both the controller and the lib file more clearly arranged. And not all controllers need the proxy functionality.
On documentation I plan work after demo release, as now I prefer good functionality. (I also plan edit skeletons to reflect current state)
Please don't slip with documentation. Having good documentation and good testcases make development more scalable as its much easier for others to jump in and help. Klaus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Klaus Kaempf wrote:
* Josef Reidinger <jreidinger@suse.cz> [Jul 14. 2009 10:12]:
As it set some fields of controller and uses logger from controller I think that this is good place for it. If I move it to library, then it must be some module, which is include to controller and at least need two more lines of code to include this functionality.
Those two lines are fine as they make both the controller and the lib file more clearly arranged. And not all controllers need the proxy functionality.
OK, so I move it to separate lib.
On documentation I plan work after demo release, as now I prefer good functionality. (I also plan edit skeletons to reflect current state)
Please don't slip with documentation. Having good documentation and good testcases make development more scalable as its much easier for others to jump in and help.
Add people before release to speed up is the worst possible think, but I add some documentation (even if I think that no one read it :). -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Josef Reidinger <jreidinger@suse.cz> [Jul 14. 2009 10:39]:
On documentation I plan work after demo release, as now I prefer good functionality. (I also plan edit skeletons to reflect current state)
Please don't slip with documentation. Having good documentation and good testcases make development more scalable as its much easier for others to jump in and help.
Add people before release to speed up is the worst possible think,
Oh, I fully agree with you here. But what if you're hit by a bus on your way home tonight ? ;-) Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Josef Reidinger wrote:
Klaus Kaempf wrote:
* Josef Reidinger <jreidinger@suse.cz> [Jul 14. 2009 10:12]:
As it set some fields of controller and uses logger from controller I think that this is good place for it. If I move it to library, then it must be some module, which is include to controller and at least need two more lines of code to include this functionality. Those two lines are fine as they make both the controller and the lib file more clearly arranged. And not all controllers need the proxy functionality.
OK, so I move it to separate lib.
On documentation I plan work after demo release, as now I prefer good functionality. (I also plan edit skeletons to reflect current state) Please don't slip with documentation. Having good documentation and good testcases make development more scalable as its much easier for others to jump in and help.
Add people before release to speed up is the worst possible think, but I add some documentation (even if I think that no one read it :).
OK, done both. Just how can I generate rdoc? (now I test it by run it myself and rake doc or rake rdoc doesn't work) -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (2)
-
Josef Reidinger -
Klaus Kaempf