Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - RedBully

Pages: [1] 2 3 4
Suggest new features / TypeScript Support
« on: November 23, 2016, 01:05:41 am »

Do you or will you be providing type definitions for TypeScript similar to those provided by



Help for ParamQuery Pro / jQuery 1.12 support
« on: August 08, 2016, 08:13:08 pm »

Paramgrid uses the jQuery UI zIndex function:

However, this function has been removed from version 1.12 of jQuery and so the grid no longer works with this version.

(I am using v3.2.0 of the grid).

Please can you advise if later versions of the grid will support later versions of jQuery.

Help for ParamQuery Pro / Remote Data
« on: July 17, 2015, 04:35:35 pm »

I am currently using local data, local header filtering and local sorting in my grid.
I want to start using remote data, remote header filtering and remote sorting and your demos show me how I can do this.

However, in addition to the ObjectModel, ColumnModel and DataModel required by pqgrid, I also use additional meta data about the rows, columns and cells that I store in JSON objects outside of the grid.  This meta data is used to help render the grid (through colModel.render) and for other functionality used outside of the grid.

Question 1: If I implement a URL for handling pqGrid requests for data and filterered data, Should I use dataModel.getData and dataModel.postData so that I can include my own meta data in the request and response sent to the server?

Question 2: Other than some snippets in your demos, do you have documentation on the structure of the JSON objects sent to the server in the case of fetching paged/filtered/sorted data?

In order to use 'remote' data, I will need to create server side classes that I can deserialise the JSON from pqGrid into.  This essentially couples my pqgrid code on the client to server side code in a way that is not currently done and will mean that I have to ensure that my server side code is kept up to date with future releases of pqgrid.

Question 3: I think I would prefer to be able to use a callback method to fetch data instead of having to specify dataModel.Url or dataModel.getUrl.  In this way I can use my own AJAX framework to send and receive both pqgrid data as well as my own meta data and keep the pqgrid code decoupled from the server side code.  Is this currently possible or will you be able to implement this in a future version of pqGrid?

Question 4:  Could I use dataModel.beforeSend to intercept requests and return false.  I can then get beforeSend to carry out my own call to the server and then call 'refreshView' on return.  Does beforeSend have access to the JSON specifying filter and sort information?

Thanks very much

Help for ParamQuery Pro / Re: any demo showing use of DetailModel?
« on: July 06, 2015, 11:45:22 pm »
Thanks very much!

Help for ParamQuery Pro / Re: any demo showing use of DetailModel?
« on: July 06, 2015, 03:08:14 pm »

Given that use of virtualX and VirtualY improves rendering speeds for large number or rows and columns, why are these options not defaulted to true?

Under what circumstances is it better to have virtualX/virtualY set to false?

Here's a code snippet taken from the part of the code that builds the HTML to be rendered. Hope this helps

Code: [Select]
//Get a handle on the cell in the grid
var $cell = ui.$cell;

//Build the dropdown (NB We must include name=dataIndx for it to work correctly with paramgrid code)
//We must also include the Id so that Select2 can target easily using #id
var $sel = $("<select id='" + dataIndx + "' name='" + dataIndx + "' class='" + ui.cls + " grid_cell'>" + optionsHtml + "</select>");
var $div = $("<div></div>");

//Put the select into a div so that when we display select2, it is positioned in the cell.

//Append the div to the cell

//Activate the select2
    allowClear: true,
    dropdownAutoWidth: true,
    minimumResultsForSearch: 5

News / Re: Upgrade to Pro Version 3.0.0
« on: July 01, 2015, 07:41:11 pm »
Lovely! Looking forward to upgrading!

I have managed to implement Select2 for inline editing (see screenshot).  (Using Pro 2.4.1)  So it is possible.  I'll try and find out how I did it.

