
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Hello, and thanks for your interest in Dynein in-app user feedback plugin for XAML Windows Store apps.
I. Introduction
The plugin is part of Myelin in-app feedback management solution, which is a web service based at https://www.tfp0.com .
You'll have to register and get an API key before you can fully integrate the plugin into your app. This project is in
active development, and we welcome any early adopters willing to try it. We especially welcome any feedback, both
positive and negative.
The registration is open to anyone and is currently free.
II. Getting started
You may download a sample package that contains a page that is hooked up to invoke the plugin. The package is called Timefork.DyneinXaml.Sample.
Getting started should be relatively straightforward. You only need to do three things:
a) get your API key at http://www.tfp0.com (requires registration). b) during your app startup, initialize the plugin with the API key. The syntax is as follows (this is where your API key is used):
Dynein_Xaml.Dynein.Initialize("00000000-0000-0000-0000-000000000000");
You need to do this once per app start, and it has to be done before the user gets a chance to use the charm bar, and after Application object has been constructed. Good places to do it include App.OnLaunched() or App.OnWindowCreated();
c) Create an extra settings option for your settings flyout, and hook it to Dynein launcher. The syntax is as follows (all code is in C#):
eventArgs.Request.ApplicationCommands.Add(
// arg1: command id (more or less arbitrary)
// arg2: text to use for your custom menu selection
// arg3: command handler that executes when the option is selected.
new SettingsCommand("FeedbackId", Dynein_Core.Lang.UiCommandLabel(), new UICommandInvokedHandler(Dynein_Xaml.Dynein.Launch))
);
and the proper place to do this would be the callback for CommandsRequested. Here is the pattern suggested by an official MSDN sample for customizing settings commands. This goes into you app.xaml.cs (App class implementation):
protected override void OnWindowCreated(WindowCreatedEventArgs args)
{
SettingsPane.GetForCurrentView().CommandsRequested += OnCommandsRequested;
}
private void OnCommandsRequested(SettingsPane settingsPane, SettingsPaneCommandsRequestedEventArgs eventArgs)
{
// {any custom setting options you may implement will also be registered in this function}
eventArgs.Request.ApplicationCommands.Add(
new SettingsCommand("FeedbackId", Dynein_Core.Lang.UiCommandLabel(), new UICommandInvokedHandler(Dynein_Xaml.Dynein.Launch))
);
}
Some of these types are from Windows.UI.Popups and Windows.UI.ApplicationSettings namespaces, so make sure you have appropriate "using" directives.
III. JavaScript apps
We also have a feedback plugin for HTML apps. The package is called Timefork.DyneinHtml, and has a companion sample package Timefork.DyneinHtml.Sample . You can also download required files manually from https://www.tfp0.com/s/windows8 .
IV. Support
For support or other inquiries, send mail to
support@timefork.com
=======
Regards,
Timefork team
FAQs
Unknown package
We found that timefork.dyneinxaml demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.