SAC Input Control - Custom Widget - custom-widgets

I need to create a custom widget Input control for SAP Analytics Cloud basically the same as native but with more customization. The customization part will be pretty simple and I know how to do it, but I need some ideas on how to start implementing this custom widget. I already am working on a dropdown hierarchy custom widget with SAPUI5, don't really like this approach, but I am open to this. If anyone has any idea or experience in building this, I would much appreciate the help/input/ideas.

Related

PowerPoint - how to run a macro automatically?

I'd like to run a macro that sets the zoom to 100%, something like Windows(1).View.Zoom = 100, every time ANY file is opened in PowerPoint. The files are already created, so using a template to set the zoom is not possible. How can I do this?
There isn't really a way (that I am aware of) to do this through a macro or powerpoint add-in. You might be able to do it using a custom web add-in but I don't have enough experience with that to provide an example.
After looking around there have been a few success stories. One of which is creating a custom UI element and then adding an onLoad hook to that.
Here is the thread.
Here is a link to the Custom UI Editor Tool However I had no luck in getting it to work. I believe (This is only my theory) that it is not compatible with the latest .NET framework.
If you do end up trying to do this, here is a link to the xml formatting documentation for UI elements. And a link to a little tutorial related to this.
Sorry I couldn't be of more help. This should at least get you started. If anyone else has a simpler way I would love to know as well.

When to use UI Plugin or PlaceHolder

As far as I have understood so far, one can create a custom (native) UI component by following the guide in the NativeScript UI Plugin documentation
But there is also this PlaceHolder that can be added into the XML and then instantiate a custom UI component to be displayed in it.
So what are the differences between both and when to use each of them?
It's completely your decision. In my opinion, if you are going to reuse the component and want to share with the community then make a plugin. There is no right or wrong answer to be honest :)

MvvmLight and CustomMessageBox

Is there a proper mvvm way to show CustomMessageBox from the view and get callback from it?
This sample is quite nice, but it uses hardcoded MessageBoxButton (only Yes/No/YesNo are avaivable, but i need custom buttons).
This contains lots ofuseful info about Messages in MvvmLight, but DialogMessage is also showing only YesNo sample (also no custom buttons).
Figured out that Cimbalino toolkit (Cimbalino saves the day again!) has quite nice custom messagebox.

Best practices of building composite custom controls WPF

Can You tell me about subj?
For example I need to create new custom control that must be derived from datagrid and toolbar. And I want that new control to expose/propagate properties of base controls in order they to be accessed easily. The only way I know is deriving a class. Then descendant automatically gets all properties of ancestor. But multiple deriving in C# is prohibited, so I don't know how to expose properties and other behavior of second control... Styling and templating of such custom control is also needed.
Thanks!
In WPF inheritance is "out". ;O) Actually, it was complicated before WPF already, but with WPF you get various really powerful alternatives.
For the basic control I thing you'd better go with composition, create some usercontrol and make it contain a ToolBar and a DataGrid. You can then expose these as public properties, if you need to manipulate them from outside.
For special feature additions, attached properties are a very versatile mechanism.
Watching a window from windowsclient.net is a good place to start.
Make sure you understand dependency properties well.
Reading wpf blogs is my best guest for what to do then.

Cocoa Interface Builder's 'Attributes Inspector' like window

I'm making a Cocoa application, and I would like a panel like the 'Attributes Inspector' in Interface Builder. So with big tabs on the top and collapsable/expandable groups. Does anyone know how I can do this?
This is an image of the Attributes Inspector:
Attributes Inspector http://developer.apple.com/documentation/DeveloperTools/Conceptual/XcodeQuickTour/Art/hello_win_attributes.jpg
So I actually want to make a window like the one shown in the image above.
InspectorKit is FOSS on github.
There's no built-in Cocoa controls to do this. You're going to have to write some custom views which replicate the functionality.
There some good advice for creating custom controls in the answers to this question: Looking for info on custom drawing of interface components (Cocoa)
If you need additional help, I recommend you ask smaller, more specific questions explaining what you've tried and what hasn't worked.
I've written some custom classes to do this- it ended up being less work than I expected. I broke it down into two separate components which can be used independently- the first handles the icons at the top and performs the view switching and the second handles the expandable panes:
My code is available at github and is under the BSD 2-clause license.

Resources