Hi, LeeBB, thanks for the reply. Food for thought...
In no way am I conveying layout with the wireframe. In fact quite the contrary. Just showing as task-oriented perspective of what a page is supposed to do. I find myself using lots of lists to format the tasks descriptions on each page; noting important things in italics or bold, and I find using a wiki's simplified markup (WSML :) )makes this much easier than continually having to go <ul><li>, etc. I do also think a link inline is far more intuitive than ones at the bottom of each page. I found a really nice wiki - http://www.openwiki.com - the site is down now, but navigating with google's right click view cached snapshot worked :-) And the download link worked too (looks like they have a db problem). Sad thing is it works on .asp :-((, but it works *well* (as a wiki of course), and has been very nicely done and thought out. Is open source too. It seems to address your concerns. Although it doesn't display a full site map with all the content (like yours), it does have a table of contents macro, listing all pages in alphabetical order. With a large site, a detailed site map could become unwieldy. I am also using it to convey the development reuirements to my programming team, and sometimes that means putting additional stuff in, which I do in footnotes, which the wiki lets you do. It also has some features, which seem really cool for making wireframes: - In-line versioning so you can see all changes made, *with difference engine*, highlighting changes, and records who made what changes (built-in mini source control!) - Full text search - Macros to include common stuff - I find myself creating the same wireframe content for many different pages. - Table of contents macro (aka site map). I may be abe to edit the asp to show the tables text too. Shouldn't be too hard - Support for customisation of headers and footers (you can do this with Lees by midifying the source). - Having different wireframes in separate virtual directories - often I don't want one client to see anothers wireframe. - Footnotes - Customisable stylesheets Cons: - Uses a database - Difficult to sepearate wireframes, unless creating a new virtual directory. Unfortunately Lee I also found some bugs in your s/w (main one being the parser thinks a line break means start the next page)- which I kludge fixed and sent to you. So, it has some advantages and so does your s/w. For now I am still evaluating which one best serves my needs. Will keep you posted. But give openwiki a try. It really has some cool stuff... Later Steve ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
