wice_grid 3.6.2 → 4.1.0

data/spec/support/test_app/app/views/custom_ordering/_grid.html.erb

@@ -0,0 +1,10 @@
+<%= grid(grid, show_filters: :always) do |g|
+
+  g.column name:  'ID', attribute: 'id', filter: false
+
+  g.column name:  'Status Name', attribute: 'name'
+
+  g.column  name:  'Created' do |status|
+    status.created_at.to_s(:db) if status.created_at
+  end
+end -%>

data/spec/support/test_app/app/views/custom_ordering/index.html.haml

@@ -0,0 +1,24 @@
+:css
+  table.my-grid {
+    border: 1px solid red;
+  }
+  table.my-grid tr.my-header {
+    background-color: #ebebeb;
+  }
+
+
+.well
+  %h2= current_page_title
+  %p
+    It is possible to override the default ordering by specifying SQL Strings. "Status Name" in the first table is done
+    by the length of the status name. Ordering "Status Name" in the second table is actually replaced by ordering
+    by column.
+
+= show_code
+
+.row
+  .col-md-6
+    = render   'grid', grid: @status_grid1
+
+  .col-md-6
+    = render   'grid', grid: @status_grid2

data/spec/support/test_app/app/views/custom_ordering_on_calculated/_grid.html.erb

@@ -0,0 +1,14 @@
+<%= grid(grid, show_filters: :always) do |g|
+
+  g.column name:  'ID', attribute: 'id', filter: false
+
+  g.column name:  'Status Name', attribute: 'name'
+
+  g.column name:  'Created' do |status|
+    status.created_at.to_s(:db) if status.created_at
+  end
+
+  g.column name: 'Task Count', attribute: 'task_count', sort_by: ->(status) { status.tasks.count } do |status|
+    status.tasks.count
+  end
+end -%>

data/spec/support/test_app/app/views/custom_ordering_on_calculated/index.html.haml

@@ -0,0 +1,23 @@
+:css
+  table.my-grid {
+    border: 1px solid red;
+  }
+  table.my-grid tr.my-header {
+    background-color: #ebebeb;
+  }
+
+
+.well
+  %h2= current_page_title
+  %p
+    It is possible to support ordering on calculated fields with custom_sort. When using this method you must specify
+    an (arbitrary) attribute name, which is used as a query parameter.
+  %p
+    Note that this method requires loading every result of the query into memory and running the Proc on each, so is
+    unsuitable for a large number of results or expensive calculations.
+
+= show_code
+
+.row
+  .col-md-6
+    = render   'grid', grid: @status_grid

data/spec/support/test_app/app/views/custom_ordering_with_arel/_grid.html.erb

@@ -0,0 +1,10 @@
+<%= grid(grid, show_filters: :always) do |g|
+
+  g.column name:  'ID', attribute: 'id', filter: false
+
+  g.column name:  'Status Name', attribute: 'name'
+
+  g.column  name:  'Created' do |status|
+    status.created_at.to_s(:db) if status.created_at
+  end
+end -%>

data/spec/support/test_app/app/views/custom_ordering_with_arel/index.html.haml

@@ -0,0 +1,24 @@
+:css
+  table.my-grid {
+    border: 1px solid red;
+  }
+  table.my-grid tr.my-header {
+    background-color: #ebebeb;
+  }
+
+
+.well
+  %h2= current_page_title
+  %p
+    It is possible to override the default ordering by specifying Arel objects. "Status Name" in the first table is done
+    by the length of the status name. Ordering "Status Name" in the second table is actually replaced by ordering
+    by column.
+
+= show_code
+
+.row
+  .col-md-6
+    = render   'grid', grid: @status_grid1
+
+  .col-md-6
+    = render   'grid', grid: @status_grid2

data/spec/support/test_app/app/views/custom_ordering_with_proc/_grid.html.erb

@@ -0,0 +1,10 @@
+<%= grid(grid, show_filters: :always) do |g|
+
+  g.column name:  'ID', attribute: 'id', filter: false
+
+  g.column name:  'Status Name', attribute: 'name'
+
+  g.column  name:  'Created' do |status|
+    status.created_at.to_s(:db) if status.created_at
+  end
+end -%>

data/spec/support/test_app/app/views/custom_ordering_with_proc/index.html.haml

@@ -0,0 +1,21 @@
+:css
+  table.my-grid {
+    border: 1px solid red;
+  }
+  table.my-grid tr.my-header {
+    background-color: #ebebeb;
+  }
+
+
+.well
+  %h2= current_page_title
+  %p
+    It is possible to override the default ordering by specifying a Proc which generates custom sql code. "Status Name"
+    is sorted alphabetically unless
+    = link_to 'a sort_by_length parameter is in the request.', sort_by_length: true
+
+= show_code
+
+.row
+  .col-md-6
+    = render   'grid', grid: @status_grid

