Announcement

Collapse
No announcement yet.

CSS for mobile, how it is handeled?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • CSS for mobile, how it is handeled?

    hi, since this section is for mobile, i wounder first how to control the mobile stuff CSS from a GUI? i have the menu for example "navigation" for mobile does appear black, with black font, can't change anything in that.. with ugly blue button no-matching at all with the navigation layout...

    also the other stuff, how it is being controlled? there is no such options in themes (css) templates... i found some css generated when deployment or generating source code... but this is useless as it will be overwritten anyway if generated again or deployed again by SC engine...

    who knows how to control this please share... it is totally not clear for everybody AFAIK - (Albert Acronyms )

  • #2
    I just did some testing with SC8 samples. Generated the whole Sample project and tested most of the apps on my mobile phone. So far not even one screen looked god, so it seems like either something must be trigerred to convert the App into responsive layout or simply it does not work at all. Some App layout properties have a MOBILE tab but no information, no help no nothing how to get the grid or form look good on the mobile device. I have also asked to any specific mobile examples but so far no response from NM, so it looks like we are stuck on that.
    I would also like to know the same - which is how to control the look of the mobile templates ???

    Arthur
    -----------------------------------------
    Arthur Klisiewicz
    dATA POINT SOFTWARE
    www.datapointsoftware.com

    Comment


    • #3
      Originally posted by aka View Post
      I would also like to know the same - which is how to control the look of the mobile templates ???

      Arthur
      Same thing Arthur, they don't seem to have GUI to control mobile templates, yet?!

      However, for other PC-based templates, it worked for me even in SC8 you can change a lot of things in CSS templates... just copy one of the existed css themes and change whatever you want, make it default and use it in your applications.... but the "menu" application is annoying to adjust the icon... still looks doesn't response at all.

      I'm sure you are aware about cache in this regard is very important to remove your cache so new css take effect,, try also hard-reload, such as Control+F5.


      Mike

      Comment


      • #4
        I also tested a lot of applecation. And found out that the templates in the CЫЫ does not always correspond to what you want to see. So for the start, select the correct template.
        I use application from http://www.intellectsoft.net

        Comment


        • #5
          well, i have not used css for mobile. so it is little tricky for me.
          best online casino sites
          Last edited by archercrane; 10-31-2014, 02:45 AM.

          Comment


          • #6
            You can optimize emails for smart phones and other handheld devices by creating a separate set of styles to be used by devices that recognize media queries.

            This means you can create emails that adapt to the resolution they are viewed on and output content to suit, for example: narrowing the line-length of paragraphs to make them more readable and prevent sideways-scrolling, or reducing the dimensions of an image. Devices that don't recognize media queries will just apply your default styles

            Check out W3C Recommendations for Media Queries to learn more.

            Comment


            • #7
              rr you have a lot of overtime job these days

              Comment


              • #8
                Major part of the problem is that ScriptCase is still using jQuery v1.8.2

                The latest is v1.11.2 and several intermediate versions fixed IOS and Android related problems, as well as Safari issues.

                jQuery v1.8.2 was released in 2012. jQuery v1.11 was released well over a year ago. When will ScriptCase update?


                Dave
                Dave Prue
                Code Whisperer
                Lahar International Corp
                www.lahar.net

                Comment


                • #9
                  Originally posted by daveprue View Post
                  Major part of the problem is that ScriptCase is still using jQuery v1.8.2

                  The latest is v1.11.2 and several intermediate versions fixed IOS and Android related problems, as well as Safari issues.

                  jQuery v1.8.2 was released in 2012. jQuery v1.11 was released well over a year ago. When will ScriptCase update?


                  Dave
                  Hi Dave
                  Good point really
                  Since you are the expert in this, can't we upgrade it manually in the libraries or something?! what is the consequence?

                  Comment


                  • #10
                    Mike,

                    Yes, we can, but then I would have to add that to the list of 14 other things that I have to do manually before/after doing a Scriptcase update.

                    What is more efficient, Scriptcase spending 2 hours to fix it properly, or 50 of us each spending an extra hour on each update (how many already this year alone) ?

                    Frustrating, to say the least.

                    Dave
                    Dave Prue
                    Code Whisperer
                    Lahar International Corp
                    www.lahar.net

                    Comment


                    • #11
                      Originally posted by daveprue View Post

                      What is more efficient, Scriptcase spending 2 hours to fix it properly, or 50 of us each spending an extra hour on each update (how many already this year alone) ?


                      Dave
                      100% with you.

                      Comment


                      • #12
                        not to speak of the hours it would take to test any issue with both the officially SC supported jquery version and the newer one, to check if the issue is caused by the newer jquery

                        Comment


                        • #13
                          Originally posted by robydago View Post
                          not to speak of the hours it would take to test any issue with both the officially SC supported jquery version and the newer one, to check if the issue is caused by the newer jquery
                          hehe tell me about hours of testing things dude, even after supposed it is working fine by sc guys, when reaches to us we discover lots of other stuff, sometimes old bugs appear

                          summary
                          with each sc update, expect 3 things
                          1 old bugs show up
                          2 whatever points you want it to be fixed, never close to
                          3 you need to change your own libraries and stuff

                          bonus: if new feature is there, expect more stuff

                          the surprise factor is also important: once you're done setting your development environment, happy to start working and testing, sc gives alert, lalaaa new version is there! WTF i just upgraded, did i not upgrade properly!? check changelog, supriseeee, new version, with single small fix to something nobody requested

                          get use to it, and be positive guys, they do update regularly, bugs are getting less, it is obvious they are spending more time and efforts lately, we should be thankful

                          Comment

                          Working...
                          X