Thanks @CleanShot! You implemented my feature request: save screenshots as WebP 🎉
Huge help for #UDINA docs and great for performance! #CleanShotX#macOS
It's so cool that @geertjanklaps#SAPCDS Launchpad plugin also supports RTA, so you can easily test your own CustomPage within #SAPFioriElements using key user adaptation in a modern clean core approach.
-> Annotation driven freestyle design
(OnStack or Side-by-side)
@geertjanklaps @mianbsp Maybe we should met and have a look together. While reverse engineering, the next thing on top of cdm is cep (central entry point) used in WorkZone as new UserExperience. Also supporting Integration Cards. But i will wait till next LTS, because each ui5 release introduces changes
It seems that SAP has integrated the cds-launchpad-plugin functionality from @geertjanklaps into #SAPBuildCode, but in a static (tools) way. The new dev-cap-tools package updates the sandbox app entry point(s) on start, but preview crashes watcher accessing .git/maintenance.lock
@geertjanklaps I think yes, because it just adds sandbox apps pre start into a local folder where index.html is copied into it. But currently still issues, see @mianbsp post. I am personally using cdm/cep bootstraping, even if not officially supported with our new #UBOTT SaaS (supporting TSX)
@mianbsp @geertjanklaps@wolf_gregor Using cds add sample doubles all apps and crashes service while starting apps. I think it needs some fixing, till all usecases will work as expected
@grahamrobbo The Fullstack Joule Tutorial also shows the problems with documentation when the Joule generator keeps generating different code and you get stuck. https://t.co/FCdLKxS9CN
Somehow I survived the last week with #SAPBuildCode, despite all the bugs and restrictions like 'System limit for watchers reached', blocked/used ports, restricted Simple Git ,… Lucky to go back to VSC next week. Best issue is, that after git init, tools crash on .git directory
@mianbsp @MustafaBensan The funniest thing was that #SAPEventMesh missed this marketing campaign and then delivered the new name at the end of February (see my update for SAP Cloud Platform Enterprise Messaging)
I needed an overview of the current #SAPDevelopmentTools. Somehow nothing fit properly or the image quality was poor. In the end, I was glad that I made my own diagram to include non-SAP relevant things.
@MustafaBensan Thanks Mustafa. SAP Build Code seems to be the new BAS. You can even update an existing plan. Also looking at the discovery services, both services share the same support component. Maybe i should add FKA BAS for code and FKA AppGuyver for app 😆
@jasper_07@mauriciolauffer Also figured it out some month ago, that new ushell extension api starts using it. I am a little bit scared, because old api never published => no ts types generated. I just a lot private props. That will be hard in the future!
The future is now! I tried to find a prompt that describes the daily work of an SAP developer with #SAPBuildCode and #SAPJoule. I think the result already describes how it feels to be a generative AI-based code developer 🧑💻
In the future I plan to document #SAPBTP relevant #SAPCloudALM scenarios for #UDINA. Currently the Cloud Connector Scenario Builder already supports required services: https://t.co/1EqoemNzt7
There was a small problem with the new #SAPCAP Visualize Deployment Descriptor function when using cds-plugin-ui5, which @pmuessig fixed yesterday with 0.11.1. THX. For "CDS: Preview as Diagram" also install extension https://t.co/PCNa53xeVo
SAP S/4HANA Public Cloud still lacks with PP functionality concerning confirmations. Today created a custom #SAPUI5 svg control, because micro charts does not fit needs. How nice (and easier) would it be if css was directly part of the custom control...
The current developments of #SAPCAP regarding #TypeScript have certainly made points of the full stack example obsolete:
- cds build takes care of @cds-models
- cds add typescript -> tsconfig.json
- mbt needs tsconfig.cdsbuild.json (see doc)
- eslint.config.mjs
- tsx instead ts
Hooray! #SAPWorkzone feature "automatic content refresh for integrated HTML5 applications after update" again shifted to Q4/2024 (initially planned for Q3/2023). This is actually a must-have and not a nice-to-have! 😉