Background |
Now that Design Studio 1.6 is available, karol.kalisz and I have taken strides to port over our existing SCN Design Studio SDK Development Community components to the new 1.6 SDK patterns that reiner.hille-doering has mentioned here: What's New in Design Studio 1.6 SDK I previously mentioned some changes in a blog post here (Sneak Peak - SCN Design Studio 1.6 SDK Components), however I am creating an SCN Document this time so that others can modify this document going forward to keep everything up to date. Why 3.0? At certain points along the way, we've had to make the decision to commit future development to a newer version of Design Studio that means no further support for older versions. With Design Studio 1.6, many new features along with SDK changes to support the new sap.m mode mean that we must make a clean break. This means that Design Studio 1.6 is a pre-requisite for anything related to our 3.0 components, just like for our 2.0 components, 1.4 was required. You can still download the older 1.0 and 2.0 components from GitHub.
| ||||||||||||||||
Source Code |
Source Code can be found on GitHub here: GitHub - org-scn-design-studio-community/sdkpackage: SDK Package of SCN Design Studio Community |
Community Components Blog List/Timeline |
Component Library & Documentation |
We can offer the overview of all components and documentation on functions.
You can find it here Component List 3.0 - SCN Design Studio Community
Besides the list of components, you can find also "Download" link and instructions how to install. It is better for you to use the ZIP installation (direct links provided above) as this allows you to store the installed ZIP locally. But, github is also having versionized ZIPs - in case your copy is lost.
What Has Changed? |
Simplified Categories
In order to try to save a little space and keep things tidy, we now have only 4 categories:
M Mode Support
With 1.6, SAP has offered up a more official support for UI5 sap.m components. As a result, existing SCN Community components that are based on sap.m will be supported first in 'M' mode, and for a time being in 'Classic' mode. As we see M mode mature hopefully in future versions, people will make the switch to 'M' mode for their apps. You will also see new SCN Community components that we not possible in 'Classic' mode before (without ugly hacks) become available now only in 'M' mode (such as Switch and Slider and more.)
Streamlined Additional Properties Sheet (APS) Nearly all components, no matter what category or original author, now support an easy to use APS that generates itself. This means consistent UI for designers, and less time spent by developers in the community to implement, as the APS generation code really takes care of it all for you. A separate technical document for community developers (old and new) will be posted with the details.
We have made many important internal code re-factorings using the RequireJS module pattern which has been an opportunity for us to make a few bug fixes along the way, as well as streamline some old code. There may be some initial bumps in the road early on with 3.0, but a goal is to re-visit existing components and FIX either bugs or incomplete features in order to make this a more reliable and appealing package for the community.
|
Questions/Comments/Feedback |
In the past, SCN comments have provided one channel to report bugs or ask for features or provides general feedback and ask questions. For general feedback and questions, please provide them here on SCN as always, but we'd encourage you to post actual feature requests and bugs on GitHub as an issue so that they can be tracked and not lost in the sea of comments. This helps you and the SCN developer community. The place to do this is here: Issues · org-scn-design-studio-community/sdkpackage · GitHub Going forward look for additional new components and more reliable existing components! |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |