On Wed, 7 Jun 2000, Neeme Praks wrote:
>
> I created a simple customization feature: there can be more than one
> PSML file (both, in the case of default user and in the case of
> authenticated users). Right now it searches for this file in this order,
> if the custom file is specified:
> 1. username_customFile.psml
> 2. customFile.psml
> 3. default.psml
>
> Otherwise it uses the old pattern:
> 1. username.psml
> 2. default.psml
>
> I was thinking, maybe it is beneficial to also add one more fallback
> mechanism, to use the following search order in the case of custom file:
> 1. username_customFile.psml
> 2. username.psml
> 3. customFile.psml
> 4. default.psml
>
> I'm not sure about this, though. Anybody else, comments?
>
I am not sure how this should look either. Off the top of my head having a
directory with all the users with multiple custimizations means that
directory is going to be chock full o stuff. Maybe IMHO too much stuff.
> Ideally I would like to put different files for different users in
> separate directories.
> Default/default.psml
> Default/customFile.psml
> Neeme/default.psml
> Neeme/customFile.psml
>
+1 with caveat
I like this but I would also go one step further and make the directory
configurable by assigning each user a home directory on the server. I am
not sure how to do this because Jetspeed currently doesnt require a
database, which is where I would store the home directory.
> Would be cleaner solution, but it wouldn't be backwards compatible...
>
IMHO Jetspeed is at a stage of development where this type of backwards
compatibility is not such an issue. As a matter of fact I believe that
too much thought on backward compatibility too early can be very
detrimental because it can tie you into something you have totally
outgrown...
I think in the future when our user
base is much larger and more established we will need to think about a
more formal deprecation scheme
> I was also thinking about the user personalization in the case of
> current codebase (no Cocoon2, etc.).
> When user specifies different files, Jetspeed tries to find the user's
> personal file, if not found, would take the common file (for all users)
> with that name, if that is also not found then would take the deafult
> file for all users.
> In case user modifies something on some page (minimizes a portlet, etc),
> Jetspeed creates a copy of the common file for the user and then saves
> changes to that file. This would save disk space, as quite many of the
> users probably won't want to use the personalization features.
>
> Also, this rises the issue of storing metainformation about these files:
> I want to show kind of toolbar to the user with links to some or all
> possible custom files.
>
> Any comments?
>
I think that personalization is very important to Jetspeed and I will try
to help you along on this as much as possible. I may even get to helping
write code.
In the meantime keep digging in the code and submitting more patches.
I didnt write the original code on this so I wont commit the patch, but
maybe Kevin could weigh in on this.
I would like to hear from Kevin on these changes and would like the active
developers to weigh in on personalization in general.
Some questions,
What should be configurable?
colors?
which portlets to display on a page?
Page title?
Page meta-data?
If we have more than one personalized page (which I would like to +1 that)
how do we navigate between pages?
Should users be able to share some of their personalized pages with
friends/world/anyone?
How would the permissions look on this?
Jeff Prickett
[EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