data/spec/support/test_app/app/views/custom_ordering_with_ruby/_grid.html.erb

@@ -0,0 +1,10 @@
+<%= grid(grid, show_filters: :always) do |g|
+
+  g.column name:  'ID', attribute: 'id', filter: false
+
+  g.column name:  'Status Name', attribute: 'name', sort_by: ->(status) { [status.number_of_vowels, status] }
+
+  g.column  name:  'Created' do |status|
+    status.created_at.to_s(:db) if status.created_at
+  end
+end -%>

data/spec/support/test_app/app/views/custom_ordering_with_ruby/index.html.haml

@@ -0,0 +1,23 @@
+:css
+  table.my-grid {
+    border: 1px solid red;
+  }
+  table.my-grid tr.my-header {
+    background-color: #ebebeb;
+  }
+
+
+.well
+  %h2= current_page_title
+  %p
+    It is possible to override the default ordering by specifying a Proc to define the key to sort on. This key can be
+    a method of the model or other Ruby code. "Status Name" sorts on Status#number_of_vowels.
+  %p
+    Note that this method requires loading every result of the query into memory and running the Proc on each, so is
+    unsuitable for a large number of results or expensive calculations.
+
+= show_code
+
+.row
+  .col-md-6
+    = render   'grid', grid: @status_grid

data/spec/support/test_app/app/views/dates/_grid.html.erb

@@ -0,0 +1,25 @@
+
+<%= grid(@tasks_grid) do |g|
+
+  g.column name:  'ID', attribute: 'id', filter: false
+
+  g.column name:  'Title', attribute: 'title'
+
+  g.column  name:  'Archived', attribute: 'archived' do |task|
+    task.archived? ? 'Yes' : 'No'
+  end
+
+  g.column name:  'Due Date', attribute: 'due_date' do |task|
+    task.due_date if task.due_date
+  end
+
+  g.column name:  'Added', attribute: 'created_at' do |task|
+    task.created_at.to_s(:db)
+  end
+
+  g.column name:  'Updated', attribute: 'updated_at', filter_type: :rails_datetime_helper, filter_control_options: {start_year: 2011} do |task|
+    task.updated_at.to_s(:db)
+  end
+
+
+end -%>

data/spec/support/test_app/app/views/dates/index.html.haml

@@ -0,0 +1,52 @@
+.well
+  %h2= current_page_title
+  %p
+    WiceGrid provides four filters for selecting dates and time:
+
+    %ul
+      %li
+        %code
+          \:jquery_datepicker
+        \- Jquery datepicker (works for datetime, too)
+
+      %li
+        %code
+          \:bootstrap_datepicker
+        \- Bootstrap datepicker (works for datetime, too)
+
+      %li
+        %code
+          \:rails_date_helper
+        \- standard Rails date helper
+
+      %li
+        %code
+          \:rails_datetime_helper
+        \- standard Rails datetime helper
+
+    Specify a date/datetime filter just like you specify any other filter:
+
+
+  %p
+    Default filters are defined in configuration constants
+    %code
+      Wice::Defaults::DEFAULT_FILTER_FOR_DATE
+    and
+    %code
+      Wice::Defaults::DEFAULT_FILTER_FOR_DATETIME.
+    By default
+    %code
+      \:jquery_datepicker
+    is used for both dates and time.
+
+
+
+
+
+
+
+= show_code
+
+.row-fluid
+  .col-md-12
+    = render   'grid'

data/spec/support/test_app/app/views/detached_filters/_grid.html.erb

@@ -0,0 +1,23 @@
+<%= define_grid(@tasks_grid, hide_submit_button: true, hide_reset_button: true) do |g|
+
+  g.column name:  'ID', attribute: 'id', detach_with_id: :id_filter
+
+  g.column name:  'Title', attribute: 'title', detach_with_id: :title_filter
+
+  g.column  name:  'Description', attribute: 'description', detach_with_id: :description_filter
+
+  g.column  name:  'Archived', attribute: 'archived', detach_with_id: :archived_filter do |task|
+    task.archived? ? 'Yes' : 'No'
+  end
+
+
+  g.column name:  'Due Date', attribute: 'due_date', detach_with_id: :due_date do |task|
+    task.due_date.to_s(:short)
+  end
+
+
+  g.column   do |task|
+    link_to('Edit', edit_task_path(task))
+  end
+
+end -%>

data/spec/support/test_app/app/views/detached_filters/index.html.haml

