I am looking for documentation for Ace to do "Floating UI" , i want to to like facebook "Chat Heads". So far there is no documentation only mentioning coming soon , which means avaliable but undocumented right?. Is it already available in github latest master?
They decided to close the support for this project:
As of December 2016, this project is no longer maintained by Microsoft. We built ACE to provide developers with an “escape hatch” to access native code from within JavaScript. After nearly a year in production, we learned that most developers are satisfied with the access granted by Cordova’s Plugin Model. Thus, we’ve discontinued active development. We appreciate your interest in the project and hope you found it exemplary of Microsoft’s commitment to experimentation and open source software. if you're interested in continuing this project, please feel free to fork it. As of December 2016, we will no longer monitor or respond to open issues. You can keep up with other projects from Microsoft’s Cordova team by visiting http://taco.visualstudio.com. Thanks for your support!
I was also looking some plugin to implement "chat heads" in Cordova, without any luck :(
Related
Fiware Cepheus home page says that its branch is archived and 'read only' now.
https://github.com/Orange-OpenSource/fiware-cepheus
So does it mean:
1. There would be no future support and development in this community?
2. As alternative we should use 'Perseo' as its similar in functionality
https://perseo.readthedocs.io/en/latest/
In general, archiving a GitHub project means that "the project is no longer actively maintained.https://help.github.com/en/articles/about-archiving-repositories
The Fiware Cepheus page also states that "no new features will be added, nor issues fixed by the original team." So this means option 1 is the answer to your question.
There exists 21 forks of this project, so perhaps the community is moving over to one of those?
I am not familiar with 'Perseo', so I cannot tell you if option 2 is a good solution or not.
Yes, further information can be found in the FIWARE 7.4 Release Note
As announced at the Porto Global Summit 2018, five generic enablers
were placed under analysis and have subsequently been removed:
Proton, 3D-UI, FiVES, Cepheus, Aeron IoT Broker
Perseo is the now the
preferred generic enabler for complex event processing, replacing
Proton and Cepheus. 3D-UI. FiVES and Aeron are no longer seen to be a
good fit with the FIWARE project.
If you want to use Complex Event Processing you are left with two choices:
Convert your project to use Perseo and continue to enjoy community support and development.
Continue to use an archived CEP processor, fork it and make further bug fixes on your own.
Recently added Firebase Storage and Authentication to my Unity project. I work on Windows, have a single Unity Pro License, and want to export my App for iOS, as I have done many times before in this dev process.
However, since the addition of Firebase, I'm told I apparently can't export my Firebase-Enabled Unity project for iOS without swapping Unity to an OSX device (which I don't have in comparable quality).
I've noticed a singular thread here where a supposed workaround was discussed, but can't seem to pull it off myself:
"The plugin that comes with firebase depends on cocoapods to handle
transient dependencies. If you look at the Assets ->
PlayServicesResolver -> IOSResolver -> Settings
You can configure it to generate the podfile but not do the remaining
steps." - from user johnb003, March 18th 2017.
Can't seem to find the configuration settings described here. Scoured the forums/communities for solutions, but no results elsewhere.
So, that said, any other Firebase user have a workaround for this issue? I adore the collective Google has put together with their product, but I can't really afford to invest in another Unity Pro License just for the sake of working off of my sub-standard Macbook. Thoughts?
Looks like there's a Google Github project, Unity JAR resolver, describing how the Unity Play Services Resolver works for each target platform.
The documentation is pretty extensive, and solutions are use-case specific, so I can't give you much help on specific podfile settings, but hopefully you can sift through it yourself.
I notice Google Play has flagged my AR apps developed in metaio with this message:
Security alert
Your app is using a version of OpenSSL containing a security vulnerability. Please see this Google Help Centre article for details, including the deadline for fixing the vulnerability.
Security alert
Your application has an unsafe implementation of the WebViewClient.onReceivedSslError handler. Please see the alerts page for more information."
I'm hoping it's an easy fix, such as replacing DLL files. Seems I have till July 11th to sort it.
Anyone had this problem and resolved?
Thanks
PS. I use metaio creator, output to arel, copy that output into an app folder template I created which I run through Android Studio/Xcode to generate the final build.
In case you are looking for alternatives, Wikitude came up with a fix a few days ago: http://www.wikitude.com/blog-sdk-update-openssl-upgrade/
Cheers!
Wikitude team
I am about to build an extension where every user has
to grant access on his Evernote account.
I am a bit confused about all this authorization thing,
so I would be glad if someone could give me any advice
about if I can use OAuthorizer on this extension or
whatever he thinks is good to know about it.
Thanks!!
You can consider using OAuthorizer, but I recommend you look into alternatives (and report back if you find them!).
I am using OAuthorizer in version 1.9 of my goo.gl lite extension.
When 1.9 was reviewed, the reviewer expressed concern that I was including another extension within my own (as well as a secondary issue with synchronous HTTP requests within OAuthorizer). I have not resolved these issues yet myself.
Ideally, extension authors could just specify an OAuth library as a dependency, and it would be installed automatically, without requiring copying the library in, or multiple copies if the user had multiple OAuth-using extensions.
In the meantime, "copy it in" is the only option I'm aware of.
Another issue is that OAuthorizer does not seem to be actively developed. The last commit of mozilla/oauthorizer was on Jan 23, 2012. There may be a better or more actively developed library out there.
I have used Symfony 1.4 since it's release, but I now have the option to upgrade to Symfony2 for my next project. Does anyone have any experience? Is anybody currently building a production app on Symfony2 or have in the past few months?
EDIT: yes, Symfony2 website has been put up with a clear message saying the framework will be released tomorrow! There is no 'beta talk' but it does clearly state on the installation page that you should use 1.4 for new projects.
EDIT: somebody voted to close because this question is apparently 'too localized'. Is that not what tags are for?!
Symfony2 should be released in March and I'm guessing it should be in the next few days. The Preview Release always had a note next to it that it is not ready for production. I cannot tell how much is that really true and how much is that just the usual "beta talk".
If you've noticed, they changed the symfony2 page that now doesn't go to the preview page but to the symfony.com instead. Also some new tutorial(s) came up. And the download page shows a promising "Will be available tomorrow" message!
I tried out playing around with the symfony2 sandbox but before porting my application to it, I've decided to wait for the release version. If your project is not pressing, I'd suggest the same. Should be around the corner.
Just my two cents ;)
EDIT: Btw, if you look in the blog, you can see that
The public API of Symfony2 will be
frozen in just a few days. Therefore,
this week developers committed some of
the last big impact changes to the
code repository: the Response was
removed from DIC, CompatAssetsBundle
was removed in favor of AsseticBundle,
and the boostrap files were also
removed.
This can only mean a stable version out soon!
I would say yes, as long as you're aware that it's a preview release and take the necessary precaution i.e. keeping an eye on the error logs.
There are alot of sites using symfony2 in production including the VPS control panel at ServerGrove and OpenSky (developed by the creator and main contributor to doctrine orm and odm projects).
The Release Candidate comes this month sometime, which signifies the API becoming stable! Hooray!
This link from the Symfony2 blog outlines the road map for the Symfony2 release.
There's also the Symfony2 Bundles site which is a collection of bundles that already exist for Symfony2
They said it will be available soon.
But you already can download it from github and start learning it and migrating to it. I've been doing that since December last year and the only problem was changes in API. But now it must be more stable and it's safe to migrate to it.
The 'is not ready for production' note meant no support and no guarantees that everything works and tomorrow something won't change. And if it changes, it was your problem to find out what and how.
While the original plan was to release a stable release candidate last week around the Symfony Live conference in Paris, it was announced there that it would be delayed for what I guess should be at least a couple of more weeks, which I agree is a good thing.
That means that the API is not stable yet and might change, and that those changes might break BC. The standard package which is now available for download on the new website is a PR like the previous releases were.