Support Forum
Search found 2328 matches
Well, the only way of debugging in phantomjs is using "t.diag(message)". Tests may fail because of different rendering engine - phantomjs is using Webkit (not the latest version). In general, running tests in phantom should be equal to running them in Safari. Do you see the same failures i...
Hm.. seems if condition in `t.waitFor()` (which is used by the `t.waitForRowsVisible`) will not be fulfilled, the failure will not be reported, fixing that.
We are very glad to announce that the private beta of Siesta is now available! Documentation is available in the /docs folder of the package, and getting started manual is at /docs/#/api/Siesta. Please note, that the package is private, please do not share it in any media. Your feedback is very welc...
Below is the list of features in our roadmap - please review and let us know what's important to you! Please PM me the re-ordered list from thread, starting from most important features for you. [*] Add more examples [*] Improve the testing of asynchronous code - make tests easier to read / write. [...
Sure, thats possible with some additional effort. You will need to manually generate the "columns" config for gantt, based on your data. Same for fields in store - create a new model, subclassing the Sch.model.Event.
Not yet, the calendar is currently global and shared by all tasks/resources.
The most flexible way to customize the "system" parts of the editor will be to subclass the "Sch.plugins.EventEditor" plugin. See the DemoEditor class in the "eventeditor" example. Then you can use properties of the editor class, for example to add the additional handle...