Thread: [Rainbowportal-devel] issues with module gallery creation, suggestions welcome.
Brought to you by:
danijel_kecman,
manudea
From: Chris F. <ch...@cf...> - 2003-09-28 01:56:52
|
Hey rainbow team, I am working on a module to showcase "Add-In modules" by 3rd party contributors that are not included in the core. Hopefully this will be the rainbow version of snowcovered or the asp.net control gallery. There are a few issues in this module that I have not yet decided how to resolve, looking for suggestions. I am still somewhat of a newbie with rainbow so there might be an easy fix I'm not aware of, either way here goes. 1: Edit permissions for owner. I don't think rainbow supports an "edit by owner" permission. The idea is to use workflow so that an author can submit code and rainbow can review it before approval. The problem is that the author will not be able to update their entry without giving them full scale edit permissions for all listed items since permissions are on a per module/tab basis and this module has multiple items with different owners. This should be something we address soon with rainbow IMHO. 2: File safeguards to prevent deleting/overwriting other peoples files. Downloadables are stored on the file system, I need some method to ensure they do not use the same file name as an existing file that they didn't create and over write it. Since I was considering adding multiple-downloads per item, I might use dynamically created subfolders. As of right now files are stored in _Rainbow\ModuleGallery, the idea would be to have files stored in _Rainbow\ModuleGallery\ModuleName so that if they do over-write a file it is their own file. 3: Pictures/Methods. Thumbnails have been requested but I don't see they fit into the equation. The gallery view that shows all of the modules on a page/category doesn't have room for them, the detail view will have a large picture. I am thinking I will simply set a maximum size for a picture in terms of width/height, any pictures above the size will be resized and any pictures below will be centered in the cell of the table. Suggestions? 4: Version compatibility. I want to have version compatibility for each module/rb version. I read about the issues DNN is having with compatibility from 3rd party contributions, I would like to prevent the same. I can do this one of two ways. a: single text field with delimiter. Let sql server do a full text search. Advantage is that it is simpler, cost is that it is slower. b: a composite entity table(rb_ModuleGallery(1)->(M)rb_ModuleGalleryCompatibility(M)<-rb_Versions). Forgive the ascii representation of a crows foot diagram. This would allow better searching for users to select only compatible and tested modules. There it is. If anyone wants the code, send me an email. I do not know if it is in CVS yet and the module is still considered to be late alpha/early beta. Cheers, Chris Farrell ch...@cf... |
From: mark m. <mar...@ho...> - 2003-09-28 11:31:36
|
1) Edit Owner Permissions The current Discussion Module allows individuals to edit their own postings without having module-wide edit permissions. You can use it as an example on how to implement this feature. I agree this feature should be added to all modules, we just need someone to volunteer to edit the base class and all of the existing modules. 2) File safeguards: The Documents Module, Pictures, and probably a few others have the same issue. Hopefully a single strategy can be agreed to. 3) I agree thumbnails aren't needed. I also agree to your resize/center logic. 4) This needs more thought than I can spend right now. Please do coordinate with Graz on this. Mark -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of Chris Farrell Sent: Sunday, September 28, 2003 2:45 AM To: rai...@li... Subject: [Rainbowportal-devel] issues with module gallery creation, suggestions welcome. Hey rainbow team, I am working on a module to showcase "Add-In modules" by 3rd party contributors that are not included in the core. Hopefully this will be the rainbow version of snowcovered or the asp.net control gallery. There are a few issues in this module that I have not yet decided how to resolve, looking for suggestions. I am still somewhat of a newbie with rainbow so there might be an easy fix I'm not aware of, either way here goes. 1: Edit permissions for owner. I don't think rainbow supports an "edit by owner" permission. The idea is to use workflow so that an author can submit code and rainbow can review it before approval. The problem is that the author will not be able to update their entry without giving them full scale edit permissions for all listed items since permissions are on a per module/tab basis and this module has multiple items with different owners. This should be something we address soon with rainbow IMHO. 2: File safeguards to prevent deleting/overwriting other peoples files. Downloadables are stored on the file system, I need some method to ensure they do not use the same file name as an existing file that they didn't create and over write it. Since I was considering adding multiple-downloads per item, I might use dynamically created subfolders. As of right now files are stored in _Rainbow\ModuleGallery, the idea would be to have files stored in _Rainbow\ModuleGallery\ModuleName so that if they do over-write a file it is their own file. 3: Pictures/Methods. Thumbnails have been requested but I don't see they fit into the equation. The gallery view that shows all of the modules on a page/category doesn't have room for them, the detail view will have a large picture. I am thinking I will simply set a maximum size for a picture in terms of width/height, any pictures above the size will be resized and any pictures below will be centered in the cell of the table. Suggestions? 4: Version compatibility. I want to have version compatibility for each module/rb version. I read about the issues DNN is having with compatibility from 3rd party contributions, I would like to prevent the same. I can do this one of two ways. a: single text field with delimiter. Let sql server do a full text search. Advantage is that it is simpler, cost is that it is slower. b: a composite entity table(rb_ModuleGallery(1)->(M)rb_ModuleGalleryCompatibility(M)<-rb_Versi ons). Forgive the ascii representation of a crows foot diagram. This would allow better searching for users to select only compatible and tested modules. There it is. If anyone wants the code, send me an email. I do not know if it is in CVS yet and the module is still considered to be late alpha/early beta. Cheers, Chris Farrell ch...@cf... ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel |
From: Graziano P. <gra...@du...> - 2003-09-29 15:54:37
|
hi Chris we are planning to create a kind of shop for 3rd parties modules / skins / services rainbow based. I'm sure that there are a lot of hidden modules and the aim is to generate revenues for developers / contributors and to collect commercial stuffs. this should help all of us (easier to buy a module instead of generate a clone). you will receive an email so soon about this new feature i think that ur job may be interesting also thinking to the rainbow shop thnx p.s. if anyone is interested in knowing something more about the shop, pls write to me at gra...@du... - thnx ----- Graziano Poretti http://www.rainbowportal.net - http://www.duemetri.com ----- Tutte le informazioni contenute in questo messaggio di posta elettronica ed i files ad esso allegati sono riservati e possono essere utilizzati esclusivamente dal destinatario specificato. L'accesso all' e-mail e l'eventuale uso del suo contenuto da parte di qualsiasi soggetto a cio non autorizzato, sono severamente proibiti. Nel caso in cui si riceva il messaggio per errore e assolutamente vietato usarlo,copiarlo o, comunque, divulgarlo mediante comunicazione e/o diffusione e bisogna provvedere sia alla sua cancellazione sia alla distruzione di tutte le copie esistenti All the informations and attachments included in this message are strictly reserved and can be viewed and used by the specified recipent only. The use of the content by any other subject except the recipent is strictly forbidden. In case of receipt of this message by mistake it's strictly forbidden the use, copy or forwarding of it and in any way and it must be destroyed, included all the existing copies. -----Messaggio originale----- Da: rai...@li... [mailto:rai...@li...]Per conto di Chris Farrell Inviato: domenica 28 settembre 2003 1.45 A: rai...@li... Oggetto: [Rainbowportal-devel] issues with module gallery creation, suggestions welcome. Hey rainbow team, I am working on a module to showcase "Add-In modules" by 3rd party contributors that are not included in the core. Hopefully this will be the rainbow version of snowcovered or the asp.net control gallery. There are a few issues in this module that I have not yet decided how to resolve, looking for suggestions. I am still somewhat of a newbie with rainbow so there might be an easy fix I'm not aware of, either way here goes. 1: Edit permissions for owner. I don't think rainbow supports an "edit by owner" permission. The idea is to use workflow so that an author can submit code and rainbow can review it before approval. The problem is that the author will not be able to update their entry without giving them full scale edit permissions for all listed items since permissions are on a per module/tab basis and this module has multiple items with different owners. This should be something we address soon with rainbow IMHO. 2: File safeguards to prevent deleting/overwriting other peoples files. Downloadables are stored on the file system, I need some method to ensure they do not use the same file name as an existing file that they didn't create and over write it. Since I was considering adding multiple-downloads per item, I might use dynamically created subfolders. As of right now files are stored in _Rainbow\ModuleGallery, the idea would be to have files stored in _Rainbow\ModuleGallery\ModuleName so that if they do over-write a file it is their own file. 3: Pictures/Methods. Thumbnails have been requested but I don't see they fit into the equation. The gallery view that shows all of the modules on a page/category doesn't have room for them, the detail view will have a large picture. I am thinking I will simply set a maximum size for a picture in terms of width/height, any pictures above the size will be resized and any pictures below will be centered in the cell of the table. Suggestions? 4: Version compatibility. I want to have version compatibility for each module/rb version. I read about the issues DNN is having with compatibility from 3rd party contributions, I would like to prevent the same. I can do this one of two ways. a: single text field with delimiter. Let sql server do a full text search. Advantage is that it is simpler, cost is that it is slower. b: a composite entity table(rb_ModuleGallery(1)->(M)rb_ModuleGalleryCompatibility(M)<-rb_Versions) . Forgive the ascii representation of a crows foot diagram. This would allow better searching for users to select only compatible and tested modules. There it is. If anyone wants the code, send me an email. I do not know if it is in CVS yet and the module is still considered to be late alpha/early beta. Cheers, Chris Farrell ch...@cf... ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel |
From: manu <ma...@du...> - 2003-09-30 08:21:05
|
1. Edit permissions for owner. Well, this is a great thing. Unfortunately is a mod tha would change = core and now we are stabilizing things. I will not for it in the new authorization project. In the meantime we can do 1 module for one author and set permission accordingly. This should be enough for a start. ------------------------------------ Emmanuele De Andreis Technical Manager DUEMETRI Internet Solutions Provider RAINBOW PORTAL Main portal - http://www.rainbowportal.net Sourceforge CVS - http://sourceforge.net/projects/rainbowportal/ Support Forums - http://www.rainbowportal.net/ASPNetForums Bug Tracker - = http://sourceforge.net/tracker/?group_id=3D66837&atid=3D515929 -----Messaggio originale----- Da: rai...@li... [mailto:rai...@li...] Per conto di = Chris Farrell Inviato: domenica 28 settembre 2003 1.45 A: rai...@li... Oggetto: [Rainbowportal-devel] issues with module gallery creation, suggestions welcome. Hey rainbow team, I am working on a module to showcase "Add-In modules" by 3rd party=20 contributors that are not included in the core. Hopefully this will be the rainbow version of snowcovered or = the=20 asp.net control gallery. There are a few issues in this module that I have not yet decided how to resolve,=20 looking for suggestions. I am still somewhat of a newbie with rainbow so there might be an = easy=20 fix I'm not aware of, either way here goes. 1: Edit permissions for owner. I don't think rainbow supports an "edit = by=20 owner" permission. The idea is to use workflow so that an author can submit code and rainbow can review it = before=20 approval. The problem is that the author will not be able to update their entry without giving them full=20 scale edit permissions for all listed items since permissions are on a per module/tab basis and this module has multiple=20 items with different owners. This should be something we address soon with rainbow IMHO. 2: File safeguards to prevent deleting/overwriting other peoples=20 files. Downloadables are stored on the file system, I need some method to ensure they do not use the same file name as an=20 existing file that they didn't create and over write it. Since I was considering adding multiple-downloads per = item,=20 I might use dynamically created subfolders. As of right now files are stored in _Rainbow\ModuleGallery, the idea = would=20 be to have files stored in _Rainbow\ModuleGallery\ModuleName so that if they do over-write a file = it=20 is their own file. 3: Pictures/Methods. Thumbnails have been requested but I don't see = they=20 fit into the equation. The gallery view that shows all of the modules on a page/category doesn't have room for=20 them, the detail view will have a large picture. I am thinking I will simply set a maximum size for a picture in terms of = width/height, any pictures above the size will be resized and any pictures below will be centered in the cell of the=20 table. Suggestions? 4: Version compatibility. I want to have version compatibility for = each=20 module/rb version. I read about the issues DNN is having with compatibility from 3rd party contributions, I would like to=20 prevent the same. I can do this one of two ways. a: single text field with delimiter. Let sql server do a full text search. Advantage is that it is simpler, cost is that it is slower. b: a composite entity=20 table(rb_ModuleGallery(1)->(M)rb_ModuleGalleryCompatibility(M)<-rb_Versio= ns) .=20 Forgive the ascii representation of a crows foot diagram. This would allow=20 better searching for users to select only compatible and tested modules. There it is. If anyone wants the code, send me an email. I do not know = if=20 it is in CVS yet and the module is still considered to be late alpha/early beta. Cheers, Chris Farrell ch...@cf... ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel |