Comments on: Ext Calendar http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/ Because I want to be like the cool kids too Fri, 03 Feb 2012 05:39:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: titreşimli vibratör http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-687 titreşimli vibratör Fri, 21 Oct 2011 17:43:00 +0000 http://kinsey.no/blog/?p=42#comment-687 yorgunluk ;) yorgunluk ;)

]]> By: Joomla extensions http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-669 Joomla extensions Thu, 13 Oct 2011 05:22:00 +0000 http://kinsey.no/blog/?p=42#comment-669 I found your posts very interesting. In fact after reading, I had to go show it to my friend and he enjoyed it as well. Thanks.    I found your posts very interesting. In fact after reading, I had to go show it to my friend and he enjoyed it as well. Thanks.   

]]> By: Jon http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-265 Jon Tue, 19 Jan 2010 23:28:57 +0000 http://kinsey.no/blog/?p=42#comment-265 I had tried that and got a 'u is null' error - debugging isn't that great with ext! This seems to happen when it enters the: ts.view = Ext.DomHelper.append(_tableContainerCell, { tag: "div", cls: "Overlay" , true); ts.view.dom.ts = ts; of the _insertTimespan function. I had tried that and got a 'u is null' error – debugging isn't that great with ext! This seems to happen when it enters the:

ts.view = Ext.DomHelper.append(_tableContainerCell, {
tag: "div",
cls: "Overlay"
, true);
ts.view.dom.ts = ts;

of the _insertTimespan function.

]]> By: Jon http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-518 Jon Tue, 19 Jan 2010 23:28:00 +0000 http://kinsey.no/blog/?p=42#comment-518 I had tried that and got a 'u is null' error - debugging isn't that great with ext! This seems to happen when it enters the: ts.view = Ext.DomHelper.append(_tableContainerCell, { tag: "div", cls: "Overlay" , true); ts.view.dom.ts = ts; of the _insertTimespan function. I had tried that and got a 'u is null' error – debugging isn't that great with ext! This seems to happen when it enters the:

ts.view = Ext.DomHelper.append(_tableContainerCell, {
tag: "div",
cls: "Overlay"
, true);
ts.view.dom.ts = ts;

of the _insertTimespan function.

]]> By: oyvindkinsey http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-264 oyvindkinsey Tue, 19 Jan 2010 22:57:14 +0000 http://kinsey.no/blog/?p=42#comment-264 Is actually right there in the comments, <pre> _cal.loadData([{Text:"sampleevent",Id:24234,StartTime:_startTime,EndTime:_endTime}]); </pre> Is actually right there in the comments,
<pre>
_cal.loadData([{Text:"sampleevent",Id:24234,StartTime:_startTime,EndTime:_endTime}]);
</pre>

]]> By: Øyvind Sean Kinsey http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-517 Øyvind Sean Kinsey Tue, 19 Jan 2010 22:57:00 +0000 http://kinsey.no/blog/?p=42#comment-517 Is actually right there in the comments, <pre> _cal.loadData([{Text:"sampleevent",Id:24234,StartTime:_startTime,EndTime:_endTime}]); </pre> Is actually right there in the comments,
<pre>
_cal.loadData([{Text:"sampleevent",Id:24234,StartTime:_startTime,EndTime:_endTime}]);
</pre>

]]> By: Jon http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-263 Jon Tue, 19 Jan 2010 22:31:20 +0000 http://kinsey.no/blog/?p=42#comment-263 How do you recommend showing existing data on start-up? I expected the following code to do so, on startup - but it is not shown when the app loads. var ts = { data: {Id: 1, StartTime: new Date('2010-01-22 11:00:00.0'), EndTime: new Date('2010-01-22 16:00:00.0')} }; _cal.insertTimespan(ts); Any suggestions? How do you recommend showing existing data on start-up?
I expected the following code to do so, on startup – but it is not shown when the app loads.

var ts = {
data: {Id: 1, StartTime: new Date('2010-01-22 11:00:00.0'), EndTime: new Date('2010-01-22 16:00:00.0')}
};

_cal.insertTimespan(ts);

Any suggestions?

]]> By: Jon http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-516 Jon Tue, 19 Jan 2010 22:31:00 +0000 http://kinsey.no/blog/?p=42#comment-516 How do you recommend showing existing data on start-up? I expected the following code to do so, on startup - but it is not shown when the app loads. var ts = { data: {Id: 1, StartTime: new Date('2010-01-22 11:00:00.0'), EndTime: new Date('2010-01-22 16:00:00.0')} }; _cal.insertTimespan(ts); Any suggestions? How do you recommend showing existing data on start-up?
I expected the following code to do so, on startup – but it is not shown when the app loads.

var ts = {
data: {Id: 1, StartTime: new Date('2010-01-22 11:00:00.0'), EndTime: new Date('2010-01-22 16:00:00.0')}
};

_cal.insertTimespan(ts);

Any suggestions?

]]> By: Øyvind Sean Kinsey http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-262 Øyvind Sean Kinsey Tue, 19 Jan 2010 08:18:50 +0000 http://kinsey.no/blog/?p=42#comment-262 Hm, I was sure it used a store, maybe I did that with a later version somewhere else.. Anywhat, it should be quite easy to extend it with a store. Just bind the deleteTimespan, updateTimespan etc to the proper events and vice-versa :) Hm, I was sure it used a store, maybe I did that with a later version somewhere else..
Anywhat, it should be quite easy to extend it with a store. Just bind the deleteTimespan, updateTimespan etc to the proper events and vice-versa :)

]]> By: Øyvind Sean Kinsey http://kinsey.no/blog/index.php/2009/02/27/ext-calendar/comment-page-1/#comment-515 Øyvind Sean Kinsey Tue, 19 Jan 2010 08:18:00 +0000 http://kinsey.no/blog/?p=42#comment-515 Hm, I was sure it used a store, maybe I did that with a later version somewhere else.. Anywhat, it should be quite easy to extend it with a store. Just bind the deleteTimespan, updateTimespan etc to the proper events and vice-versa :) Hm, I was sure it used a store, maybe I did that with a later version somewhere else..
Anywhat, it should be quite easy to extend it with a store. Just bind the deleteTimespan, updateTimespan etc to the proper events and vice-versa :)

]]>