go to post Evgeny Shvarov · Jul 13, 2018 Actually the voting has already resulted into the coming webinar. See the announcement )
go to post Evgeny Shvarov · Jul 2, 2018 Thanks, Oleg!But it's not about to map DeepSee globals, though this is helpful. Do you want to provide more details on this repository? Why map and what are the globals?
go to post Evgeny Shvarov · Jun 27, 2018 Que bueno! :)But I would be happy even if you suggest the way how to contribute to your solution to introduce an another language support.
go to post Evgeny Shvarov · Jun 27, 2018 Here are slides for @Evgeny Shvarov session "Printing and Emailing InterSystems DeepSee Reports"
go to post Evgeny Shvarov · Jun 27, 2018 Hi, Francisco!Great stuff!Could it be possible to add other languages support to your solution? E.g. Russian?
go to post Evgeny Shvarov · Jun 21, 2018 Hi, Lucas!I don't know the answer, but you could check Class Explorer and maybe implement same visualisation library to visualise production interconnections.Another example of classes visualisation is Callsmap by @Oleg Dmitrovich
go to post Evgeny Shvarov · Jun 21, 2018 Hi, Shameer!As @Nicole Aaron mentioned, there is no officially proposed folder structure for your InterSystems project, but I can share one typical approach.The upper folder is basically named "src" assuming source code inside.Files inside "src" could be splitted by source type. E.g.:"cls" - for ObjectScript classes,"inc" - for include files,"mac" - for mac routines,"dfi" - for DeepSee dashboards and pivots.Every class name consists of package(s) and class itself. So class package could be projected to a folder. E.g. source code for the class Sample.Person will be stored in the file with following path:/src/cls/Sample/Person.clsThere are numerous projects on Github which use similar approach. You can find examples of such projects via these cacheobjectscript-udl tag, e.g. this project.HTH
go to post Evgeny Shvarov · Jun 19, 2018 Thank you, Lucas. But the thanks should go to @Oleg DmitrovichAs for CSP - it is a file, and can be edited via VS-Code just as a file in a versioned folder.If you are looking for exporting tools, I can recommend isc-dev module, which can export code as single files in a dedicated folder structure (including DeepSee stuff), can export a single kits - large xml kits, say releases, and also patches which a commit, or a set of commits in git.
go to post Evgeny Shvarov · Jun 19, 2018 Hi, Lucas!Why do you need to export CSP? Couldn't you edit CSP just in place?If you want a particular feature to be introduced, please put the issue here.BTW: 1,400 downloads: not a bad number!
go to post Evgeny Shvarov · Jun 19, 2018 Hi Francisco! Maybe, if we see a lot of requests on it. Your vote is counted!
go to post Evgeny Shvarov · Jun 19, 2018 Hi Minsu!We didn't plan that for this time. But there will be recording we'll publish on InterSystems Developers YouTube Channel.
go to post Evgeny Shvarov · Jun 17, 2018 Hi, Community!You can apply your enhancement requests to DC in this repository.And you can monitor the progress in this kanban projects. E.g. here is the June 2018 project.
go to post Evgeny Shvarov · Jun 15, 2018 We can. Request it in InterSystems Brazil office and we'll arrange it.
go to post Evgeny Shvarov · Jun 15, 2018 Could you please share a sample code with ordering of the main grouping to understand the problem better?
