Replies

• jl_newtrax Posts: 2Questions: 0Answers: 0

  February 2014

  Allan, do you expect full compatibility between DataTables 1.10 and jquery-datatables-editable 2.3.3 right off the bat? I'll try it myself later this month, but what issues or gotchas should I be looking for?
  
  https://code.google.com/p/jquery-datatables-editable/
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  February 2014

  The project you link to isn't part of the DataTables project, so it isn't maintained by myself. Indeed, I don't believe it is maintained by anyone now since it is marked as deprecated. So to answer your question directly, I don't know.
  
  DataTables 1.10 will be fully compatible with Editor 1.3, which will be released alongside 1.10 and leverages many of the new features of DataTables.
  
  Allan
• jl_newtrax Posts: 2Questions: 0Answers: 0

  February 2014

  Thanks for the reply. Actually I didn't know about Editor until yesterday, and I've been using this unofficial plugin for a while now. So I'll keep Editor in mind in case of compatibility issues.
• phax Posts: 16Questions: 4Answers: 0

  February 2014

  Hi Allan!
  Just a small note on the 1.10-beta2 docs:
  http://next.datatables.net/reference/option/#Internationalisation
  The text is a bit misleading as the object "language.aria" must in reality be addressed as "oLanguage.oAria" - maybe you can update this for beta3 :)
  Thanks, Philip
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  February 2014

  The `language.aria` option should work just fine as shown here: http://live.datatables.net/widagek/1/edit .
  
  You can use the old Hungarian notation styling if you want - but camelCase now the preferred styling. See: http://next.datatables.net/upgrade/1.10-naming
  
  Allan
• ALMMa Posts: 1Questions: 0Answers: 0

  March 2014 edited March 2014

  DataTables 1.10 beta 2 compatible classes and binder to use with ASP.NET MVC.
  Works ONLY with the new camel case API.
  
  The idea is not to create a master solution to all of your problems. It simply binds variables and help you avoid working with raw request parameters.
  
  https://github.com/ALMMa/datatables-mvc
• liedekef Posts: 8Questions: 0Answers: 0

  March 2014

  Hi,
  
  I'm trying out DataTables 1.10 beta 2, and it's working great (I was having an issue with bSaveState and hidden columns, which is fixed here). But I saw nowhere in the new doc a reference to the old "iDataSort". In the new version, it seems "datasort" works just fine, it's just not documented :-)
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  March 2014

  The old hungarian notation is no longer documented in the 1.10 docs, in favour of the camelCase notation. This is noted in the 'new' release notes ( http://next.datatables.net/new/1.10 ):
  
  > With 1.10, DataTables now accepts both camelCase notation and the original Hungarian notation for parameter, with camelCase being the preferred, and documented, option. As with the API this change is fully backwards compatible.
  
  Allan
• liedekef Posts: 8Questions: 0Answers: 0

  March 2014

  I imagined something like that. But still: "datasort" is not documented on the new site (or I looked in the wrong places).
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  March 2014

  Renamed to `orderData` in 1.10 for naming consistency: http://next.datatables.net/reference/option/columns.orderData . `dataSort` / iDataSort will still work for backwards compatibility.
  
  Allan
• allan Posts: 61,972Questions: 1Answers: 10,160 Site admin

  March 2014 edited March 2014

  Reminder to all - please open a new thread for reporting issues. This way we (I!) can keep track of each individual one.
  
  Allan