User Answers

Hi Jude,

 

For questions like this you should use TRC https://trc.intersystems.com/ -- this is likely related to your environment setup which shouldn't be shared publicly and there are not many Trak people on the Developer community anyway.

 

Cheers

Sergei

One thing to consider is that Community Edition has a restriction on how many additional namespaces and databases you can have (and that's exactly zero). So while it may be nice to be able to have 3rd party tool in it's own database, it would also be nice to be able to use it from within USER and %SYS.

  • The easiest to start and learn and run samples and look around is Studio since it already comes with Cache pre-installed and you don't need to install or configure anything else.
  • Once you are ready to start with your project, switch to Atelier since it comes with integrated Source Control which is essential for project development.

Did you check GetCPUTime() method of that class?

I believe it's enough to have [Final] keyword set in deployed mode to give a developer a hint that this class should not be extended.

If you want to enforce this behaviour, I would add a check into each method as a first line , something like

if $this.%ClassName(1)'="My.Class" quit $$$ERROR(50000,"don't extend this class")

Since all code will be deployed, developers will not be able to remove this check easily.

I would add support for both strings and streams, similar to what we have for other interchange formats (XML, JSON etc). This is pretty much what their reference implementation on the website does as well. Since this is a binary format, you need to be careful with character encoding.

Looks like you are trying to get your property from Collection instead of object itself. You likely forgot to call .GetAt(i) method before referencing .value.

Hi Nael,

 

I'd suggest to "print" from IE to PDF first, using CutePDF as a default printer, and then use Adobe Reader or similar tool to print to printer. That should require less scripting of IE and more manageable solution overall.

 

Regards

Sergei

You should definitely store your storage schema in VCS. When you first compile and install your solution into an environment, it doesn't really matter -- as you said, storage will be generated automatically during compilation. However, this will cause major issues when you'll have to upgrade your environment to a newer version of your class and keep the data.

If you had a class definition in Version 1 of your system with properties Address, Zipcode your storage schema will look like

node=$LB($ClassName,Address,Zipcode)