[OGo-Users] Changes to trunk, Testing
Sebastian Reitenbach
users@opengroupware.org
Mon, 11 Feb 2008 09:45:29 +0100
users@opengroupware.org wrote:
> On 10.02.2008, at 20:16, Sebastian Reitenbach wrote:
> > I did not implemented anything regarding the topic. I just said, how
> > it is
> > right now, however you name it group or category.
>
> Please reread the thread (especially the last 8 mails or so)
> _carefully_ before posting any more mails on the topic.
well, it seems, we have a small communication problem, understanding the
meaning of the words of each other ;)
>
> > Unfortunately you removed the important part, here it is again ;) :
>
>
> We have _long_ left the discussion on 'how it is right now'. I have
> understood the issue you have:
> ---snip---
> Thats correct, though the fact is visualized in the resourcemanager
> ---snap---
>
> And posted a suggestion on how to solve it:
> ---snip---
> >> I think it would be more useful to persist the fact that the user
> >> selected a 'group' (hence doesn't care which projector he gets).
> ---snap---
>
> And pointed you _again_ on it:
> ---snip---
> Your example does not apply if the user would choose to store a
> category (like "projectors") instead of a specific projector.
> ---snap---
>
> And _yet_ another time:
> ---snip---
> ---snip---
> >> I think it would be more useful to persist the fact that the user
> >> selected a 'group' (hence doesn't care which projector he gets).
> ---snap---
> (or how did you try it???)
> ---snap---
As said, I selected the group "Projectors" in the calendar proposal to
create the whole day event and I went into a conflict.
>
> If you want to continue the thread please focus on the topic and
> elaborate why this wouldn't solve the issue you have and why your
> 'amount' column would be better.
I already wrote in another mail, that the amount might be a bit too
complicated, therefore I reverted back to the bool field, "ignore conflicts"
Unfortunately, the bugzilla is not available right now, but I'll create a
bugzilla entry when it is running again, about the missing ability to choose
a "resource group" when creating an appointment not using the proposal
function.
>
>
> I'm pretty sure its the correct(tm) solution for implementing your
> requirement using the existing setup (_not_ some amount column).
> However, I wouldn't put too much work into implementing that in the
> perspective that:
> ---snip---
> Resources require a rework anyways. Its more likely that resources
> will become another SQL-view on top of the company table to enhance
> consistency with iCalendar.
> ---snap---
> Which BTW is the same like 'resources are participants', in case this
> isn't obvious.
yes, and I think that such an implementation would do what I want, so I'm
fine with that, looking forward to the time when it will be implemented.
that was my last mail to that topic, not stressing the topic any further.
cheers
Sebastian