facebook

Additional files

  1. MobiOne Archive
  2.  > 
  3. Getting Help – General
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #330562 Reply

    appmos
    Member

    I read in the documentation that must include the images / css / etc through the “Additional Files” option. I have to do it on the first screen or on their screens where css / images are being used? These files must be in the same root of *.mobi files when added or not needed? Are there any further documentation on this subject?

    Thanks

    #330597 Reply

    appmos
    Member

    I really need a help with this problem because images and CSS are not being applied when I publish de android apk file.

    Thanks

    #330598 Reply

    support-michael
    Keymaster

    @appmos

    We are updating the docs and mobione 2.2 to provide better instruction on how to include additional files in your project. Here is a quick set of guidelines:

    1) the 1st screen that is rendered when your app launches is known as the “Startup Screen”.
    1a) there should only be 1 design file with the Startup Screen property enabled/checked.
    1b) When generating code for you application, it should be initiated on the design with the Startup Screen property enabled

    The 1a & 1b are not enforced at this time (MobiOne 2.1 and earlier ver)

    2) Additional files, JavaScript libraries and Style Sheets properties should only be defined on the startup design.
    – they will be ignored if specified on a non-startup screen
    – these file are copied into the root /www folder of your project

    3) If a .mobi file is specified in the Additional Files list then code will be generated for it, all of its linked design files (gotoScreen actions), and its additional files/js libs/css style sheets will be imported.

    #330600 Reply

    support-michael
    Keymaster

    > I read in the documentation that must include the images / css / etc through the “Additional Files” option.

    You only need to explicitly include additional resources (files/js/css) when you are doing something advanced such as dynamically referencing a resource at runtime that is not already referenced by a design file. Some examples for when to use these properties include:
    – dynamically change an image widget’s src to a new image, include the new image as an Additional File
    – dynamically navigate to screen that is no directly linked by a gotoScreen action, include the .mobi file as an Additional File
    – your custom HTML widget content requires custom css and js, include using Style Sheets and JavaScript Libraries properties respectively

    Can you describe your use of these properties in more detail for us to assess?

    #330602 Reply

    appmos
    Member

    Hi Wayne

    Thanks for all explanations. It’s great to know that we have a program update. Do you know whether the aspect ratio option was included in the new version?

    So, even if I am using a CSS / Image only on screen #3 or #5, I´ll need to include the files in the first screen?

    I’m just using CSS to apply styles. I’m also willing to assemble a image gallery using Photoswipe and use also a 360 ° view system and I don´t know if I have to add these jquery files (plugins) as well (in fact, I posted this question yesterday on the forum). The first image of the 360 ° view plugin appears during testing but does not appear after the application. If is possible to use these plugins in MobiOne, then I’ll need to add all the images used in Photoswipe/360 ° View?

    Thank you

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: Additional files

You must be logged in to post in the forum log in