Personal and Collaborative Productivity...
...the Best of Both Worlds !
When you use the 4D Job Wallet component with 4D Server you can still operate according to your own priorities without impacting other users.
By default, wallet-based code views are local to the workstation and support the full range of features including method calls & caller inspectors, grouping and library creation.
With a single command, local wallets are shared network-wide where they continue to enjoy a richly-featured existence accessible to all developers.
Client views are synced in realtime with default propagation set, while all functions are supported including coding notes, centrally managed logs and library import/export.
A Well Behaved Guest
The component impacts minimally on your operating priorities when deployed with Team Developer. For example, a choice of propagation modes lets you enjoy an optimal performance/footprint balance according to your needs. Network assets are managed in the background without needing access to your data file, plugins, or support from the host structure.
Complex hierarchical code views are transparently managed so that integrity is always maintained - even if conflicting updates are submitted simultaneously from disparate workstations. This allows multiple users to work on the same wallet view in realtime as if it were on their own workstation.
You can even work with realtime propagation disabled if required since the server daemon can resolve conflicts retrospectively, no matter how many updates other users made since the last local refresh !
Universal and Portable
All the new multi-user features are bundled into a single version of the component which configures itself automatically according to standalone or client-server environment.
Likeways, 4D Job Wallet's home folder is compatible with both 4D standalone and server. This means you can move your entire structure folder - including component and 4D Job Wallet based code views - seamlessly between desktop and server without loss of continuity.
In network mode, 4D Job Wallet optimally capitalises on all resources to deliver as much shared advantage as possible.
For example specialised tasks that are processing-intensive (such as dependency parsing) may be performed on the client which first requests them but their results are then cached and made centrally available to all workstations for an instantaneous response to later requests.