Ask for help related to our Calendar 2.x version


Post by philipp.froebel »

Hi,

i testing the integration of brynthum calendar in a ExtjS6.6.0 application.

The sencha cmd build for testing and production faild with the fowlling error if the bryntum-calendar package is required in app.json.
----
[ERR] loading page file:///Users/pfroebel/bin/Sencha/Cmd/6.6.0.13/ant/build/slicer/theme.html?_baseDir=%2FUsers%2Fpfroebel%2FWork%2Fgit%2Ffrn-calendar%2Fbuild%2Ftemp%2Ftesting%2FFrnCalendar%2Fslicer-temp
setting base href to : file:///Users/pfroebel/Work/git/frn-calendar/build/temp/testing/FrnCalendar/slicer-temp/
registering ready listener...
== Unhandled Error ==
ReferenceError: Can'''t find variable: Set

  undefined:984
  :625 in s
  :625
  :640
  :625 in s
  :625
  :1962
  :625 in s
  :625 in e
  :625
  :625
  :625

[ERR] 
[ERR] BUILD FAILED
[ERR] com.sencha.exceptions.ExProcess: phantomjs process exited with code 2
[ERR]   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMetho
[ERR] dAccessorImpl.java:62)
[ERR] 
[ERR] Total time: 24 seconds
----
Without the bryntum-calendar package the cmd build dont faild.

Regrads
Philipp
Attachments
sencha-error-20200306.log
(63.85 KiB) Downloaded 104 times

Post by mats »

Currently Calendar supports 6.7.0 and 7.0. You can find supported versions in our changelog: http://bryntum.com/products/calendar-for-extjs/changelog

Tired of debugging javascript errors in web applications? Try our powerful error logging service RootCause


Post by philipp.froebel »

hi mats,

thanks for the very fast reply.

with Ext 6.7.0.210 and cmd v6.7.0.63 the build error is still available

see the sencha error log

regrads
philipp
Attachments
sencha-error-20200306.log
(63.75 KiB) Downloaded 126 times

Post by mats »

Ok please upload a zip file with your environment and we'll see what's wrong.

Tired of debugging javascript errors in web applications? Try our powerful error logging service RootCause


Post by philipp.froebel »

hi mats,

her is my environment (frn-calendar.zip)

cp or link Extjs to /ext and run sencha app build -test or -prod

can you have also a look on the day view and week view, it looks so the views not correctly renderd in dev build

regrads
philipp
Attachments
weekView.png
weekView.png (45.03 KiB) Viewed 3717 times
frn-calendar.zip
(1.21 MiB) Downloaded 136 times

Post by pmiklashevich »

Hello,

You included wrong css file. Please check out this guide: https://www.bryntum.com/docs/calendar-for-extjs/#!/guide/sencha_cmd
In case of trial, you need to include cal-triton-all-debug.css. You can find this file in the distribution:
- calendar-2.0.6-trial/resources/css/ext/cal-triton-all-debug.css (if you're using Ext 6.x);
- calendar-2.0.6-trial/resources/css/ext7/cal-triton-all-debug.css (if you're using Ext 6.x);

If you copy corresponding file to the /resources/ folder in your application with the same folder structure, the code in app.json might look like:
    "css": [
        {
            // this entry uses an ant variable that is the calculated
            // value of the generated output css file for the app,
            // defined in .sencha/app/defaults.properties
            "path": "${build.out.css.path}",
            "bundle": true,
            "exclude": ["fashion"]
        },
        {
            "path": "resources/css/ext/cal-triton-all-debug.css",
            "bundle": true
        },
Best regards,
Pavel

P.S. Please note, when you have a license themes are available, so you can define application theme instead of having css file included.
Pavel Miklashevich - Core Developer

Post by philipp.froebel »

Hi Pavel,

thanks for your help now everything works fine. the case "Using trial version with Sencha Cmd" i never saw it :-) - sorry for wasting your time.

Our product owner are testing the calendar right now. With whom can we talk about the right license?

Best regards,
Philipp

Post by mats »

Great to hear you are unblocked! Please contact sales [at] bryntum . com for license questions.

Tired of debugging javascript errors in web applications? Try our powerful error logging service RootCause


Post Reply