Next , I realised there’s actually a way to quit smoking without giving up smoking, thus allow the smoker their pleasure and also habit but save him or her from the damaging effects of smoking.

What I am speaking about are e-cigarettes. You can read about most of the negative effects connected with smoking cigarettes and the way an electronic cigarette can help you quite smoking or simply permit you to follow your current routine and acquire your kick without the damaging side effects associated with cigarettes on my web page http://electroniccigarette0.com

P.S. I really hope this will not get deleted because of having a hyperlink to my web-site as I just try to inform and help.

May God bless everybody

Chrissy M.

Agile would say, choose the most important feature and build that, then the next one, so why not build an ordered list of features and do them one-by-one.

1) I think what this idea really shows is that there are two ways of recording interaction. One as your showing, is a more abstract way less defined way (where page relationships are shown but they don't really say how one person goes from one page to another). Second, a more refined way would be to record the detailed interaction (click, hover, typing, etc) as well as giving it a specific position on a page. This idea of less defined / more defined goes 100% fully with what I've been trying to push forward with this product as part of the concept of "flexible fidelity". Namely, designers at times will sketch out work in a less or mote detailed way depending on their state of mind. One quick example of this is the text tool where you can draw a few lines of dummy text very rapidly (low fidelity) but then you can come back to it and give it more detail by typing actual words (high fidelity). So thumbs up for doing this!

2) Having said that. I say the detailed way of recording interactions (with position) as they already occur now, is priority for 0.1. I think we could do this perhaps later?

3) Perhaps you already envisioned it this way, but I think the interaction defined in the detailed way should be automatically visible in this sitemap view, in that both views are always in sync. Earlier on I've also started thinking about the concept of automatically generated site map documentation visible here:http://fluidia.org/wp/2009/03/auto-create-design-...

Having said this, I still feel we need to work more on ironing out the details of representing and recording the detailed interactions of complex interactions such as drags, movement, transitions, delays, durations and timing in the context of the existing experience thread functionality. That's probably priority for 0.1 If someone wants to take this on, that would be great. We could have a more discussion about this if required.

Sounds good?
Jakub