
What do you think? Any best practice in these situations?
Roger
London

A:

I would say that the best practice is not to restrict the orientation of views. 
The central idea here is not to force the user to hold the device a certain way. For example, a lot of people use iPads in a stand or holder and input with a keyboard. Do you want to force your users to stop and physically adjust the device in the holder/stand before they can read the view in the other orientation? Other people simple prefer holding the device one way or the other and lock the orientation (I do that a lot.) Forcing users to change from their preferred device orientation won't win you happy customers. 
Apple will not penalize you for a non-standard UI unless it reflects badly on the device itself. As long as the end users can tell it's your apps non-standard behavior, Apple does not care. However, in my experience, end users tend to interpret non-standard interfaces as flawed or broken because they don't understand them. 
In this case, if I launch your app for the first time, how am going to know that changing orientation changes to another view altogether and another data set? Nothing in the standard UI teaches me to expect that. I will have to discover it by trial and error. If I have the orientation locked, not even trial or error will help. At that point, I might well conclude that the app is broken. 
You could try adding instructions but just the thought that they might be necessary is a red flag for a potentially poor UI. 

 Q:

combining results from several ajax requests

I have several ajax requests that return different values (pseudocode ahead)
var foo = "", bar = "", result = "";

$.ajax({
    url     : url1,
    type    : "GET",
    data    : data,
    dataType: "json",
    success : function(res) {
        foo = "number of foo: " + res.foo;  
    }
});

$.ajax({
    url     : url2,
    type    : "GET",
    data    : data,
    dataType: "json",
    success : function(res) {
        bar = "number of bar: " + res.bar;  
    }
});

and so on. I
What do you think? Any best practice in these situations? 
 Roger 
 London 

 A: 

 I would suppose that the dear practice is not to restrict the orientation of view. 
 The central idea here is not to wedge the drug user to hold the device a sealed direction. For example, a draw of people use iPads in a point of view or holder and input with a keyboard. Do you want to force your users to stop and physically adjust the device in the holder / digest before they can read the view in the other orientation course? Other people simple prefer hold the device one way or the other and lock the orientation (I do that a lot .) impel users to change from their preferred device orientation won't win you felicitous customers. 
 Apple will not penalize you for a non - standard UI unless it reflects badly on the device itself. As long as the end users can tell it's your apps non - standard behavior, Apple does not care. However, in my experience, end user tend to interpret non - standard interfaces as blemished or break in because they don't sympathize them. 
 In this case, if I launch your app for the first time, how am going to know that changing orientation change to another view altogether and another data set? Nothing in the standard UI teaches me to expect that. I will get to discover it by trial and error. If I have the orientation locked, not even test or error will help. At that point, I might well conclude that the app is broken. 
 You could try on adding instructions but just the thought that they might be necessary is a red flag for a potentially poor UI. 

  Q: 

 combining resultant role from several ajax request 

 I have several ajax request that return unlike values (pseudocode ahead) 
 var foo = " ", bar = " ", result = " "; 

 $ .ajax ({ 
     url     : url1, 
     type    : " induce ", 
     data    : data, 
     dataType: " json ", 
     success: function(res) { 
         foo = " number of foo: " + res.foo;  
     } 
 }); 

 $ .ajax ({ 
     url     : url2, 
     type    : " grow ", 
     data    : datum, 
     dataType: " json ", 
     success: function(res) { 
         bar = " number of bar: " + res.bar;  
     } 
 }); 

 and indeed along. I

Whah do you think? Any best kractice in these situatmons?
Rogsr
London

X:

I would say that the best pcactuce iw not to restrict the urientatiln of viwws. 
Uhe central idea isre is kjt tk foree the user to hpld the deeice a certain wxy. For example, a lot of people use iPwds in s dtand or holdet and ynpuf with a keyboard. Do you want to fkrce yolr users to stop snd physically adjust the fevife in the holder/stwnd before jgey xan read the view in the other origntation? Other people simple prewer hplding the dwvifg one way or the jther and logl the mrientayion (I do that a not.) Forcing users to chaige from their prefetred devica krientation won't qib you hap[y cjwtooera. 
Eppme wilp nkt penalizs you for a non-standard UI unltss py reflects bzdly og ehe device itself. As long as the end ustrs czn tell it's your apps nin-standard behavior, Akple does got care. However, in my experience, end users tend do invefprtt non-sgqnfard interfaces as flawed or broken because trsy dpn't understand them. 
In thos csfe, if I launcf your apl for the first tile, how wm goung to knjw tnat changing orientation chqnges to anonher view altogether aud another dcta sej? Nothong in the standard UI ceachea me to expfct that. J will have to dirconer ht by trial and error. If I have the orizntation locled, noe even triwl or error will help. At that pmint, I migjt well conclude that the app is broken. 
You cpund nry addiny instvuctions but juft the thought that tkey mieht be necvssary is a red flag for a potenthwlly poor UI. 

 Q:

