Re: serving additional pages
anatoly techtonik <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <CAPkN8xJ37PPE4O9VkTUigowpLyoakWpUzgCU7gkN3QQK_iqovw@mail.gmail.com> |
FWIW. To make such things easier through extension mechanism (and to get nice URLs) I've started routing implementation for Roundup (https://wiki.python.org/moin/Routing). I am not sure if I'll be able to complete the task - the basic functionality is there https://bitbucket.org/roundup/roundup/commits/branch/routing but documentation, tests and extension point for inserting route rules from extensions are hanging. I may need help with those. On Mon, Oct 13, 2014 at 6:02 AM, Stuart McGraw <[email protected]> wrote: > On 10/12/2014 06:16 PM, John P. Rouillard wrote: >> Hello: >> >> In message <[email protected]>, >> Stuart McGraw writes: >>>I have read the Web Inferface part of the Roundup docs but I still >>>do not understand how to do the following... >>> >>>I want to add an additional page (linked to from home.html) that >>>is not associated with any action, >> >> I assume rather than action, you mean any class. >> >>>just some additional html text. >>>I want it to be processed by the template engine (because it uses >>>the layout macro in page.html) so I don't want a static file, yes? >> >> Correct. >> >>>I do not understand how to name it and with what url to access it? >>>A clue (or better yet, an answer :-) would be greatly appreciated. >> >> Yeah, it's not quite obvious. >> >> If you name the additional page: home.additional.html and use the >> link: >> >> http://host/tracker/index?@template=additional >> >> does it do what you want? The file name format format is: >> >> object.view.html >> >> where object is usually user, issue, _generic or it can be the word >> index (or home). If index/home is used, there is no context provided >> to the template. >> >> See: >> >> http://roundup.sourceforge.net/docs/customizing.html#determining-web-context >> >> where it says: >> >> 1) with is no path we are in the “home” context. See the “home” >> context below for details. “index” or “home” paths may also be used >> to switch into “home” context. >> >> Then the "home" context says: >> >> The “home” context is special because it allows you to add >> templated pages to your tracker that don’t rely on a class or item >> (ie. an issues list or specific issue). >> >> Let’s say you wish to add frames to control the layout of your >> tracker’s interface. You’d probably have: >> >> A top-level frameset page. This page probably wouldn’t be >> templated, so it could be served as a static file (see serving >> static content) >> >> A sidebar frame that is templated. Let’s call this page >> “home.navigation.html” in your tracker’s “html” directory. To load >> that page up, you use the URL: >> >> <tracker url>/home?@template=navigation >> >> Roundup trackers come with a default "example" of home.classlist.html >> that is in the tracker's html directory. >> >> Does that help? > > Yes, indeed. I was missing that the file needed to be named home.xxx.html > (I named it xxx.html), I think because I hadn't grasped the "context" part > of "home context". (Or maybe the "home" part? :-) But it's working now > and another concept has been clarified, thanks. > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://p.sf.net/sfu/Zoho > _______________________________________________ > Roundup-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/roundup-users -- anatoly t. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ Roundup-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/roundup-users