Aaron Nabil wrote: > Thank you. Again, I should warn everyone that I don't know ruby, rails or > postgres, I'm mostly limited to cut-and-paste and have at best a tenuous > grasp of what the code is doing, so please don't use any code I post on > your production pentabarf system without carefully examining it.
Never mind. Ruby, Rails and PostgreSQL are not that hard and your recent patches looked fine to me. >>First of all we should think about a name for this system. >>The name is needed for the controller and it would also appear in URLs >>to this system. > > I think I did that, sort of. The code I sent out was a back-port of my > initial > attempt at building my own submission system that I could play with as > a sandbox and not worry about it getting broken from a patch. These are > the files that ended up getting changed or created... > > pentabarf/app/controllers/visitor_controller.rb > pentabarf/app/helpers/application_helper.rb > pentabarf/app/helpers/visitor_helper.rb > pentabarf/app/views/layouts/visitor.rhtml > pentabarf/app/views/visitor/_modification_buttons.rhtml > pentabarf/app/views/visitor/_sidebar.rhtml > pentabarf/app/views/visitor/account_done.rhtml > pentabarf/app/views/visitor/event.rhtml > pentabarf/app/views/visitor/events.rhtml > pentabarf/app/views/visitor/index.rhtml > pentabarf/app/views/visitor/new_account.rhtml > pentabarf/app/views/visitor/person.rhtml > > which was a lot of junk to include as a patch for someone just to see what > it looked like, so I just stuck the few changed lines back in the original > submission system. > >>I thought of schedule but it doesn't really fit and >>there is already a controller with that name in pentabarf. Do you have a >>better proposal which expresses the purpose of the system. > > I have no preference for a name, but it looks like I called mine "visitor", > if we are talking about the same thing. Maybe "self_scheduler" or > "personal_schedule" or "myschedule" or some variation. I'd also be > happy leaving it in the submission system, but that may not be appealing > or practical for you, and of course the URL says "submission". But it > might avoid some unnecessary duplication, it is a small amount > of code. I would prefer a noun describing an action but until we come up with something better I will name it visitor which is quite good already. I don't like including this stuff into the submission system because their purpose differs a lot. The submission system is used in the call for papers phase long before the conference starts. People submit their papers and talks at the submission system. The visitor system is used shortly before they conference starts and maybe during the conference. People can look at the schedule and add events to their own schedule and get a personalized schedule/ical/xcal. Separating them also allows enabling and disabling them separately. The code duplication is not that much in my oppinion. The only code that gets duplicated is the account creation and activation this should probably be moved into a separate controller anyway. >>I think we should make a separate visitor role for this system, >>otherwise your conflict system might get totally cluttered by the >>conflicts of the visitors. > > Yes, I was simply going to mask out visitor/visitor conflicts in > the conflict system. Another role would be great, say, "attendee", the > conflict system could ignore attendee/attendee conflicts but > could still still flag speaker/attendee conflicts. We often have panelists > who say that they want to be sure to able to go listen to some other > panel discussion, so the system should be able to warn for those > conflicts. Attendee sounds fine. The visitor role was created exactly for the purpose you described. I will make a new conflict for attendee which is silent on the conflict page. > Speaking of roles, we also need some way to allow people who > create a new person (via the submission or "myschedule") system > to attach or remove themselves as an "attendee" to an event but prohibit > them > from promoting themselves to speaker or coordinator of that event. I will write procedures for this. > Sorry about the log file and .htaccess file, it had many more, I just > missed those two. Never mind. To implement the visitor system minor database changes are necessary. I will not apply them to 0.2.0 but will tag a new version once the system is functional. I will of course include a sql-script to upgrade the database from 0.2.0 to 0.2.1. Sven -- Sven Klemm <[EMAIL PROTECTED]> GnuPG: 0x71084F86 | 1319 F0DF B317 91F0 E48E 1957 7AF9 604C 7108 4F86
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pentabarf mailing list pentabarf@mail.skyhub.de https://mail.skyhub.de/cgi-bin/mailman/listinfo/pentabarf