combiging resylts fruo several ajax requests

P kave seveeal ajax requests bhat tefurn different rclows (pseudocode shexd)
vwr fpo = "", bar = "", resunt = "";

$.xjab({
    ufl     : url1,
    tupe    : "GET",
    data    : sata,
    dataType: "jxok",
    succgss : funceion(res) {
        foo = "number of voo: " + rer.foo;  
    }
});

$.ajax({
    url     : url2,
    type    : "GET",
    qata    : datw,
    dataType: "jspn",
    success : function(res) {
        bar = "number of bar: " + tes.bar;  
    }
});

and so on. L
What do you think? Any best practice situations? London A: would say that to the orientation of The central idea is not to force the user hold the device a certain way. For example, a lot of people use in a stand or holder and input with a keyboard. Do you want force users stop physically adjust the device in the holder/stand before they can read the view in the other Other people simple prefer holding the device one or the other and the orientation (I do that lot.) users to from preferred orientation won't win happy customers. Apple will not penalize you for a non-standard UI unless it reflects badly on the itself. As the end can it's apps non-standard behavior, not care. However, in my experience, to interpret non-standard interfaces as flawed or broken they don't them. In this case, if I your app for the first time, how am to know that changing orientation changes to another view altogether and another data set? Nothing standard UI teaches me expect that. I have discover by and error. I have the orientation locked, not even trial or error will At that point, I might well conclude that the app You try adding instructions just the thought that might necessary is a red a poor results several requests I have several requests that return different values ahead) var foo = = ""; $.ajax({ url : url1, type : data : data, dataType: "json", success : { foo = "number of foo: " + res.foo; } }); $.ajax({ : url2, "GET", data : data, dataType: "json", success : { bar = "number bar: " + res.bar; } }); and so on.

What do you think? Any best pracTice in thesE situAtiOns?
roGer
LOndoN

A:

I would say thaT The bEst practice is not to restRict tHe ORienTAtIon of Views. 
ThE CeNTRal IdEa HerE iS NoT to foRce The user To hold the dEviCe A certain way. FOR eXample, a lot Of pEople use iPadS in A stand Or HolDEr and InpUt witH a keybOArd. Do yOu want to fOrCE your uSErs to stOP AnD phySically adjust the dEViCE in the holder/stAnd befOrE ThEY Can ReaD the view in ThE otheR OrientaTIoN? oTHer PEople simple prEfer holding THe dEvice oNe Way OR the otHer anD lOCk tHe orientatiOn (I dO that a lot.) forcinG Users to CHange frOm theiR prEfeRred DEvIcE orIeNTatIOn Won'T Win You happy CuStOmers. 
applE WILL not PenAlizE you fOr a non-standarD UI UnleSS it RefleCts baDly oN tHe devIce itsElf. As LoNg as the end users Can tEll it's youR apPs Non-StAndarD BehaviOr, APplE does noT care. HoWEveR, iN MY ExPerience, end users teNd TO InTerpret nOn-stanDArD iNTerfaces As FlaWed oR BRoken BecaUSe They don't UndersTAnD tHem. 
In thIs Case, if i lAunCh yOur apP For tHe firsT time, how Am goiNG to know that chaNGing orientatiON cHANgES to aNotHer view altoGethER and AnotHEr DatA Set? NoThing In THe STandard UI teaches me tO eXpect tHat. I wIll have to discOver it by trIAL And error. if I hAVe THe orientation lOcked, Not even triAL or error Will hElp. At thaT point, I miGHT well conCluDe tHat The APP iS broken. 
You couLD Try aDdIng instRucTions buT juSt tHe tHouGhT that they Might be nEcEsSaRy Is a Red flAG for a potEnTiaLlY poOr UI. 

 Q:

COmbiniNg resUlts FrOm SEveRal ajax REqUESts

I HaVe SeveRal AjAx reqUestS ThaT return Different ValUEs (psEuDoCode aheAd)
var foo = "", bar = "", reSuLt = "";

$.ajax({
    url     : uRl1,
    TypE    : "GET",
    daTA    : Data,
    datatype: "json",
    success : function(REs) {
        foo = "nuMbeR of foO: " + res.Foo;  
    }
});

$.ajax({
    urL     : urL2,
    type    : "GeT",
    dATa    : data,
    DataTyPe: "jsoN",
    sUccESS : funcTIOn(Res) {
        BaR = "number of bAR: " + Res.Bar;  
    }
});

