[pLog-svn] r3385 - in plog/trunk:class/action/adminjs/tinymcejs/ui locale templates/admin

[Oscar Renalias]

On 12 May 2006, at 07:58, Mark Wu wrote:

> Hi Oscar:
>
> I see.
>
> 1. I will come up a new plugins structure, and change the menu.xml  
> and all
> related menu settings in plugins after we discussed

I am not really sure what this is going to improve. You still need,  
in some plugins, to have several different new menu entries in  
different places. Like the 'hostblock' or 'contentfilter' plugin,  
which need entries for the global management and for the blog- 
specific management.

The whole point of the dynamic menu system was to allow plugins to  
add new options to it so that it looks like, from an end-user  
perspective, that those options are there because they belong to the  
core. If some plugins have abused this functionaltiy and places  
entries all over the place, probably it's time to review those  
plugins and see whether they are really needed. But implementing a  
top-level "plugins" section woud defeat the point of the dynamic  
menus system in my opinion.

>
> 2. About the item 1, I think there will be no more new request
> parser/generator. In my original idea, user only deal with 5 request
> parser/generators ... (plain, pretty, custom, mod_rewrite, subdomain)
>
> But, we add a new parareters [htaccess_enabled] to url settings.
>
> If user choose yes, we will use the original 5 request parser/ 
> generators
> ....
>
> ==> the pretty will url will look like
> http://server/lifetype/function/path/info
>
> If user choose no, we will use the two new request parser/ 
> generators  to
> replace the original pretty url and custom url ..
>
> ===>http://server/lifetype/index.php?{function}={/path/info/}
>
> So, the change is transprent, user won't see the different.
>
> And this method also make our code or UI more clean.

Perhaps it doesn't sound that bad after all, but I fail to see what  
the difference is between this new method and normal plain URLs. The  
'?' is still there...