Hi
I tried RSVP module a few days ago and I found it so incredible much complicated for standard visitor that I had to turn off.
There a lot of settings, various tabs, which are useless for standard visitors, and I almost lost inside that settings too.
When I am thinging for standard visitor who wants just send invitation to his friends about event what he just found, (probably just select some of his friends, and press send rsvp - everything i 1 minute), so I think it is imposible to do with this module until 10 minutes.
Did you try ever RSVP in facebook or other community site? There is everything simple. Simplicity is great. Nobody from standard visitors has time to learn use some functionality on webpage. And who really wants tons of settings, there still could be a closed fieldset with name "advanced settings" where it everything could be.
I really appreciate your work on this promising module, I will be hoping that it will be more simple to fast understand and use.
Thanks
Igorik
http://www.somvprahe.sk
Comments
Comment #1
ulf1 CreditAttribution: ulf1 commentedThanks for the comment.
I agree that the options when creating an invitation can be overwhelming, but the settings screen has not been designed for the "average" authenticated user in mind, but rather a moderator/admin to create an invitation.
I will keep this in mind for the next release.
At the moment the sending of invitations is not done by the cron job but rather manual directly when you click the "send invitations" link.
But I send an invitation today to 50 users in less then 20 seconds. So if it takes for you 1 minute to send one invitation you surely do something wrong or your webserver is slow.
Thanks,
Ulf
Comment #2
jaxpax CreditAttribution: jaxpax commentedI can agree with igorik. And I feel that this is not that is unique with just this module. The Drupal modules often seems to be better suited to "Superusers", the kind of users that have the time to learn about a system, simply because they have to learn, e.g. in a corporate Intranet.
A way to deal with this, I think, would be if the developer could split up the features in a very complex module plus the ability for the administrator to handle fine grain settings, more often than one can sometimes see in complex modules. But in complex modules like this the linearity from a "normal" user perspective is hard to fulfil as a developer, with a developers knowledge as a reference.
Something that is also kind of "dangerous" is that we "Drupalites", after a while, gets use to how it works in the world of Drupal. The logic in how Drupal developers think when they come up with an idea and the many terms that we use in the GUI when creating/configuring the sites, often gets far to complicated for a "normal" user. This is something that needs to be addressed more often in the Drupal community, so that we won't risk developing for the sake of our own.
Comment #3
ulf1 CreditAttribution: ulf1 commentedI agree.
The problem tends to be that in the CMS/open source world, developers write the modules mostly for their own purpose, and because of the developers knowledge the usability for others is mostly not perfect. And because the developers do their work mostly for free, changes tend to be more of the technical kind, but not focusing on usability.
If you do not like a module for what ever reason and seriously want to improve it, write a proposal and send it to the developer with some money attached. That way the developer has a reason to improve certain aspects of a module he otherwise would not consider doing.
For the RSVP module the final target is actually quite easy. At the end it should work similar like evite with all the bells and whistles but at the other end as easy to work with.
Still a long way to go...
Thanks,
Ulf
Comment #4
jaxpax CreditAttribution: jaxpax commentedYes a lot of time is spent by the developers and I guess that for the most part we site developers/configurers tend to get some what spoiled with how much that's get us served.
Ulf, how much of what igorik is asking for can be achieved with some simple CSS hacking, just for hiding elements that's not wanted?
//patrik
Comment #5
ulf1 CreditAttribution: ulf1 commentedThe invitation setup is done in function rsvp_addedit_form in file rsvp.module,
And here are some thoughts of making the form elements invisible: [#257334]
I started working on V2 and that will have an easier to use user interface.
~
Ulf
Comment #6
jaxpax CreditAttribution: jaxpax commentedAha, this is great. This is so good to know about. This raise my interest in start coding myself ;-)
Comment #7
ulf1 CreditAttribution: ulf1 commentedThe upcoming rsvp 6.x-2.x-dev release will support a basic and an extended mode when creating and editing invitations.
~
Ulf
Comment #8
jaxpax CreditAttribution: jaxpax commentedahh sounds great, Ulf!
I will look in to what it does as soon as possible, thanks!
//Patrik