Is it possible to convert a standard PHP based widget integrated with google maps API to a flash based widget? If yes, what are the ways?
I expect it will generally be a manual process, because the code styles are so different, code-to-code conversion would be likely to be difficult/fragile/error-prone. The only automatic way that I could conceive of is a html-to-flash-ui conversion, which would get you a static look or prototype to start with, but wouldn't help you in the creation of the active/reactive/dynamic elements of the new flash widget.
A quick google search brings up a few paid references to html to flash conversion, as well as a few pages mentioning some libraries that might be worth pursuing, if just as a shortcut to creating a prototype that you would have to refine:
http://drawlogic.com/2008/01/11/as3-flash-to-html-conversion-library-htmlwrapper/
and here:
http://osflash.org/flashml
Since there is one free library, there may quite likely be others as well.
Related
I've got a GA script library, which contains some Google Docs operations that I use a lot (such as specific formatting, heading numbers or specific searches). When I want to use these functions, I currently add a script to the document, that loads the menu builder (in the library), and then add the library to that script. That seems to be the shortest way of using the library across multiple files. I have these questions:
(1) Is there a way in which these library functions can be available to all my Google Docs, without having to load them per document? My understanding is that this is not possible.
(2) Is this correct: The best way to make these library functions available would be to build an extension, and publish this on the Chrome store. (Possibly as 'beta extension'?)
If this is correct, then could somebody point me to a simple step-by-step guide for turning scripts into docs extensions? I've looked around, but what I saw wasn't all that clear. Ideally I'd like to be able to update the extension frequently, as it's still under development.
Thanks!
I have started a crash course of IndexDB API. I have heard from the author that the API is a little bit confusing. Primarily, as we have been working with the promise pattern as this API doesn’t use this pattern. Secondary, there are different wrappers, one of them seems is from Github author’s personal library so I suppose he have created it.
However looking for a different flavor, I found this one: http://dexie.org/. Also supports the Promise pattern. See http://dexie.org/docs/Promise/Promise, http://dexie.org/docs/API-Reference#query-items . It seems “promising”.
Also I found that the IndexDB 2.0 API was created post the video time. It is already being supported since beginning of 2017. From a Mozilla developer, I found since Firefox 51 (Jan 2017) it is already there. And he wrote what’s the differences among 1 and 2 versions https://hacks.mozilla.org/2016/10/whats-new-in-indexeddb-2-0/
So my question is if at this point is better to use the wrapper libraries or to use the native IndexDB API in terms of cross-browsing and support and better practices?
It all depends on what you want to do with indexeddb -
If you are learning indexeddb for your interest or for knowledge then you should go for plain indexeddb. Learn and research as much you can, because it has too many apis and you will have to write code for every type of situation.
You want to use indexeddb in your project and dont have much time to explore indexeddb. You only want to do some database operations and release your project. In this case - you should go for indexedd library. This way you dont need to worry about indexeddb code . You will just write simple code using the library.
For instance : check out this article - https://dzone.com/articles/crud-operation-in-indexeddb-using-jsstore. How a library makes indexeddb so easy.
Hope this will help you.
Are there any advantage of using TVML over custom App (media based App not a game) for Apple TVOS? From what I read from Apple's documentation I could not figure out any such advantage (though it mostly talks about TVML/TVJs).
For iOS (Swift, Objective C) developers, using custom seems like easier, faster and with more possibilities.
I think whatever templates are provided by Apple can be build using UIKit because internally it is UIKit. Right?
[Update]
Let me rephrase my original question as the answers so far are not given any points in favour of custom App. I agree that #shirefriendship has some real valid points in favour of TVML (biggest one is- > App changes possible w/o an App update). Are there any advantages of using custom over TVML? Like anything not in reach of TVML?
Having already built an application using TVML/JS and now working on a native application I would say that the Javascript option is aimed more towards beginners or basic applications.
TVML applications provide an easier, faster way to build standard applications with common features/user interface. We used it to rapidly build a prototype of an application. Now that we've launched the application and it's getting some uplift (featured in What to Watch and Top Free Apps UK) we are now rebuilding it natively to add additional features such as analytics, crash reporting, custom interfaces and other bits to increase re-circulation and custom recommendations.
#shirefriendship's answer provides a good explanation to the benefits of TVML applications and I think this is a good option for beginners, prototype applications or even basic applications.
Native applications provide alot more control over how the application looks, works and feels. Having access to most of the iOS SDK's allows you to do more such as integrating Cloudkit, develop 2D & 3D games and more.
Once we have finished development of our native TV application I'll update the answer with some more information such as development time between the two different versions, features in the application etc.
UPDATE: To answer your second question, yes you can pretty much develop ANY user interface / template using UIKit, the TVML templates provide user interfaces that would be commonly used / quite handy. Using UIKit you could replicate or customize any of the pre-defined templates or build something completely new.
It is true that you have more flexibility with custom UIKit code. With enough time, you could potentially create an app that behaves similarly to a TVML/TVJS app...but why reinvent the wheel?
There are certain advantages to using TVML Templates, even if you are primarily a Swift/Obj-C developer.
TVML templates provide a familiar experience for the user. Have you
ever used the Netflix TV app, or HBO GO, or iTunes? They all use
TVML Templates and have a distinct look and feel to them. This cuts down drastically on design time.
Templates are incredibly easy to implement, even with very little
JavaScript experience. Auto-layout is taken care of for you. Lazy
loading images occurs automatically. The behavior of every UI
element on the screen has already been taken care of by Apple.
The templates are structured yet customizable. Templates are plug
and play, but you can still customize certain aspects of the UI
elements Styles and Attributes
You can host your TVML/TVJS files on a web server. This allows you
to make changes to your app without your user needing to download an
update to your app.
You can mix and match TVML with custom UIKit. Want Custom behavior with UIKit sometimes, but for standard views, you'd prefer a template? Why choose? You can have BOTH in the same app. Check out my answer here that describes how: How To Mix UIKit and TVML Within One App
When in doubt, try it out! Mess around with the Catalog App from Apple and see if you like TVML templates. You might surprise yourself.
MSK
The primary advantage of TVML is that it is all javascript which appeals to a broader base of developers.
Not sure about your second question regarding developing templates via UIKit
I have done a fair bit of Automation programming using Access to drive the operations of other Office programs. This has been straightforward because the references needed are specific Microsoft programs and I get help learning the type libraries from the Developer Reference Help pages and exploring the classes, methods, and properties in the object browser.
I've also used type libraries from Lotus Notes and Adobe Acrobat to integrate specific functions of those programs, but I needed to use SDKs to understand those objects and methods.
Now I'm looking to automate a web browser control in future projects. I can find specific code samples if I search very specific topics, like [vba] http post web form, but what I'm really looking for is a higher-level review of type libraries and active-X controls. I've found snippets of code using SHDocVw and MSHTML, but I am looking for some guidance on which type libraries to use in this area and how to explore other possibilities.
I have used the Web Browser control in Access 2010, which I believe uses the Microsoft Internet controls reference.
Please see the following screenshot for more information. Note the code changes the zoom of the Web Browser so that an image zooms to fit.
http://screencast.com/t/WsqWTlZRnh
The documentation I found referring to the object used is at the following location:
http://msdn.microsoft.com/en-us/library/aa752127(v=vs.85).aspx
Good look…
(I hope this is a valid question)
As I stated in my title, I'm looking for a fairly easy to moderately easy idea for some sort of online raster analysis map. I'm familiar with ESRI and their really awesome API, as I'm hoping to tackle something on that front. I'm also open to using the mapstraction lib.
Does anyone have any ideas for me?
Thanks!!
I'm not sure you mean image rasters or data rasters. This uses open source packages: MapServer and an AJAX client MsCross. It generates data rasters on the server and displays them in the browser. The rasters are contour plots for a plume of contamination in groundwater.
If you are already familiar with ESRI, then you should look at the ESRI Flex API ESRI Javascript API. You can use both of them to fire up Server side Geoprocessing services.
There are so many ways to skin the cat...
You may want to check the Publishing a GeoProcessing Service section of ESRI help
The basic idea is this... you use ArcMap/ArcCatalog to author a Geoprocessing Model (I am assuming you are familiar with this), which you later expose in an ArcGIS Server as a Geoprocessing Service. Publishing a model as a service is pretty easy provided you already have an ArcGIS Server configured - see the links I provided you above.
Then you can either use the free ArcGIS Explorer application to consume that GeoProcessing Service or write a webapp using Flex, or Javascript or DotNet or even python to consume that webservice.
And yeah, don't consume the webservice synchronously - stick with async.
You do unfortunately not write, what exactly you need. Do you want to display maps on a web page or in a application?
In the latter case i would recommend using http://www.openstreetmap.org/ it seems to be a little tricky in the beginning, buts data base gets better and better. A number of renderes exist, which you can integrate into your application.