componentowl-rails-archive/db/import/static_pages/home.erb

<h2>Why is Better ListView the best ListView replacement component for .NET?</h2>
<p class="intro">Let’s face it – the regular .NET ListView control included with Visual Studio is not very good and other alternatives are usually complex overkills. 
  <strong>Better ListView is just what you are looking for. It is the ideal replacement component for .NET ListView.</strong></p>
  
<div class="hilightbox"><%= link_to(t('txt.home.see_comparison_table'), features_path(featured_product)) %></div>
  
<h3><b>Fast, light-weight, pure managed code</b></h3>
<ol>
  <li>Written from scratch in pure managed C# code – does <strong class="underline">not</strong> inherit from regular ListView</li>
  <li>No dependencies</li>
  <li>Easy deployment - single DLL binary that has just 80 kB when compressed in a ZIP archive</li>
  <li>100% compatible with .NET 2.0 or higher</li>
  <li>Lightning fast. Optimized for 100.000+ items</li>
</ol>

<h3><b>Fixed all bugs and issues related to regular .NET ListView control</b></h3>
<p>Since we’ve written the whole control from scratch and it does <strong>not</strong> inherit from the regular Microsoft .NET ListView component, 
  the original ListView bugs are not present.</p>
<p>Furthermore, we’ve fixed all issues and some limitations related to the regular .NET ListView control, especially incorrect behavior and non-standard 
  implementation of many features (selections, drag &amp; drop, checkboxes, etc).</p>
<p>Surprisingly, .NET ListView <strong>does not</strong> support complex data binding. This forces developers to write additional code for populating and 
  updating the control. Better ListView, however, <strong>has the ability</strong> just like the DataGrid control – one can simply bound any IList, DataSet, 
  DataTable and several other types directly to Better ListView and left all the management on .NET internals.</p>
  
<h3><b>Better drag &amp; drop support:</b></h3>
<ol>
  <li>Insertion mark for inner reordering of items helps users preview the action</li>
  <li>Auto-scroll while reordering items added</li>
</ol>

<h3><b>Better column headers:</b></h3>
<ol>
  <li>Columns can be shown in all layouts (not just Details)</li>
  <li>Column headers have their own context menu</li>
  <li>Auto-scroll when reordering column headers added</li>
</ol>

<h3><b>Better sorting:</b></h3>
<ol>
  <li>Inbuilt sorting (zero code needed)</li>
  <li>Multi-column sort supported (use Shift+Click to add additional columns to sort)</li>
  <li>Ability to create custom comparer</li>
</ol>
  
<div class="screenshot">
  <div><%= product_image(1) %></div>
</div>

<h3><b>Images support:</b></h3>
<ol>
  <li>Each sub-item can have its own image</li>
  <li>Use both ImageList control or individual images</li>
  <li>Supports images of all sizes</li>
  <li>Can automatically resize images nicely if needed (no pixelated horrors!)</li>
  <li>Column header images are supported</li>
</ol>

<h3><b>Better checkboxes:</b></h3>
<ol>
  <li>Checkboxes can be used in all layouts (not just Details)</li>
  <li>Fixed behavior. Checkboxes behave as expected – this makes Better ListView user friendly, compared to regular ListView.</li>
  <li>Three-state checkboxes supported</li>
</ol>

<div class="screenshot">
  <div><%= product_image(2) %></div>
</div>

<h3><b>Looks and feels great</b></h3>
<ol>
  <li>Better ListView always fully utilizes the current Windows theme</li>
  <li>Double-buffered and flicker-free</li>
</ol>

<h3><b>Fixed bugs and wrong behavior of regular .NET ListView</b></h3>
<p>The regular ListView has various obscure bugs (like events firing twice) and non-standard implementation of behavior in many cases. We’ve fixed all the bugs, 
  and made it to <strong>always behave as expected</strong>. See more below.</p>

<h3><b>User friendly:</b></h3>
<p><strong>Leverage the user knowledge of Windows Explorer ListView.</strong> The ListView in Windows Explorer is a great model, because every Windows user already 
  knows how it works and how to use it. Unfortunately, the regular .NET ListView deviates from this behavior, and is thus not user friendly. Better Listview 
  replicates the correct standard behavior of Windows Explorer ListView whenever possible. <strong>Better ListView always works as expected.</strong></p>

<h3><b>Developer friendly:</b></h3>
<p><strong>BetterListview can be used just like the common ListView.</strong> All the method names and property names are the same whenever possible. If you know 
  how to use the common ListView, BetterListview will require nearly no learning on your side. Better ListView is a true pragmatic choice &mdash;
  <strong>skip the learning time, and focus on development.</strong></p>

<h3><b>Powerful, flexible, customizable:</b></h3>
<p>Advanced features like super powerful HitTest and ability to have owner-drawn item are supported. You might be surprised by all the things that 
  are possible to do with Better ListView.</p>

<h3><b>Guaranteed supported and continued development</b></h3>
<p>Better ListView is developed as a joint-venture of two software companies that use it in their flagship products (Swift To-Do List and ImagingShop), used 
  by thousands of users daily. <strong>This is your guarantee that it will be supported and developed in the future.</strong></p>

<h3><b>Tested in real world applications by thousands of users</b></h3>
<p>Because Better ListView is used in professional consumer software applications - Swift To-Do List and ImagingShop, thousands of users work with it every day. 
  Although we do <strong>unit tests</strong>, and do thorough inhouse testing, <strong>this is your true bullet-proof guarantee that it is tested thoroughly 
    in the real world.</strong></p>

<h3><b>Other nice-to-have and might-come-handy features:</b></h3>
<ol>
  <li>Customizable searching by typing</li>
  <li>Ability to set custom size for items in all layouts</li>
  <li>Any element of the control can be customized with properties and owner-drawing</li>
</ol>