>
> Because it is unclear where to store the overlay selection.  (Cookie?
> Session?  The database?)

As a user I do like that currently it remembers my last view so I have
vote for cookie.  From empirical data it looks as if the selection of
overlay is stored in the database itself for the authenticated user.
Since no one signs in to unauthenticated calendar how could SchoolTool
remember each persons view? Even if there was a way I think that
having the database handle that is probably a bad idea. Why take on
more responsibility than you have to have to?  These public calendars
could get  quite a lot of hits depending on the organization. Maybe if
the same practice was employed for the authenticated user it might
trim some fat off the database too.  Not that I'm saying it's fat! 
--ducks to avoid high heel--  :)   Either way we could make the
default view whatever the authenticated user is set for.


> So, the admin chooses the contents of the overlay portlet, and the
> choice is stored in the database as a site preference.

That's how it's currently done.  It's works well although practically
no one inuits that TT stands for time table.


>
> I have to say I didn't quite understand those scenarios.
>

I'm just trying to illustrate that if the program changed tomorrow it
probably wouldn't offend anyone.  Does that make more sense?


Thanks,
Peter


On 12/13/05, Marius Gedminas <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 12, 2005 at 06:10:07PM -0500, Peter Hartmann wrote:
> > Why not just use the existing overlay interface  (cal and TT columns)
> > for authenticated users?
>
> Because it is unclear where to store the overlay selection.  (Cookie?
> Session?  The database?)
>
> > >   (1) designing the user interface for this (which calendars should be
> > >       overlaid and where?  Can the anonymous user decide by
> > >       himself/herself, or is it a decision made by the site
> > >       administrator?)
> >
> > Regarding the existing overlay interface: I like that the
> > administrator chooses which calendars a user can overlay, if any, and
> > that the user can choose of that list which she actually views.
>
> So, the admin chooses the contents of the overlay portlet, and the
> choice is stored in the database as a site preference.
>
> The unauthenticated user can check/uncheck the checkboxes to
> enable/disable overlaying of those calendars.  Where is the selection
> remembered?  I think the session makes most sense.
>
> Did I get this right?
>
> Sounds like a plan.  The next step would be to create a wishlist issue
> and wait patiently.  Or find an interested Python developer that has
> some spare time.
>
> > Scenario #1:
> (snip)
> > Scenario #2:
> (snip)
>
> I have to say I didn't quite understand those scenarios.
>
> > Doesn't it make sense to give this existing feature to
> > unauthenticated users? What do you think?
>
> It does.
>
> Marius Gedminas
> --
> HOST SYSTEM NOT RESPONDING, PROBABLY DOWN. DO YOU WANT TO WAIT? (Y/N)
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFDnqG7kVdEXeem148RAqd3AJ9uJpnBbGphBZJ5Pg1qpp8BXdy+qwCgkCu+
> GPlAmEb0LpElB3SHcFVTJAk=
> =RcRp
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Schooltool mailing list
> [email protected]
> http://lists.schooltool.org/mailman/listinfo/schooltool
>
>
>
_______________________________________________
Schooltool mailing list
[email protected]
http://lists.schooltool.org/mailman/listinfo/schooltool

Reply via email to