Interpretation - Android
Hello
I know who have already tested a million times and the interpretation for 7 Android devices in DPS App Builder option does not work in Galaxy 10 '.
Anyone have this problem?
Thank you
Use strict refunds only for devices of the Amazon, no Android devices such as the Galaxy tabs.
Tags: Digital Publishing Suite
Similar Questions
-
Native Android application / refunds does not
Hi all
I tried to put in place the new native Android app on my tab 10 '' in order to get the real "app-feeling."
Creation and get the App on the Pad works like charm - but it was a pain...
I have developed Android refunds in landscape mode (1280 * 752) and refunds iPad in portrait and landscape (1024 * 768 / 768 * 1024) with a single identity card - which worked very well until I tried to update to the new native application.
While the old library was not fixed to a single display mode, the news starts with the portrait and does not charge any interpretation Android (which are made only for landscape / 1280 * 752) as it doesn't appear that the iPad preview blurred.
Maybe there is a solution or a tip?
Thanks in advance.
Yes, this specific approach does not work with the Android native Viewer. We are looking for the closest match which is larger than the screen size, so let's choose 1024 x 768.
Currently, the only solution is to create a separate publication for these "renditions" Android account and point the Viewer to this account.
I'm working on some changes to App Builder that will make this better, but we won't have that work done in our next release. I hope that we can adapt the rejection after.
Neil
-
After only iOS for a couple of years, as we move into android, thus creating a rendering of 1280 x 800. All surprisingly easy except for two things that work very well on the ipad:
1. audio only "plays in the background to the folio.
and
2. video streaming does not play in full screen (but rather in a very small window in the middle of a screen empty)
Any help or comment on this would be much appreciated.
Thanks in advance.
1. playing in the background at the Folio: this feature is only available on the iPad or the iPhone.
2. see this thread for the full screen problem video http://forums.adobe.com/thread/1407159
-
How to import contacts to android
After I reset my one touch heat e I re - import my contacts from my old nexus of Galaxy, which extends from cyanogen with local contacts.
I can export the ther contacts in different formats - the last time I did, I does in vcf, csv and xml - but only csv has worked to import.
but: all metadata was messed up.
This is my vcard format that I get Android (CSV):
-no name
BEGIN:VCARD\nVERSION:2.1\nN:; Test; ------nFN:Test\nTEL; CELL: 000 - 000\nEND:VCARD\n-with lastname
BEGIN:VCARD\nVERSION:2.1\nN:Tester; Test; ------nFN:Test Tester\nTEL; CELL: 000 - 000\nEND:VCARD\nFiled any not all names and 'CELL' is not interpreted as a phone number, indead all numbers listed as "NULL" (nice to see on every phone call.)
also N and FN fields where not interpreted completely or correctly. After import, I had ~ 10% contacts without name field filled in.
What is the right way to import contacts from an account local android (whithout proprietary components)?
the problem was:
Android has stored contacts in vCard 2.1 format.
by following the instructions here: https://support.mozilla.org/en-US/kb/add-manage-and-share-contacts-firefox-os#w_import-from-phone-memory-or-memory-card, I managed to convert contacts to vCard 3.0 format.
Once the import worked!
-
MacAir slow Yosemite 10.10.5 running. Can anyone interpret this info from Etrecheck?
My system has been Beach balling excessively lately. I recently installed Norton AV, which may be the main issue. I ran EtreCheck, with the following result; someone knows how to interpret it, and I'd do anything other that uninstall Norton? Thank you.
EtreCheck version: 2.9.12 (265)
Report generated 2016-05-16 11:09:46
Download EtreCheck from https://etrecheck.com
Time 01:54
Performance: Excellent
Click the [Support] links to help with non-Apple products.
Click [details] for more information on this line.
Problem: Beachballing
MacBook Air (13 inch, mid 2011)
[Data sheet] - [User Guide] - [warranty & Service]
MacBook Air - model: MacBookAir4, 2
1 1.7 GHz Intel Core i5 CPU: 2 strands
4 GB RAM not extensible
BANK 0/DIMM0
OK 2 GB DDR3 1333 MHz
BANK 1/DIMM0
OK 2 GB DDR3 1333 MHz
Bluetooth: Old - transfer/Airdrop2 not supported
Wireless: en0: 802.11 a/b/g/n
Battery: Health = Normal - Cycle count = 237
Intel HD Graphics 3000
Color LCD 1440 x 900
OS X Yosemite 10.10.5 (14F1605) - since the start time: about 2 days
SM128C SSD APPLE disk0: (121,33 GB) (Solid State - TRIM: Yes)
EFI (disk0s1) < not mounted >: 210 MB
Macintosh HD (disk0s2) /: 120,47 go-go (89,67 free)
Recovery HD (disk0s3) < not mounted > [recovery]: 650 MB
Apple internal memory card reader
Camera FaceTime from Apple Inc. (built-in)
Apple Inc. Apple keyboard / Trackpad
Apple Inc. BRCM20702 hub.
Apple Inc. Bluetooth USB host controller.
Apple Inc. Thunderbolt_bus.
Mac App Store and identified developers
/ Library/Extensions
[loading] com.symantec.kext.SymAPComm (12.9.1f13 - SDK 10.8 - 2016-05-01) [Support]
com.Symantec.kext.FileSecurity [no charge] (12.9.1 - SDK 10.8 - 2016-05-01) [Support]
[loading] com.symantec.kext.fw (5.6 - SDK 10.8 - 2016-05-01) [Support]
[loading] com.symantec.kext.internetSecurity (5.7 - 10.8 SDK - 2016-05-01) [Support]
[loading] com.symantec.kext.ips (3.10.4 - SDK 10.8 - 2016-05-01) [Support]
[loading] com.symantec.kext.pf (5.9.1 - SDK 10.8 - 2016-05-01) [Support]
[loaded] 5 tasks of Apple
[loading] 145 tasks Apple
[operation] 46 tasks Apple
[killed] 16 tasks Apple
16 killed processes lack of RAM
[loaded] 48 tasks Apple
[loading] 135 tasks Apple
[operation] 63 tasks Apple
[killed] 16 tasks Apple
16 killed processes lack of RAM
[loading] com.citrix.AuthManager_Mac.plist (2014-11-18) [Support]
[operation] com.citrix.ReceiverHelper.plist (2014-11-18) [Support]
[operation] com.citrix.ServiceRecords.plist (2014-11-18) [Support]
[failure] com.symantec.errorreporter - periodicagent.plist (2016-05-01) [Support]
[loading] com.symantec.nis.application.plist (2015-09-22) [Support]
[operation] com.symantec.uiagent.application.plist (2013-01-16) [Support]
[failure] com.adobe.fpsaud.plist (2016-04-15) [Support]
[operation] com.symantec.deepsight - extractor.plist (2013-01-24), [Support]
[failure] com.symantec.errorreporter - periodic.plist (2016-05-01) [Support]
[loading] com.symantec.liveupdate.daemon.ondemand.plist (2014-09-23) [Support]
[loading] com.symantec.liveupdate.daemon.plist (2014-09-23) [Support]
[failure] com.symantec.nav.migrateqtf.plist (2015-09-17) [Support]
[operation] com.symantec.sharedsettings.plist (2015-08-13) [Support]
[operation] com.symantec.symdaemon.plist (2014-09-17) [Support]
[loading] com.google.keystone.agent.plist (2016-03-06) [Support]
iTunesHelper Application (/ Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)
Agent application of file transfer Android (~/Library/Application Support/Google/Android File transfer/Android File Transfer Agent.app)
Dropbox application (/ Applications/Dropbox.app)
[ongoing] com.getdropbox.dropbox.17072
[ongoing] com.Google.Android.mtpagent.48312
[loading] 360 tasks Apple
[operation] 136 tasks Apple
[killed] 33 tasks Apple
CitrixICAClientPlugIn: 11.9.0 - SDK 10.9 (2014-11-18) [Support]
QuickTime Plugin: 7.7.3 (2015-10-26)
Flash Player: 21.0.0.226 - SDK 10.6 (2016-04-23) obsolete! Update
FlashPlayer - 10.6: 21.0.0.226 - SDK 10.6 (2016-04-23) [Support]
NortonInternetSecurityBF: 1.11.0 - SDK 10.6 (2016-05-01) [Support]
Default browser: 600 - SDK 10.10 (2015-09-10)
Norton Internet Security - Symantec Corp. - http://macplugin.norton.com/?ext=NIS (2016-02-11)
Flash Player (2016-04-15) [Support]
Norton\nQuickMenu (2016-05-01) [Support]
Time Machine not configured!
28% WindowServer
2% fontd
kernel_task 2%
0% loginwindow
0% SystemUIServer
Top of page process of memory: ⓘ
Com.apple.WebKit.WebContent (3) 971 MB
Kernel_task 433 MB
SymDaemon 172 MB
Com.apple.WebKit.Plugin.64 164 MB
Mdworker (10) 123 MB
29 MB of free RAM
3.97 GB used RAM (524 MB cache)
132 MB used Swap
May 14, 2016, 06:22:40 /Library/Logs/DiagnosticReports/SymDaemon_2016-05-14-062240_[redacted].crash
/ Library/Application Support/Symantec/*/SymDaemon.bundle/Contents/MacOS/SymDaemon
May 13, 2016, 17:33:20 self-test - spent
1. remove the Symantec/Norton software.
2. There is problem of not having enough RAM and RAM is not extensible.
I hope that removing the software Norton will help.
Best.
-
Newbie wanting to AIR w / extensions to native code and the Protocol of Android accessory
My interests include prototyping and very specific to very specific real-world applications of programming solutions. So I bought a Playbook after viewing the quick "prototyping" video in this blog:
http://devBlog.BlackBerry.com/2011/12/BlackBerry-PlayBook-Arduino/
I tell myself I can do cela or something similar with PIC Basic Pro and a Microchip IC. Although it has been nearly six months, from what I can tell, the RIM developers have failed to deliver on explaining how to use native code and the ancillary Protocol Android to connect in series on client's port to the mini-USB of the Playbook.
Is RIM people please, show us how set up the programming environment, use the code, the mini-USB port on client Playbook, the adapter USB (where to buy, what is it exactly?), so we can use the USB client connected to an Integrated Circuit Programmable to connect in series with an AIR running on the Playbook application.
Kenneth Mark Klausner
How this kind of thing is that you have the hardware (Controller USB etc.), and there different registers, buffers, etc. that must be handled. The first layer of software, what made this manipulation, is a device driver. While in some operating systems (Linux, for example), you can write yourself, or port code Besides, material in the PlayBook is accessible only by the drivers as part of the operating system, which means that the RIM should provide their.
These drivers are may be incomplete. We do not know that for some.
Drivers expose a particular interface to the next higher step of the software, an interface that must be respected. This interface is generally quite low, and the driver can support the features that cannot be exposed to third party software, so for this and probably other reasons, we can not directly access (and are prevented by security mechanisms).
There is another layer of software on top of the pilot, commonly called a library. This library is also provided by RIM, as part of the operating system.
This library can be incomplete as well. We do not know the details, but I suspect someone who knows this level of the design of the system and who attended the BB10 Bluetooth and USB discussion group would be able to interpret what they heard there to clarify.
It's this library which provides what we call a bit of hand-wavingly API 'USB '. This is an interface in C language, with a set of data and calls structure function definitions that enable higher level code perform different operations related to USB.
If you want to write a DONKEY, you write about this library, not the level of driver and not material. You have no choice in this matter, as it is applied by the security of the OS.
So to sum up, if we refer to 'USB API' they're talking about essentially the library routines, and it is necessary to talk to this API to get whatever it is the case here. The API can be described in the header files (there is something), or maybe he's going to be an API different than what I see out there. Whatever it is, it is undocumented in other places at the moment, so all who want to enter this need to make much low level experiment (talking to the library).
They can have the documents which cover this and perhaps code samples to talk to the library. If the version of the operating system we have has the incomplete versions or buggy drivers or libraries, this could explain why they have not pushed this documentation and code for us.
I think that I heard that they are gathering input (requirements, use cases, comments) from people in this session. Who tells me that they are still working on some details, and when they are at a stage like that they simply don't tell us publicly where they are, deadlines, or what it will look like when it is done.
And so expect.
-
iPhone 5 rendering on Android devices 16:9
I did an ipad and android with an interpretation mutli-folio application 1024 x 768. Now, I need to adapt this application for iPhones. So I am building 2 new related files: 1136 x 640, and 480 x 320. These refunds will also improve the android app (black bands is more in some cases): devices android 16:9 will logically download the 'return' of the iphone 5.
But I tested my app on two different devices to android 16:9 and get two different results:
-Samsung Ace 4 (4.4.4 android, 1080 x 1920 screen) shows the rendered 1136 x 640 (fullscreen)
-Huawei G620S (4.4.4 android, 720 x 1280 screen) shows the rendering of 1024 x 768 (with large black bands).
Why is it different?
Thank you for your help.
We try to load the correspondence of nearest size that we can, and these screen sizes are different, so different folios get selected.
Fortunately, we have a feature in App Builder to help with this, if you want to ensure that your Android devices will never see the folio 1136 x 640 use rendering feature advanced in the Android app generator. Select 1136 x 640 in the Tablet and smartphone from drop-down menus, rebuild your application, then send it to Google.
Neil
-
Can someone tell me please a tutorial or any information concerning best practices on this workflow? I have created multiple applications for all devices? (or all Apple products reside in one application?) I'm confused about how it works with DPS. We have created only at this stage of the applications for the iPad and Android tablet.
One of my layouts can be used for multiple devices?
I realize, these are all different folios, but I need to see how best to implement. I looked for references but some resources seem there are many versions and I can't use the best search terms to find.
Thank you in advance!
S
You can use PDF 1024 x 768 for all devices except the iPhone. iPhones require their own interpretation.
-
Hello
Our android app shows folios to users on android phones - I guess that the proportions of the phone is the same as the proportions of our folios. But its unrealistic to read magazines on the screen of a phone, and we would like to limit the list of folio (or the application itself) only android tablets.
The Google game store allows us to exclude devices, but only one by one and they more than 7000 on their list of dynamic feature!
They also say the following:
"Availability of device provides a dynamic list of compatible devices, based on the settings of your manifest. For example, if the manifest of the APK file specifies a size of widescreen, the console will reflect the supported devices that can find your application in the Google game. "
which means, I think, that manifest our app Android DPS gives play some information on what devices to allow the application.
Play our Supported Devices limited to 1791 and their strange Machines 7000 while the manifesto seems to play some information.
is there a way that we can limit the size of the screen in our DPS android app? Could we publish the manifesto? probably not, but maybe someone out there has a better suggestion.
(we chose "Use strict interpretation logic" in the advanced settings for the construction of the app).
Thank you
Vauneen
The viewer Android works on phones and tablets and there is no way via App Builder to say "fair tablets. You can publish a folio unique to a different size and put a note telling him that you do not publish content to phones and then with advance refunds ensure that the folio size is the only illustrated on phones.
That said, I encourage you to just let your Tablet problems appear on phones. When we did our native Android application development we used almost exclusively designed by tablet content to test, but almost all our test devices were the phones. Content of the Tablet is surprisingly readable on the phone, especially with the larger machines Samsung as the S4, Note, etc, and we support pinch and zoom so that readers can see tiny text. While trying to exclude Android phones that cut you on a LARGE number of potential readers for your title.
Neil
-
I have an app for iPad/iPhone and another for Android smartphone, BUT both use the same accounts. The Android smartphone has easily taken the iPhone version, resized it and no problem. BUT when I added an iPad (in the same account) the Android smartphone version does just that, the iPad version. Any thoughts? I have to publish the Android smartphone on another account? This means that I need to change the file twice for each account? !! ? !
You use the web App Builder to make your Android app? Or did you build a viewer Android inherited with the help of client desktop App Builder?
If you use the web App Builder you can turn on a configuration of rendering advanced in the wizard and then choose the size of your iPhone in the drop-down list in the Tablet and Smartphone and forcing all Android devices to display your interpretation of the iPhone.
Neil
-
Design a showcase custom iOS and Android
Hi everyone, I am designing a CS for iOS based on barebone example by Derek Lu (http://www.adobe.com/devnet/digitalpublishingsuite/articles/getting-started-with-v2-librar y-and-store - api .html). So I tried the sample on iOS and it works.
Then I downloaded on an Android app as a library and Im getting the error: ERR_UNKNOWN_URL_SCHEME.
OK, so I downloaded the Android front custom since the Store configurator and took the file AdobeLibraryAPI.min.js. I changed the API file from my iOS-Custom shop (Derek Lus) with that of the Android Store Configurator.
But now the Android app shows no Folios, just a white screen. I checked via remote debugging for error messages: exception "Interpreted as Script but transferred with MIME Type text/plain resource" there are no errors.
Device: Nexus 10 @ Android 4.4.4
Debugging using the latest Chrome Canary on Mac (39.0.2129.0 64-Bit)
Replace the main.js with that file in the zip to Acrobat.com shared - files. This should solve the problem.
Neil
-
Hi all
I created a native android app. I need to publish on a 2560 x 1600 android tab, the problem is that in my library, I have my ipad version of 2048 x 1536 and 1024 x 768.
I know that when I create my native Android app, that I should be able selected my native interpretation in only 2560 x 1600, but in the library of android app generator tab of web I see only the option of 2048 x 1536 and 1024 x 768.
Please do you have any idea?
TX
The drop-down list lists only folio sizes that you have published in the account of publication of your application. Make sure that you have actually published a folio of 2560 x 1600, and then you will be able to select from the drop-down list.
Neil
-
Error occurred during the application of packaging: Android - x 86
Hello
I tried to export ARMAMENTS existing Android for Android - x 86:
This application uses to 2 ANE for In - App purchases. One for iOS and another for Android. I repacked the Android DONKEY file to be compatible with Android - x 86 and I also add the new Flash Builder ""-arch ' with the value of "x 86" and place it before '-shops ". "
Error occurred during the application of packaging:
output file is not writable
use:
ADT - checkstore SIGNING_OPTIONS
ADT-certificate - cn < name > (-UO < org - unit >)? (o < org - name >)? (-c < country >)? (- validityPeriod < years >)? (1024 RSA: 2048-RSA) < pfx file > < password >
ADT-help
ADT-migrate SIGNING_OPTIONS (< air-file-in > | < flown-file-in >) < fichier_resultat >
ADT-package SIGNING_OPTIONS (-aerial target)? <>Package-output (FILE_OPTIONS < app-desc > | < input-package >)
ADT-package SIGNING_OPTIONS-target flown < output-package > (< app-desc > FILE AND PATH OPTIONS | < input-package >)
ADT-package - target (apk | apk-debug | emulator apk | apk-captive-runtime) (CONNECT_OPTIONS? |) LISTEN_OPTIONS? ) (- airDownloadURL < url >)? (ARCH_OPTIONS)? SIGNING_OPTIONS < output-package > (< app-desc > PLATFORM-SDK-OPTION?) FILE-AND-PATH-OPTIONS | PLATFORM-SDK-OPTION < input-package >? )
ADT-package - target (ipa-test | ipa-debug | ipa-app-store | ipa-ad-hoc: ipa-test-interpreter | ipa-debug-interpreter | ipa-test-interpreter-Simulator | ipa-debug-interpreter-simulator) (CONNECT_OPTIONS? |) LISTEN_OPTIONS? ) (- sampler)? ANE_LINK_OPTIONS? AOT_MODE_OPTIONS? SIGNING_OPTIONS < output-package > (< app-desc > PLATFORM-SDK-OPTION?) FILE-AND-PATH-OPTIONS | PLATFORM-SDK-OPTION < input-package >? )
ADT-package SIGNING_OPTIONS? -target native SIGNING_OPTIONS? <>Output-package (< app-desc > FILE AND PATH OPTIONS | < input-package >)
ADT-package SIGNING_OPTIONS? -migrate SIGNING_OPTIONS-target native SIGNING_OPTIONS? OPTION-PATH < output-package > < app-desc > FILE_OPTIONS
ADT-package SIGNING_OPTIONS? -bundle target SIGNING_OPTIONS? <>Output-package (< app-desc > FILE AND PATH OPTIONS | < input-package >)
ADT-package SIGNING_OPTIONS? -target the donkey < output-package > < ext-desc > ANE_OPTIONS
ADT-prepare < airi-file > < app-desc > FILE_AND_PATH_OPTIONS
ADT-sign SIGNING_OPTIONS (-target (air: flown | ane))? (< airi-file > | < unsigned-ane-file >) < fichier_resultat >
ADT-devices OPTION of platform PLATFORM-SDK-OPTION?
ADT - installRuntime OPTION of platform PLATFORM-SDK-OPTION? DEVICE OPTION? (- < apk file > package)?
ADT - installApp OPTION of platform PLATFORM-SDK-OPTION? DEVICE OPTION? -package < apk file. IPA-file >
ADT - uninstallRuntime OPTION of platform PLATFORM-SDK-OPTION? DEVICE OPTION?
ADT - uninstallApp OPTION of platform PLATFORM-SDK-OPTION? DEVICE OPTION? -appid < app - id >
ADT - launchApp {OPTION of platform PLATFORM-SDK-OPTION? DEVICE OPTION? (port - debuggerPort)? -appid < app id >}
ADT - runtimeVersion OPTION of platform PLATFORM-SDK-OPTION? DEVICE OPTION?
ADT - appVersion OPTION of platform PLATFORM-SDK-OPTION? DEVICE OPTION? -appid < app - id >
ADT-version
SIGNING_OPTIONS:-< type > stores (-< store > keystore)? (- storepass < pass >)? (- alias < aliasName >)? (- keypass < pass >)? (- providerName < name >)? (- tsa < url >)? (- service-profile <>layout)?
FILE_OPTIONS: < fileOrDir > * ((C-< dir >< fileOrDir > +) |) (-e < file > < path >)) *
ARCH_OPTIONS:-arch (armv7 | x 86)
CONNECT_OPTIONS:-connect < host >
LISTEN_OPTIONS:-listening < port >
ANE_LINK_OPTIONS:-hideAneLibSymbols (yes | no)
ANE_OPTIONS:-CFC < EFA > (-platform < name > (-platformoptions < file >). < fileOrDir > * (C - < dir > < fileOrDir > +) *) *.
FILE-AND-PATH-OPTIONS: (OPTION-PATH |) FILE - OPTIONS) - AND-PATH-FILE OPTIONS?
OPTION: PATH - extdir < dir >
Platform-OPTION:-platform (android: ios)
PLATFORM-SDK-OPTION:-platformsdk < platform-sdk-home-dir >
OPTION: DEVICE-device (deviceID | ios simulator)
AOT_MODE_OPTIONS:-useLegacyAOT (yes | no)
Hello
I am able to repro the bug, if I change the 'DEMAND' while packing the apk and change it to "somedirectory/helloworld.apk' to 'helloworld.apk '. So a quick solution would be to remove all path and do simple APPLICATION parameter value 'helloworld.apk' when packing with - arch argument.
Also, there is a known issue with FB4.7 that it will fail to install the APK for Android device when they are packed with the option Ark on export Release version. So always choose option 'Keep bin-release-temp file' that will keep the APK even if FB fails to install/launch of the device.
-Nimisha
-
Problems with rendering shadows and gradients in folios Android
Does anyone have experience or solutions on how to solve a problem with damaged feathers, transparency and shadows in the "renditions" Android/folios?
In the interpretation of the iPad (1024 x 768), there are several frames scrollables, multi-state objects with transparencies and gradients etc. When it is seen on Android devices, if specific rendering of the iPad or Android rendered, it restores transparency, gradients and shadows as a white tone and that he is not rich somehow.
Is this a known problem or there at - there a way around this?
Is this problem resolved when you change vector to Raster (or vice versa)?
Edit: To add a color to this, we have an old bug that we decided to not no difficulty last year titled: "Display of MSO with transparency applied is different with 'Pixelated' and 'Signifying' at the discretion of MSO." Looking at the details of this bug, it seems to be exactly what you are light (whiteness in transparency on vector), so I hope that my question above translates a work around.
Thank you
Dave
-
Reconstruction of the Folios Android
Hello, I'm looking for suggestions on the workflow for Android 7 '' tablet. We currently have applications in both iTunes store GooglePlay (and Amazon). So far, I had used 1024 x 768 to build folios between all devices. However, we have just bought a Google Nexus 7 and downloaded our app only to discover that our folios are unreadable due to the proportion 4:3 and 3:2. I would like to rebuild our folios for the Android Tablet but since they are already published I do not know where to start.
If I take the approach of 'Lazy Susan' by Bob #1 scenario (referring to article "creating DPS Folios for Android devices") and reuse my iPad and do documents a size of 1600 x 1200, would I need to:
(1) do not publish and then republish the folio?
(2) is it a good idea to reuse the the same publication ID?
(3) if so, what happens to the version from Amazon?
(4) does it matter if I decide to do a 'V' guidance document only when it was previously the two?
(5) will be the user then download the folio 'new' and delete/Archives of the folio published previously?
I guess if I choose to either go "all the way" and/or "Sensible shortcuts", these two processes would have the same questions (don't not publish/republish, etc..) I think it's good to add "renditions" at this stage because it is ' sort of ' a 'new '... Is this correct?
Any help would be appreciated. Thank you.
If you looked at your application on a larger HD Android tablet, you'd be even more disappointed what looks like your folio of 1024 x 768. It looks like a small stamp in the middle of a black screen. It is the big drawback of the 'Lazy Susan' approach, at least for now. (In a future release, Android viewers should be able to evolve the contents upwards or downwards. That will simplify things, and I need to revise my orientation.)
(1) there is no reason to not publish/republish the folio No. Simply create a new format 1600 x 1200 using the eponymous Folio, ID and product Date of Publication settings used in the folio of 1024 x 768. Of course, the problem with this approach is that 1600 x 1200 is still 4:3 aspect ratio, which does not look great on the 16:9 aircraft - ish. Consider creating 1280 x 800 for the Android source files and re-use for each rendition.
(2) what do you mean by reusing the same "publication ID"? If you mean using the same ID of role/title Application for iOS and Android, yes you can, but it often complicates things. It is generally easier to create separate accounts (title IDs) for iOS and Android. If you mean something else by "publication ID", please specify.
(3) the Amazon version should be fine, unless you have activated strict refunds (which you don't want to do in your case). Still, I can't understand the question.
(4) it is not a problem to create a folio double orientation for rendering and a folio of single-direction for another interpretation.
(5) which is a little tricky. If a user has already opened the application, the spectator is part rendering of 1024 x 768 and unfortunately does not check for a rendering again until the application itself in uninstalled/reinstalled.
Regarding your question on the addition of "renditions" at this point, that's perfectly fine. Addition of "renditions" doesn't hurt existing users, and this makes things better for your new users.
The key to success is to make sure that you configure your source files, so that they can be easily imported. Most of the editors take the road to "Shortcuts" sensible and create different renditions based on two or three sets of source files.
Maybe you are looking for
-
Tecra A8 - DVD does not properly
Hello My Tecra A8 has started giving me problems when I want to read a DVD/CD. If I launch the system with a disk in the drive, then explore correctly reads and shows the details of the data on the disc, though it may be music, games, DVD, movies etc
-
Definition of 2565 cable NI PXI / PCB definition Support
Hello Currently, I have a switching relay NI PXI-2565 and I was wondering what the best / recommend ways to connect this device with respect to the chassis and a PCB. I am interested in what the mating connectors should be for a straight through cab
-
How to get tilted periodic waveform in labVIEW?
Hello I want to draw a waveform that has range of 0 to 360 and have a frequency of 50 Hz. the logic that I used in my code is like: 50 HZ = 0.02 seconds. 360/0.02 = 18000 (means multiply each sample to 18000 to get inclined wave that offers an amplit
-
Device flashing red lights r200 printer does not
flashing red lights the printer does not
-
I can see the knobs, but I don't see the logic in what happens when I press a button.
I can see the knobs, but I don't see the logic in what happens when I press a button. With every key I pressed a quick screen comes first, but I can't use the sliders to make whatever it is - either by touching the screen or by using the arrows on th