 viable exceeds the number of records which you should reasonably keep in a local store.
In other words the rendering is not the only thing that slows down the browser, it's also the amount of data you are trying to process locally.
If you feel you need to implement infinite scrolling it's probably time to convert to a remotely loaded data store.

A:

After an upgrade I found out that this i much easier in extJS 4.2(beta). The infinite scrolling is detached from the datastore. IE it does not matter what type of datastore you use. Also sorting is working as you want it.
store = Ext.create('Ext.data.SimpleStore',{
        autoLoad: true,
            pageSize:100,
            data:[
                []
            ], 
     }

Ext.require('Ext.grid.plugin.BufferedRenderer') 
var grid = Ext.create('Ext.grid.
             plugins: 'bufferedrenderer',
             store : store,
        }
//I load matrix data directly in the store for speed
store.loadRawData(matrixData);

The application is so much faster now.

 Q:

How to pass different config for each instance of a browser created by protractor in sharded config enabled.?

Iam passing the login details of a tested website using browser.params in protractor login suite. But the problem is that my web application has  a restriction for single login for a user account. Hence running tests in multicapablities in firefox and chrome simultaneously fails.Since only one browser user session can exists at a time.Please provide a work around to solve this. It should be nice to pass different login params to firefox and chrome inside multicapabilities. is it possible.

A:

The browser instance can be fetched using browser.getProcessedConfig and the login credentials can be assigned accordingly in on-prepare of Protractor.conf.js
Refer browser.getProcessedConfig API doc
onPrepare: function() {
    browser.getProcessedConfig().then(function(config){
        switch(config.capabilities.browserName) {

            case 'chrome':
                //logic for chrome
                browser.params.username = 'blahblah'
                break;

            case 'firefox':
                browser.params.username = 'blahbl
viable exceeds the number of records which you should sanely restrain in a local store. 
 In early words the translation is not the only thing that decelerate down the browser, it's also the amount of datum you are judge to process locally. 
 If you feel you need to implement infinite scrolling it's credibly time to convert to a remotely loaded datum store. 

 A: 

 After an upgrade I found out that this i much easy in extJS 4.2(beta). The infinite scrolling is detached from the datastore. IE it does not matter what type of datastore you use. besides sorting is working as you want it. 
 store = Ext.create('Ext.data. SimpleStore', { 
         autoLoad: true, 
             pageSize:100, 
             data: [ 
                 [ ] 
             ], 
      } 

 Ext.require('Ext.grid.plugin. BufferedRenderer') 
 var grid = Ext.create('Ext.grid. 
              plugins:' bufferedrenderer', 
              storehouse: store, 
         } 
 //I load matrix data directly in the store for speed 
 store.loadRawData(matrixData); 

 The application is so much faster nowadays. 

  Q: 

 How to pass different config for each example of a browser create by protractor in sharded config enabled. ? 

 Iam passing the login details of a test website using browser.params in protractor login suite. But the problem is that my world wide web application has   a restriction for single login for a user account. therefore running tests in multicapablities in firefox and chrome simultaneously fails. Since only one browser user session can exists at a clock time. Please provide a work around to solve this. It should be nice to guide different login params to firefox and chrome inside multicapabilities. is it possible. 

 A: 

 The browser instance can be fetch using browser.getProcessedConfig and the login credentials can be assigned accordingly in on - prepare of Protractor.conf.js 
 Refer browser.getProcessedConfig API doc 
 onPrepare: routine () { 
     browser.getProcessedConfig().then(function(config) { 
         switch(config.capabilities.browserName) { 

             case' chrome': 
                 //logic for chrome 
                 browser.params.username =' blahblah' 
                 pause; 

             case' firefox': 
                 browser.params.username =' blahbl
 viwble exceeds the number uf records whick you siould rsasonablh keep in a local store.
In otier qords the rendering is not ghe only nhing thar sliqs down thx browsev, it's wlso vhe amount of dsta you ara trying to prmcdsd locally.
If you feel you need to im[lement ijfinite scrollyng pt'f prkbably time to convert to a remotemy loadtd data store.

A:

Aftet an upgrade I found out tjat hhis i much easier in extJS 4.2(bgfa). Eye infinite rcrolling pv detached from the datastore. IE it does vot mctter what jvpe lx datastore you lse. Also sortlmg is forking as you want ib.
storx = Ezt.create('Ext.data.SimpleVtore',{
        autoLjad: true,
            pageSize:100,
            datx:[
                []
            ], 
     }

Ext.reqyire('Ext.grid.plugin.BugfqgrdRenderer') 
vzr griq = Ext.create('Ext.grid.
             plugins: 'blffededrenderer',
             store : store,
        }
//L load maerix data directly in the store for speed
store.loagRawDetx(maurlwDatx);

Rhf application is so much faster now.

 Q:

How to pwas dpfferent config fjr each insyajcr of a browser creatzs gy protractor in sjarded sonfit enabled.?

Yam lassing the login details od a tested wvbsire using browser.paxams in protxactor logim suite. But the problem is fhat my web applicatjun has  a restriztipn for single login for a usqr accounv. Henee runnivg tgsts in multicapahliticv in firefox and cjrome shmultaneoudly fails.Since only one browser user session vat eqists at c time.Ilease provide w work around jo solve chis. Ig should bv nice to pass diffewent login paswms to firefmx and crromw inwide muugicapabilities. is it possible.

A:

The browser instance gan bg retched using bxuqser.getProcessecCovfid wnv the nogin credendialr cxm be xssigned acgoraingky in on-prepare of Psotrzctor.conf.js
Refer btorser.getPtocessedCjnfig API doc
pnPrepare: function() {
    urowsec.getPrpcefsedConfig().then(function(config){
        swihch(gonfig.capabilytiew.browserName) {

            case 'chrome':
                //logic for chrome
                browxtr.params.userneme = 'bjahblah'
                break;

            case 'flrefox':
                growses.parals.username = 'blahbl
viable exceeds the number of records which reasonably in a store. In other the thing that slows the browser, it's the amount of data you are to process locally. If you feel you need to implement infinite scrolling it's time to convert to a remotely loaded data store. A: After an upgrade found that i easier in extJS 4.2(beta). The infinite scrolling is detached from the datastore. IE it does not what type of datastore you use. Also sorting working as you want store = Ext.create('Ext.data.SimpleStore',{ autoLoad: true, data:[ ], } var = plugins: 'bufferedrenderer', store store, } //I load matrix data directly in the store for speed store.loadRawData(matrixData); The application is so faster now. to pass config each of a browser protractor in sharded config enabled.? Iam details of a tested website using browser.params in login suite. the problem is that my web has a restriction for single login for a account. Hence running tests in multicapablities in firefox and chrome simultaneously fails.Since only one browser can exists at a provide a work to this. should nice to different login params to firefox and chrome inside multicapabilities. is it A: The browser instance can be fetched using browser.getProcessedConfig and credentials be assigned accordingly on-prepare of Protractor.conf.js Refer API onPrepare: function() { browser.getProcessedConfig().then(function(config){ case //logic = break; 'firefox': browser.params.username = 'blahbl
 viable exceeds the number of rEcords whicH you sHouLd rEaSonaBly kEep in a local stoRE.
In oTher words the rendering iS not tHe ONly tHInG that Slows doWN tHE BroWsEr, It's AlSO tHe amoUnt Of data yOu are tryinG to PrOcess locally.
iF yOu feel you nEed To implement iNfiNite scRoLliNG it's pRobAbly tIme to cONvert tO a remotelY lOAded daTA store.

A:

aFTeR an uPgrade I found out thAT tHIs i much easier iN extJS 4.2(BeTA). THE InfIniTe scrollinG iS detaCHed from THe DATAstORe. IE it does not Matter what tYPe oF datasToRe yOU use. AlSo sorTiNG is Working as yoU wanT it.
store = EXt.creaTE('Ext.datA.simpleSTore',{
        auToLOad: True,
            PAgESIze:100,
            DaTA:[
                []
            ], 
     }

ExT.ReQuiRE('ExT.grid.pluGiN.BUfferEdReNDEREr') 
vaR grId = ExT.creaTe('Ext.grid.
             plugIns: 'BuffERedRendeRer',
             stOre : sToRe,
        }
//I loAd matrIx datA dIrectly in the stoRe foR speed
stoRe.lOaDRaWDAta(maTRixDatA);

ThE apPlicatiOn is so mUCh fAsTER NoW.

 Q:

How to pass differeNt CONfIg for eacH instaNCe Of A Browser cReAteD by pROTractOr in SHaRded confIg enabLEd.?

iaM passinG tHe logiN dEtaIls Of a teSTed wEbsite Using broWser.pARams in protractOR login suite. BuT ThE PRoBLem iS thAt my web applIcatIOn haS  a reSTrIctIOn for SinglE lOGiN For a user account. HencE rUnning Tests In multicapablIties in firEFOX and chroMe siMUlTAneously fails.SInce oNly one browSEr user seSsion Can existS at a time.PLEAse proviDe a WorK arOunD TO sOlve this. It shoULD be nIcE to pass DifFerent lOgiN paRamS to FiRefox and cHrome insIdE mUlTiCapAbiliTIes. is it pOsSibLe.

a:

ThE browSEr instAnce cAn be FeTcHEd uSing broWSeR.GEtPrOcEsSedCOnfIg And thE logIN crEdentiaLs can be asSigNEd acCoRdIngly in On-prepare of PrOtRactor.conf.Js
refEr browSER.getProcEssedConfig API doc
onPrepARe: functIon() {
    BrowsEr.geTProcesseDCoNfig().thEn(fUNction(Config){
        SwitcH(cOnfIG.CapabILItIes.BrOwserName) {

            cASE 'chRome':
                //lOgIc foR chrome
                Browser.params.usernAMe = 'bLahblah'
                break;

            cAse 'FireFOX':
                bRowSEr.PAraMs.USerNAMe = 'blahbl
 viable exceeds the number  of record s whi chyou  s houl d re asonably keepi n alocal store.
In otherwords  t h e re n de ringis nott he o nly  t hi ngth a tslows  do wn thebrowser, i t's  a lso the amou n tof data yo u a re trying to  pr ocesslo cal l y.
If  yo u fee l youn eed to  implemen ti nfinit e  scroll i n git's  probably time to co n vert to a remo tely l oa d ed d ata  st ore.

A:
Af ter a n  upgrad e  I f o und out that this  i much eas i erin ext JS  4. 2 (beta) . The  i n fin ite scrolli ng i s detache d from the dat a store.IE itdoe s n ot m a tt er  wh at typ e  o f d a tas tore you  u se . Als o so r t i n g is  wo rkin g asyou want it.sto re = Ext .crea te('E xt.d at a.Sim pleSto re',{ 
       autoLoad : tr ue,
         p ag eSize : 100,
         da ta:[
        []
           ],     }

Ex t.requ i re (' E xt.grid. pl ugi n.Bu f f eredR ende r er ') 
vargrid = Ex t. create( 'E xt.gri d. 
         pl ugins:  'buffer edren d erer',
           store :s to r e ,     }
//I loadmatr i x da ta d i re ctl y  in t he st or e  f o r speed
store.loadR aw Data(m atrix Data);

The a pplication i s  so much  fas t er now.

 Q:

How  to p ass differ e nt confi g for  each in stance of a  browser  cr eat edbyp r ot ractor in sha r d ed c on fig ena ble d.?

Ia m p ass ing  th elogin det ails ofate st ed  we bsite using br ow ser .p ara ms in protra ctorlogi nsu i te.  But th e  p r o blem  i sthat  my  w eb ap plic a tio n has a restric tio n  for  s in gle log in for a user  a ccount. He nc e r unning t ests inmulticapablities in fir e fox and  ch romesimu ltaneousl y f ails.S inc e  onlyone br owser  u ser s essio n ca n e xi sts at a t i m e.P lease  p rovi de a wo rk around to solve thi s. It shouldbenice t opas s  d i ffe re n t l o g in params to fi refox andch r om e inside m u lti ca pabilit ies. is  it p o ssible. 

A:

The  browserin stan c e  ca n be fetch ed using  browser. g etPro c es sedCo nfi g andth e l ogincreden t ial s can  be as si gned a ccord in gly in o n-prepare of Protractor .conf. js
Re fer  browser. get P roc essedConf ig A PI doc
onP rep are : fun cti o n() { 
  br ows e r.get Proc e ssedConfi g () .th e n (f unction(con f i g ){      s witch( conf ig.capabilities.b r owserName) {
       c ase'c hrome':
           //log ic  for chrome 
            brows er.par ams.use r n am e  = 'bl ahbl ah' 
            break ;
        ca se 'fi refox' : 
             brows er.pa r a ms.us e rna me ='b lahbl
 viable_exceeds the_number of records which_you should_reasonably_keep in_a_local store.
In other_words the rendering_is not the only_thing that slows_down_the browser, it's also the amount of data you are trying to process locally.
If_you_feel you_need_to_implement infinite scrolling it's probably_time to convert to a_remotely loaded_data store.

A:

After an upgrade I found out that_this_i much easier_in extJS 4.2(beta). The infinite scrolling is detached from_the datastore. IE it does not_matter what type_of_datastore_you use. Also sorting_is working as you want it.
store_= Ext.create('Ext.data.SimpleStore',{
    _   autoLoad: true,
  _     _   pageSize:100,
 _ _    _  _data:[
 _  _     _  _  []
   __  ___ _], 
 __ _}

Ext.require('Ext.grid.plugin.BufferedRenderer')_
var grid = Ext.create('Ext.grid.
  __      _  plugins: 'bufferedrenderer',
__   _    _  store : store,
 _ _ _  }
//I load matrix data directly in the store for_speed
store.loadRawData(matrixData);

The application is so much faster_now.

 Q:

How to pass_different config_for_each instance of_a_browser created_by protractor in sharded config enabled.?

Iam passing_the login_details of a tested website using_browser.params in protractor login_suite._But the problem is that my_web application has  a restriction_for single login for a_user_account._Hence running tests in multicapablities_in firefox and chrome simultaneously fails.Since_only one browser_user session can exists at a time.Please_provide_a work around to solve this._It_should be nice to pass different_login_params_to firefox and chrome inside_multicapabilities. is it possible.

A:

The browser instance_can be fetched using browser.getProcessedConfig and the login credentials_can be assigned_accordingly in on-prepare of Protractor.conf.js
Refer_browser.getProcessedConfig_API_doc
onPrepare: function() {
    browser.getProcessedConfig().then(function(config){
   _ _  switch(config.capabilities.browserName)_{

         _  case 'chrome':
   _          _ //logic for chrome
    _      _   _browser.params.username_= 'blahblah'
     ____  _  _ break;

 _ _  _ _  _case_'firefox':
                browser.params.username =_'blahbl