From: Misztur, C. <CMi...@ma...> - 2013-10-26 19:35:02
|
Is there a reason for the sub-collections and not keeping all html files together? ________________________________________ From: Florent Georges [li...@fg...] Sent: Saturday, October 26, 2013 2:03 PM To: eXist DB ML Subject: [Exist-open] eXide-created app, and structured links Hi, I used eXide to create a new webapp, using the plain design (using Boostrap, but not the eXist design). So the main entry point in the file ./index.html (at the root of the webapp structure). In order to add some structure, I have links to sub-areas, say "buy" and "sell", stored in sub-collections, the main entry point for each of them being their own index.html: ./buy/index.html ./sell/index.html Of course, they have their own set of files in both collection, in order to achieve "buy" and "sell" goals. But the menu at the top of the page, configured in ./templates/page.html, has a link to the main home page as being ./index.html, so depending where the user is, it is once a link to the homepage, once a link to "buy", and once a link to "sell". The same applies to the default CSS file, that ./templates/page.html refers to as "resources/css/style.css". But depending what page applies that template, it might need "../" in front of it. What is the best way to adapt that link (those links)? In order to reflect the actual structure of the application? Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Exist-open mailing list Exi...@li... https://lists.sourceforge.net/lists/listinfo/exist-open ________________________________ The contents of this message may be privileged and confidential. Therefore, if this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Please consider the environment before printing this e-mail |