All Answers

The setup needs access to the downloadable files that can be downloaded only with a connection. In any case, the server doesn’t need the full setup. The setup is only needed to install the project templates, toolbox items, and designer assemblies in the GAC. The installer cannot update the deployment assemblies since they should be in the /bin directory and the installer doesn’t register them with the GAC.

The server only needs the deployment which includes at least two Wisej assemblies. See https://docs.wisej.com/deployment/. It also needs the wisej-server.lic file that can only be generated with an internet connection using your development machine. Once it’s generated it’s part of the application and can be deployed along with the app to a server without access to the internet. To generate the server lic file, simply run the app once on the connected development machine.

HTH

Best,

Luca

Hi Alex,

That was a problem with the active color in Classic-2.

All system labels in Wisej are always localized in all languages. Wisej selects the localization for each client in this order:

– the language forced in the url by adding ?lang=el (i.e. for Greek)
– the language forced in the applications json file https://docs.wisej.com/docs/concepts/configuration (see the culture setting)
– last, the preferred language reported by the client’s browser.

We are going to publish soon an integrated extension control using the full calendar library: http://fullcalendar.io/. It works with Wisej’s data store (similar to the data grid) requesting only the visible pages and supporting a large number of records. The control itself supports dragging, extending, full day, custom rendering, colors, etc. It’s extremely flexible and perfectly integrated with Wisej’s object model.

Best,

Luca

Please update Concepts – Configuration accordingly.

It’s already available using

Application.Theme see the definition of the ClientTheme class.

You can read just about any value from the theme and resolve the indirections (colors, fonts and images):

// Read the height of the caption bar.
var titleHeight = Application.Theme.GetProperty<int>("window/captionbar", "height");

// Translate a color.
var color = Application.Theme.GetColor("windowText");

// Read and translate the button's hovered back color.
var color = Application.Theme.GetColor("button", "textColor", "pressed");

Notice that the appearance path requires a forward slash.

The last optional argument is the state name. The default is “default”. The states are mixed, so if you read “hovered” if you get the values inherited from “default” and overridden or added by “hovered”.

I  noticed a problem though with the public GetColor(), GetFont() and GetImage(), they only read from properties and not from styles. If you need to read a style value for now use GetStyle() and the resolve it using GetColor(), Font, Image. And also the public GetImage() always returns null. That’s WJ-7568.

If it worked, GetImage() returns an actual System.Drawing.Image from the url or the base64 png or gif – but NOT from the svg images. The svg renderer is plugged in only at design time.

Best,,

Luca

Hi Ewan,

The themes in the Documents folder are copied for the Theme Builder. To deploy a theme you have to copy it in the \Themes directory in your app.

You can change the default theme in the json config file for a specific app, or set the theme as the default in in web.config, or change it at runtime using Application.LoadTheme(name). The name is always just the name – no path and no extension.

You can find the configuration description here:

https://docs.wisej.com/docs/concepts/configuration

And a detailed description of the theme system here:

https://docs.wisej.com/theme-builder/

Best,

Luca

Hi Mariano,

thanks for your interest in Wisej.

Yes, it´s possible and already used for some of our and beta users applications (on Microsoft Azure).

For more details about deployment, please also take a look at the deployment chapter in our documentation:

https://wisej.com/docs/html/Deployment.htm

Hope that helps.

Best regards
Frank

Hi Andrew,

The hotKey is F7,

or with C#

Application.ShowConsole = true;

And for logging Wisej use http://qooxdoo.org/qxl.apiviewer/latest/#qx.log.Logger

test case:

Application.Eval("Wisej.Core.log('info','cooool-124');"); // you can use "info", "warn", "error", "debug" OR
Application.Eval("Wisej.Core.logWarning('cooool-warning');");
Application.Eval("Wisej.Core.logInfo('cooool-info');");
Application.Eval("Wisej.Core.logError('cooool-error');");
Application.Eval("Wisej.Core.logDebug('cooool-logDebug');");

Happy coding,

Kevin (ITG)

Hi Page,

this was logged as #2834 and is fixed in Wisej release 2.5.23

Best regards
Frank