Help for ParamQuery Pro / Re: Column Filter Callback
« on: May 30, 2015, 07:49:31 pm »
I've not received the build you said you would send and so I have updated my code to use pqSelect instead of select2.
This is now working though I would like to return to select2 when you bring out the next version.

I used both your API documentation and your demo example to help me update my code.  It was quite difficult and so might I suggest the following improvements to your API documentation that would have made my life easier:

- Explain what prepend does and how it must be used.  If you don't use prepend then your first option will appear to be pre-selected in the filter but not actually applied.  Also, you cannot deselect the first option.  The prepend object that you should use also varies depending on whether you want a single select or multiple select dropdown.  The demo gives examples of a key/value pair to use but the documentation does not explain what this means in the context of single select dropdown and multiple select dropdown.

- Make it clear that if using a filter type of 'select' then the value should be set to [] or null depending on whether a multiple select dropdown or single select dropdown is being used.

- Make it clear that attr='multiple' property is required if type='select' and multiple select drop down is required

- Make it clear what JSON structure is required for the 'options' if grouping is applied. An example on non grouping is given and the coder has to infer the structure.  The demo is using grid.getData which hides the structure and so an example of the actual JSON structure required would be very useful in the documentation.  I spent a lot of time wondering if my options JSON structure was correct because I had not used prepend and I was getting incorrect result.

Finally, I'd like to say the paramgrid is a fantastic product.  Powerful and very flexible.  If you could make the documentation a little better then it would truly be a first class product.

Help for ParamQuery Pro / Re: Column Filter Callback
« on: May 27, 2015, 04:48:20 pm »
Yes please.  We are not in production yet but currently going through a testing phase.

Help for ParamQuery Pro / Re: Column Filter Callback
« on: May 26, 2015, 08:57:36 pm »

Sorry, I've not had time to put together a test for you.

However, I was finding that just returning an html string in the call back was failing to work:

Code: [Select]
"type", "function (ui) { return "<select><option>Option 1</option><option>Option 2</option></select>"; }

Do you have an update on the release of the latest version please?  I need to get my filter working now and so have to decide whether to rework my code to use your pqSelect or wait for the new version so that my workload is reduced.  I'd prefer to wait because it should mean less work for me but I need to get filtering working by end of this week either way.

Help for ParamQuery Pro / Column Events
« on: May 26, 2015, 08:44:40 pm »
Please could you add events to the API so that I can create custom code to handle changes to column order, sort direction, sort index etc  in the same way that you have the columnResize event.

Help for ParamQuery Pro / Re: Column Filter Callback
« on: May 07, 2015, 02:00:19 pm »
Thank you for your reply.

My select2 code using 2.1.0 is working fine and the grid is filtered correctly based on my selection.  I've used the range condition and made sure that my option values match with the values in the grid cells.  (Although I'm using a special render method for the cells so that the option label is displayed instead of the option value)

My Options are currently supplied in JSON format as below which I think is incompatible with your pqselect.

Could you indicate when the bug fix/next version will be available because I don't want to spend a lot of time re-working my filter code if the bug fix means the pqgrid code works as it did in 2.1.0

Code: [Select]
"OptionGroups": [
                "Label": "Group 1",
                "Options": [
                      "Label": "Red",
                      "Value": "1"
                      "Label": "Pink",
                      "Value": "2"
                "Label": "Group 2",
                "Options": [
                      "Label": "Brown",
                      "Value": "3"
                      "Label": "Orange",
                      "Value": "4"

Help for ParamQuery Pro / Re: Setting Height after initialisation
« on: May 06, 2015, 07:18:01 pm »
Thank you for this. Please could you update the documentation to say the same about the 'refresh'.

Help for ParamQuery Pro / Re: Setting Height after initialisation
« on: May 06, 2015, 03:17:37 pm »
My current work around is to count the number of rows in the grid before initialisation and to change the options before initialising the grid.  This is a weak solution because the heights of the individual rows can vary.

Pages: [1] 2 3 4