[geeklog-devel] User Profile Plugin API

[Blaine Lang]

I agree and would like to extend this screen and make the api's more 
flexible but one of the current design requirements or limitations when 
I did this work for 1.4.1 was that it had to work with Javascript 
disabled. We could continue to enhance the API's and Account Admin 
screen the same way where no panels effectively get displayed as new 
framed set of fields (fieldset) if JS is disabled. I think it's a good 
idea to still have a non-js enabled view - do all agree?

Another requirement I have seen is being able to not display certain 
tabs and while that can be done by removing the content from the 
templates, maybe we should have config options to remove them.

Blaine


Joe Mucchiello wrote:
> Before 1.5 releases, could something be done about the User Profile 
> API. PLG_profileVariablesEdit() is fine. The problem is 
> PLG_profileBlocksEdit(). They don't make sense now that the 
> userprofile is using the NavBar. The blocks must show in the Preview 
> tab and that's unfortunate. It would be really nice if the plugin 
> could create a new tab. My suggestion is to change the return from 
> plugin_profileblocksedit to a be either a string (as it is now) or an 
> assoc array. If a string is returned, it goes in the preview tab as 
> usual. If an array is returned, tabs are added to the navbar using the 
> key as the tab name and the value as the page data. If the name is 
> already existing, the data is appended to page.
>
> I haven't really researched this completely, but it would be more 
> consistent with the new interface.
>
> ----
> Joe Mucchiello
> Throwing Dice Games
> http://www.throwingdice.com
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>