Community
Participate
Working Groups
Our current toolkit documentation for iOS is pretty fragmented (some parts can be found in the reference, some other in the user manual) and thereby - unstructured: it's hard to find information about supported components and how they fit into our abstracted component system (e.g. swipe capabilities - the manual only says "many" components support this) - I'd expected these information in the reference manual (instead they can be found in the user manual) - heterogeneous in terminology: e.g. "(iOS) Tab Components" are derived from "Tabbed Components". - incomplete: e.g. I couldn't find any information about the newly added action for checking a badge count [1] - lacks of understandable images to categorize components by sight into our supported (and abstracted) view of components I assume that this is also the case for other toolkits (like the win / winapps or even JavaFX). [1] https://jubula.atlassian.net/browse/JUB-409
We have plans to redesign the setup of the reference manual and to move the information from the user manual to there.
We have dropped support for the iOS Toolkit