@@ -0,0 +1,79 @@
+.well
+  %h2= current_page_title
+  %p
+    Filters can also be detached from the grid table. This is a 3-step process.
+
+  %ol
+    %li
+      First, define the grid with helper
+      %code define_grid
+      instead of
+      %code grid
+      \. Everything should be done the same way as with
+      %code grid, but every column which will have an external filter, add
+      %code detach_with_id: :some_filter_name
+      in the
+      %code column
+      definition.
+
+    %li
+      Then use
+      %code grid_filter(grid, :some_filter_name)
+      to render filters.
+
+    %li
+      Finally, use
+      %code render_grid(@grid)
+      to actually output the grid table
+      \.
+
+= show_code
+
+= render   'grid'
+
+
+.row
+  .col-md-2
+    ID:
+  .col-md-10
+    = grid_filter @tasks_grid, :id_filter
+
+.row
+  .col-md-2
+    Title:
+  .col-md-3
+    = grid_filter @tasks_grid, :title_filter
+  .col-md-7
+
+
+.row
+  .col-md-2
+    Description:
+  .col-md-3
+    = grid_filter @tasks_grid, :description_filter
+  .col-md-7
+
+.row
+  .col-md-2
+    Archived:
+  .col-md-10
+    = grid_filter @tasks_grid, :archived_filter
+
+
+.row
+  .col-md-2
+    Due date:
+  .col-md-10
+    = grid_filter @tasks_grid, :due_date
+
+
+.row-fluid
+  .col-md-12
+    .external-buttons
+      %button.btn.btn-primary.wg-external-submit-button{'data-grid-name' => 'grid'} Submit
+      %button.btn.btn-default.wg-external-reset-button{'data-grid-name' => 'grid'} Reset
+
+.row-fluid
+  .col-md-12
+
+    = render_grid(@tasks_grid)

data/spec/support/test_app/app/views/detached_filters_two_grids/_grid.html.erb

@@ -0,0 +1,23 @@
+<%= define_grid(tasks_grid, hide_submit_button: true, hide_reset_button: true) do |g|
+
+  g.column name:  'ID', attribute: 'id', detach_with_id: :id_filter
+
+  g.column name:  'Title', attribute: 'title', detach_with_id: :title_filter
+
+  g.column  name:  'Description', attribute: 'description', detach_with_id: :description_filter
+
+  g.column  name:  'Archived', attribute: 'archived', detach_with_id: :archived_filter do |task|
+    task.archived? ? 'Yes' : 'No'
+  end
+
+
+  g.column name:  'Due Date', attribute: 'due_date', detach_with_id: :due_date do |task|
+    task.due_date.to_s(:db)
+  end
+
+
+  g.column   do |task|
+    link_to('Edit', edit_task_path(task))
+  end
+
+end -%>

data/spec/support/test_app/app/views/detached_filters_two_grids/index.html.haml

@@ -0,0 +1,85 @@
+.well
+  %h2= current_page_title
+  %p
+    An example of two grids with detached filters functioning independantly of each other.
+
+= show_code
+
+= render   'grid', tasks_grid: @grid1
+= render   'grid', tasks_grid: @grid2
+
+.row
+  .col-md-2
+    ID:
+  .col-md-4
+    = grid_filter @grid1, :id_filter
+  .col-md-2
+    ID:
+  .col-md-4
+    = grid_filter @grid2, :id_filter
+
+
+.row
+  .col-md-2
+    Title:
+  .col-md-4
+    = grid_filter @grid1, :title_filter
+  .col-md-2
+    Title:
+  .col-md-4
+    = grid_filter @grid2, :title_filter
+
+
+
+.row
+  .col-md-2
+    Description:
+  .col-md-4
+    = grid_filter @grid1, :description_filter
+  .col-md-2
+    Description:
+  .col-md-4
+    = grid_filter @grid2, :description_filter
+
+
+.row
+  .col-md-2
+    Archived:
+  .col-md-4
+    = grid_filter @grid1, :archived_filter
+  .col-md-2
+    Archived:
+  .col-md-4
+    = grid_filter @grid2, :archived_filter
+
+
+.row
+  .col-md-2
+    Due date:
+  .col-md-4
+    = grid_filter @grid1, :due_date
+  .col-md-2
+    Due date:
+  .col-md-4
+    = grid_filter @grid2, :due_date
+
+
+.row
+  .col-md-6
+    .external-buttons-grid1
+      %button.btn.btn-primary.wg-external-submit-button{'data-grid-name' => 'grid'} Submit
+      %button.btn.btn-default.wg-external-reset-button{'data-grid-name' => 'grid'} Reset
+
+  .col-md-6
+    .external-buttons-grid2
+      %button.btn.btn-primary.wg-external-submit-button{'data-grid-name' => 'grid2'} Submit
+      %button.btn.btn-default.wg-external-reset-button{'data-grid-name' => 'grid2'} Reset
+
+%p
+
+.row
+  .col-md-6
+    = render_grid(@grid1)
+
+  .col-md-6
+    = render_grid(@grid2)