ForeUI is an easy-to-use UI prototyping tool, designed to create mockup / wireframe / prototypes for any application or website you have in mind.
ForeUI
Home / ForeUI Blog /

All posts in Uncategorized

April 11, 2010

ForeUI V2.20: Zoom In and Zoom Out

by

Hi everybody, it is Monday again 🙂   This time we bring you the zoom in/out feature, which will help you a lot when you want to tweak the details of the wireframe or preview the whole design.   The V2.20 also contains some enhancements and bug fixings (see below).

Zoom In / Out

This feature is requested by Jeffrey Werner about 6 month ago, and we also received similar requests from other channels (email, twitter etc.).  Now you can choose the zooming scale from the list at the bottom right corner, you can also input any percentage value for zooming:

 It is also possible to change the current zooming scale from the menu:

As you can see in the popup menu, you can use hotkeys to change the scale as well:

  • Ctrl =: Zoom In (Cmd = in Mac OS)
  • Ctrl -: Zoom Out (Cmd – in Mac OS)
  • Ctrl 1: Zoom to 100% (Cmd 1 in Mac OS)
  • Ctrl 2: Zoom to 200% (Cmd 2 in Mac OS)
  • Ctrl 3: Zoom to 300% (Cmd 3 in Mac OS)
  • Ctrl 4: Zoom to 400% (Cmd 4 in Mac OS)
  • Ctrl 5: Zoom to 50% (Cmd 5 in Mac OS)

Smartly Update Custom Event Name

This is quite useful enhancement.  When you duplicate an element with some custom event handlers defined, if the custom event name contains the id of the element, the id part will be replaced with new id automatically.

This is quite useful if you need an element has its exclusive custom event:  just use the element id as prefix of the custom event name.  You can pack such an element into custom element, thus it can always handle its own event, no matter how many instances are created.

Here is an example.  It is an interactive slider element (you can download it from the community).  It has its exclusive custom event “TextBox_Slider_AdjustPos”, which starts with the element id “TextBox_Slider”.  So you can create as many instances of it as you want and they will not interfere each other.

Text Editor Placement

In previous versions, the text editor for editing text element is not allowed to exceed the bounds of the plot.  That’s not reasonable and inconvenient.  Now we improve it a little bit and don’t restrict the text editor placement so tough:

Other Enhancements:

  • Ajust the text positioning for all text elements.
  • Do not bring the progress window to top when exporting in progress.  (Thank Remco Douma’s suggestion)
  • Show warning message when trying to load a plot created by higher version.  (Thank Tim’s suggestion)

Fixed Bugs:

  • Bug_0180: Set the date of Calendar element to the last day of the month, all buttons after the date will be filled incorrectly.
  • Bug_0181: Arrow Line element is not rendered properly in simulation.  (Thank Jeremy Kerr for reporting)
  • Bug_0182: TextBox with initial invisible state can not really become visible via “Change Visibility” action.
  • Bug_0183: Add custom element to user-defined element category and restart the software, the category will be lost.  (Thank pohldoug for reporting)
  • Bug_0184: “Set Global Cursor” action does not work for Rectangle and some other elements since V2.17.   (Thank Jeremy Kerr for reporting)
Feature | ForeUI | Uncategorized | Update
| |
March 31, 2010

Simulate Drag and Drop with ForeUI

by

From V2.17 ForeUI supports the drag and drop simulation.  This post will introduce how to make element draggable.  Just remind that if you want to simulate a draggable window, that will be quite easy: just check the “Draggable” option for the Window element.

From V2.17 all elements can become draggable.  What you need to do is to handle the mouse events properly.

Before going deep into the details, lets take a look at the analysis of drag and drop behavior (drag from P1 and drop to P2):

During this process, there will be three mouse event triggered orderly: Mouse Down, Mouse Move and Mouse Up. To simulate the drag and drop behavior, we need to handle these mouse events in this way:

  • Mouse Down:
    • Mark the current status as “dragging”.
    • Cache the current location P1 as the dragging start point
    • Cache the current location of the element that being dragged as the element origin
  • Mouse Move:
    • Calculate the current offset against the dragging start point (P1), and move the element base on its origin and the offset.
  • Mouse Up:
    • Mark the current status as “not dragging”.

