- Published: Sunday, 16 November 2014 11:48
You may have noticed, we missed our hoped for delivery date of the next version of EasyTable Pro! Well, we stalled on our Footable update at the 95% point due to a few bugs.
The first is a bug where it seemed that Footable was looking at the viewport size incorrectly.
After a long wait, on Friday we finally got a it confirmed that Footable v2 (the current release) uses the enclosing block (so a DIV for example) to calculate the hide/show breaks and NOT the viewport. So, what this means is our code is fine, their labels are misleading unless you have the table displayed in a full page width block that is at least 1025 pixels wide. It turns out we should have looked through the GitHub issues.
Apparently this will be resolved in the v3 release (which looking at the issues log on Github is some months overdue, a month ago the V3 branch was due in two weeks, now it's due in a month…).
The second bug that stopped us was the "custom breakpoints" option was not overriding the default values. Again this is looking like it will be fixed in version 3, we considered putting a hack in but since starting on this Footables core has gone from 2.0 to 2.0.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199 and finally last week to 2.0.3. So we've decided to go without custom breakpoints until the 3.0 release.
So, where does that leave Footable for EasyTable Pro! At this point we're at the 95% point for the first Beta 1 release, which I expect to have out on Monday/Tuesday along with a new version of the Joomla Search Plugin for EasyTable Pro! As with all of our Beta's it wil be feature complete, have passed the testing suite and just need real user confirmation that all is good before being released as stable.
Wait! What's that about a new Search Plugin? Oh we've updated the EasyTable Pro! Search Plugin for Joomla 3.3+ and that will be out on Monday or Tuesday as well. While we'll be calling it a Beta version it's feature complete and we only really want to make sure some users have tested it before we label it as a stable release.
There's only a few things left to implement before testing can start, and as mentioned I'm hoping to finish them by Monday or Tuesday.