It might be helpful to provide this information outside the tar file, so that users can inform themselves before downloading…
I've just uploaded the README file in the help section of the project and I've modified the support page so now it points to the Help page: https://sourceforge.net/projects/inkscape-pages/forums/forum/1802502/topic/4547043
The location of the 'export-pages' directory needs to be reconsidered
I've uploaded a new version of the extension which is saving everything in the user home folder in a folder called pages-export instead of the extensions folder:http://sourceforge.net/projects/inkscape-pages/files/inkscape-pages-0.99-1.tar.gz/download
On the other hand the installation of the extension files could optionally be to the user extensions directory
I don't specify the installation directory in the install script. I just do a `inkscape -x`. I prefer this method because on older Linux system the location of the inskape config folder could be for example ~/.inkscape instead of ~/.config/inkscape. Practically the folder is indicated by inkscape itself.
As soon as I will have access to a Windows box, I will implement a .bat file to create an install for Windows also and there I will use the %APPDATA%.
However, if somebody wants to install everything in the home folder, I described the way to do this in the README file, which is now also online.
The same applies to the shortcuts file: put a minimal 'default.xml' into the 'keys' sub-directory of the inkscape user profile
This I didn't understood. Could you please be more specific? Right now, I am editing the default.xml file from the keys folder from the same level as the extension's folder. I suppose that this isn't what you meant, since this I am doing already.
Unfortunately yes, I had to write it in this way. The SVG standard does not include layers. The layers are created by the inkscape team using a group with a custom attribute. I am also using the groups to organize the pages. I use the current layer to display the current page number and to display all the elements of the current page and I use another hidden layer to organize the other pages. If you use layers for organization, you could very easy use the pages for organization. If you put things on a layer and then hide them to use elements from another layer and so on, this is exactly what this extension is doing.
To leave the possibility to use the layers, it would mean that the extension shouldn't use them. It would be very difficult to implement this extension without using some layers. This being said, this remains one of the TO DO things (re-enabling the layers) if the demanding of the feature will justify the time necessary to implement it. It would be much more complicated to implement something like this without the use of the layers. And even so, there are some issues that needs to be solved. For example, when you create a layer on a page, would it be visible on another page? If so, what about it's elements? Normally the elements should be visible only on the page in which they are created. Wouldn't this generate confusion?
Regarding the table extension, it needs an update the first chance I get. I am creating the table in the root folder and I will modify it to create the table in the current layer.
PS: Sunday I will leave on holiday for three weeks and I don't know if I have Internet or time to answer or to implement anything. So, if I don't react for this period, please be patient with me. I have to allocate some time for my wife and my children