Re: [Exist-development] 2.0RC1 notes

[Jens Ø. P. <oe...@gm...>]

Hi Joe,

On Dec 4, 2012, at 7:16 PM, Joe Wicentowski <jo...@gm...> wrote:

> - BetterForm occupies 2 spaces in the installer package and the Dashboard; in the installer the items are called "bfDemos" and "bfReferences".  It also occupies 2 spaces in the Dashboard, but both icons point to the same URL: http://localhost:8080/exist/apps/betterform/dashboard.html.  Seems a little odd and potentially confusing to users.  Can 2 apps be installed into the same subcollection of /db/apps/?

Both the betterFORM Demos and the betterFORM Feature Explorer files are installed inside the betterform collection which is inside /db/apps/. The betterform collection itself is installed when either of the two are installed. The betterFORM dashboard is static and links to both the demos and the feature explorer, even though both are not necessarily installed - this does not look good.

I think the idea is that users should have the choice of installing either of these apps independently, but then the apps should actually be separate, which they are not. If the demos and feature explorer depend on a betterFORM library, this library should be installed as a dependency of the demos and the feature explorer and, as Joe suggests, have different collections immediately below /db/apps/ (it should probably be separately installable as well).

> - XSLTForms occupies 2 apps in the installer package, but it makes a clear distinction between XSLTForms and its demo.  This is good.  Oddly, there is only one icon in the Dashboard though.  

The XSLTForms Files are a resource package and therefore has no web view, so I don't think it should be displayed in the Dashboard. However, it should appear as installed in the Package Manager when it is installed as a dependency, which is not the case now.

> Also, I'd suggest making the demo's app name lower-cased (XSLTForms-Demo > xsltforms-demo) ; otherwise, it appears first in the list of apps in /db/apps.

The reason why I used upper-casing for the demo files is that XSLTForms is an established product; upper-casing is not used for the library files, since there is an established practice of referring to them with the lower-cased form. There are other packages using upper-casing (TEIXLingual), so perhaps it would be easiest simply to make sorting case-insensitive. 

Cheers,

Jens