Hi, I've been looking at your treeview control and still have some questions. I am looking for a file-system-based site navigation for a public website, and would have to meet a few requirements:
1. I need the final output to be table-less, purely stylesheet-driven (not inline style), accessible html -- preferably a bulleted list. We don't need advanced features like right-clicking, windows ui simulation, drag-drop, etc. Just a clean, simple output that can be read by a screen reader or other alternate agent.
1. I need the final output to be table-less, purely stylesheet-driven (not inline style), accessible html -- preferably a bulleted list. We don't need advanced features like right-clicking, windows ui simulation, drag-drop, etc. Just a clean, simple output that can be read by a screen reader or other alternate agent.
2. One thing the out-of-box sitemap provider will do is to consider the current node to be the parent, so it populates the node structure from the current node downwards. This works until you get to a page in a folder, and then it dumbly considers that page, not its parent folder, the top node. So, you don't see that page's siblings, and you don't get a link back to the parent folder.
We'll use an out-of-box breadcrumb control in conjunction with this to take care of the section context. We would need the provider to populate the folder nodes from the current parent downward, and populate all of the current parent's immediate child nodes. So you would see the current parent folder, any subfolders, and any files in the current folder. The folder names in the nodes are the names of the folders. The page file names in the nodes are taken from the Title attribute of the page file. Like this.
<Breadcrumb> Home > About
About Us (the page is currently showing about/default.aspx)
Introduction (intro.aspx file)
Board of Trustees (board.aspx file)
Jobs (folder path about/jobs)
Introduction (intro.aspx file)
Board of Trustees (board.aspx file)
Jobs (folder path about/jobs)
When you clicked "Jobs" you'd be taken to jobs/ and see this:
<Breadcrumb> Home > About
Jobs (the page is currently showing about/jobs/default.aspx)
Requirements (requirements.aspx file)
Equal Opportunity (equal_opportunity.aspx file)
Requirements (requirements.aspx file)
Equal Opportunity (equal_opportunity.aspx file)
When you clicked "Requirements" you'd be taken to the page and see this:
Jobs (this is now a link to the ../about/jobs/ folder path)
Requirements (requirements.aspx file -- this is the current page)
Equal Opportunity (equal_opportunity.aspx file)
3. The provider should support an arbitrary level of folder nesting (whatever is there, it will find it). It should ideally only iterate through the current context, and should have some soft caching method so that it doesn't have to crawl after the first time unless the file structure has changed. We want to ease the load on the server but we don't want to have to restart the application every time we update the files.
Requirements (requirements.aspx file -- this is the current page)
Equal Opportunity (equal_opportunity.aspx file)
3. The provider should support an arbitrary level of folder nesting (whatever is there, it will find it). It should ideally only iterate through the current context, and should have some soft caching method so that it doesn't have to crawl after the first time unless the file structure has changed. We want to ease the load on the server but we don't want to have to restart the application every time we update the files.
If your software will do this, please let me know.
Thanks in advance,
David Morgan