wiki:WikiStart

Version 5 (modified by martini, 7 years ago) (diff)

--

Welcome to the Workplace Shell Toolkit (wpstk)

The Workplace Shell Toolkit API encapsulates the complexity of the handling of some of the tasks being most time consuming to code.

The following major APIs of the Workplace Shell Toolkit possibly are of particular interest:

  • Settings and Details Manager
  • Extended Attributes Manager
  • Memory Mapped Files Manager
  • Text Message File (TMF) Support
  • NLS related functions
  • Process related functions
  • PM helper and PM control functions
  • Bubble Help API
  • Buildlevel Query and Set API

Check the Workplace Shell Toolkit Information page.

From here you can report bugs and view your tickets.

Binaries

See http://wpstk.netlabs.org/en/site/index.xml

Feedback and Support

If you find bugs, please create a New Ticket.

You must be logged into TRAC to create tickets. Please login with your Netlabs login id. If you do not have a login id, you can request one at http://www.netlabs.org/en/site/member/member.xml. If you have troubles acquiring a Netlabs login id send an e-mail to Netlabs Community Mailing List.

For technical support, try eCS-Technical Yahoo Group.

There used to be a support mailing list at http://groups.yahoo.com/group/wpstk-dev/, but this group seems to have gone missing.

History

Christian Langanke developed wpstk. He used some code of other authors as mentioned in the included help file. This site was created while transferring the cvs source code into svn together with xwlan. Additional benefit is the ticket system here.

Building wpstk

  • check out complete source tree from svn (trunk)
  • follow the included documentation

Screenshots

Feel free to contribute ;-)

Credits

  • Dmitriy Kuminov
  • Christian Langanke
  • Chris Wohlgemuth
  • Steven Levine
  • Michael K. Greene
  • Radim Kolar
  • Sergey I. Yevtushenko
  • Yuri Dario
  • Ulrich Moeller
  • Adrian Gschwend (running netlabs.org)
  • Andreas Buchinger set up this page in January 2013

If we forgot anyone, please let us know. It was unintentional.