1. #11
    jay@moduscreate.com's Avatar
    Join Date
    Mar 2007
    Location
    Frederick MD, NYC, DC
    Posts
    16,353
    Answers
    102
    Vote Rating
    79
    jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all

      0  

    Default


    They shouldn't step on each other. I will warn you however, that the architecture is not really optimal. Think about how much JavaScript the browser has to utilize for one widget. An entire framework for one small set of functionality.

    Brian, I highly suggest rethinking your strategy if you can. You're headed down the road of instability and an unmaintainable application.

  2. #12
    Sencha Premium Member
    Join Date
    Feb 2012
    Location
    Raleigh, NC
    Posts
    418
    Answers
    23
    Vote Rating
    136
    brian428 is a splendid one to behold brian428 is a splendid one to behold brian428 is a splendid one to behold brian428 is a splendid one to behold brian428 is a splendid one to behold brian428 is a splendid one to behold

      0  

    Default


    Thanks for the confirmation.

    The architecture isn't something I have control over; the client manages that side of it and we're tasked with building a number of the widgets that will be used in the larger container.

    There are downsides, but size isn't an issue (client memory and bandwidth are high). They are much more interested in being able to consolidate a wide range of apps and data sources on servers across their infrastructure together into one interface. This is a pressing need for them since currently many of these systems are underused because of the sprawl across their network. So for the client, a consolidated interface essentially trumps any of the negatives for their selected approach.

  3. #13
    Sencha Premium Member
    Join Date
    Oct 2011
    Location
    Huntsville
    Posts
    227
    Answers
    6
    Vote Rating
    -6
    mark0978 is infamous around these parts mark0978 is infamous around these parts

      0  

    Default


    In this case, it seems like a single extjs instance in the browser using divs for the portlet regions would make the most sense from a memory standpoint. If each portlet has its own namespace (and maybe makes use of a common namespace for utility functions) it should be easy to build and remain sane.

    I'm doing a similar project right now and that is the path we have chosen, our portlets though are much more tightly woven than yours though, essentially being different ways of looking @ similar data. I'm figuring several of our stores will common and then each little portlet will be its own "app" within the wrapper app.

  4. #14
    jay@moduscreate.com's Avatar
    Join Date
    Mar 2007
    Location
    Frederick MD, NYC, DC
    Posts
    16,353
    Answers
    102
    Vote Rating
    79
    jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all jay@moduscreate.com is a name known to all

      0  

    Default


    Quote Originally Posted by brian428 View Post
    Thanks for the confirmation.

    The architecture isn't something I have control over; the client manages that side of it and we're tasked with building a number of the widgets that will be used in the larger container.

    There are downsides, but size isn't an issue (client memory and bandwidth are high). They are much more interested in being able to consolidate a wide range of apps and data sources on servers across their infrastructure together into one interface. This is a pressing need for them since currently many of these systems are underused because of the sprawl across their network. So for the client, a consolidated interface essentially trumps any of the negatives for their selected approach.
    Understood. I just thought i'd share my $.02 as a community member

Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..." hd porno faketaxi