In the community you can find a Draggable Container custom element. If you place it in your plot, it will become draggable in simulation. Here is an example.

Actually it is a TextBox element. It becomes draggable because it handle mouse events as above. Here is its behavior definition:

As you can see, the dragging status, dragging start point and element origin are stored in global properties. The most important action is the “Move Element” action, it move the TextBox to this new location:

NewX = ElementOriginX + CurrentCursorX – DraggingStartX

NewY = ElementOriginY + CurrentCursorY – DraggingStartY

One thing should be noticed is the three mouse events are not fully the same than those we mentioned before. The “Mouse Move” is replaced by “Global Mouse Move”, and the “Mouse Up” is replaced by “Global Mouse Up”. Let’s make a comparation for these events:

Events
 Native Mouse Event Global Mouse Event
Mouse Down
 Mouse is pressed on the element. Mouse is pressed anywhere.
Mouse Move
 Mouse is move on the element. Mouse is moved anywhere.
Mouse Up
 Mouse is released on the element. Mouse is released anywhere.

From the table above you can see the “Mouse Move” and “Global Mouse Move” is quite similar, but the global event will be triggered no matter where the mouse cursor is. Here is an example to show the reason to use “Global Mouse Move” and “Global Mouse Up” instead of “Mouse Move” and “Mouse Up”:

Let’s say we have two elements: A and B. B has a higher z value. When we drag element A towards B, B will cover A since B has higher z value. When this situation happens, element A can not receive the “Mouse Move” and “Mouse Up” events since element B intercept them. To avoid this situation, we should use “Global Mouse Move” and “Global Mouse Up” events.

Once you understand the mechanism to simulate drag and drop, you will find that all elements can be dragged if you’d like to. Here is an example for drag and drop simulation, you can download its .4ui file from the community.

Feature | ForeUI | Uncategorized
|
March 28, 2010

ForeUI V2.17: Drag and Drop Simulation and Enhanced Tabs

by

This biweekly release bring us the ability to simulate drag and drop in prototype.  Also it provides the enhanced Tabs and Vertical Tabs elements.  There are other new features, enhancements and lot of bug fixings, please read on.

Drag and Drop Simulation

Now with ForeUI you can simulate the drag and drop behavior in your prototype:

This powerful feature is suggested by snortch.  Since drag and drop can be described as a procedure like this: Mouse Down->Mouse Move->Mouse Up, we need to handle these three mouse events.  Each mouse event can have “Native” and “Global” versions:  The (native) Mouse Down event will trigger only when the mouse is pressed on the element;  The Global Mouse Down event will trigger no matter where you press the mouse.  The situation exists for other mouse events as well.  So we have 6 new mouse events:

  • Mouse Down:  Mouse pressed on the element.
  • Mouse Move:  Mouse moved over the element.
  • Mouse Up:  Mouse released on the element.
  • Global Mouse Down:  Mouse pressed at any place.
  • Global Mouse Move:  Mouse moved anywhere.
  • Global Mouse Up:  Mouse released at any place.

For simulating a drag and drop, we just need to pick 3 of them to handle.  A typical case for dragging an element to move is: Mouse Down->Global Mouse Move->Global Mouse Up.

In the mouse event handler we need to access the current cursor position, so the {Current_Cursor_X} and {Current_Cursor_Y} global properties are provided. 

We understand that simulating drag and drop is not very easy, so we submit a Draggable Container custom element and a Drag and Drop Example plot in ForeUI user community.  You can use the Draggable Container directly when you need to simulate a single draggable object, or you can reference the example if you need to simulate more complex cases.

Enhanced Tabs / Vertical Tabs Element

From this version, the Tabs and Vertical Tabs elements support icon in each tab, and you can also specify the height of the tab.

Re-Edit Custom Element Content

In previous versions, once you create the custom element, you can change its information later, but no easy way to edit its content.  Now things become easier:  just click the “Edit Element” button in the custom element information window, you will open the custom element in a new tab.  After that you can edit the custom element like a single-page plot.

