Ext.ux.LiveGrid

[jheid]

Thx, I'll have a look at it. The extension was not coded having reading from a flat file in mind (as performance will decrease the larger the file is), but from a conceptual point of view, this should work nonetheless.

The XML file is generated on demand (with the offset and limit parameter), just like your JSON example.
XML is quite an overhead (IMHO JSON is, too) though.

[ThorstenSuckow]

The XML file is generated on demand (with the offset and limit parameter), just like your JSON example.
XML is quite an overhead (IMHO JSON is, too) though.

Okay, I understand the problem now. Since the XML file represents a range of buffered items which are available once the file has been generated, you have to set the bufferSize-value to the count of items available in the xml file. In your given example, this would be "50".


Regards

Thorsten

[jheid]

Okay, I understand the problem now. Since the XML file represents a range of buffered items which are available once the file has been generated, you have to set the bufferSize-value to the count of items available in the xml file. In your given example, this would be "50".


Regards

Thorsten

I don't really understand... Where's the difference between the JSON (using "start" and "limit") and the XML parts (using "start" and "limit")?
The dynamic XML works with Ext's paging and I thought that your solution is compatible with that...?

[ThorstenSuckow]

I don't really understand... Where's the difference between the JSON (using "start" and "limit") and the XML parts (using "start" and "limit")?
The dynamic XML works with Ext's paging and I thought that your solution is compatible with that...?

I'm at work now and have no access to the sources, so this was just a guess. I wasn't aware of the fact that you can page through a XML file using EXT. However, this means your XML file does not change during the lifetime of a pageable Ext component and sits right there in the directory with it's fixed number of items and waits to be paged.
I'll take care of this, just can't do it right now.

[jheid]

I'm at work now and have no access to the sources

I know this problem

, so this was just a guess. I wasn't aware of the fact that you can page through a XML file using EXT.

As I said it's a dyamically generated XML file with a fixed amount and as much children as defined by "start" and "limit".

However, this means your XML file does not change during the lifetime of a pageable Ext component and sits right there in the directory with it's fixed number of items and waits to be paged.
I'll take care of this, just can't do it right now.

True. The "base" XML file does not change and has for example 50 items (in fact there are 800 so a life-grid is very good for that).
In your example the number is 5000 so I'm confused about any difference between your example and mine.

Perhaps I can give you the example:

/pflege/get-data-Netz.xml?start=10&limit=10 will produce

<?xml version="1.0"?> 
<data> 
 <objects count="50"> 
  <netz><name>10</name></netz> 
  <netz><name>11</name></netz> 
  <netz><name>12</name></netz> 
  <netz><name>13</name></netz> 
  <netz><name>14</name></netz> 
  <netz><name>15</name></netz> 
  <netz><name>16</name></netz> 
  <netz><name>17</name></netz> 
  <netz><name>18</name></netz> 
  <netz><name>19</name></netz> 
 </objects>
</data>

[ThorstenSuckow]

I know this problem



As I said it's a dyamically generated XML file with a fixed amount and as much children as defined by "start" and "limit".



True. The "base" XML file does not change and has for example 50 items (in fact there are 800 so a life-grid is very good for that).
In your example the number is 5000 so I'm confused about any difference between your example and mine.

Perhaps I can give you the example:

/pflege/get-data-Netz.xml?start=10&limit=10 will produce

<?xml version="1.0"?> 
<data> 
 <objects count="50"> 
  <netz><name>10</name></netz> 
  <netz><name>11</name></netz> 
  <netz><name>12</name></netz> 
  <netz><name>13</name></netz> 
  <netz><name>14</name></netz> 
  <netz><name>15</name></netz> 
  <netz><name>16</name></netz> 
  <netz><name>17</name></netz> 
  <netz><name>18</name></netz> 
  <netz><name>19</name></netz> 
 </objects>
</data>

In your case, the "count" attribute should then equal to 800. The BufferedGrid needs to know the total number of records in the underlying data repository. Please try this.

[jheid]

In your case, the "count" attribute should then equal to 800. The BufferedGrid needs to know the total number of records in the underlying data repository. Please try this.

Hmpf. Of course the count attribute will be correct. It's just the count of the sample XML file I provided you to show you the problem

[ThorstenSuckow]

Hmpf. Of course the count attribute will be correct. It's just the count of the sample XML file I provided you to show you the problem

hehe... looks like I have to consult the sources at last...

[sfrancolla]

hehe... looks like I have to consult the sources at last...

Hey MindPatterns. Nice work! I just finished skimming through the thread. Are you keeping an enhancement list for this? I and obviously many others are likely very interested in helping building out this component either by helping you organize ideas and/or contributing coding time. You're the author, so it's up to you, but have you given any thought into creating a project for it somewhere?

Thanks.

[andrei.neculau]

@sfrancolla - I'm just putting out my opinion. The following has nothing to do with Thorsten (MindPatterns). This version is still at 0.1 (alpha). So far there hasn't been an update. Just a sneak preview publishing - "official" publishing of the extension pack has been said to be made next weekend.

As for creating a project for it... ExtJS is a project. An extension or a component pack which is at least 5 very big/useful components could be a project. For an extension pack like this one will never need more than a changelog, live demo, usage information. Contributing with code/ideas is always welcome throughout the ExtJS community forum. You will just need to state your view and optionally post your code - you could as well zip your new code and attach it, or create a live demo somewhere. Creating a project (by that understanding changelog, bug tracker, suggestion posting, help, etc) for this is a bit far-fetched don't you think?

@Thorsten - it was bad that you gave your first name, in the first post to the thread. Now I'm inclined to use your first name, while others know/refer to you as MindPatterns