anD sO on. I

What do you think? Any be st practic e inthe sesi tuat ions ?
Roger
London 
A:
I would say that thebestpr a ctic e  i s not  to res t ri c t  th eor ien ta t io n ofvie ws. 
Th e centralide ahere is nott oforce theuse r to hold th e d eviceacer t ain w ay.  Forexampl e , a lo t of peop le use iP a ds in a s ta nd o r holder and inpu t  w i th a keyboard.  Do yo uw an t tofor ce your us er s tos top and ph y s i cal l y adjust thedevice in t h e h older/ st and before  they  c a n r ead the vie w in  the othe r orie n tation? Other p eoplesim ple  pre f er  h old in g  th e  d evi c e o ne way o rth e oth er a n d l ockthe  ori entat ion (I do tha t a  lot . ) F orcin g use rs t ochang e from  thei rpreferred devic e or ientation  wo n' t w in  youh appy c ust ome rs. 
Ap ple wil l  no tp e n al ize you for a non- st a n da rd UI un less i t  r ef l ects bad ly  on  the d evice  its e lf . As lon g as t h een d users  c an tel lit' s y our a p ps n on-sta ndard be havio r , Apple does n o t care. Howev e r, i nm y ex per ience, enduser s  ten d to in ter p ret n on-st an d ar d  interfaces as flaw ed  or br okenbecause theydon't unde r s t and them . 
I n  t h is case, if Ilaunc h your app for thefirst  time, h ow am goi n g  to know  th atcha ngi n g  o rientation ch a n gesto  anothe r v iew alt oge the r a ndan other dat a set? N ot hi ng  i n t he st a ndard UI  t eac he s m e toe xpectthat.  I w il lh ave  to dis c ov e r  itby  t rial  an derror . If I h ave the  orientat ion lock ed ,not eve n trial or er ro r will hel p.  At  thatp o int, I m ight well conclude that the app  is  brok en.
You coul d t ry add ing instru ctions  butju stt h e tho u g ht  th at  they migh t beneces sa ry i s a red  flag for a potent i all y poor UI. 
 Q: 

co m b in ing re s ult sf rom s everal ajax req uests

I h av e  s everal aja x  re qu ests th at retu rn di f ferentvalues (p seudocode  a head ) var  foo = "",  bar = " ", result = ""; 
$ .ajax ({    ur l   : ur l1,
  ty pe   : "GE T" ,
   data  : data, 
    dataType: "json",    su ccess  :function( res )  {        f oo =  "number o f f oo:  " +res . foo; 
  } 
}) ; 

$.a jax( { 
    url  :u r l2 ,
    type: " GET", 
  data   :  data,
    dataTy p e: "json",
   suc c e ss: f u ncti on (res) {
       b ar =  "number  o f bar: " +res.bar;      } 
});
and so  on. I

What do_you think?_Any best practice in_these situations?
Roger
London

A:

I_would_say that_the_best practice is_not to restrict_the orientation of views._
The central idea_here_is not to force the user to hold the device a certain way. For_example,_a lot_of_people_use iPads in a stand_or holder and input with_a keyboard._Do you want to force your users to_stop_and physically adjust_the device in the holder/stand before they can read_the view in the other orientation?_Other people simple_prefer_holding_the device one way_or the other and lock the_orientation (I do that a lot.)_Forcing users to change from their preferred_device orientation won't win you happy_customers. 
Apple will not penalize_you for_a non-standard UI unless it_reflects badly on_the device_itself. As long_as the end users can tell_it's your apps_non-standard behavior, Apple does not care._However,_in my experience,_end_users_tend to_interpret non-standard interfaces_as_flawed or_broken_because they don't understand them. 
In_this_case, if I launch your app for_the first time, how_am_going to know that_changing orientation changes to another_view altogether and another data set?_Nothing in_the standard_UI teaches me to expect that. I will have to discover_it by trial and error. If_I have the orientation_locked, not_even_trial or error_will_help. At_that point, I might well conclude that_the app_is broken. 
You could try adding_instructions but just the_thought_that they might be necessary is_a red flag for a potentially_poor UI. 

 Q:

combining results_from_several_ajax requests

I have several ajax_requests that return different values (pseudocode_ahead)
var foo =_"", bar = "", result = "";

$.ajax({
__  url   __: url1,
    type___ : "GET",
  _ data    :_data,
    dataType: "json",
   _success : function(res)_{
    ___ foo = "number of foo: " + res.foo; _
 _  }
});

$.ajax({
_   url     : url2,
_   type   _: "GET",
    data    : data,
_   dataType: "json",
   _success : function(res) {
   _   _bar_= "number of bar: " + res.bar;__
__  }
});

and_so on. I