Home / Page 2

tradexcel12

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 370 total)
  • tradexcel12
    Participant
    in reply to: Kindle Fire HDX #17062

    Good idea on the “curtains”! I have a couple places that can use that. Thanks!

    tradexcel12
    Participant
    in reply to: Kindle Fire HDX #17060

    Not exactly Anna. I take an image, think of an old time parchment sort of thing, and it has irregularly shaped sides and top and bottom, as if the paper were torn a bit. I make it either Nexus 10 size or iPad retina size. Either way works. Set it as a png. Now when you use that for your background, there will be “holes” along the sides where the paper is “torn” or ragged. That allows the background of the device to show through. When another device with a different foot print is used, it resizes that ragged sided page to fit it's dimensions. So the background area might be bigger, or smaller, but it still looks like you intended to fill the screen with a ragged piece of paper.Alternatively you could set the background to black, put the ragged page graphic on that black background and then letterbox it and it would still look like it was a merely a ragged page on the screen's background.

    tradexcel12
    Participant
    in reply to: Kindle Fire HDX #17057

    Reza, a sneaky little trick I use is an irregular shaped background “page”. That way it's impossible to tell where the “page” ends and the device starts and I don't have to letterbox (which I just really dislike for some reason). I use the Nexus 10 dimensions and 300 PPI resolution and just let the device rescale it as it wants to. That may not work on all book page types, but works great on many of them.

    tradexcel12
    Participant
    in reply to: Kindle Fire HDX #17054

    They also both use 300 PPI so watch your original images – if they are less than 2560 x 1600 x 300 PPI they may look a little fuzzy on the device. They'll look fine in the simulator but can be a little off on the actual device itself.

    tradexcel12
    Participant

    Linda – Alex has left out a very important warning on all Kwik versions. There should be a huge banner that pops up after you install that says WARNING: This is a very addictive program and the more you use it, the more you will find you can do with it and the more you will want to use it until you have no waking thought that isn't somehow connected to actions and buttons and animations and such"I have been known to frighten passing postal delivery people and small animals with my shouts of joy while working with Kwik and making things work as I want them to. Glad you've joined the fun!

    tradexcel12
    Participant
    in reply to: Photoshop font size messed up #17066

    Anna – for me it didn't matter what version of PS I was using – 6 or CC. Updates from PS do NOT fix the bug. For me it only showed up when I synced the text. I looked at the code and found where it was being written to that funky small size (mine was 13.7 HAHAHAHA) and before my final publishing changed every single page to the correct size in the lua code. If you correct it once and go back to PS, PS will reset it to the incorrect size again. There might be a better way to handle it, but I haven't found it yet.

    tradexcel12
    Participant
    in reply to: Is Corona SDK going off the rails? #16915

    OK so Composer is actually Storyboard 2.0 sort of. LOL There was discussion about SB 2.0 on the Corona forums, it looks like that was replaced with what they are now calling Composer. Don't care what it's called so long as it works. HAHAHA

    tradexcel12
    Participant
    in reply to: Is Corona SDK going off the rails? #16913

    I assume this is the post you're referring to http://coronalabs.com/blog/2014/01/21/introducing-the-composer-api-plus-tutorial/Alex - what does this do to the release of a fully functional Kwik 3 that is compatible with the stable public builds?

    tradexcel12
    Participant
    in reply to: Dialogue Boxes – 1 to the next etc. #16697

    I too use a lot of text, as my story is the important part and the images and animations merely an enhancement of the story. (I write for older readers, this approach may not be correct for pre schoolers)If you merge your text with the chat bubble it will become an image and then placement is assured to be exactly what you set up. Some devices have some issues  with text and Adobe also sometimes has a bug on text size where it resizes your text - VERY annoying!Check your font size in the simulator - if it looks good there, it's good on the device. There is no perfect size. The resolution is so good on devices that even very tiny text is legible. Unless you're old like me, and then you just take your glasses off and squint a little and it works. LOLThe amount of text and available space often determines text size. But try to be consistent throughout your pages. In other words, if you use 36 on three pages, don't suddenly go to 48 just because you have more room. It's bad for the readers. But if you have more text on one page than another, it's ok to drop that page down a few points so it all fits nicely.You need to use as much dialog as it takes to tell your story. No more, no less. Same with the length of your book - it should be as long as it needs to be to tell your story. There is no magic number.I find I set up everything on a page including the text and dialog before adding animations. For me, it's easier to figure out what I want to do with animations and effects when I"m looking at a completed page. But this would be your choice - whatever follows your thought process will work best for you.One word of advice - actually two. Use a story board of some sort - paper and pencil works, spreadsheets work, pdf's work. In other words, plan your pages on paper first, even it's just to put the text and a general image idea there. Add some ideas about animations - they will probably change as you go, but at least you will have some idea of what to do on each page and get a feel for the entire book.Second, on your first one, break it into little pieces. Get one part of one page working the way you want, then move on to the next part until that page is done. Then go to the next page, rinse and repeat. Using story boards and doing things in small increments will keep you moving forward without feeling overwhelmed. And will let you work faster since you have a road map and are building on what you learned the day before.Best of luck on your book!

    tradexcel12
    Participant
    in reply to: Full proportional screen fill for iPhone and iPad? #16844

    I only work with tablets but I suspect you are running into what I have with the differences between iOS and droid screen sizes. If you start with say a Nexus 10 – you need to have your full screen image 2560 x 1600 x 300 DPI. The Apple retina is 2048 x 1536 x 264. If you make two rectangles in your favorite image program that match those dimensions, you will immediately see the problem. They are different shapes. If you try to use the Apple size you must stretch it to fill the Nexus screen. That stretching will make your other layers stretch also and they end up not being positioned correctly and not looking right. The ONLY way to keep things in the right places, and looking correct is to letterbox it and then you have the black bars.If you try to use the Nexus size, You may have better results, because you're taking something large and chopping it down. BUT the positioning is still suspect and the results might not be any better than the letter boxing. Universal IMO works well with business apps that just have buttons or data on the screen. But when you get to the sorts of things we book authors do, I have had no luck with any work around and a Universal build, other than to do two sets of images - one in the shape of the droids, and one in the shape of the Apple devices. The retina dimensions scale nicely to ipad mini's and iPhones, and the droids scale nicely from the Nexus 10. Not knowing what you are working on, if it is a book type app, you might try to do an irregular page as the background image - one that makes the black bars appear to be a part of the design itself. Think something like a torn parchment with irregular sides. Doing two or even three sets of images actually doesn't take very long once you have your work flow cast in concrete, especially now with the features of Kwik 3.

    tradexcel12
    Participant
    in reply to: page thumbnails not showing up for page navigation #16575

    Glad to see you have those back at work. WHOO HOO no more Flash setups.

    tradexcel12
    Participant
    in reply to: page thumbnails not showing up for page navigation #16573

    Did I read that right? The new storyboard will be in Next?

    tradexcel12
    Participant
    in reply to: Multiple books & In App Purchases #16834

    Just a word of caution on the Apple kid's section. They seem to hand pick what will go into that category. At least right now. It doesn't seem to be automatic inclusion like other categories. So if your books don't get in, don't assume you've done something wrong. It could just be the human who reviewed your book forgot to hit the right key.

    tradexcel12
    Participant
    in reply to: Which road to take – Universal or Device Specific #16808

    I trust someone else will correct me if I'm wrong, but the iPad build will only use the iPad sized images, the Droid, their appropriate images, and so forth when it's time to do the final build for submission.Personally I'm a control freak, so I do two versions of every project. One in the Nexus 10 resolution, then I take those layouts and chop them down to iPad retina resolution. But I'm a control freak when it comes to images so remember that's just a personal thing.

    tradexcel12
    Participant

    Alex – if you let your clones watch Despicable Me 2, that could be the problem with them! They pick up all sorts of bad habits from that movie!

Viewing 15 posts - 16 through 30 (of 370 total)

Privacy Preference Center

Strictly Necessary

these coolies are for WP-SpamShield, gdpr-wp, woocommerce, paypal

PHPSESSID, SJECT16, JCS_INENREF, JCS_INENTIM, gdpr, woocommerce_cart_hash, woocommerce_items_in_cart, woocommerce_recently_viewed, wordpress_, wordpress_logged_in_, wordpress_sec_, wordpress_test_cookie, wp_woocommerce_session_, AKDC, akavpau_ppsd

Functionality

WordPress cookie created when auto-saving a post in the editor.

wp-saving-post, wp-settings-, wp-settings-time-

Performance

google analytic

__utma,__utmb,__utmc,__utmz,_ga,_gid,_gat

Advertising