Results 1 to 4 of 4

Thread: Designing a full pledge application with EXT JS

  1. #1
    Ext JS Premium Member
    Join Date
    Jun 2013
    Location
    Philippines
    Posts
    64
    Answers
    1
    Vote Rating
    0
      0  

    Default Designing a full pledge application with EXT JS

    We are making an application were we need to have this requirements.

    - Login (API Authentication)
    - Logout (Killing the current user session)
    - Dashboard (which has lots of application menus )
    - Application (like Inventory, Reports , Stats and etc)

    I saw the Desktop sandbox example in the EXTJS package when I downloaded it and I think I like to have our application behave like this.

    My question are

    - how can I separate all of this requirements? Do i need to have a controller for each?
    - is there's a way to create an Application/Window class that will be have like an independent program?

    I hope you can help me regarding my query

  2. #2
    Sencha User existdissolve's Avatar
    Join Date
    Jan 2010
    Location
    Kansas
    Posts
    522
    Answers
    32
    Vote Rating
    89
      0  

    Default

    Question #1: No, you don't necessarily need a controller for each. The typical advice is to create controllers based on major sections of functionality of the application. So for example, if you have an Inventory management section, perhaps a single controller would be good to manage things related to Inventory management.

    Question #2: What do you mean by "behave like an independent program?"

  3. #3
    Ext JS Premium Member
    Join Date
    Jun 2013
    Location
    Philippines
    Posts
    64
    Answers
    1
    Vote Rating
    0
      0  

    Default

    Thanks for the reply..

    Regarding my other question , if you look at this desktop sample

    http://docs.sencha.com/extjs/4.2.1/extjs-build/examples/desktop/desktop.html

    It's like each application were independent from each other.. Please correct if im wrong but we have a large team so I'm thinking of separating modules or features for each individuals. We will just have a default Application/Window container

  4. #4
    Sencha Premium Member dawesi's Avatar
    Join Date
    Mar 2007
    Location
    Melbourne, Australia (aka GMT+10)
    Posts
    1,093
    Answers
    25
    Vote Rating
    56
      0  

    Default

    You could of course just break the different sections into various apps and use different namespaces to run them and also have a namespace for the desktop or core interface.

    There are also a couple of implementations of sub-applications around the forums for 4.x
    Lead Trainer / Sencha Specialist
    Community And Learning Systems

    Lead Architect
    DigitalTickets.net

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •