closed
Public

Announcement: http://www.foreui.com/blog/?p=643

Summary:

New Feature: Table element supports content scrolling

New Feature: Allow setting table cell alignment separately with “” at the beginning of text.

New Feature: New “Set Cell Value” action for table element.

New Feature: Table/List/Tree/Tabs/VerticalTabs elements support “Set Selected Index” action.

New Feature: Input the action target element id directly.

New Feature: Invoke post commands after DHTML exporting.

Enhancement: Avoid selecting header of table element in edit mode.

Enhancement: Press Backspace to delete element for non-Mac system.

Fixed Bug_0120: Main window may be hidden when click the action button on page management window.

Fixed Bug_0122: Calendar element is not displayed correctly in FireFox.

Fixed Bug_0123: Tabs/VertcialTabs/Tree/List/Table elements should invoke the handler for “Selection Changed” event when default selection is changed.

Fixed Bug_0124: Sometimes Page Up/Down can not switch page in simulation after clicking some element.

Fixed Bug_0125: List/Tree element without selected item is not painted correctly in simulation.

4 answers

Good work Xavier, please consider adding Post Build command support to .4UI file as I may not want to do it for every file I export.

#1
  1. Hi Tim, can you give me more details? What do you mean the "Post Build command"?

Thankyou for adding the ability to execute commands the DHTML export.

I feel it is better to have this defined at the Plot file level instead of an Application setting as I don’t necessarily want it to happen for every single Plot file I export to DHTML. Apologies if I wasn’t clear about this in my original request.

e.g. Build Steps in Properties of a Visual Studio project.

#2
  1. Hi Tim, actually we've considered this before implementing the feature. However the plot file is designed to contain only the prototype data, the building configuration should not be carried by the plot file. The plot file can be used cross-platform, but the command lines are platform related, it is not suitable to contain this information in plot file.

Hi Xavier,

Your call, but unfortunately it makes this feature pretty much useless for me. In my original request I referred to Visual Studio’s External Tools support – these can be triggered manually from within the application. No biggie, it can be triggered outside the app. But a menu option in ForeUI would make it easier.

I don’t agree with your restriction on what should go in the plot file based on platform. Most people wouldn’t share their plot files with anyone else so there is no issue. And even if they did, they simply don’t include post export commands. It’s the DHTML or PDF they are more likely to share.

In fact, with all respect, I don’t like you putting these restrictions because you think someone could mess up the system – this is a product aimed at technical people, and we like to set things up just the way we want them ;)

Look at how many add-ons are available for Visual Studio to customise and extend the environment, build process etc. Anyone of them could potentially break the system, and you just refresh the install in the extreme case.

I really like your app, and I can see great potential for it, and I really like your active development and support, that is why I am being so pro-active in requesting enhancements.

Right now, your system is very cool for doing the UX prototype and generating an interactive version that can be easily deployed to a web site.

For me it’s ensuring the complete prototype+review cycle that I outline in my other post is as simple as possible to achieve that would make ForeUI a killer app, and possibly make you a leader in the marketplace.

Anyway, I don’t want to take up anymore of your time in too many discussions, you’ve got a 2.0 release to get ready :)

Kind regards,
Tim

#3
  1. Thanks for your comprehension Tim. I think you can wait for the command line exporting feature (your another suggestion), it will allow you to integrate ForeUI into your own work flow.

    The post command feature will still be useful, people can use it to do many other things. e.g. submiting exported files to remote site; check in exported files to SVN; test exported file in all web browsers; pack exported files and email to somebody etc. Although it is not the feature you want, I really appreciate your inspiring ;-)

    Actually ForeUI is not aimed at technical people only, it aimed at all people that involved to application design, including technical and non-technical people. Different people may use ForeUI in different levels, but we hope everybody can find ForeUI helpful.

New Feature: Table element supports content scrolling

Fantastic! :)

New Feature: Allow setting table cell alignment separately with “” at the beginning of text.

Nice! :)

New Feature: New “Set Cell Value” action for table element.

Great! :)

New Feature: Table/List/Tree/Tabs/VerticalTabs elements support “Set Selected Index” action.

Cool! :)

New Feature: Input the action target element id directly.

Really nice! :)

Enhancement: Avoid selecting header of table element in edit mode.

Nice! :)

Thanks for some great improvements!

#4

This question is now closed