I want to include designs to my current UI from another UI using QTdesigner
Related
Is it possible to add some links in opportunity navigation pane ? I want to move process (Prospecting (Active), Pre-Quota,...) navigation to marked area.
See in picture what I mean.
No you can't do this. The logic of the process flow is controlled by a workflow which you can change. However, the display within the UI is done by the CRM platform and cannot be changed.
The area that you want to move it to is the Command Bar (it used to be called the ribbon in CRM 2011). This can be customized by adding or removing buttons but nothing as extensive as moving entire sections of the form around. You might be able to mimic some of the functionality of the process flow from custom buttons in the command bar. However, I think it would be unlikely to yield much benefit for the amount of work involved.
I am trying to convert some of my old applications into new Windows Store App design. Some of these applications use Tabs to represent multiple functionalities of the applications. For example, I have a simple English-German dictionary with two main functionality:
Translate English to German
Translate German to English
each represented in a separated Tab.
I have looked around various applications in Metro style and found no equivalent to Tabs.
It is possible to create Tabs manually (using buttons and ...) but they probably had a reason for not including such thing in default elements.
What's the proper way to design such concept in Metro?
You could implement "tabs" in two ways:
Use the top app bar, like Internet Explorer
Provide on-screen buttons in the header of the app (and style them to look like Pivot items in Windows Phone 7)
However, I believe that tabs should be used for independent activities. In your case, most users would want to easily swap from one translation to another. So, I recommend that you implement an interface similar to http://www.bing.com/translator/ or http://translate.google.com/
You could look into using the FlipView control. A typical example showing where this is used is the control used for navigating screenshots in the Windows Store. You can make use of buttons (or whichever control you choose) to change and track the currently displayed item in the flipview.
Reference: http://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.xaml.controls.flipview
Is there a way for one Cocoa application to attach drawer-like windows to another application? We might for example want a terminal drawer that followed around a particular Finder window.
There is a program called DTerm that opens little transparent windows over Finder windows, but one might prefer persistence.
You may want to checkout SIMBL. It allows you to write nifty bundles that are loaded into the application your targeting. If you go along with it I'd reccomend using class dump to gather more information on the application your working with (although Im not sure it would work with Finder)
I m fairly new to working with the TFS SDK and & was wondering whether it's possible to use/write a custom editor 'control' for the work item text editor.. in order to provide more powerful editing capabilities (images, tables etc).
Does anyone know whether this is possible without breaking the rules of physics and/or whether there are already 3rd party solutions out there?
I don't know of any 3rd party tools to JUST do that, I am quite fond of Telerik TFS Work Item Manager though.
It is definitely possible to include a custom control on your work item form essentially displaying images. Here is the offical MSDN for Work Item Tracking Custom Controls. There are some ready-made custom controls on Codeplex: TFS Work Item Tracking Custom Controls.
Lastly a good discussion: Display Image in work item form for TFS. (About really having rich-text within the work items like tables etc. I couldn't find anything)
I need to develop a simple document-based application but using only one window, the documents should open in views separated by tabs.
How can I achieve it?
The answer is you can achieve what you want with a lot of hackery to shoehorn the Cooca NSDocument architecture into a single-window style. But you really don't want to do that. It's much easier to write your own system for document handling from scratch. Start with the Non-document based application template and go from there. NSDocument expects to have its own window (and associated NSWindowControllers).