New “Key Up” Event

This event will be triggered when any key on keyboard is released.  It will be useful if you want to catch the inputing text in edit box, the Key Down event can not do the job as the value of edit box will be updated after the Key Down event (and before the Key Up event).

Other Enhancements:

  • Support copying/pasting hex color value in color picker. (Suggested by Ulrich)
  • Commit data when page title and page note edit field lose its focus. (Suggested by Tim, Remco and Ulrich)
  • Show error message when pressing Ctrl+D to call action editor for a selected group.  (Suggested by Ulrich)
  • List recent plot files in “File” menu.  (Suggested by Remco and Tim)
  • Can configure the maximum number of recent file records.
  • Change the menu structure for Mac OS.  (Suggested by Remco)
  • Change some menu hotkeys for Mac OS. (Suggested by Remco)
    • SHIFT+CMD+Y: Slide Show
    •  SHIFT+CMD+Z: Redo
    •  SHIFT+CMD+S: Save As
    •  CMD+Q: Quit ForeUI

Fixed Bugs:

  • Bug_0166: TextBox element can not restore visibility after hidden by its container. (Thank Ulrich for reporting)
  • Bug_0167: Press ENTER after changing plot size in plot configure window, the window is closed but the changed is discarded. (Mac OS only.  Thank Remco for reporting)
  • Bug_0168: Can not add image that smaller than 10×10 into image dock (while the minimum image size should be 5×5). (Thank Andre for reporting)
  • Bug_0169: Modification will be lost if saving on a read-only plot file, no message is shown. (Thank Steffen Neumann’s report via email)
  • Bug_0170: Use ComboBox to switch page, the popup list will not be hidden automatically in IE.  (Thank Herve.Seger’s report via email)
  • Bug_0171: The selection of popup list in ComboBox should be cleared after hiding the popup list. (Thank Herve.Seger’s report via email)
  • Bug_0172: In Mac OS X, after closing the about dialog in ForeUI menu, another “V1.00” about dialog will pop up. (Thank Remco for reporting)
  • Bug_0173: Saved .fce file contains inconsistent page id.
  • Bug_0174: Element categories with small button will not update its style when UI theme is changed.
  • Bug_0175: Input file name without “.4ui” suffix for new plot file, the recent file history will save an incomplete record.
  • Bug_0176: After clicking the “Ok” button in settings window, it always ask for restarting ForeUI, even there is nothing changed.
  • Bug_0177: The thumbnail for newly added or loaded custom element can not be updated when UI theme is changed.
  • Bug_0178: The scrollable range in element category is too big when displaying small element buttons.  (Thank Ulrich for reporting)
  • Bug_0179: The scrollable range in element category is not updated after a filter keyword is entered.  (Thank Ulrich for reporting)
Feature | ForeUI | Uncategorized | Update
| | | |
March 14, 2010

ForeUI V2.15: German Language Supported

by

Hello friends, there are two weeks elapsed since the V2.12 relased.  So it is time to rollout a new version 🙂  We will try to release new version for every two weeks.  I think two weeks is a suitable duration as the update will not be too small or too big, also users don’t have to update the software too frequently.  The update today includes German language support, new event,  new property and some enhancements and bug fixings.

German Language Support

Here we must thank Marcus Barkhahn for the translation.  He contacted us about two months ago and asked for this task, and finished translating the 1400+ sentences himself.  Thank you Marcus Barkhahn, with your help ForeUI supports Germany language now!

 To change the current language, just go to the settings window (menu “Advanced->Settings”), and choose language in the drop-down list under “General” tab:

Press Shift + Arrow Key to Nudge Element

This feature is requested by Danm.  Now you can hold the Shift key to accelerate the moving of element with keyboard.

If you need to change the step length of movement when Shift is pressed, you can go to menu “Advance->Settings” and change the value under the “Edit” tab:

Icon in Menu Bar

This feature is requested by Ari and daniel.goertzen.  Usually the menu bar has no icon but Mac OS is an exception, also we need icon in menu bar when creating wireframe for website.

