1. #1
    Sencha User
    Join Date
    Sep 2010
    Location
    Netherlands
    Posts
    120
    Answers
    3
    Vote Rating
    4
    aacoro is on a distinguished road

      0  

    Default Answered: Design of sample application

    Answered: Design of sample application


    Hi all,

    I'm a bit strugling in the decision of how to design my simple application.
    I want to create a sort of Kanban board to integrate with our system (all the tasks that should be picked up come from our own system (MSSQL).

    I can load the tasks into a gridpanel. But how should I represent the kanban lanes? Should I go with 1 grid for every lane, or use panel with custom HTML or something else that I miss??

    I prefer to create something like leankitkanban:
    leankit_ipad.jpg

    PS: We already use leankit but I am playing with a custom implementation on our own database just to improve some processes.. and to learn Ext Js

    Love to hear you advise!
    Last edited by aacoro; 22 Aug 2011 at 11:52 AM. Reason: typo errors

  2. If I were trying to implement the UI in that screenshot I don't think I'd use a grid at all.

    'To Do', 'Doing' and 'Done' would almost certainly just be components in an hbox.

    Within each section I see 2 obvious alternatives, depending on exactly what you want it to do. The lightweight option is to use a View:

    http://docs.sencha.com/ext-js/4-0/#!/api/Ext.view.View

    The heavier option is to implement each colored square as a component. Not sure exactly what layout I'd use to layout the squares, maybe vboxes nested in an hbox (or vice-versa).

    Ultimately I think it comes down to factors like how rich the content of the squares is and what the user interactions would be... clicking, dragging, etc.

    I suspect what I'd do in practice is to attempt to write it as a view and when that proves more difficult than I thought do it the other way instead.

  3. #2
    Sencha Premium Member skirtle's Avatar
    Join Date
    Oct 2010
    Location
    UK
    Posts
    3,572
    Answers
    540
    Vote Rating
    310
    skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future

      0  

    Default


    If I were trying to implement the UI in that screenshot I don't think I'd use a grid at all.

    'To Do', 'Doing' and 'Done' would almost certainly just be components in an hbox.

    Within each section I see 2 obvious alternatives, depending on exactly what you want it to do. The lightweight option is to use a View:

    http://docs.sencha.com/ext-js/4-0/#!/api/Ext.view.View

    The heavier option is to implement each colored square as a component. Not sure exactly what layout I'd use to layout the squares, maybe vboxes nested in an hbox (or vice-versa).

    Ultimately I think it comes down to factors like how rich the content of the squares is and what the user interactions would be... clicking, dragging, etc.

    I suspect what I'd do in practice is to attempt to write it as a view and when that proves more difficult than I thought do it the other way instead.

  4. #3
    Sencha User
    Join Date
    Sep 2010
    Location
    Netherlands
    Posts
    120
    Answers
    3
    Vote Rating
    4
    aacoro is on a distinguished road

      0  

    Default


    Thanks skirtle for your thoughts

    I will consider to use the component for the boxes. The components should be draggable, that is for sure.

    Clickable is not a requirements, since we have our own system opened where you can modify data. This is just for representing the data in a day by day view to see which items we picked up.

    Thanks man!

  5. #4
    Touch Premium Member
    Join Date
    Apr 2011
    Posts
    6
    Vote Rating
    0
    mrdunky is on a distinguished road

      0  

    Default Something like this?

    Something like this?


    I just came accross this today.
    Not ExtJS, but he describes how he uses <divs> with JQuery, and this may give you some ideas...

    http://codebrewery.blogspot.com/p/microview.html


  6. #5
    Sencha User
    Join Date
    Sep 2010
    Location
    Netherlands
    Posts
    120
    Answers
    3
    Vote Rating
    4
    aacoro is on a distinguished road

      0  

    Default


    Yaeh, I see similarities... thank you for sharing this url :-)

  7. #6
    Sencha User
    Join Date
    Sep 2010
    Location
    Netherlands
    Posts
    120
    Answers
    3
    Vote Rating
    4
    aacoro is on a distinguished road

      0  

    Default


    For the different vertical lanes (example: To do, In progress and Finished) would you create for each lane a seperate Store or just one store and filter the right records out?

    Cause I added one store and if I filter like this:

    Code:
    Store.filter('lane', 'ToDo');
    This will affect the other lane too, cause I filter on the same store here...

  8. #7
    Sencha Premium Member skirtle's Avatar
    Join Date
    Oct 2010
    Location
    UK
    Posts
    3,572
    Answers
    540
    Vote Rating
    310
    skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future skirtle has a brilliant future

      0  

    Default


    Filtering and sorting are as much a part of the store as the data. If you need different filters then you'll need different stores. If you have a lot of similar stores then I'd extend Ext.data.Store and create multiple instances of the subclass.

  9. #8
    Sencha User
    Join Date
    Sep 2010
    Location
    Netherlands
    Posts
    120
    Answers
    3
    Vote Rating
    4
    aacoro is on a distinguished road

      0  

    Default


    Quote Originally Posted by skirtle View Post
    Filtering and sorting are as much a part of the store as the data. If you need different filters then you'll need different stores. If you have a lot of similar stores then I'd extend Ext.data.Store and create multiple instances of the subclass.

    hmm... Extending the store is perhaps the way to go, because all the data will remain the same execpt for one field: lane. With the lanes field I want to identify in which lane to show the component.

    By extending a store i do the following? :
    - define a proxy for each subclass?
    - define fields on model and not the store?

    I just don't see the whole picture yet, how to extend the store so that each subclass loads the proper data.. sorry

Thread Participants: 2

Tags for this Thread

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