Render apiary documentation locally with the V4 interactive documentation - apiblueprint

I would like to render API Blueprint documentation in the v4 interactive documentation format locally using apiary-cli or something similar.
I recently started using Apiary. Currently I am generating docs locally using apiary preview but this generates v3 documentation using the old interactive documentation views.
apiary preview --output=./reporting.html --path=./doc/reporting/reporting.apib
I would like to see the new view locally to check my changes before pushing changes to the remote docs view to everyone. Is there any way to view the v4 view without pushing to remote?

The v4 is still in preview. We are in the stage of gathering feedback and progressively adding features to it. This one in particular isn't yet available, but it's on our roadmap.
Meanwhile you can use the online editor, via apiary.io, to preview your changes.

Related

Is it possible to export a google doc using the ?export=pdf option, through a Google Sites link?

I work for a healthcare facility, with which we have a google site that we upload information to, to keep it centralized for everyone. I found this information on the Google Workspace help page, and when I put together my link and test it outside of the site, it works perfectly fine. When I insert it into our Google Site, it fails over and acts like it will download, but doesn't. Any ideas?
If this isn't possible, I have another question. Is there an option to export a published Google Doc using the ?export=pdf option? Our main goal is to keep the forms up to date, without manually changing the link every single time.
Google Workspace PDF Export Info

XD Plugin API and Components

I am trying to write an XD plugin that dynamically populates an artboard with components, but I don't see any mention of components in the XD plugin API. Is it possible to look through the file and find available components and place them on stage? Better yet, maybe even pull a component from a specific file in the cloud?
Unfortunately, it isn't possible to create symbol instances (that's what components are called in the APIs), yet. Here is the explaining quote from the plugin docs:
It is not currently possible for plugins to create a new component definition or a new SymbolInstance node, aside from using commands.duplicate to clone existing SymbolInstances.
(https://adobexdplatform.com/plugin-docs/reference/scenegraph.html#symbolinstance)
There is a feature request open for it in the official plugin developer forums which you can vote for. According to Steve Kwak (Adobe), however, this seems to be problematic due to the edit context, meaning it may still take a while until we get API access to that.
There, unfortunately, also, as of yet, isn't any way to list the available symbols for a document. For the other asset types, this is possible via the assets module (cf. https://adobexdplatform.com/plugin-docs/reference/assets.html), but not (yet) for symbols.
I hope this helps (although it's probably not the answer you've hoped for).

TYPO3 workspace preview not working with forms and HTTP POST data

The following question has been asked in the #typo3-cms Slack channel:
A customer of us wants to use the workspaces feature. Thats working fine. But he cannot test his forms because workspaces are not supporting POST requests. (POST requests are incompatible with keyword preview), does anyone have an idea how to make plugins which are working with POST method testable in workspaces or any other workaround?
Explanation of the scenario and behavior
The check to prevent HTTP POST requests from being executed points back to TYPO3 CMS 4.0 in 2006 when the workspaces feature was introduced into TYPO3 (see accordant Git revision from back then).
Since the workspaces preview link initializes a backend user in an untrusted application context, the check has been used to prevent administration actions from being executed - today one would do that differently and use XSRF protection tokens for that.
The handling of these workspace preview links also was part of a security issue in sprint 2016 with the aim to remove possible security side effects in that regard further (see TYPO3-CORE-SA-2016-012 for details).
There are several possibilities to preview workspace changes:
Preview link from workspace module
In the top-bar of the workspace module in the TYPO3 backend, the preview link can be send to other parties that don't have credentials to access the TYPO3 backend. This mechanism basically leads to the problems with HTTP POST as mentioned above.
This behavior is implemented in the class PreviewHook in either the system extension version (up to and including TYPO3 CMS 7) or workspaces (since and including TYPO3 CMS 8). There's currently no easy way to by-pass the HTTP POST check, except granting possible previewers real and limited access to the TYPO3 backend with a valid user account.
Preview contents directly from page module
Editors that have access to the TYPO3 backend should use the regular preview mechanism of TYPO3 in the page module - this is the same for live versions and workspace changes. The only difference if working in a workspace is, that the website frontend shows additional workspace related widgets to compare changes.
Using this mechanism, the HTTP POST problems mentioned in the beginning of this answer don't occur and e.g. forms can be used without any limitations.
If the previous method of creating the workspace preview link has been used with the same browser already, a cookie ADMCMD_prev has been created which still triggers the preview link behavior and still leads to problems with HTTP POST - even if the regular preview mechanism is used as described in this section. To circumvent that, this cookie has to be cleared manually in the browser.

How to integrate Google tag manager with Xamarin Android?

I want to integrate Google tag manager in Xamarin.
For iOS, there is a documentation on how to do so when consuming Google analytics SDK.
However, there is no documentation at all for Android integration.
Any suggestions?
I don't think you need any Xamarin documentation for using Tag Manager with Xamarin.
Tag manager comes with Google Play Services, so you just need the Xamarin component for Google Play Services:
https://components.xamarin.com/view/googleplayservices
The documentation for Tag manager is here:
https://developers.google.com/tag-manager/android/v4/
As #Andrei suggested, I used in Google play services, although the configuration was not so trivial..
I have created a sample project you can find here to demonstrate how to use Google tag manager in Android.
In short, after you install the SDK, you should call these lines in the your mainActivity class:
var tagmanager = TagManagerClass.GetInstance(this);
var pendingResult = _tagmanager.LoadContainerPreferNonDefault("GTM-XXXXXX",
Resource.Raw.gtm_analytics);
pendingResult.SetResultCallback(new TagMnagerResultCallback(), 2, TimeUnit.Seconds);
And after the callback has been called, you can fire your events like this:
_tagmanager.DataLayer.PushEvent("openScreen", DataLayer.MapOf("screenName", "testScreen"));
You might want to check my post. I explained how to do enhanced ecommerce and if you think could be valuable.
Summary is:
Add Google tag Manager component
Go to Google tag manager web admin, pick android code and go to latest version published. There you should see an option to download a binary file
Name binary as you want and place it inside Raw folder
In Setup or main android class, implement the basic wire up pointing to downloaded Binary in Raw file (This is key)
Create app view event as documentation display, in Tag Manager portal
add basic open screen tracking and watch real time in Google analytics. It takes few minutes to see the data, first time could take up to 24 hours depending on your account
Check my blog post for further details and let me know if still have questions and I will put together the full implementation.
Cheers

Liferay : Any one has updated jquery.tweet.js?

Has any one used and updated jquery.tweet.js for liferay 6.1
after following important note from seaofclouds.com,
Important note about Twitter's API changes
Twitter has discontinued its unauthenticated v1.0 API,
so this widget has stopped working as of 2013-06-11.
Twitter wants your only option for on-page widgets to be
their own Embedded Timelines, but there are workarounds
which involve installing server-side code to support this widget.
Please see this discussion for more details.
If yes, let me know steps to do ?
I am also trying, If done i ll update
Till then waiting for reply, might be save my time.
Thanks
Basic wrapper for Seaofclouds / Tweet.js that incorporates functionality with Twitter's v1.1 API
https://github.com/StanScates/Tweet.js-Mod

Resources