Auto-Fit the Screen of Mobile Web Browser

We take the inspiration from Tobias Severin’s question.  By adding the meta declaration in the exported DHTML, the mobile web browser will zoom the page properly after the loading.  So if you design a 320×480 wireframe, you will get the 1:1 simulation in iPhone Safari.

This enhancement is not only for iPhone, Android system can also take the benefit.  The two pictures below shows the effects on Google Nexus One.

DHTML Exported with ForeUI V2.12 or Lower

DHTML Exported with ForeUI V2.15 or Higher

Changing Workspace Location

This feature is requested by pgbw.  This feature is useful when you don’t have enough space in your user folder.  Also it may solve the issues caused by non-native workspace.

Other New Features:

  • New “Element Initialized” event.  The event is triggered when the element is initialized.  It is similar with the “Page Loaded” event for page.
  • New “Current_Page_Title” global property.   The global property to represent the title of current page. (Requested by Tim)

Other Enhancements:

  • Right-clicking item in action editor will select the item before showing context menu.  (Requested by Tim)
  • Remember the recently used case type in Switch Branching editing.
  • Set property action supports setting numeric value.
  • Add a button for custom element creation in floating tool pane.

Bug Fixings:

  • Bug_0160: Temporary folders for elements in user defined category is not removed from workspace after closing ForeUI.
  • Bug_0161: Modify the action for group member, the modification will be discarded after moving the group.
  • Bug_0162: Renaming the custom global property should also update them in expression.
  • Bug_0163: The properties in the message of User Decision Branching are not updated when properties are renamed.
  • Bug_0164: Select an element that supports image, drag an image from image dock to the element, the floating tool pane should be restored after releasing the mouse.
  • Bug_0165: Change icon command for Tree/List/Menu can not undo correctly.
Feature | ForeUI | Uncategorized | Update
| | |
February 28, 2010

ForeUI V2.12: New Document and Bug Fixings

by
1

As the first update after the long leave, this version includes 14 bug fixings.  Although no new feature is provided, the following news is still exciting: A brand new ForeUI document is available!

New Online Document

As usual you can launch the document via the menu “Help->Online Help Content”, that will bring you to the ForeUI document page.  But you will see the content of the page has been changed completely.  The new document introduce all things about ForeUI systematically.  No matter you are beginner or advanced user, you will find the document very helpful.

ForeUI Online Document

Bug Fixings

14 bugs have been fixed in this update.

  • Bug_0146: If a folder is nested under a page, it can not be removed. (Thank r10k for the reporting)
  • Bug_0147: There is a delay when start drag selecting. (Thank r10k for the reporting)
  • Bug_0148: The height of Calendar header is significantly reduced in simulation if the calendar is big.  (Thank Remco Douma for the reporting)
  • Bug_0149: Double-click the image in group can not change its image source.
  • Bug_0150: Group member A covers B, B may be hidden if A is set to invisible in simulation.
  • Bug_0151: Can not get the specific cell value of table in simulation.  (Thank Justin for the reporting)
  • Bug_0152: Empty table body can not be painted in simulation.  (Thank Abhishek Misra for the reporting via email)
  • Bug_0153: When dragging window element that contains element group, the group members can not be moved correctly.
  • Bug_0154: The entired Window element are draggable in simulation, it should be limited to header only.
  • Bug_0155: Select a group and press Ctrl+D, that allows adding behavior to group (which should be disabled).
  • Bug_0156: Should not allow deleting the page if all other pages are nested under it.
  • Bug_0157: If page B is nested under page A, remove page A, then undo will meet error.
  • Bug_0158: “Change State” action is not listed for TextEditBox element.
  • Bug_0159: Invisible element in group should be painted semi-transparently in design phase.

Slight Enhancement

 This version also include a slight enhancement: move the “From Image File…” menu item to top when choosing image.  This is requested by Ulrich and we think it is reasonable: moving cursor to the bottom may trigger the icon libraries dispaly one by one, which is annoying.

ForeUI | Uncategorized | Update
1…678910…21