Re: Managing packages in the workbench
- To: mathgroup at smc.vnet.net
- Subject: [mg108858] Re: Managing packages in the workbench
- From: Hannes Kessler <HannesKessler at hushmail.com>
- Date: Sun, 4 Apr 2010 07:45:45 -0400 (EDT)
- References: <hp1ueq$6b9$1@smc.vnet.net>
I was looking for such a clear statement in the Workbench help. Best regards, Hannes Kessler On 1 Apr., 13:01, "David Park" <djmp... at comcast.net> wrote: > One Application ==== One Paclet ==== One Folder directly = in > $UserBaseDirectory/Applications. > > PacletInfo.m should be at the top level. > > The application may contain many packages and many documentation pages. > > It's possible that SOME of the resources for the project, such as package= s > or some ancillary documentation notebooks, perhaps for each package, coul= d > be at deeper levels within the project. You might have to set Properties, > Project Paths. Any Guide pages should be in the standard place. But you > could make a Guide page with hand constructed links to your own set of > notebooks. > > Having an application with hundreds of packages in a nested structure see= ms > a little dubious to me. It creates an extensive management problem. > > David Park > djmp... at comcast.nethttp://home.comcast.net/~djmpark/ > > From: H. Ke=DFler [mailto:kessler.han... at googlemail.com] > > On 28 Mrz., 11:06, David Bailey <d... at removedbailey.co.uk> wrote: > > > > > H. Ke==DFler wrote: > > > My primary problem is that I would like to create help pages of > > > Mathematica packages stored in directories which are not at the top > > > level of my private Mathematica Applications directory. The Workbench > > > creates hyperlinked help pages for such packages which work inside th= e > > > Workbench but not when exported to the corresponding subdirectory of > > > the Mathematica Applications directory. I checked the example you > > > provided on your homepage (http://www.dbaileyconsultancy.co.uk/ > > > m_documentation/m_documentation.html). But it seems that this example > > > also deals with help pages for a package in a directory which is on > > > the top level of the Mathematica Applications directory. If I am > > > wrong, please correct me. But I would really appreciate if you can > > > provide more details how to deal with packages in in deeper > > > subdirectories of the Mathematica Applications directory, no matter o= f > > > using the Workbench or some other approach. > > > Although I only tested the procedure described on my website on a > > package structured in the standard way, I think you could generalise it > > to some extent to deal with a non-standard setup (for example, the > > indexing procedure uses complete path names), but there is no guarantee > > that Mathematica will not make some assumptions that prevent this worki= ng= > == > > . > > > Clearly, the best approach would be to try the process out on a toy > > package organised in the standard way, then generalise that to a toy > > example of your nested structure, and only then move on to your real > > problem with some confidence that it would work! > > > David Baileyhttp://www.dbaileyconsultancy.co.uk > > I've got the workbench to deploy the package files and the > documentation to a folder 2 directory levels below $UserBaseDirectory/ > Applications. The PacletInfo file gets deployed to $UserBaseDirectory/ > Applications/dir1/dir2/PacletInfo.m, the guides notebooks to > $UserBaseDirectory/Applications/dir1/dir2/Documentation/English/ > Guides/..., the application packages themselves to $UserBaseDirectory/ > Applications/dir1/dir2/.. > > But Mathematica does not find the documentation. Perhaps it can find > only PacletInfo.m files in $UserBaseDirectory/Applications/dir1 and > not in deeper directory levels? > > When I open a documentation notebook manually, the links in it to > other documentation notebooks dont' work. Such a link looks, for > example, as "paclet:English/ref/someReferencePage". I was not > successfull to modify the links manually. > > The workbench documentation is rather unclear on the functionality of > the paclet system. Is it possible to describe in a single PacletInfo.m > file the documentation of several applications? Do you know where to > get more information? > > Best regards, > Hannes Kessler