[tyndale-devel] Crosswire bookmarks and initial sketch of user login
chris at burrell.me.uk
Tue Mar 22 02:29:13 MST 2011
I agree that in some respects it is strange. The rationale behind having to
log on for Bookmarks and not history is that history is something people
expect to be able to clear from their cookies. Bookmarks I would expect to
be able to get back to at a later date or on a different computer. If I were
using a different PC, would I expect to see my bookmarks and/or my history?
My feeling is that at least the bookmarks where I've intentionally said
"bookmark this!" I'd like to see all over the place. The problem is that if
we don't get people to log in, then we can't track their bookmarks across
anything but a cookie which is valid for that particular session/until the
cookies get cleared.
Maybe it's a bit like a wishlist and the history on Amazon. With the history
you kind of expect them to track it With the wishlist it's tied to your
account a bit more.
perhaps the history should be tracked server side as well. Happy to make
changes, but thought I'd try and explain why it is so, first. (obviously the
login prompt will come up for other features as well if they require logging
On 21 March 2011 20:02, David Instone-Brewer
<davidinstonebrewer at gmail.com>wrote:
> Yep - that works nicely.
> It seems strange though - you don't expect to log in for this.
> What about putting registration at Install Bibles instead, and reserve
> login for notes and other personal stuff?
> You often have to give an email address to download stuff nowadays, so it
> seems more normal.
> The blinds in the middle work really nicely.
> David IB
> At 18:19 21/03/2011, Chris Burrell wrote:
> There should be a new version of STEP on
> It should contain Bookmarks (well viewing them). There's some test code in
> there at the moment, to automatically create a user in a in-memory database:
> username/email: t at t.c
> password: password
> The user can't do anything, so the data is not particularly sensitive! You
> can register another user if you like (again, if i rebuild this disappears,
> and it's not encrypted or anything like that at the moment).
> Once logged in, you should be able to see two bookmarks. The history should
> now also be based on cookies, so that when you come back later, whatever
> passage you were viewing is there. The data displayed under "History" is
> stored in the cookie too and therefore persists across sessions. History is
> stored in the in-memory database and therefore is only available when you
> log in.
> NOTE: There is a noticeable gap where the user can't delete a gap (also, if
> the tomcat server gets restarted, or when i redeploy, then the data
> tyndale-devel mailing list
> tyndale-devel at crosswire.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tyndale-devel