On a project written with ExtJs 6, I'm looking for the ability to have multi-level grouping on a grid.
I don't want to group the records on multiple columns but on one level, but each column to be grouped on its own level.
I found some examples for ExtJs, but all pages have broken link to source code (old references).
My goal is to be able to group columns on one, two or three levels depending on the user's choice.
Gridpanel ExtJs proposes by default to group only on one level. I'm looking to expand that.
Sounds like you could use a Tree Grid, each branch being a level.
I solved my issue by migrate ExtJs framework to version 7.5
And then using the "AdvancedGroupingSummary" grid's feature which allows multi-level grouping
Related
For displaying my tabled data I am currently using the angular datatables Here's the link. I am mostly satisfied with it up to some things.
The only problem with the angular datatables is, that I cannot manually delete a row from the table. There is some angular way for editing and deleting rows, but then the table get rerendered, so all sorting and paginations get lost. I found another solution (smart tables), but I didn't find if there is a possibility to edit/delete a row entry (from the table). Here is a little comparison.
I use angular-datatables for the following purposes:
Displaying some data with pagination and/or scrollbars
Defining own header width for every column
Searching over all columns / searching over some columns
Rendering some columns with custom html code (for example I put some action buttons in it, or make the entries in some cols to links)
Sorting values on every column (ascending, descending)
Disabling sorting on some columns
Multiselect on rows (highlighting a row and save the id of the dataset behind the row for actions)
NO editing/deleting rows
My question is, if you can do the same with smart-table
I figured out, that already all points are implemented well.
pagination: yes / scrollbars: no?
yes
yes
yes
yes
(yes?)
multiselect: yes, accessing selected data id no?
no?
I am only not sure about the 1st, 6th, 7th and 8th point. Can you give there a statement?
I could switch to smart tables, if there are all listed options available in it.
Thanks
Pagination? yes, you have pagination out of the box, you can even change the default template and functionality
Sorting? you can ENABLE sorting by adding an optional st-sort directive to the column header
Multiselect? no, but it's easy to implement over smart-table (done it once)
Deletion? you can delete rows (that is, doing DELETE over http and slicing the array if successful)
and if there is any additional functionality you'll need in the future that ST doesn't already have, you can create your own plugin for it. the docs are you friend
I'm using Alfresco 4.1.6 and Solr 1.4.
I'm reading about the possibility of using classifications for the nodes, specified with a type d:category in an aspect on the content model.
A good time of searchs in our project are the most important, is the reason I try to design the best option possible for this. Our repository have over 2 millions of documents, spread over directories, where each user (we have 3000 users aprox) have an own root path.
For the queries (FTS_ALFRESCO), we actually use TYPE (we have 5 distinct types of nodes defined on our model) and custom properties (all of them that we use in the queries are indexed).
My question is... Imagine I change my model and use one of our properties like a category. I delete a property and create an aspect with d:category with this property. The search will be more efficient and quickly if I search by TYPE, property and category? Alfresco gives me a best performance if I search this value like a category instead of when I search this value like a normal indexed property? Or really is the same? Whats the benefits of use this like a category?
Category and Properties both of them has different usage.
Main difference is
Property:You could have different value of same property for each content
Category:You will have same category which can be associated to muliple contents
So, based on your requirement you have to choose which one you want to use. As far as performence is concerned I guess category based search will be faster(I haven't really tried it though).
I was wondering if there's a way in Solr 4 or higher, to merge facets together based on a mapper. I have a lot of products inside my database with terms (inside the taxonomy "color" for example) which actually mean the same. For example the color red is described as:
red
bordeaux
light red
dark red
I would like to merge such terms, cause I don't want to bother the user with hundreds of choices, when I can reduce that number to dozens. I'm trying to figure out what's the best way to do this, create a separate table inside my database (used to map the id's of terms together) or use functionality in Solr to do this on index-time. I read something about Pivot Facets, but I guess that's the way to go if there is already an hierarchy? Because those different terms of red are just flat (are not grouped together, yet). Any advices?
EDIT:
Guess I found a solution: http://www.wunderkraut.com/blog/how-to-combine-two-facet-items-in-facet-api/2015-03-26. Any thoughts about this? Looks good to me though.
Problem
(Using Solr 4.3.0) I can't seem to get the includeCollapsedDocs parameter of Field Collapsing feature to work. Has this feature been dropped? I've only found a few mentions of it here and there.
Use case
I have indexed versioned documents so that each version is a separate document. So I use the field collapsing feature to group the versions together. But doing so I will have lost the unique meta data of each version. For example I need to be able to list the dates of each version when I display it. So I'm thinking that 'includeCollapsedDocs' would allow me to have both the groups and the documents with the meta data.
The parameter to set to get the collapsed documents to show is 'group.limit'. So instead of setting 'collapse.includeCollapsedDocs.fl=*' I set 'group.limit=10'.
I need to read the documentation more carefully.
I need to merge cells across multiple rows. Something similar to a RowSpan on the cell. This is because I have two columns in the grid. Column 1 can have duplicate values that relate to the values in the column one. I want to merge values in the column 1 to just appear once for all the rows in column2.
Is there a way to achieve this on the DataGrid in Silverlight 5?
I am sorry to say this but most Silverlight grids do not support cell merging. At least not out of the box. I have resorted to using Component One studio for Silverlight in order to achieve this, and even then it hasn't been exactly a walk in the park.
Consider C1 Data Grid control. Here is a sample on merging grid row and column headers with sample code and a small write up. The down side of such solutions is that C1's controls are extremely expensive :( I wish Microsoft came up with some enhancements in SL5 that would accommodate for such issues.