[albatross-users] Authentication/Login example for RandomModules

[Sheila King]

--On Thursday, May 22, 2003 9:13 PM +1000 Dave Cole 
<djc at object-craft.com.au> wrote:

>>>>>> "Sheila" == Sheila King <sheila at thinkspot.net> writes:

>  For the
> people that are interested, you can have a look at the format that I
> have settled on by looking here.
>
>         http://www.object-craft.com.au/~djc/albatross/tag-ref.html
>
> It is only worth looking through until section 5.2.2.12 (because that
> is where I am up to).

I will try to take a look at it sometime in the next few days.

> At one point I was considering placing a table like the one for
> SimpleContext
>
>
> http://www.object-craft.com.au/~djc/albatross/pack-simplecontext.html
>
> for all prepackaged classes in chapter 8.  Maybe the rows in the table
> should be sorted by method name.

Since the methods are grouped by Mixin in the diagram, it would make
more sense to have them sorted alphabetically in the table. That way you
have two ways of searching. By Mixin (diagram) or Alpha (table).

> Sheila> The manual would benefit from more examples of Random Page
> Sheila> apps. You are welcome to use my example, or adapt it, if you
> Sheila> think it would be useful.
>
> Thanks.  I am going to concentrate on finishing off the documentation
> for the release.  I will try to resist distractions...  Andrew, are
> you able to have a look at the application?  Without seeing what you
> have done I think that it would be worth either cutting back the silly
> little popview application, or just adding a complete new application
> to the Application Guide that uses a random page structure.

I liked the POP View application. I suppose it could be because I am an
email Freak, however it seemed a somewhat meaningful, albeit simple,
example that most readers should be able to grasp. Even if you've never
worked with the rfc822 classes and the like, the concept of how an email
box works, listing messages and then clicking to read particular ones, is
a very familiar concept for most people.

Anyhow, here is a vote to keep the popview example.

On a different note:

I noticed something about my app the other night, that I didn't like:
If I log out and then use the browser's Back button, it takes me back
to the Main Account page. This is because the page is cached. However,
I would prefer if it were not possible to do that.

So...right now I'm trying to create my own class that will not cache
the pages. I changed the CachingTemplateLoaderMixin to just the
TemplateLoaderMixin, but this was not enough to prevent caching.

So, now I guess I am really going to have to dig in and see how to send
"no-cache" directives to the browsers, and probably override the
page_display method in the RandomPageModuleMixin.


-- 
Sheila King
http://www.thinkspot.net/sheila/
http://www.k12groups.org