go to post Evgeny Shvarov · May 4 Is it very complex to develop a new DICOM adapter that will use global streams instead?
go to post Evgeny Shvarov · Apr 28 Thank you very much, @Enrico Parisi ! This looks like what I was looking for! It is also looks as a perfect new generation for the deprecated %ZEN with: set sc=##class(%ZEN.Auxiliary.jsonSQLProvider).%WriteJSONFromSQL(,sql) Which only provides string, but not %DynamicArray so will not work for Spec First REST API.
go to post Evgeny Shvarov · Apr 28 @Arun Nadarasa - thank you for introducing the power of Lovable in Digital Health to many-many people! Including myself ;)
go to post Evgeny Shvarov · Apr 28 I can call after-install scripts, of course! Now this makes sense! The only question - is it OK? :) It looks a little ... dangerous?
go to post Evgeny Shvarov · Apr 28 Thanks, Enrico! Namespace, of course! I prefer usualy the simplicity of having one Database in one Namespace if possible. Your great answer doesn't answer though my question. The situation is: I deploy a package, which contains: persistent class(es), data(generated ok, but could be different), WebApp (aka CSP app). I deploy a Role also, which will be used by the WebApp. Role need the access to database... Here is my question, which database resource do I provide to the role as I don't know the namespace the package will be installed by a potential user?
go to post Evgeny Shvarov · Apr 26 HI @Touggourt ! You can start e.g. from this template . So you can clone or use as a template this github repo. When IRIS starts in this it is prepared to work with Python in any supported modes. Here is the related article.
go to post Evgeny Shvarov · Apr 25 Thank you, @Ashok Kumar T ! Never used %WriteResponse() before. May I ask you to provide the full method? I shared the persistent class in the updated post.
go to post Evgeny Shvarov · Apr 24 "Let's remember this tweet" ;) I suggest we test the water in 6 month/one year. I believe all the frameworks(current or new AI-focused) will be a tool for AI to construct the frontend at least. Same for the backend. Or maybe we'll use "GPT Memory" concepts instead of relational/multi-model databases we used to work with.
go to post Evgeny Shvarov · Apr 17 Great article, @Timothy Leavitt ! I think it is questionable the recommendation not to use AI for the spheres you are not familiar with. E.g. I'm not a frontend developer at all but the AI capabilities in AI generation are awesome and give me an opportunity to immediately have an MVP in frontend and also to build prototypes fast which was impossible in a preAI times.
go to post Evgeny Shvarov · Apr 17 also, thanks to @Semion Makarov swagger ui app is updated to support Swagger 3.1 version. and functionality is improved greatly!
go to post Evgeny Shvarov · Apr 17 Great article! Thank you @Pablo Frigolett ! Also, if you develop in Docker there is an issue with server name, and my version of the same GetSpec method is: ClassMethod GetSpec() As %DynamicObject { Set spec = {}.%FromJSON(##class(%Dictionary.CompiledXData).%OpenId("dc.Sample.v2rest.spec||OpenAPI").Data) Set url = $Select(%request.Secure:"https",1:"http") _ "://"_$Get(%request.CgiEnvs("SERVER_NAME")) _ ":" _ $Get(%request.CgiEnvs("SERVER_PORT")) _ %request.Application Set spec.servers = [{"url" : (url)}] Quit spec } Thanks to @Lorenzo Scalese !
go to post Evgeny Shvarov · Apr 16 @Mario Sanchez Macias concluded the final most optimal option here.
go to post Evgeny Shvarov · Apr 12 How can we improve it - is to publish more "good" ObjectScript to Github and other open-source repositories and share best practices here :)
go to post Evgeny Shvarov · Apr 12 Hi @Anna Golitsyna ! I appreciate you watched the video. Indeed it (AI Copilot) is not that bad sometimes especially in simple cases and sometimes can even surprise like "reading thoughts" what to put next so VSCode+Copilot could be more effective in coding ObjectScript vs just Studio and occasional copy-paste from ChatGPT. But I agree with @Dmitry Maslennikov that the very fact that AI can "talk" ObjectScript/Mumps is mostly because of Open Exchange initiative and its impact on Github.com, where ObjectScript is listed as a recognizable language (thanks again to @Dmitry Maslennikov to his impact to it about 10 years ago).
