I'm looking at adding multilingual support to a couple of open source projects I'm working on. The solutions are already developed in CSP so I am not looking for alternative approaches.
I'm wondering what would be the best approach for CSP and separate JavaScript files.
Initially I was wondering if I should bake the default system language text at compile time, or provide the end user with a language selection option at run time.
When I add a parameter to dataCombo for loading it on runtime and the property editable set to 0, dynamically loading content for dropdown through parameter works fine.
But, when I set editable to 1, to implement user search in dataCombo, loading through parameter is not working, it is loaded all rows, but I need loading on some parameter. It don't see the parameter, when editable is 1.
Is it normal behavior of dataCombo? But how about user search in dataCombo on this case? When editable is 0, we can't enter any character in dataCombo.
Hi world, i work actually on an intersystems project , my question is :
i've my Rest class that receive an HTTP request from a client side , i want to know how extract data from this http request , for example : date , id_client and measures taken by the client ( i need to extract a weight value catched from a connected scale to my smart phone via bluetooth ) .
a.k.a.. "The World of Widgets Returns!" or "Paternity leave damages Instructional Series momentum"
In our last lesson, we combined 2 separate classes to appear as the same property. We now have the ability to Update our Widget catalog, but what if we want to Create a Widget? Thankfully, we've already done 90% of what we need, just by implementing Edits
I have a <tablePane> element with OnCreateResultSet and OnExecuteResultSet methods; autoExecute is "false" but the OnCreateResultSet and OnExecuteResultSet methods are nevertheless called on page load.
I want the user to be able to press a button to submit the parameters, then have this button call tablePane.executeQuery() to execute the query.
autoExecute is simply igonored. We're on 2014.1.3 with plans to upgrade to 2016 soon.
Are there more settings I need to set? Or is this attribute simply ignored?
Caché Version String: Cache for UNIX (Red Hat Enterprise Linux for x86-64) 2016.2.1
We have a mirrored Ensemble system (110, backup and 210, primary). At one time (14:00) there is a disruption in the production. The messages are not being processed.
Twilio is a great tool for programmatically initiating and managing phone calls. In this example we'll go over basic account setup, create a Cache Class to manage our interaction with the Twilio API, and initiate a phone call from the Cache Terminal.
The full Class used in this example is available on GitHub as well.
the ODBC driver is truncating the string to 50 characters.
If I run this same command with $system.SQL.Shell(), this doesn't occur. I did a test creating several parameters for COSClass_Methode, and they all have a 50 character limitation.
I wanted to share a little tidbit which is in the Studio documentation (http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls?...) but many people who have been using the InterSystems Studio for a long time missed the addition of this *very* useful feature, and every time I mention this to an audience I see at least one face light up because of how excited they are to learn about it!
Within Studio, the Output pane (View -> Output) is actually misnamed. It is actually an Input/Output window which can be used to run Caché ObjectScript commands!
I accidently clicked the mouse into the output window of studio (where you get the compile results etc) and typed soemthing in there (by mistake) and it came back with <SYNTAX>.
I've been playing with it further, and it's like a cut down version of terminal.
I can "s x=1" and the "w x" and sure enough, it will display "1" (ie the value of x)
when I call one of my utilities ie "d ^dev", my utility runs as expected, but when I try entering a value (my utility was waiting on a read *x) it generated a <SYNTAX> error.
In my previous posting about the new support in QEWD for JSON Web Token (JWT) support, I mentioned that it was a key step in enabling Micro-Service support in QEWD. In this post I'll give some background to how they work and the thinking behind them.
If you haven't heard about Micro-Services and/or want to learn more, there's lots of information available if you do a Google Search. Here's a good starting point:
Hello, I just noticed that the following query is not allowing when using cached queries.
The compiler will accuse the code about missing a closing quote. Just so you know, if I use this query dynamically it works, so I guess it's related to the code linting.
When I go through the Atelier Cheat Sheet on the connection configuration, it talks about an Eclipse master password and asks for two hints to remember the master password. However, it does not specify the master password. I can only assume the master password is the same as the Cache instance password.
Can anyone shed some light on this master password, where or how it is used, and any other useful information?
I am trying to capture the write of a method to test the response in an unit test. I know everything works because one of my colleagues ran the code and did not froze on his machine.
I don't what is the cause of the freeze. I know that at line Use $io::("^"_$ZNAME) it stopes because i have put some write functions after every line in WriteCapture method and i only saw the first write function in terminal
I also used debug and in this case it didn't froze
By update
XDATA is used for a whole host of ISC libraries to store things like Zen pages, BPL logic and DTL transformations.