just a few bits

Your feedback here will be highly appreciated.
pagemeeting
Posts: 10
Joined: Wed May 13, 2009 11:41 pm
Location: Strasbourg, France
Contact:

just a few bits

Postby pagemeeting » Sat Jul 25, 2009 8:40 am

This app is really slick, but its approach is really hard as far as templates and their components are concerned.
May be a default template with 3 steps and a very basic permissions scheme would help to start?
I have been able to get what I wanted, but I am still missing a view which shows me what I am doing, because the resulting behaviour depends on states and transitions at the same time, but it is difficult to know what you do unless you write it down as a block diagram, and it easy to go in circles. And to ass to the confusion, a user can belong to several groups + roles, so not easy to figure out where you go. And that is the major brake for success of this app.
May be a treeview would help representing the states and related transitions a better way than a flat display? I have done a similar thing once to represent book components which could be interleaved or embedded, and it did help users to figure out the page numbering.
Now some tiny bits:
- groups should be called Global groups in menu versus local groups in projects
- disabled buttons would be better grayed out than unvisible
- welcome screen should be blank if the no guest is enabled
- if it does not add too much complexity, maybe a component would be welcome as sub-project? for instance, you may have a dev guy for coding, another one for UI, and a common one for test, and i'd like in this case to separate things for the first 2 devs guys depending on which component is concerned.
And a remark, when changing state, and no assignment is required, why does it go to "fields" if none has been set? couldn't this be skept in this case?
too old to rock and roll, too young to die

User avatar
Artem
eTraxis Support
Posts: 227
Joined: Mon Sep 15, 2008 2:51 am
Location: Auckland, New Zealand
Contact:

Re: just a few bits

Postby Artem » Mon Jul 27, 2009 12:49 pm

Thank you for sharing your feel of eTraxis - such feedbacks are really useful and help me to improve the system. Let me answer item by item:
May be a default template with 3 steps and a very basic permissions scheme would help to start?
The demos, available at www.etraxis.org, have one prepared and ready-to-use simple template. I think I should just share the XML-file of this template to let other people import it and play with.
I have been able to get what I wanted, but I am still missing a view which shows me what I am doing, because the resulting behaviour depends on states and transitions at the same time, but it is difficult to know what you do unless you write it down as a block diagram, and it easy to go in circles. And to add to the confusion, a user can belong to several groups + roles, so not easy to figure out where you go. And that is the major brake for success of this app.
May be a treeview would help representing the states and related transitions a better way than a flat display? I have done a similar thing once to represent book components which could be interleaved or embedded, and it did help users to figure out the page numbering.
Yes, you are absolutely right. The inconvenience and incomprehensibility of existing interface of creation a template was always my headache. I was hurrying up on initial development of eTraxis and made this part of interface just in the fastest way, keeping in mind that I can improve it later. And I still have a plan to do it, in new "2.0" release line of eTraxis, which is under progress (that's why I didn't publish any new releases recently) and going to be released by this Autumn. Meanwhile, the only thing I can say - current interface is not intended to design a new template, it's only intented to enter one. But things will change, I hope, and the treeview idea looks like it can make the trick.
groups should be called Global groups in menu versus local groups in projects
Accepted, will change.
disabled buttons would be better grayed out than unvisible
Accepted, will change.
welcome screen should be blank if the no guest is enabled
Accepted, will change.
if it does not add too much complexity, maybe a component would be welcome as sub-project? for instance, you may have a dev guy for coding, another one for UI, and a common one for test, and i'd like in this case to separate things for the first 2 devs guys depending on which component is concerned.
Yes, I agree it's required. Actually, the situation, you described, inspired me to implement subrecords. Here is how I saw it. If several engineers have to do something to fix the bug, you can create subrecords. Any record (named "parent") can have unlimited number of subrecords. Also, each subrecord can be dependency. Parent record cannot be closed, if it has at least one opened subrecord as dependency. Let's assume, that to fix the bug your team needs:
  • fix the code (some developer has to do this),
  • update tests (some test engineer will do),
  • update design documentation (one more engineer).
In this example, you can create three different subrecords and assign them to three different engineers. Master record (parent) should also be assigned to somebody, who will just track subrecords and will close parent record, when all subrecords are done.

But as I found later, the subprojects approach is very popular, is used in several other similar systems (e.g. Redmine), and already is familiar to people. So I started to think whether I should implement subprojects too. Your post is just a proof that I should.
And a remark, when changing state, and no assignment is required, why does it go to "fields" if none has been set? couldn't this be skept in this case?
Well, I don't want just to skip it, because it can way to accidental change of a state - this screen with "none" fields works just as confirmation in this case. Of course, I thought about normal confirmation via JavaScript "confirm" message box, but I'd like to keep use cases similar to each other, that's why I chose to confirm via the same type of page.
Best regards,
Artem

User avatar
Artem
eTraxis Support
Posts: 227
Joined: Mon Sep 15, 2008 2:51 am
Location: Auckland, New Zealand
Contact:

Re: just a few bits

Postby Artem » Wed Oct 14, 2009 7:05 am

groups should be called Global groups in menu versus local groups in projects
disabled buttons would be better grayed out than unvisible
welcome screen should be blank if the no guest is enabled
Hi,

Just want to inform you, that all three items above are implemented in new version 2.0.1, which has been released today.

Best regards,
Artem
Best regards,
Artem


Who is online

Users browsing this forum: No registered users and 1 guest