The JWSCL does not need to be setup. The only setup is needed to create a binary unit file (DCU-file) for the JEDI API Headers as described here.

If finished make sure that you have added the source path of JWA to your project or general library path. After that you can also add the source path to the JWSCL source folder (…\trunk\source) to the project or general library path so all projects can easily use JWA and JWSCL.

Eventually you can start using JWA and JWSCL as simple as possible. Just add the units to your uses clause. Be aware that the order of including units may change Delphi’s behavior if an identifier with the same name is declared in several units.

  1. JwaWindows instead of Borland’s Windows unit.
  2. JwaVista for Vista enhancements. (These features may be integrated into jwaWindows one day)

Some types in these JWA units are double. JwaVista recreates and extends them to add Vista support. Example:
The new _TOKEN_INFORMATION_CLASS type from JwaVista.pas has several new additions:

  1.  
  2. _TOKEN_INFORMATION_CLASS =
  3. JwaWindows._TOKEN_INFORMATION_CLASS +
  4. (
  5. TokenElevationType
  6. TokenLinkedToken
  7. TokenElevation
  8. TokenHasRestrictions
  9. TokenAccessInformation
  10. TokenVirtualizationAllowed
  11. TokenVirtualizationEnabled
  12. TokenIntegrityLevel
  13. TokenUIAccessTokenMandatoryPolicy
  14. TokenLogonSid
  15. );

However if you add JwaVista behind JwaWindows in your uses clause you will only use the types from JwaVista. Some functions in JwaWindows or other libraries that use JWA may not know these types. To get the correct type you have to explicit adress the JwaWindows type.

  1.  
  2. var fooTokenInfo : jwaWindows._TOKEN_INFORMATION_CLASS;
  3. …
  4. foo(fooTokenInfo);

JWSCL does not really need an order of its units.

Send post as PDF to www.pdf24.org
convert this post to pdf.