#19 Remove TAppDictionary

[Vidar Hasfjord]

If I am not mistaken this component was only needed for Win16. No that we no longer support 16-bit we should remove it unless it has some other purpose. If so, that should be better documented.

[Vidar Hasfjord]

TAppDictPidImp, the 16-bit implementation of TAppDictionary, was removed in [r748]. TAppDictionary now always uses the 32-bit implementation, TAppDictInstImp, which is practically a singleton.

TAppDictionary itself has been retained for backwards compatibility.

[Vidar Hasfjord]

I've reopened this, as the removal of TAppDictionary may be reconsidered for version 8, as part of the cleanup and removal of backwards compatibility and obsolete components.

Note that TAppDictionary was removed from Owlet in [r2193].

[Sebastian Ledesma]

TAppDictionay it's used in OCFNext wich i currently use.
Said that I still to move my big app to OWLNext 7 , so I'm still years to use OWLNext 8.

[Vidar Hasfjord]

@sebas_ledesma wrote:

TAppDictionary it's used in OCFNext

Thanks for the feedback. That's interesting. If TAppDictionary has a meaningful purpose as a dictionary in OCFNext, and hence cannot be replaced by a static application pointer accessor (e.g. TApplication::GetApplication, like I've done in Owlet [r2193]), then I guess a good solution is to move TAppDictionary to OCFNext where it is actually used purposefully.