Julia Package for UI development - user-interface

I want to develop a user interface written in Julia, with the following requirements:
Widgets: top menu, tabs, checkboxes, radio button, range sliders, text-fields
Widgets state: enabled/disabled, hidden/unhidden
I need your advice about the best Julia package to develop my GUI (preferable web-based but can also be desktop-based).
Thank you so much,
Sara

Related

Delphi Rad Studio, is there any way to hide GUI components in the gui editor

i was wondering if there was any way that you could hide certain GUI components in the GUI editor, in rad studio. not actually hiding the component on run with .hide() function, i mean just so that i can work on the other components and design. for example if i have a panel that pops up that is reused over and over again with certain elements but that covers my screen i cant work on the other components. is the only solution to create the components dynamically?

Putting a window in main menu xCode

Is there a way to place a window in the main Menu on xCode?
Also, is there a decent way for a beginner to learn objective C to create a User Interface?
You don't put windows on menus, in Cocoa. But you are certainly talking about a "view", which is a general container for subviews, buttons, images and alike.

Where do I find the "Collapsible Panel" Cocoa control in Interface Builder?

I'm trying to add a collapsible panel to a panel I added in the Interface Builder, similar to the one found in Office 2008 and XCode itself.
This is the collapsible panel for those that don't know it:
OS X collapsible panel http://grab.by/3Hqv
Any idea how I can add this to my project? Google hasn't been of much help.
This is most often referred to as a "disclosure view" or "disclosure panel" and usually has to come with an intelligent container view (that grows/shrinks/scrolls correctly with multiple disclosure subviews). There is no such control as part of the API. Most developers roll their own while some use third-party open source.
The Omni Frameworks have one such control that works very well (including "tear-off" panels, etc., if I recall correctly). The drawback: it's a large framework and has a lot of other stuff in it as well.
InspectorKit is another. It's more focused (just the control itself and an IB plugin), but the last incarnation I tested did have a few UI issues with the Interface Builder plugin.
I've also written a framework for handling this: SFBInspectors

Styling a BlackBerry Application to Look Like an iPhone

I am porting an application from iPhone to BlackBerry. BlackBerry apps tend not to look as polished as iPhone, but naturally, I would like to maintain as much polish as I can, without breaking any important UI conventions. Are there any UI components that can help with this?
NB. I am planning to follow all important UI conventions. For example, I will use the BlackBerry Menu instead of a tab bar for providing access to help and some other advanced options.
Links
Make BlackBerry UI Components Look Like iPhone Components
You can extend blackberry controls with custom drawing, or implement own one extending Field class. Also you may draw a bitmap background (skin) for each control state.
See also
UPDATE How to – Implement advanced buttons, fields and managers
naviina - iPhone-style Field for Blackberry
SO - Blackberry User Interface Design - Customizable UI
This is one of those instances where providing the answer to the question you have asked is tantamount to helping commit a crime!
That sounds dramatic but as developers we have a responsibility to provide the user with a good experience - this means an experience that conforms to their expectations and makes it easy for them to Get Things Done!
I know how pissed off I get when developers implemented custom interfaces in desktop applications and there I have an entire keyboard and mouse to help me navigate!
If all I have is a touchscreen or a tiny trackball and buttons then I am going to be even more pissed off.
Unless you are revolutionising user input and design on Blackberry devices - which, no offence, I doubt you are - then stick to the conventions and guidelines for that platform.
Make your software easy to use and easy to learn - do not ask a user to relearn their own platform to use your app!

UX Design for Disabled Controls w/ the Touch Interface

So we're re-designing a desktop application so that it's also usable with thye Touch Interface with Windows 7. We've consulted the UX guidelines.
For some part of the UI, there are toolbox icons that are disabled because of some arcane rules (the software communicates with a hardware device). We disable the actions that aren't applicable (because of some condition) and let the user hover the mouse on the tool icon to see the tooltip explanation on why that tool is disabled.
Since there is no "hover" for the touch interface (windows 7, iphone, ..) what is a better pattern/model for this?
Thanks!
Not an official solution but here's how I'll approach this until a better solution is available:
Make the item look disabled but still be clickable.
Add an overlay icon (of a question or similar) so it looks more than just disabled.
When clicked, display the message that would have been in the tooltip. Preferably in a non modal way and that doesn't require acknowledgement.
One option is to leave the control enabled and show a message when it is clicked to say why it won't do anything. However as stated in 'Disabled Menus Are Usable' this throws away valuable information for an experienced user (although this is less of an issue for icons than menus as there are usually less icons to go through than menus).
Another possibility is to provide a control like the click for help tools that were popular a few years ago. The user would first click on the 'why is this disabled' control, then click on the control that is disabled. This is however a rather clunky solution.
Another problem with toolbox icons on a touch interface is that the tooltip text is often essential as it is often impossible to convey complex/domain-specific actions with an icon. i would imagine many users on a touch only device will just use the menus instead as they can work out what they will do.

Resources