[ISSUES] Closed: (JLCP-200) Store user preferences
[email protected] Sun, 29 Jun 2003 08:14:32 -0500 (CDT)
| Newsgroups | gmane.comp.java.javalobby.communityplatform |
|---|---|
| Message-ID | <[email protected]> |
Message:
The following issue has been closed.
Resolver: Matthew Schmidt
Date: Sat, 28 Jun 2003 8:25 PM
Some default user preferences are set on user creation and topics in forums pay attention to the # of items on a page. Same with the items in a folder of private messages.
---------------------------------------------------------------------
View the issue:
http://jira.jlcp.org/secure/ViewIssue.jspa?key=JLCP-200
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JLCP-200
Summary: Store user preferences
Type: New Feature
Status: Closed
Priority: Critical
Resolution: FIXED
Time Spent: Unknown
Estimate: 2 days
Project: Javalobby Community Platform
Components:
User Interaction Module
Fix Fors:
0.9.0 (Jupiter)
Versions:
0.9.0 (Jupiter)
Assignee: Matthew Schmidt
Reporter: Matthew Schmidt
Created: Wed, 7 May 2003 11:41 AM
Updated: Sat, 28 Jun 2003 8:25 PM
Description:
We need someone to make a Hibernate model that stores a user's preferences mapped to each user with a many-to-one. Example preferences include what type of thread view, how many private messages to list on one page, links per page, files per page, etc. This is important, so if someone could pick it up, that'd be great. All this should be editable through the profile page and it shouldn't take too long. Once its in place, we'll need another many-to-one object (I think) on JLCPUser.hbm.xml that holds the preferences object. Then all our pages can check that in the taglibs to know how many to fetch with each request.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.jlcp.org/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira