Questions / issues migrating from Xataface-2.x to 3.x

[Eric Sisler]

Hello,

Finally getting around to migrating an old server from Xataface-2.x to 3.x.  Overall it is working and I like the updated interface, but I've run across a couple of problems:

1) The browse view no longer has previous | next arrows.  Did I miss a configuration option or  a different way of doing this?  I use this to scroll through records a lot.

2) The narrower list display wastes a lot of screen real estate, particularly on higher resolution monitors.  Using the 'full-width.list = 1' config option causes the browser's horizontal scrollbar to display, but doesn't entirely solve the problem.  Having to scroll all the way to the bottom to use the built-in horizontal scroll isn't entirely useful either, you lose the column titles.  Is there a way around this?

3) I think this problem also exists in the 2.x series: I moved most of the tables to drop-down menu items, which works nicely.  However it seems at least one table is required in the conf.ini file to avoid throwing a webserver 500 error when no table is included in the URL, in particular when a login is required.  My thought was to fix this via index.php, but I don't know if this would cause other breakage:

if(!isset($_REQUEST['-table'])) {
    $_REQUEST['-table'] = $_GET['-table'] = 'table_name';
}

Any & all help is appreciated, and thanks for a great piece of software we've gotten a lot of use out of.

-Eric

[Steve Hannah]

1) The browse view no longer has previous | next arrows.  Did I miss a configuration option or  a different way of doing this?  I use this to scroll through records a lot.

Try setting the "show_details_controller" preference to 1.

http://xataface.com/wiki/preferences

 

2) The narrower list display wastes a lot of screen real estate, particularly on higher resolution monitors.  Using the 'full-width.list = 1' config option causes the browser's horizontal scrollbar to display, but doesn't entirely solve the problem.  Having to scroll all the way to the bottom to use the built-in horizontal scroll isn't entirely useful either, you lose the column titles.  Is there a way around this?

I made a couple of changes in a branch that seems to improve this.  Short screencast here:
https://youtu.be/gpRL12rQvaA

PR here: https://github.com/shannah/xataface/pull/134

Please try out this branch and let me know if it accomplishes what you need.
 

3) I think this problem also exists in the 2.x series: I moved most of the tables to drop-down menu items, which works nicely.  However it seems at least one table is required in the conf.ini file to avoid throwing a webserver 500 error when no table is included in the URL, in particular when a login is required.  My thought was to fix this via index.php, but I don't know if this would cause other breakage:

if(!isset($_REQUEST['-table'])) {
    $_REQUEST['-table'] = $_GET['-table'] = 'table_name';
}

Yeah you need at least one table there.  You can decouple the tables list from the menus though. 

https://shannah.github.io/xataface-manual/#tables-navigation-menu

Best regards

Steve

Any & all help is appreciated, and thanks for a great piece of software we've gotten a lot of use out of.

-Eric

--
You received this message because you are subscribed to the Google Groups "Xataface" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xataface+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xataface/CAJ7Rquhz%2BXS_KRr%3DXF7V_iBNcam1x8mLx1POLq_6mbntvte3Qw%40mail.gmail.com.

--

Steve Hannah

Web Lite Solutions Corp.

[Eric Sisler]

Hi Steve,

Thanks for the update, here is some followup:

1) The browse view no longer has previous | next arrows.  Did I miss a configuration option or  a different way of doing this?  I use this to scroll through records a lot.

Try setting the "show_details_controller" preference to 1.

http://xataface.com/wiki/preferences

This did the trick, but the "show_details_controller" config option is not listed there or the docs on GitHub.

  

2) The narrower list display wastes a lot of screen real estate, particularly on higher resolution monitors.  Using the 'full-width.list = 1' config option causes the browser's horizontal scrollbar to display, but doesn't entirely solve the problem.  Having to scroll all the way to the bottom to use the built-in horizontal scroll isn't entirely useful either, you lose the column titles.  Is there a way around this?

I made a couple of changes in a branch that seems to improve this.  Short screencast here:
https://youtu.be/gpRL12rQvaA

PR here: https://github.com/shannah/xataface/pull/134

Please try out this branch and let me know if it accomplishes what you need.

This branch provides a much-improved list display IMO, thanks!  Will it get rolled into the regular release at some point?  Question: with "full-width.list = 0" there's a blank space on the left.  In the 2.x series it had links for "new [table_name]", "all [table_name]", "search results", "last record viewed" and optionally pre-defined search buttons / other functions.  I see the buttons/functions have been moved to the kabob menu next to the "new record" button.  Is there a way to restore the breadcrumbs (for lack of a better word) or is this space reserved for something else?

 

3) I think this problem also exists in the 2.x series: I moved most of the tables to drop-down menu items, which works nicely.  However it seems at least one table is required in the conf.ini file to avoid throwing a webserver 500 error when no table is included in the URL, in particular when a login is required.  My thought was to fix this via index.php, but I don't know if this would cause other breakage:

if(!isset($_REQUEST['-table'])) {
    $_REQUEST['-table'] = $_GET['-table'] = 'table_name';
}

Yeah you need at least one table there.  You can decouple the tables list from the menus though. 

https://shannah.github.io/xataface-manual/#tables-navigation-menu

 I actually walked through this documentation to restore the 2.x drop-down menus as the syntax changed.  Even with all tables as part of drop-down menus it appears there needs to be at least one table in conf.ini to avoid the webserver 500 error above, unless I have missed something?  The code above effectively sets the default table when none is specified via the URL, but would it cause other breakage?

Thanks!

-Eric