[geeklog-devtalk] Re: [geeklog-devel] Blocks again...

[Tony Bibbs]

Wim,

I had suggested a similar associative table earlier but yours is unique 
in that it includes permissions at the associative level.  That is an 
interesting addition worth noting, however, is before the block-level 
security would be applied, the topic level security would come first 
(i.e. if you don't have access to the topic, you won't have access to 
any of the blocks).  Anyway, that is an interesting idea worth considering.

--Tony

Wim Niemans ri wrote:


>Hello,

>

>To my opinion, to implement a many to many relationship from block to 

>topic and vs, is to add an extra table to GL. Any other solution will 

>show only bugs and more bugs. An extra table opens up a nice extra 

>effect, that the same multiple select, or whatever comes up for the 

>user interface, can be included on topic level *and* on block level.

>

>GLtable 'layout_index'

>tid, bid, user_rights, group_rights

>

>Reflecting more on this feature, more beautyfull options can be 

>added: add a 'category' and let anything belong to a 'category': 

>event, plugin, contact, static page, user groups, and on, even 

>several topics or articles could belong to the same category.

>Think of colors when referring to categories.

>Look at the comment engine to see that anything can be linked to 

>anything.

>

>In this way, GL can group the information in articles, events, 

>plugins in a better and more effecitive way. I like the idea of 

>having the announcement (calendar) of the first geeklog seminar for 

>some time *automaticly* displayed within the 'about geeklog' topic.

>Or find the articles on 'security' under the event 'third network 

>security congres'. Find also a route drawing block as a left side 

>block to the calendar (and only there). Not that anybody has to 

>implement that, but it is possible, and community websites will use 

>that.

>

>Anyway, just dreaming I guess. 

>

>Cheers,

>wim niemans

>

>

>On 9 Jul 2004 at 12:00, geeklog-devtalk-request at lists.geeklog.net wrote:

>

>  

>

>>Vinny,

>>

>>    

>>

>>>Before we go through and implement this (assigning blocks to multiple

>>>topics) we should make sure that we have an idea for a decent user

>>>interface.  Otherwise it could make the block admin page very confusing.

>>>      

>>>

>>Simon already mentioned multi-select listboxes. A list of checkboxes may

>>be another alternative.

>>

>>Actually, my main concern here is with the representation of this

>>information in the database. The topics have a topic id of up to 20

>>characters. Instead of one topic, we now need to store a list of topics.

>>Any suggestions?

>>

>>The topics for the daily digest are currently stored in a VARCHAR(255) -

>>which means that you can have only around 10 topics there, before we run

>>out of space (and that case isn't even handled at the moment). So whatever

>>we come up with for the blocks should also be used there ...

>>

>>bye, Dirk

>>

>>    

>>

>

>

>_______________________________________________

>geeklog-devtalk mailing list

>geeklog-devtalk at lists.geeklog.net

>http://lists.geeklog.net/listinfo/geeklog-devtalk

>  

>