Back to dreamler

fredrik.stal@gmail.com

← The Dreamler Community

My feedback

  1. Ability to edit previous chat massages in activities

    3 votes
    Vote
    Sign in Sign in with Dreamler
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Feature requests and ideas » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Thomas Wingate responded

    Thinking some more about this we decided to do editable comments on some form in the future.

    fredrik.stal@gmail.com commented  · 

    Ofc i'm a Dreamler user! I love it and see great potential! :D

    (hope to see editable comments in the future ;)

    fredrik.stal@gmail.com commented  · 

    Just because you call something a chat does not mean it is a chat ;)

    Better than to theorise about this is to evaluate how your users use it. Do they sit there chatting with other participants or do they for instance use it to leave notes, comments or questions on progress or halts?

    I believe the answer is obvious but that is just from my perspective and as such, imho, irrelevant as sole basis for change.

    Ask your users and get a collected view of the matter.

    fredrik.stal@gmail.com shared this idea  · 

  2. Resources should be added to participants (or some other list/database)

    4 votes
    Vote
    Sign in Sign in with Dreamler
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Feature requests and ideas  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Thomas Wingate responded

    Makes a lot of sense to be able to handle resources as persistent instances, in the same way as we do with project participants today.

    This has been in the works for a long time but the prerequisites are library functionality and UI, multi-node manipulation and a decent UI to add/copy/instance such resources on the gameboard using the modeling tool.

    There are also a bunch of unanswered questions relating to this. The biggest one probably how to handle alterations to persistent objects and template components being used across multiple projects over time?

    fredrik.stal@gmail.com commented  · 

    Go a little agile on this and just expand the functionality of "participans". You have a complete functioning database and UI for this. Just add other resources (persons) to it, et voila, a first step in solving the problem.

    fredrik.stal@gmail.com shared this idea  · 

Feedback and Knowledge Base

(thinking…)