(I’m doing a brain dump here, no pressure!)

Please consider:

* Page navigation tree (left hand side)

* Jump to page dropdown (top/bottom of page)

* Tooltip property for all supported elements (displayed when hovering over item)

* .HTML file ‘template’ – placeholder tags you define are replaced in the .HTML – this allows us to style/customise page as we want. e.g. tag ‘@@@Body@@@’ would be substituted with core pages data.

I see you use a lot of positioning so this looks like it would require a bit of a rework though..

3 answers

Thanks Tim 🙂

Page navigator is already planned, it may not be the same form but the feature will be there.

As for the tooltip, we prefer user to implement it with behavior editor. That will be easy: handle Mouse Over and Mouse Out event and show / hide a balloon element.

About the html ‘template’, I understand your wish to have more control to the html content, but we could not open this interface to users since the html structure is the base to ensure the simulation works. ForeUI can simulate not only website but also desktop apps, the generated html code is for preview or usablity testing, it is not supposed to be used as a final code.


Hi Xavier,

* Tooltips
Sure, I can do actions, but think about the pain when you want to have tooltips for a lot of elements on a lot of pages.
Perhaps you could add a ‘Set Text’ operation for the Balloon and Post-It elements so I can have only one on the page and change text as necessary via actions.

* Template support

(This is a continuation from the previous post on the standard javascript files).

Here’s what I want to do to put my all my feature requests into context:

1. Do UX prototype in your great tool
2. Generate DHTML
3. Deploy DHTML to a web site for other people to review and provide feedback on
4. Take feedback and refine system
5. Do loop until done

Now, what I need to do is wrap the generated DHTML in an interface that facilitates this collaborative process, and I’m working on a design for that now.
Template support would make this a lot easier as I would implement this framework in the template and your stuff gets ‘merged’ with it.

Have a think about it, but it is important to consider what happens after the DHTML is generated i.e. who is going to look at it, how it is going to be used to refine the UX design etc.

In the meantime I will come up with a tool to do it. is an example (not a great one though) of the sort of collaboration that I’m heading for. The key is an integrated experience for designers as well as reviewers.

PS I don’t think anyone intends of using your code as a development base 😉



Good idea about improving the Balloon and Post-It elements, a “Set Text” action is really needed.

About the template thought, actually we are considering the same use case as you mentioned. I guess you are trying to implement a widget for feedback collection, just like the widget provided by this GetSatisfication site. I really think that’s a good idea, and we may provide such a widget too. As for integrating the widget to the generated DHTML, we need to find out an approach. Doing html content insertion or replacement with the “export post command” is a way that you can take now. Using tags for html content replacement… it works but I just can’t imagine how to implement it in the tool.


This question is now closed