go to post Evgeny Shvarov · Jun 28, 2017 Hi, Kishan!Yes, you don't need DeepSee to develop solutions with iKnow.And also you can make solutions which combine iKnow and DeepSee.
go to post Evgeny Shvarov · Jun 26, 2017 Hi, Jeffrey!Would you please provide the link to the deleted post?Last week we had two spam posts and these posts were unpublished.
go to post Evgeny Shvarov · Jun 26, 2017 Mike!I've checked comments and answers order - it seems they work well e.g. in this your post.Please comment if you have any issues with it.
go to post Evgeny Shvarov · Jun 25, 2017 Hi, Mike!Thanks for the feedback. I agree, it's a mess now. This would be fixed.The idea how to fix:Accepted answer would be on top (if any).All the rest answers would be sorted by date asc order.Comments would be sorted in asc order.
go to post Evgeny Shvarov · Jun 22, 2017 Hi, Fred! I'm using the following: do $System.OBJ.ImportDir("/your/dirfor/source","*.xml;*.cls;*.mac;*.int;*.inc;*.dfi","ck",,1) It will import and compile COS code either in XML or in UDL (cls) format.
go to post Evgeny Shvarov · Jun 22, 2017 Hi, Pete!Thanks for the feedback! We would investigate that.
go to post Evgeny Shvarov · Jun 20, 2017 Hi, Rubens!Thank you for the wide answer, very interesting.I agree with you on "no subfolders for routines" and separate folder for server-side code. May I wonder what are you using as IDE (Studio? Atelier? Something else?) and how do you import/export your code with Caché.
go to post Evgeny Shvarov · Jun 20, 2017 There was an issue with unclosed tags in the post. Now it is fixed and I think the bug solved too.
go to post Evgeny Shvarov · Jun 20, 2017 For the case of Github, I think one file per one program/class would be the better approach. You can use Atelier, like [@Amir Samary] mentioned. And in case you have no Atelier I can recommend also this very simple util: cache-udl Setup the folder with: d ##class(sc.code).workdir("your/workdir") And export everything in a namespace with: d ##class(sc.code).export() For import use: d ##class(sc.code).import() to import all, or: d ##class(sc.code).importUpdated() for the recently updated files. And yes, it exports in UDL. I think for Github UDL is more suitable. May I ask you, why do you need XML for your code files?
go to post Evgeny Shvarov · Jun 20, 2017 Just add *.INT into the list var: s list="MyPackage*.INC,MyPackage*.CLS,Folder*.DFI,*.INT"
go to post Evgeny Shvarov · Jun 18, 2017 You can use $System.OBJ.Export() for it. For every project where I need it I have a project cheatsheet file, where I have: s list="MyPackage*.INC,MyPackage*.CLS,Folder*.DFI" D $System.OBJ.Export(list,"release"_$tr($zd($h,3),"-","")_".xml") So when I need to export the whole project into importable xml file I call these two lines in terminal.
go to post Evgeny Shvarov · Jun 16, 2017 We can change the email in Global Masters to make it compatible with DC to let us count points in GM for your DC contributions. Would it work?
go to post Evgeny Shvarov · Jun 15, 2017 At least you can have the benefits of Caché Web terminal itself: Code completion (methods, classes, properties, etc), code highlighting, nice SQL shell, endless history, etc.
go to post Evgeny Shvarov · Jun 15, 2017 I think it would be a great thing. So in case you have open ssh port, you would be able to work in a handy, good looking, fool functional terminal with class code completion, code highlighting and SQL shell.Definitely, makes sense to me.
go to post Evgeny Shvarov · Jun 14, 2017 Hi, Francisco!I'm not sure we can modify the email.But you can register as a new member with another email. Would it work for you?
