Child pages
  • Suggestion: Section Manager
Skip to end of metadata
Go to start of metadata

Imported From: http://groups.google.com/group/in-portal-org/browse_thread/thread/584afb62901f5b44#

I would like to suggest new feature for developers, named Section Manager. I'll describe it's idea shortly.

Section Manager is DEBUG MODE only visible section under Configuration Tools. It contains list with all sections, at each section there's detailed information about section and also checkboxes (or dropdown) for section visibility management. So, using these controls user developer can show section, hide section or choose to display it only in DEBUG MODE or SUPER ADMIN mode.

Second main Section Manager's feature is section order management. Sections can be moved up and down, level up and level down using drag- n-drop and toolbar buttons.

Technically it all can be achieved in following way: Section Manager writes all modifications it made to Cache table (or other table). When section cache is rebuilt (using existing mechanism), after all Sections & SectionAdjustments keys are read from configs, Section Manager adjustments are applied. So result is stored in Sections Cache, where from platform reads section information.

It would attractive feature for In-Portal newbies and could be helpful specially during In-Portal-based project start phase.

8 Comments

  1. I think, that jQuery UI sortable control will ease dragging task for
    us.
  2. Sergey, Thanks a lot for bringing this idea up!

    Yes, I totally agree it will be super useful and most definitely will
    attract new users to In-Portal.

    I can add that we already have quite powerful tools for switching
    between the Admin Interfaces. As you might now in In-Portal 5 serious
    we introducing "Site Configs" feature when you can literally configure
    your own Admin by changing - sections, tabs, columns, making fields
    required or simply hide them. This is all down with the help of
    overriding default unit configs by loading simpler site config file
    for each requested prefix on the fly. While it works as expected and
    we can even have multiple set of Site Configs - I still believe that
    we still can HUGELY benefit from the better user interfaces here and
    ability to do them all online. This is where I think your idea comes
    in and rocks the world :)

    We need something that we can use in Admin to easily move things
    around by dragging as well as configuring each and every aspect listed
    above.

    Some resources to see on Site Configs and other:

    1.

    INP-16 - Getting issue details... STATUS

    (scroll down for SVN
    change sets)

    2.

    INP-161 - Getting issue details... STATUS

    (actual switch
    implementation)

    3. http://www.wil-linssen.com/demo/jquery-sortable-ajax/  (interesting
    Demo for list dragging)

    Everyone on this list what do you think on this?

    Cheers!

    PS. Sergey, I think you should register in http://tracker.in-portal.org
    - you might find many new interesting things and your input is always
    welcome!

  3. If you store all the settings in Cache or similar table - you can't easily
    move it between prod/dev/live servers and it will be a real pain to
    synchronize it all. Need to find more portable way of storing the settings.

    Sincerely,
    Konstantin Tjuterev

    Intechsystems SIA
    http://www.intechsystems.lv
    +371 6747-12-77

  4. Hi!

    As we are going to participate in development, please provide commit access
    to SVN for users kostja, sergeyg. Thanks!

    Sincerely,
    Konstantin Tjuterev

    Intechsystems SIA
    http://www.intechsystems.lv
    +371 6747-12-77

  5. Hey Kostya,

    I am glad to hear that you and Sergey are on board!

    Your SVN access will be setup and emailed you directly.

    I'd like to take a moment and outline a few basic rules for development
    process. This will help us to keep the development moving in the right
    direction.

    1. For BUGS the process is the following:

    REPORT -> DISCUSS -> PLAN -> DEVELOP -> TEST -> COMMIT -> RESOLVE

    2. For FEATURES

    DISCUSS -> PLAN -> DEVELOP -> TEST -> COMMIT -> RESOLVE

    Please note that no step can be skipped!

    IMPORTANT: NO Code can be Committed unless there is a Task (in Issue
    Tracker) for it and proper Commit Comments are used.

    More detailed rules will be posted on In-Portal.ORG website shortly.

    For those of you who is still undecided whether they want to participate
    in In-Portal code development and/or other areas of the project, we
    always welcome additional HEADS and HANDS so feel free to contact us
    here with any questions.

    Let me know if any questions on above.

    Cheers!

    --

    --
    Best Regards,

    Dmitry V. Andrejev

  6. Thanks!

    Could you also give me a link to bugtracker and create an account there? Or let me know if I could register myself. Thanks!

    Sincerely,

    Konstantin Tjuterev

    Intechsystems SIA

     <http://www.intechsystems.lv> http://www.intechsystems.lv

    +371 6747-12-77

    From: in-portal-org@googlegroups.com [mailto:in-portal-org@googlegroups.com] On Behalf Of Dmitry
    Sent: Friday, September 18, 2009 18:45
    To: in-portal-org@googlegroups.com
    Subject: Re: SVN access request

    Hey Kostya,

    I am glad to hear that you and Sergey are on board!

    Your SVN access will be setup and emailed you directly.

    I'd like to take a moment and outline a few basic rules for development process. This will help us to keep the development moving in the right direction.

    1. For BUGS the process is the following:

    REPORT -> DISCUSS -> PLAN -> DEVELOP -> TEST -> COMMIT -> RESOLVE

    2. For FEATURES

    DISCUSS -> PLAN -> DEVELOP -> TEST -> COMMIT -> RESOLVE

    Please note that no step can be skipped!

    IMPORTANT: NO Code can be Committed unless there is a Task (in Issue Tracker) for it and proper Commit Comments are used.

    More detailed rules will be posted on In-Portal.ORG website shortly.

    For those of you who is still undecided whether they want to participate in In-Portal code development and/or other areas of the project, we always welcome additional HEADS and HANDS so feel free to contact us here with any questions.

    Let me know if any questions on above.

    Cheers!

    --

    --
    Best Regards,

    Dmitry V. Andrejev

  7. Issue Tracker is OPEN for everyone to join!

    http://tracker.in-portal.org

    Kostya, you'll be promoted to development access once registered. I believe
    Sergey is already there.

    A few quick notes:

    1. We have centralized User Account system between:

    - Issue Tracker
    - In-Portal.ORG and In-Portal.COM site (both closed from Public yet)
    - Wiki User Docs
    - Wiki Development Guide

    It will auto-create accounts and auto-login on all these sites.

    2. Major Discussion and Planning for new Bugs and Development should take
    place in:

    - Bug -- http://groups.google.com/group/in-portal-bugs
    - Development -- http://groups.google.com/group/in-portal-dev

    Issue tracker should be used when we already decided and moving forward with
    development/fixes and need to post some notes.

    Questions are welcome.

    Cheers!

    DA.

    On Fri, Sep 18, 2009 at 11:25 AM, Konstantin Tjuterev <

  8. Closed, because I agree with Konstantin Tjuterev comment on migration issues between different servers.