Difference between revisions of "TODO list"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
m (→‎WPKG Client)
m (→‎WPKG Client)
Line 15: Line 15:
  
 
== WPKG Client ==
 
== WPKG Client ==
−
* add support for 64 bit Windows systems - see http://bugzilla.wpkg.org/show_bug.cgi?id=93
 
  
−
* make WPKG Client window fit on 640x480 screen resolution - see http://bugzilla.wpkg.org/show_bug.cgi?id=90
+
=== Important ===
  
−
* restarting the service locally from within the wpkginst.exe
+
* These two may have something in common - generally, offline mode sucks:
 +
** sometimes offline mode doesn't detect disconnection properly, i.e., when used in VMware (or: it detects disconnection, but logon delay still waits full time)
 +
** on some laptops, WPKG stalls on the first "pre" task. These machines disconnect the network card when running on a battery; however, WPKG hangs even if it's not running on a battery - probably the driver puts the network card in a disconnected state on bootup, and enables it later - this confuses WPKG service.
  
−
* restarting the service on remote machines from within the wpkginst.exe
+
* some laptops have only wireless connections which is enabled much later. Wait until a network connection is available - what to do with the logon delay then?
 +
 
 +
 
 +
* upgrading WPKG Client from WPKG Client is not that easy (file in use, can't upgrade myself!)
  
−
* possibility to enable more debugging:
 
−
** how long each part executed (-pre, -post, wpkg.js etc.)
 
−
** exit code of each part
 
−
** possibility to log into a file
 
  
 
* some more integration with wpkg.js: wpkg.js should be able to pass information to WPKG Client:
 
* some more integration with wpkg.js: wpkg.js should be able to pass information to WPKG Client:
−
** start selected installers with GUI (some installers break if not started with a GUI) - seems to be very complicated, and wpkg.js was already started in the background - not sure if anyone needs it
+
** start selected installers with GUI (some installers break if not started with a GUI) - seems to be very complicated, and wpkg.js was already started in the background - not sure if anyone needs it - probably we don't need this one at all
 
** parse output of wpkg.js (STDOUT) and display programs which are being installed
 
** parse output of wpkg.js (STDOUT) and display programs which are being installed
  
−
* testing setting: providing "user" for a network path doesn't work; one needs to add DOMAIN\user or WORKGROUP\user. "Test" button will say that the settings are correct even when we don't specify DOMAIN\ or WORKGROUP\ though (probably, because that path is already mapped by Windows? need to check it)
 
  
−
* add /help and /? switches to wpkginst.exe - it's not a CLI app, so probably it would be quite hard - http://bugzilla.wpkg.org/show_bug.cgi?id=101
 
  
−
* These two may have something in common - generally, offline mode sucks:
+
=== Useful ===
−
** sometimes offline mode doesn't detect disconnection properly, i.e., when used in VMware (or: it detects disconnection, but logon delay still waits full time)
+
−
** on some laptops, WPKG stalls on the first "pre" task. These machines disconnect the network card when running on a battery; however, WPKG hangs even if it's not running on a battery - probably the driver puts the network card in a disconnected state on bootup, and enables it later - this confuses WPKG service.
+
  
−
* some laptops have only wireless connections which is enabled much later. Wait until a network connection is available - what to do with the logon delay then?
+
* testing setting: providing "user" for a network path doesn't work; one needs to add DOMAIN\user or WORKGROUP\user. "Test" button will say that the settings are correct even when we don't specify DOMAIN\ or WORKGROUP\ though (probably, because that path is already mapped by Windows? need to check it)
 +
 
 +
* make possible to prevent a reboot or shutdown (i.e., we have a package which installs for 1 hour; when user restarts or shutdown, it only logs him out, installation continues, description/progress window is shown, and machine only shutdowns/reboots when everything is done)
  
 
* make possible to execute everything on machine shutdown - with the same description/progress window as with logon delay
 
* make possible to execute everything on machine shutdown - with the same description/progress window as with logon delay
  
−
* make possible to prevent a reboot or shutdown (i.e., we have a package which installs for 1 hour; when user restarts or shutdown, it only logs him out, installation continues, description/progress window is shown, and machine only shutdowns/reboots when everything is done)
 
  
−
* upgrading WPKG Client from WPKG Client is not that easy (file in use, can't upgrade myself!)
 
  
−
* command line tool for creating a crypted password (both Windows and UNIX version) - see http://lists.wpkg.org/pipermail/wpkg-users/2008-April/003213.html for example code
+
=== Boring / easy, but useful ===
 +
 
 +
* add support for 64 bit Windows systems - see http://bugzilla.wpkg.org/show_bug.cgi?id=93
 +
 
 +
* make WPKG Client window fit on 640x480 screen resolution - see http://bugzilla.wpkg.org/show_bug.cgi?id=90
  
 
* F1 launches "help file not found", should open help website
 
* F1 launches "help file not found", should open help website
 +
 +
 +
 +
=== Do we need this? ===
 +
 +
* restarting the service locally from within the wpkginst.exe
 +
 +
* restarting the service on remote machines from within the wpkginst.exe
 +
 +
* possibility to enable more debugging:
 +
** how long each part executed (-pre, -post, wpkg.js etc.)
 +
** exit code of each part
 +
** possibility to log into a file
 +
 +
 +
* add /help and /? switches to wpkginst.exe - it's not a CLI app, so probably it would be quite hard - http://bugzilla.wpkg.org/show_bug.cgi?id=101 - display a help window would be the easiest
 +
 +
 +
=== Already done ===
 +
 +
* command line tool for creating a crypted password (both Windows and UNIX version) - see http://lists.wpkg.org/pipermail/wpkg-users/2008-April/003213.html for example code
  
 
== WPKG web interface ==
 
== WPKG web interface ==
 
[http://wpkg.linuxkidd.com WPKG web interface] currently needs a maintainer. If you're interested, please let us know both on wpkg-users@ and wpkg_web_users@ [[Support|mailing lists]].
 
[http://wpkg.linuxkidd.com WPKG web interface] currently needs a maintainer. If you're interested, please let us know both on wpkg-users@ and wpkg_web_users@ [[Support|mailing lists]].

Revision as of 15:48, 29 April 2008

WPKG roadmap for 2008

If you have new ideas - please discuss it on the mailing list first.


Fixing existing bugs or feature requests

Fix bugs listed in Bugzilla: http://bugzilla.wpkg.org. Some of the bugs are ideas really, so please feel free to comment on them (or vote for them etc.).


Documentation

Write a proper documentation manual. Right now, documentation is in tiny little bits (different functionalities described on different pages). It isn't necessarily bad - but it isn't very friendly to new users.

New documentation should be an A to Z WPKG manual, with chapters, subchapters etc.


WPKG Client

Important

  • These two may have something in common - generally, offline mode sucks:
    • sometimes offline mode doesn't detect disconnection properly, i.e., when used in VMware (or: it detects disconnection, but logon delay still waits full time)
    • on some laptops, WPKG stalls on the first "pre" task. These machines disconnect the network card when running on a battery; however, WPKG hangs even if it's not running on a battery - probably the driver puts the network card in a disconnected state on bootup, and enables it later - this confuses WPKG service.
  • some laptops have only wireless connections which is enabled much later. Wait until a network connection is available - what to do with the logon delay then?


  • upgrading WPKG Client from WPKG Client is not that easy (file in use, can't upgrade myself!)


  • some more integration with wpkg.js: wpkg.js should be able to pass information to WPKG Client:
    • start selected installers with GUI (some installers break if not started with a GUI) - seems to be very complicated, and wpkg.js was already started in the background - not sure if anyone needs it - probably we don't need this one at all
    • parse output of wpkg.js (STDOUT) and display programs which are being installed


Useful

  • testing setting: providing "user" for a network path doesn't work; one needs to add DOMAIN\user or WORKGROUP\user. "Test" button will say that the settings are correct even when we don't specify DOMAIN\ or WORKGROUP\ though (probably, because that path is already mapped by Windows? need to check it)
  • make possible to prevent a reboot or shutdown (i.e., we have a package which installs for 1 hour; when user restarts or shutdown, it only logs him out, installation continues, description/progress window is shown, and machine only shutdowns/reboots when everything is done)
  • make possible to execute everything on machine shutdown - with the same description/progress window as with logon delay


Boring / easy, but useful

  • F1 launches "help file not found", should open help website


Do we need this?

  • restarting the service locally from within the wpkginst.exe
  • restarting the service on remote machines from within the wpkginst.exe
  • possibility to enable more debugging:
    • how long each part executed (-pre, -post, wpkg.js etc.)
    • exit code of each part
    • possibility to log into a file



Already done

WPKG web interface

WPKG web interface currently needs a maintainer. If you're interested, please let us know both on wpkg-users@ and wpkg_web_users@ mailing lists.

Retrieved from "https://wpkg.org/index.php?title=TODO_list&oldid=5734"