I didn't actually test it on a phone/tablet, just resized browser window. Maybe it's OK on mobile devices.

Evgeny, your link still points to localhost for some reason...

I know it's not too difficult, just thought maybe there is an API call we can use which will do the job for us.

There are few concerns, like conversions you mentioned, duplicate properties, query order nodes, etc.

For example for string http://www.intersys.com/main.csp?a=b&QUERY=abc&QUERY=xyz data array would be

data("QUERY",1)="abc"
data("QUERY",1,"O")=2
data("QUERY",2)="xyz"
data("QUERY",2,"O")=3
data("a",1)="b"
data("a",1,"O")=1

Can you try IgnoreErrors="""5202,5373"""

Still looks like a bug -- probably worth reporting somewhere... On the other hand it will probably break current solution once fixed.

I believe that would be equal to just 

if number\1=number

But 

if  +number=number,number\1=+number

doesn't allow leading zeroes either.

+1 for this. Your app could be under proxy, firewall, load balancer, on a multi-site host, and usually "default" machine name would be some networking guy's favourite cartoon character or not configured at all, rather than your app domain name anyways. 

Just have it as a config option.

You write it on a card and place it into backlog bucket based on priority

Hi Ed,

I prefer to have real-time real-world discussion near the whiteboard to leaving comments in issue tracker.

discussion about implementation strategy

You do a whiteboard discussion and write results into your Wiki/Confluence where it's easy to find it. Then you have a code review tool to make sure you implemented it correctly

references to other issues

Don't need this

cross-references to commits

Also don't need this, just write meaningful commit messages

test hints

Talk to tester

start/due dates & time spent

I usually write date the card was created in the corner to track how old it is. Then place it in the backlog based on its urgency. Don't need anything else.

milestones

You can organise your backlog into milestones.

current status

Sprint status is obvious by looking at whiteboard. For more high-level status use wiki/confluence and update it once in a while manually.

assigned person(s)

It's either written on the card or there are "person buckets" on the whiteboard. I usually don't assign issues to people until they start working on them - so if we have capacity for 20 dev days in a sprint there will be few unassigned cards on a whiteboard and people assign themselves once they pick their next card

Issues help to collect all this information and make it available later

It's a bit scary at first to just throw away all completed issues at the end of the sprint, but in reality there's nothing wrong with it. Most of this information is available via source control, and there are not many use cases where you would need to look up an old issue to have some info that's not in source control anyway.

Actually you can do similar thing (remove source code): http://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GOBJ_classes#GOBJ_deploy_classes

This will also cover use of containers for development environments

Please find slides for my presentation here https://www.slideshare.net/secret/bnUsuAWXsZCKrp (Modern Development Environment)

Please find repository here https://github.com/logist/wduk18 - you will need to load your own IRIS container and change "FROM" statement in Dockerfile - see http://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=AFL_containers_deploy_repo for instructions. You'll also need license key because REST service will not work without it.

Also don't forget to change docker storage driver if you want to run examples http://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=ADOCK_additional_driver

Good one!

You can actually use 10e21 in COS code, it's a valid number format.

I'm glad you found the solution, though still not sure about its usefulness :)

You can use $zu function directly with third parameter

$ZU(171,1) returns CPU time (in milliseconds) on any OS, as a string in format SYS_time,USER_time $ZU(171,1,pid) returns total CPU time (system + user) for process pid.

However this will return CPU time -- the time CPU was actually serving the process, not the time since process was started (when process is idle, this counter does not increase). Eduard's solution would be better if you need the total time.

OK now I'm curious where it was originally posted! :)

In that case I think it would be nice to have several ways to distribute a project:

• "compiled" / "binary" version in form of IRIS.DAT which can be added to IRIS instance as a database and then either used in separate namespace or mapped into an existing one or %All, with clear instructions on naming conventions and how to use
• "source" which can be imported into new or existing namespace and then changed (gitHub profile is enough for this type of distribution)
• for a standalone type of tool, a Docker image which can be easily run or used as a sample/demo