[wpkg-users] [Bug 42] add a time parameter

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=42


Rainer Meier <r.meier at wpkg.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |WORKSFORME




--- Comment #19 from Rainer Meier <r.meier at wpkg.org>  2008-04-05 20:06:34 ---
OK, we had quite a lot of discussions about this issue. I included a change in
WPKG now which prints some status messages to STDOUT in order to be parsed by
WPKG client. I know this is probably not the best way but I tried for about one
day to find a better one and did not succeed:

- named pipes:
In fact my preferred solution. However I did not find a way to use named pipes
from JScript in an easy and stable way without additional tools. If somebody
knows how to do it, please tell me!

- TCP sockets:
Also here I did not find a proper way to implement a TCP server where WPKG
client could read information from.

So finally I decided to use the most simple solution: STDOUT

I am going to close this discussion now. We might open a fresh one later on -
probably if somebody has some more concrete solutions and if WPKG client is
about to be enhanced.

Relevant changes from 1.1.0-M3:

NEW: Added /sendStatus flag and 'sendStatus' configuration parameter in
     config.xml. The parameter allows to enable printing of status information
     to STDOUT in order to be parsed by the calling program (e.g. WPKG client).
     This allows the calling program to display some status messages about the
     synchronization process.
     The status update might not be very linear depending on the package sizes
     but at least it allows to display the start time (and therefore also
     elapsed time to the user. So the user can see at least how many percent of
     packages have been synchronized already and for how long the current task
     is running currently.
     Users usually feel much less annoyed when waiting for a task to be
     finished if there are at least some screen updates and a kind of progress
     bar which is updating from time to time.
     Note: STDOUT was chosen due to the fact that I was unable to find a way to
     write to named pipes from JScript yet. However the implementation could
     easily be adapted to pipes or sockets.
     I also updated wrapper.js to read STDOUT of the called wpkg.js and print
     it to its own STDOUT. This required if WPKG client is going to read the
     output of wpkg.js, in that case output needs to be "chained" to be
     forwarded to the GUI.


For more information see Bug 95.


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.