rainbowportal-documents Mailing List for RainbowPortal
Brought to you by:
danijel_kecman,
manudea
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(2) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(14) |
2005 |
Jan
|
Feb
(5) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <jon...@jo...> - 2005-03-13 10:09:24
|
I saw some comments here while reading through the archive about documenting zen, and an improved theme sample for the pack. First of, i think this is a great idea, but a few issues have to be concerned. I have been playing with zen for a while, and worked out themes that do great with it. The issue comes in a few problems. 1) alot of the zens power and potential is dwarfed because of pages that are still in classic table layout, such as property pages, admin page, viewitem and edit pages. Alot of html tables, and calsses are just sort of wasted space when you are using the zen. My probelm here, i am not so sure you can jsut remove all this, because of backwards compatibilty with the classic themes and desktop panes. 2) the ie7 scripts. these are hurting the pages in my opinion. they slow down the page loads, and have issues. there are better api's that i have tested and played with such as the one on cross-browser.com that are better suited and better tested. They load quicker, and have lots of power. I will be posting my updating site theme in the next week or so, so you can see. 3) I still dont know what the zenfloater div is for if someone can explain it's purpose :-) So I guess most of my concernes with the current use of zen is its attempt to live in rainbow with the classic table parts. Maybe part of the docuementing ideas concerning theming, should make a clear divider between the two and how to go about correcting yoru app to suit zen better if that is your choice. |
From: William F. <WF...@im...> - 2005-02-21 09:18:19
|
I've found that TortoiseCVS is the easiest way to get at the CVS... It is slightly a pain to setup though because our CVS is not properly structured (the main Rainbow folder is in that admin settings CVSROOT folder)... I suggest you download that, it is an explorer shell extension (right click menu addon)... Once you are ready to go, look at the CVS page on our sourceforge project and I think somebody made a page in the confluence at support.rainbowportal.net for this as well...=20 You'll note that the current builds have some css files that overlap (multiple definitions for certain classes that should be cleaned up)... You'll want to copy the folder named for the theme you want to start with (I start zen stuff with the zen starter one) and rename your copy to whatever (no spaces)... Then it will show up in the dropdown.. You may have to change a comment in your web config (just change 1 character in the file and reupload it) to make the app restart and read the new theme list if it doesn't at first... Let us know if you need anything, Bill -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of Jody Brewster - BJI Sent: Sunday, February 20, 2005 8:01 AM To: Mark Mcfarlane; Mark Mcfarlane; rai...@li...; rai...@li...; Anne Panne Radestedt Cc: gra...@du... Subject: RE: [Rainbowportal-documents] Re: Team Lead for Designer position Great tips on that last email, I'm going to start creating a theme, and I'll document as I go along. I'll check out and use the new zen engine if that's the standard you'll be using going forward. I'll also have some mod requests since I do know alot about strict markup and css2-3. I'm also very familiar with Windows/C# development (have VS 2003) and would like to start working with the code at some point, although I'll need to learn how to access the CVS rep at somepoint. What software are you all using to access this on Windows by the way? =20 But like you said, I'll take it slow and contribute one thing at a time. But first I really need to learn the system and I guess the zen engine. By the way, I'm having alot of problems with theme/layout changing especially with additional portals. Its just not changing the theme for some reason. I'm gonna setup the project to debug and see what's happening, that will give me more insight into how Rainbow itself is made up as well. Thanks for the tips again -----Original Message----- From: Mark Mcfarlane [mailto:mar...@ar...] Sent: Sat 2/19/2005 12:16 AM To: 'Mark Mcfarlane'; rai...@li...; Jody Brewster - BJI; rai...@li...; 'Anne Panne Radestedt' Cc: gra...@du... Subject: RE: [Rainbowportal-documents] Re: Team Lead for Designer position Jody, =20 The graphics and documentation mailing lists are pretty much unused. If Graz agrees, I suggest you sign up for the developers mailing list. You will get some support there while building your designs. =20 Also, Rainbow has 2 different ways to design UI, one based on themes/layouts and the other using the new zen engine. If you are comfortable in .css then Zen may be your choice. I'm not an expert in either, but this discussion can happen on the developer mailing list. =20 mark =20 =20 _____ =20 From: Mark Mcfarlane [mailto:mar...@ar...] Sent: Saturday, February 19, 2005 8:05 AM To: 'rai...@li...'; 'Jody Brewster - BJI'; 'rai...@li...'; 'Anne Panne Radestedt' Cc: 'gra...@du...' Subject: RE: [Rainbowportal-documents] Re: Team Lead for Designer position =20 Hi Jodi, =20 We are glad you wish to contribute. You will need to eventually get CVS access working if you are going to be modifying the standard Rainbow theme components but this is not necessary from the start. =20 Step 1) I suggest that to get started you just create one simple theme/layout using one of the existing themes as a starting template to showcase your design skills. If you end up testing it on multiple platforms and browsers then indicate so in a readme file. =20 Step 2) If you like, while performing step 1 above you could write a quick step-by-step tutorial for what you did to transform one of the default themes/layouts into your new 'great design'. =20 I would encourage you to not take on too much at first. Many people with huge initial ambitions disappear after they realize how much work they have committed to. If all you do is Step 1, you will have made a valuable and lasting contribution. Maybe as you do step 1 you can take notes that will make doing step 2 easy when you get around to it :-) =20 Cheers, =20 Mark McFarlane =20 _____ =20 From: rai...@li... [mailto:rai...@li...] On Behalf Of Graziano Poretti Sent: Thursday, February 17, 2005 11:17 AM To: Jody Brewster - BJI; rai...@li...; rai...@li...; Anne Panne Radestedt Subject: [Rainbowportal-documents] Re: Team Lead for Designer position =20 hi Jody =20 well ... i haven't really completely understood your email, but if you want to join the graphic team, well .. you are the most welcome. cvs is used for the devel team only (not really important releases for skins). while in the devel community there are 1 team leader "de facto" (manu), graphic, localization and documentation teams haven't one. i added you to the graphic team and documentation team and this email is a kind of "welcome" email to you. so .. welcome on board! let me know if i can do something more for you =20 thnx for joining =20 =20 =20 <http://www.duemetri.com>=20 <http://www.duemetri.com> RAINBOW TEAM =20 Graziano Poretti Rainbow Product Manager=20 Due Metri s.a.s.=20 <mailto:gra...@du...> gra...@du...=20 tel:=20 ++39 0184 42163 URI:=20 <mailto:gra...@du...> 55...@se...=20 =20 =20 =20 =20 ----- Original Message -----=20 From: Jody <mailto:jbr...@br...> Brewster - BJI=20 To: hr...@ra...=20 Sent: Wednesday, February 16, 2005 7:13 PM Subject: Team Lead for Designer position =20 My name is Jody Brewster I'm the webmaster at Brown Jordan International and I'm interested in your team lead in the designer position. I'm extremely fluent in the web in general, cross browser compatibility, search engine optimization techniques, markup languages, css, javascript, flash/actionscript/, php, .net, c#, java/j2ee, etc. The only thing I really don't know is the intricacies of open-source development, cvs, and especially in regards to .net. I'm still new to .net, I've been forced to program in asp for the past year and we're just now starting to rework all of our asp applications for .net. We're looking at using this as an intranet portal application but I still need to look and get use to what the Rainbow team has implemented so far. In doing so, I believe what's best is for me to be proactive in the project. And I need to start by getting familiar with the interface and themes. I'm also interested in helping along with your documentation =20 =20 I'm also wondering if you all have decided on a logo yet out of the 14 or so on the Italian site my personal site http://www.nidin.com =20 =20 =20 Jody Brewster Webmaster=20 Phone: 954-960-1821 Fax: 954-960-1849 <mailto:jbr...@br...> jbr...@br... Brown Jordan International <http://www.brownjordan.com/> http://www.brownjordan.com 1801 N. Andrews Avenue Pompano Beach, FL 33069 =20 =20 =20 |
From: Jody B. - B. <jbr...@br...> - 2005-02-20 15:59:30
|
Great tips on that last email, I'm going to start creating a theme, and = I'll document as I go along. I'll check out and use the new zen engine = if that's the standard you'll be using going forward. I'll also have = some mod requests since I do know alot about strict markup and css2-3. = I'm also very familiar with Windows/C# development (have VS 2003) and = would like to start working with the code at some point, although I'll = need to learn how to access the CVS rep at somepoint. What software are = you all using to access this on Windows by the way? =20 But like you said, I'll take it slow and contribute one thing at a time. = But first I really need to learn the system and I guess the zen engine. = By the way, I'm having alot of problems with theme/layout changing = especially with additional portals. Its just not changing the theme for = some reason. I'm gonna setup the project to debug and see what's = happening, that will give me more insight into how Rainbow itself is = made up as well. Thanks for the tips again -----Original Message----- From: Mark Mcfarlane [mailto:mar...@ar...] Sent: Sat 2/19/2005 12:16 AM To: 'Mark Mcfarlane'; rai...@li...; = Jody Brewster - BJI; rai...@li...; 'Anne = Panne Radestedt' Cc: gra...@du... Subject: RE: [Rainbowportal-documents] Re: Team Lead for Designer = position Jody, =20 The graphics and documentation mailing lists are pretty much unused. If Graz agrees, I suggest you sign up for the developers mailing list. You will get some support there while building your designs. =20 Also, Rainbow has 2 different ways to design UI, one based on = themes/layouts and the other using the new zen engine. If you are comfortable in .css = then Zen may be your choice. I'm not an expert in either, but this = discussion can happen on the developer mailing list. =20 mark =20 =20 _____ =20 From: Mark Mcfarlane [mailto:mar...@ar...]=20 Sent: Saturday, February 19, 2005 8:05 AM To: 'rai...@li...'; 'Jody Brewster - = BJI'; 'rai...@li...'; 'Anne Panne Radestedt' Cc: 'gra...@du...' Subject: RE: [Rainbowportal-documents] Re: Team Lead for Designer = position =20 Hi Jodi, =20 We are glad you wish to contribute. You will need to eventually get CVS access working if you are going to be modifying the standard Rainbow = theme components but this is not necessary from the start. =20 Step 1) I suggest that to get started you just create one simple theme/layout using one of the existing themes as a starting template to showcase your design skills. If you end up testing it on multiple = platforms and browsers then indicate so in a readme file. =20 Step 2) If you like, while performing step 1 above you could write a = quick step-by-step tutorial for what you did to transform one of the default themes/layouts into your new 'great design'. =20 I would encourage you to not take on too much at first. Many people = with huge initial ambitions disappear after they realize how much work they = have committed to. If all you do is Step 1, you will have made a valuable = and lasting contribution. Maybe as you do step 1 you can take notes that = will make doing step 2 easy when you get around to it :-) =20 Cheers, =20 Mark McFarlane =20 _____ =20 From: rai...@li... [mailto:rai...@li...] On Behalf = Of Graziano Poretti Sent: Thursday, February 17, 2005 11:17 AM To: Jody Brewster - BJI; rai...@li...; rai...@li...; Anne Panne Radestedt Subject: [Rainbowportal-documents] Re: Team Lead for Designer position =20 hi Jody =20 well ... i haven't really completely understood your email, but if you = want to join the graphic team, well .. you are the most welcome. cvs is used = for the devel team only (not really important releases for skins). while in = the devel community there are 1 team leader "de facto" (manu), graphic, localization and documentation teams haven't one. i added you to the graphic team and documentation team and this email is = a kind of "welcome" email to you. so .. welcome on board! let me know if i can do something more for you =20 thnx for joining =20 =20 =20 <http://www.duemetri.com>=20 <http://www.duemetri.com> RAINBOW TEAM =20 Graziano Poretti Rainbow Product Manager=20 Due Metri s.a.s.=20 <mailto:gra...@du...> gra...@du...=20 tel:=20 ++39 0184 42163=20 URI:=20 <mailto:gra...@du...> 55...@se...=20 =20 =20 =20 =20 ----- Original Message -----=20 From: Jody <mailto:jbr...@br...> Brewster - BJI=20 To: hr...@ra...=20 Sent: Wednesday, February 16, 2005 7:13 PM Subject: Team Lead for Designer position =20 My name is Jody Brewster I'm the webmaster at Brown Jordan International = and I'm interested in your team lead in the designer position. I'm = extremely fluent in the web in general, cross browser compatibility, search engine optimization techniques, markup languages, css, javascript, flash/actionscript/, php, .net, c#, java/j2ee, etc. The only thing I = really don't know is the intricacies of open-source development, cvs, and especially in regards to .net. I'm still new to .net, I've been forced = to program in asp for the past year and we're just now starting to rework = all of our asp applications for .net. We're looking at using this as an intranet portal application but I still need to look and get use to what = the Rainbow team has implemented so far. In doing so, I believe what's best = is for me to be proactive in the project. And I need to start by getting familiar with the interface and themes. I'm also interested in helping along with your documentation =20 =20 I'm also wondering if you all have decided on a logo yet out of the 14 = or so on the Italian site my personal site http://www.nidin.com =20 =20 =20 Jody Brewster Webmaster=20 Phone: 954-960-1821 Fax: 954-960-1849 <mailto:jbr...@br...> jbr...@br... Brown Jordan International <http://www.brownjordan.com/> http://www.brownjordan.com 1801 N. Andrews Avenue Pompano Beach, FL 33069 =20 =20 =20 |
From: Daniela N. <dni...@ea...> - 2004-12-31 19:30:16
|
How about putting these golden nuggets of information/documentation/wisdom into the Rainbow Wiki Documentation space? That way it won't get lost, it is visible and searchable by all, and it becomes obvious when there is enough accumulated to warrant a new document? Daniela _________________________________________________________________ "It is with logic that we prove, but by intuition that we discover." (Henri Poincare) ----- Original Message ----- From: Mike Stone To: rai...@li... Sent: 12/30/2004 6:14:21 AM Subject: re: [Rainbowportal-devel] Style Sheet Question ( S-P-A-M5.4/5.0 ) Thank you, I will put this away someplace safe until it the doc team has a chance to take it and run with it :) Mike Stone Director of Computer Information Services Kaskaskia College 27210 College Road Centralia, IL 62801 618-545-3201 www.kaskaskia.edu >>> je...@ma... 12/30/2004 07:04:15 >>> Hi Mike, Thanks for asking this question: I am guilty of not providing documentation for this and several other new features in Page.cs cssFileList is a private member accessible only through: public void RegisterCssFile(string key, string file) There is a corresponding method: public bool IsCssFileRegistered(string key) Obviously, therefore, it is designed to be used in exactly the same fashion as the framework-provided script injectors. An example might be a particular custom module which carries it's own unique CSS. From within the module's Page_Load you could inject that CSS file into the page (using IsCssFileRegistered to make sure you only do it once for the page). There is a sister technique to this one with two similar methods: public bool IsCssImportRegistered(string key) public void RegisterCssImport(string key, string import) This would be used in the same way, but instead of "injecting" a <link>...<link> to CSS file, you feed it strings and it will write those strings into the <head> of the page enclosed in a <style> block. Another alternative is to create a custom theme to go with your custom module and use the Custom Theme per Module feature. This works very differently: it will parse the CSS found in the theme's referenced CSS file, prefix every rule-set with the module unique ID, then inject that CSS into the output page in a <style>...</style> block. This ensures that none of the injected CSS will overlap or override the page's "overall" theme, even if the same selectors are used. Here's an example of what the page output might look like: <html> <head> <title>Hello, world!</title> <meta name="generator" content="Rainbow Portal - see http://www.RainbowPortal.net"/> <META http-equiv="Content-Type" content="text/html; charset=windows-1252" /> <link rel="stylesheet" href="/rainbow/Design/Themes/zen-RainbowInfo-1/zen.css" type="text/css"/> <link rel="SHORTCUT ICON" href="/rainbow/Portals/RainbowInfo/portalicon.ico"/> <style type="text/css"> <!-- #mID10268 p{margin:0 0 0.33em 0;color:Gray;font-size:1em;font-style:italic;} #mID10268 h2{margin:0em;padding:0em 1em 0em 5px;color:Red} --> </style> <style id="spMenuStyle" type="text/css"></style> <script type="text/javascript" src="/rainbow/aspnet_client/popupHelper/popup.js"></script> </head> <body> etc... Thus paragraphs and level 2 headings in the module whose ID is 10268 will be styled differently to the rest of the page. In order for a theme to appear in the dropdown list of Custom Themes on the module's settings page, its name must start with "module-". It follows also that you'll want to keep the CSS short! Note that an alternative, depending on your requirement, would be to use Zen's technique of combining multiple CSS files. In the CSS file that is nominated by your Theme, use one or more CSS "include" statements: @import url(rainbow.css); @import url(admin.css); body{ ...blah... ...blah... } etc.... Whilst I'm on the subject, there are three more new "injectors" in Page.cs: public bool IsClientScriptRegistered(string key) public void RegisterClientScript(string key, string filePath) which will inject a <link> to Javascript file into the <head>, public bool IsAdditionalMetaElementRegistered(string key) public void RegisterAdditionalMetaElement(string key, string element) which will inject any supplied string (usually a complete <meta> element) into the <head> element, and public bool IsBodyOnLoadRegistered(string key) public void RegisterBodyOnLoad(string key, string functionCall) which will assemble supplied strings into a single onload="..." attribute and add it to the <body> element of the page. Also available (through the Site Settings page) are a DOCTYPE injector and a "body attributes" injector. Lastly, on the subject of CSS, the PortalModuleControl class has a new feature: it wraps every module in a <div> element with two attributes set as follows: <div id="mID10268" class="HtmlModule_ascx>...</div> Thus you can now target CSS rules at specific module instances (by using the ID) or all instances of a module type (by using the class). For example: #mID10268 p{color:red} will affect paragraph elements ONLY in the module whose ID is 10268 .HtmlModule_ascx p{color:red} will affect paragraphs ONLY in instances of the Html Module. Note that all these tricks are available to Classic and Zen sites - they are in the core, not specific to Zen, although Zen makes extensive use of them. I hope this explains everything. Let me know if you have any questions or problems. Jeremy (jes1111) ----------------------- Original Message ----------------------- From: "Mike Stone" <ms...@kc...> To: <rai...@li...> Date: Wed, 29 Dec 2004 22:16:47 -0600 Subject: [Rainbowportal-devel] Style Sheet Question I noticed that the Page.cs has a foreach loop to load I would think more then one .css file for a given Theme/Layout? How do you do this? I have a .css file that is for all my custom modules for my intranet mostly for datagrids and such so they all look the same, but every time I upgrade I have been manually adding them to the theme. How does cssFileList get more then one entry? ps. Yes I know I can copy a theme to a new name and just copy that theme back into the upgraded with my changes. was thinking this way might be useful for other things. Thanks Mike Stone Director of Computer Information Services Kaskaskia College 27210 College Road Centralia, IL 62801 618-545-3201 www.kaskaskia.edu ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel |
From: Mark M. <mar...@ar...> - 2004-12-27 04:25:36
|
There is a fair amount of overlap between your three scenarios, but I think with a bit of organization you can minimize content replication. The consumer one is most important today in my mind. Mark -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of Daniela Nii Sent: Monday, December 27, 2004 5:13 AM To: rai...@li... Subject: [Rainbowportal-documents] RE:Overhaul of installation document Mark wrote: "Also, I suspect there are either new steps or unnecessary steps since this doc was first created 20 months ago." Mark, I agree with you. One can see that quite a few things have been added or supercede info that is listed there. The time has come to give it a shake down. :) I was playing around with the idea of addressing three distinct installation scenarios: 1) consumer: user who wants to use official release and add-ins, 2) developer: user who wants to use the CVS build(s) to modify and expand the functionality, and 3) hosted: installing the Rainbow Portal with a third party service provider What do you think? Or did I miss something? Daniela ______________________________________________________________ "It is with logic that we prove, but by intuition that we discover" (Henri Poincare) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Rainbowportal-documents mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-documents |
From: William F. <WF...@im...> - 2004-12-27 02:41:00
|
I found the link to that... =20 http://readyset.tigris.org/ =20 They don't cover everything, but they have some good general templates that you can download in a few different formats. =20 ________________________________ From: rai...@li... [mailto:rai...@li...] On Behalf Of Daniela Nii Sent: Sunday, December 26, 2004 6:31 PM To: rai...@li... Subject: [Rainbowportal-documents] RE: Any documentation style guidelines =20 Thanks, William. I will see what I can find. =20 I will also see, if I can come up with a few guidelines for our documentation. Although, I most likely need to dive into more Rainbow documentation needs to get a picture of what kind of docs are needed for the guidelines and styles to make sense... =20 Okay, one thing at a time. :) =20 Daniela =20 _________________________________________________________________ "It is with logic that we prove, but by intuition that we discover." (Henri Poincare) =20 =20 ----- Original Message -----=20 From: William Forney <mailto:WF...@im...> =20 To: rai...@li... Sent: 12/25/2004 6:13:03 AM=20 Subject: RE: [Rainbowportal-documents] Any documentation style guidelines =20 A while ago I sent a link to an OS project that was specifically making document templates for other OS projects and such. I think it was on tigris.org, but am not sure. You could check there. =20 =09 ________________________________ From: rai...@li... [mailto:rai...@li...] On Behalf Of Mark Mcfarlane Sent: Friday, December 24, 2004 9:16 PM To: rai...@li... Subject: RE: [Rainbowportal-documents] Any documentation style guidelines =20 Hi Daniela, =20 Sorry it has taken a few days to respond to you. Unfortunately there are no documentation style guides / templates / etc in place. =20 =20 I wrote the original installation guide as a new user and as my first contribution to Rainbow about 20 months ago. At the time there was no meaningful documentation at all for the project and the web site was in trouble. After writing the install docs I spent about 9 months updating and maintaining the web site. For the past year I have had very little involvement in Rainbow due to other personal commitments. =20 Basically you can do anything you want. Show off your skills in both content and design :-). Eventually the install documentation should probably end up in Rainbow's Wiki but I personally prefer a standard doc format (like MS Word or .pdf) for easy delivery and printing of the installation document. =20 =20 If you don't apply a lot of advanced formatting, copying a document into Wiki is pretty easy. Authoring anything more than a few paragraphs in a Wiki is pretty painful so I'd write in MS Word or your favorite tool, and then we can deliver as a .doc, .pdf, or copy it into the Wiki. =20 =20 I think the Wiki concept is excellent but I find it very difficult to find content within the current Rainbow implementation. =20 Also, I wanted to thank you for your recent thoughtful comments about Rainbow on the mailing list. Rainbow will certainly benefit from your mature attitude. Please ignore the 'trash talk' that has happened in the past few days. We've only had 2 or 3 flare-ups like this in the past 20 months, in general everyone acts like adults! We've had a few well intentioned but very strong-willed people join the group recently, who haven't yet learned how express frustration constructively, and it has set off some mini-flame wars. =20 Welcome aboard, and Merry Christmas. =20 Mark McFarlane =20 =09 ________________________________ From: rai...@li... [mailto:rai...@li...] On Behalf Of Daniela Nii Sent: Friday, December 24, 2004 3:41 AM To: rainbowportal-documents Subject: [Rainbowportal-documents] Any documentation style guidelines =20 Hi Mark, =20 Do you have any documentation style and formatting guidelines, preferences that I should follow for the installation document? MS Word is the way to go? =20 Thanks a bunch, Daniela |
From: Daniela N. <dni...@ea...> - 2004-12-27 02:27:35
|
Thanks, William. I will see what I can find. I will also see, if I can come up with a few guidelines for our documentation. Although, I most likely need to dive into more Rainbow documentation needs to get a picture of what kind of docs are needed for the guidelines and styles to make sense... Okay, one thing at a time. :) Daniela _________________________________________________________________ "It is with logic that we prove, but by intuition that we discover." (Henri Poincare) ----- Original Message ----- From: William Forney To: rai...@li... Sent: 12/25/2004 6:13:03 AM Subject: RE: [Rainbowportal-documents] Any documentation style guidelines A while ago I sent a link to an OS project that was specifically making document templates for other OS projects and such. I think it was on tigris.org, but am not sure. You could check there. From: rai...@li... [mailto:rai...@li...] On Behalf Of Mark Mcfarlane Sent: Friday, December 24, 2004 9:16 PM To: rai...@li... Subject: RE: [Rainbowportal-documents] Any documentation style guidelines Hi Daniela, Sorry it has taken a few days to respond to you. Unfortunately there are no documentation style guides / templates / etc in place. I wrote the original installation guide as a new user and as my first contribution to Rainbow about 20 months ago. At the time there was no meaningful documentation at all for the project and the web site was in trouble. After writing the install docs I spent about 9 months updating and maintaining the web site. For the past year I have had very little involvement in Rainbow due to other personal commitments. Basically you can do anything you want. Show off your skills in both content and design J. Eventually the install documentation should probably end up in Rainbows Wiki but I personally prefer a standard doc format (like MS Word or .pdf) for easy delivery and printing of the installation document. If you dont apply a lot of advanced formatting, copying a document into Wiki is pretty easy. Authoring anything more than a few paragraphs in a Wiki is pretty painful so Id write in MS Word or your favorite tool, and then we can deliver as a .doc, .pdf, or copy it into the Wiki. I think the Wiki concept is excellent but I find it very difficult to find content within the current Rainbow implementation. Also, I wanted to thank you for your recent thoughtful comments about Rainbow on the mailing list. Rainbow will certainly benefit from your mature attitude. Please ignore the trash talk that has happened in the past few days. Weve only had 2 or 3 flare-ups like this in the past 20 months, in general everyone acts like adults! Weve had a few well intentioned but very strong-willed people join the group recently, who havent yet learned how express frustration constructively, and it has set off some mini-flame wars. Welcome aboard, and Merry Christmas. Mark McFarlane From: rai...@li... [mailto:rai...@li...] On Behalf Of Daniela Nii Sent: Friday, December 24, 2004 3:41 AM To: rainbowportal-documents Subject: [Rainbowportal-documents] Any documentation style guidelines Hi Mark, Do you have any documentation style and formatting guidelines, preferences that I should follow for the installation document? MS Word is the way to go? Thanks a bunch, Daniela |
From: Daniela N. <dni...@ea...> - 2004-12-27 02:13:14
|
Mark wrote: "Also, I suspect there are either new steps or unnecessary steps since this doc was first created 20 months ago." Mark, I agree with you. One can see that quite a few things have been added or supercede info that is listed there. The time has come to give it a shake down. :) I was playing around with the idea of addressing three distinct installation scenarios: 1) consumer: user who wants to use official release and add-ins, 2) developer: user who wants to use the CVS build(s) to modify and expand the functionality, and 3) hosted: installing the Rainbow Portal with a third party service provider What do you think? Or did I miss something? Daniela ______________________________________________________________ "It is with logic that we prove, but by intuition that we discover" (Henri Poincare) |
From: William F. <WF...@im...> - 2004-12-25 16:11:33
|
A while ago I sent a link to an OS project that was specifically making document templates for other OS projects and such. I think it was on tigris.org, but am not sure. You could check there. =20 ________________________________ From: rai...@li... [mailto:rai...@li...] On Behalf Of Mark Mcfarlane Sent: Friday, December 24, 2004 9:16 PM To: rai...@li... Subject: RE: [Rainbowportal-documents] Any documentation style guidelines =20 Hi Daniela, =20 Sorry it has taken a few days to respond to you. Unfortunately there are no documentation style guides / templates / etc in place. =20 =20 I wrote the original installation guide as a new user and as my first contribution to Rainbow about 20 months ago. At the time there was no meaningful documentation at all for the project and the web site was in trouble. After writing the install docs I spent about 9 months updating and maintaining the web site. For the past year I have had very little involvement in Rainbow due to other personal commitments. =20 Basically you can do anything you want. Show off your skills in both content and design :-). Eventually the install documentation should probably end up in Rainbow's Wiki but I personally prefer a standard doc format (like MS Word or .pdf) for easy delivery and printing of the installation document. =20 =20 If you don't apply a lot of advanced formatting, copying a document into Wiki is pretty easy. Authoring anything more than a few paragraphs in a Wiki is pretty painful so I'd write in MS Word or your favorite tool, and then we can deliver as a .doc, .pdf, or copy it into the Wiki. =20 =20 I think the Wiki concept is excellent but I find it very difficult to find content within the current Rainbow implementation. =20 Also, I wanted to thank you for your recent thoughtful comments about Rainbow on the mailing list. Rainbow will certainly benefit from your mature attitude. Please ignore the 'trash talk' that has happened in the past few days. We've only had 2 or 3 flare-ups like this in the past 20 months, in general everyone acts like adults! We've had a few well intentioned but very strong-willed people join the group recently, who haven't yet learned how express frustration constructively, and it has set off some mini-flame wars. =20 Welcome aboard, and Merry Christmas. =20 Mark McFarlane =20 ________________________________ From: rai...@li... [mailto:rai...@li...] On Behalf Of Daniela Nii Sent: Friday, December 24, 2004 3:41 AM To: rainbowportal-documents Subject: [Rainbowportal-documents] Any documentation style guidelines =20 Hi Mark, =20 Do you have any documentation style and formatting guidelines, preferences that I should follow for the installation document? MS Word is the way to go? =20 Thanks a bunch, Daniela |
From: Mark M. <mar...@ar...> - 2004-12-25 05:08:40
|
Daniela wrote: "I agree that the installation document needs an overhaul. ... I would like to overhaul the installation document so that the reaction to it is, "That sounds like a snap", "I can do that", etc. so that we don't lose potential users at the starting line to a great experience. :)..." Daniela, that is a great idea. The current install doc (my fault since I wrote it) is very daunting and would easily scare away some potential users. Also, I suspect there are either new steps or unnecessary steps since this doc was first created 20 months ago. Welcome aboard, go for it. Mark |
From: Mark M. <mar...@ar...> - 2004-12-25 05:04:21
|
Hi Daniela, Sorry it has taken a few days to respond to you. Unfortunately there are no documentation style guides / templates / etc in place. I wrote the original installation guide as a new user and as my first contribution to Rainbow about 20 months ago. At the time there was no meaningful documentation at all for the project and the web site was in trouble. After writing the install docs I spent about 9 months updating and maintaining the web site. For the past year I have had very little involvement in Rainbow due to other personal commitments. Basically you can do anything you want. Show off your skills in both content and design :-). Eventually the install documentation should probably end up in Rainbow's Wiki but I personally prefer a standard doc format (like MS Word or .pdf) for easy delivery and printing of the installation document. If you don't apply a lot of advanced formatting, copying a document into Wiki is pretty easy. Authoring anything more than a few paragraphs in a Wiki is pretty painful so I'd write in MS Word or your favorite tool, and then we can deliver as a .doc, .pdf, or copy it into the Wiki. I think the Wiki concept is excellent but I find it very difficult to find content within the current Rainbow implementation. Also, I wanted to thank you for your recent thoughtful comments about Rainbow on the mailing list. Rainbow will certainly benefit from your mature attitude. Please ignore the 'trash talk' that has happened in the past few days. We've only had 2 or 3 flare-ups like this in the past 20 months, in general everyone acts like adults! We've had a few well intentioned but very strong-willed people join the group recently, who haven't yet learned how express frustration constructively, and it has set off some mini-flame wars. Welcome aboard, and Merry Christmas. Mark McFarlane _____ From: rai...@li... [mailto:rai...@li...] On Behalf Of Daniela Nii Sent: Friday, December 24, 2004 3:41 AM To: rainbowportal-documents Subject: [Rainbowportal-documents] Any documentation style guidelines Hi Mark, Do you have any documentation style and formatting guidelines, preferences that I should follow for the installation document? MS Word is the way to go? Thanks a bunch, Daniela |
From: Daniela N. <dni...@ea...> - 2004-12-24 00:40:38
|
Hi Mark, Do you have any documentation style and formatting guidelines, preferences that I should follow for the installation document? MS Word is the way to go? Thanks a bunch, Daniela |
From: Daniela N. <dni...@ea...> - 2004-12-23 14:08:10
|
Oops, I sure seem to have hit a sensitive nerve with the installation document...! Lower the heat, fellow rainbowbrains! :) I haven't been watching the lists for very long so that I most likely don't know the whole story on some of the points mentioned below. So keep that in mind when reading my comments. :) Here are my observations so far: 1. We all seem to agree that the goal is to produce a simple, automated installation for the rainbow portal installer 2. The reality is: we are not there yet 3. There are only 2 issues listed under "Installation" in Jira! 4. There are over 500 threads listed in the Installation support forum! My comments to the above points: To 4 and 3.: What a discrepancy! If Jira is used to gage what issues will be addressed and scheduled for a release, the installation issue is a non-urgent, non-existing problem. Hence no or few resources are allocated. Obviously, the installation itself and/or the installation documentation need some help based on the support forum posts and views of threads. That said, I will heed my own words and I will log an issue regarding the current installation document. If Jira is indeed used as a task tracker/scheduler, my suggestion is that the support forum posters should be regularly directed to Jira (to search for a solution or log an issue) and, if there is a moderator (someone on the team who hangs out in the forum a lot), the moderator should ensure that the frequently viewed threads are captured as an issue in Jira. That would be a great way to keep track of the rough spots of the Rainbow Portal and it would allow the issues to be assigned and scheduled. This leads me to point 2: We've got to clean up what we have right now and then move step by step into an agreed upon direction. In that case, as a first step, I also suggest that we have something along the lines of a "quick start" installation document and a "troubleshooting the installation" document. BTW, that was supposed to be the topic of my original email when I started this thread... :) To 1.: Now that the rainbow portal has been around for a while and has received major boosts in functionality it is a great sign that the installation has become a subject for discussion. It means that it's no longer just the "hackers", die-hard developers playing with the Rainbow Portal but that the Rainbow Portal has gone mainstream. Let's make sure we elevate the installation/installer functionality to its own function/component because it can no longer be seen as an afterthought. Would it make sense to create a Rainbow Wiki "Installation" space to facilitate the discussion and development of the installer for the Rainbow Portal? Cheers, Daniela |
From: Daniela N. <dni...@ea...> - 2004-12-22 18:26:59
|
Aloha Mark, I agree that the installation document needs an overhaul. That actually kinda kicked me into gear to offer you my help. It was quite intimidating reading through all the info so that I dreaded the installation. Once I decided to give it a shot and see what happens, it was quite under whelming. I created an empty dB, pointed my virtual dir to the rainbow source dir, launched the browser - and voila! This is not to trivialize the special cases and odd things that can happen with the close to unlimited variations on user environments, the document just needs some major restructuring and scrubbing to get it up to speed. I would like to overhaul the installation document so that the reaction to it is, "That sounds like a snap", "I can do that", etc. so that we don't lose potential users at the starting line to a great experience. :) Now, I am sure you and the other rainbowbrains have ideas, suggestions, and examples that you would like to share with me so that I can get a feel for what we are aiming for. So, shoot! Cheers, Daniela > [Original Message] > From: Mark McFarlane <mar...@ho...> > To: <rai...@li...>; Daniela Nii <dni...@ea...> > Cc: <rai...@li...> > Date: 12/21/2004 8:19:41 AM > Subject: [Rainbowportal-documents] RE: [Rainbowportal-devel] Re: Interested in helping out with docs and qa > > Daniela, > > The installation document could really use an overhaul if you are > interested. > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Rainbowportal-documents mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rainbowportal-documents |
From: Daniela N. <dni...@ea...> - 2004-12-22 18:26:20
|
Thanks for the welcome! I am honored to be part of the rainbowbrains. :) Cheers, Daniela > [Original Message] > From: Graziano Poretti <gra...@du...> > To: Daniela Nii <dni...@ea...> > Cc: <rai...@li...>; <rai...@li...> > Date: 12/21/2004 5:26:31 AM > Subject: [Rainbowportal-documents] Re: Interested in helping out with docs and qa > > aloha Daniela! > welcome on board! > i added u to the documentation team and to the devel team ... so u can be > updated to the news coming from the rainbowbrains :-) > > both teams read this as a kind of introduction email so .... aloha to > hawaii!! > > ciao! > > RAINBOW TEAM Graziano Poretti Rainbow Product Manager Due Metri s.a.s. > gra...@du... tel: ++39 0184 42163 Signature powered by Plaxo Want a > signature like this? Add me to your address book... > ----- Original Message ----- > From: "Daniela Nii" <dni...@ea...> > To: <hr...@ra...> > Sent: Friday, December 17, 2004 7:50 PM > Subject: Interested in helping out with docs and qa > > > > Aloha dear Rainbow team, > > > > My name is Daniela Nii and I am a Software Engineer with over 12 years of > > extensive system software and object-oriented development experience > > covering product support, software systems engineering, testing and > > quality assurance and intra/internet applications. My roots are in > > Smalltalk (was with Digitalk (later ParcPlace-Digitalk) for 6 years) and > > Java and for the last two years I've been busy getting up to speed with > > .NET (C#). For the last 5 years I've been a software consultant based in > > Hawaii and I am keeping myself busy with local projects and a few long > > distance projects in Switzerland. > > > > Recently the requests for portals have gone up pretty drastically, so that > > I have been researching possible portal frameworks that I could use for my > > consulting work. I've decided to go with your Rainbow portal and would > > like to provide you with feedback as well as contributions in areas that I > > will be using through my consulting work. > > > > At this point I would like to start out in the documentation area because > > as a newbie to the Rainbow portal I will be relying heavily on the > > existing documentation, and as I've noticed, on the support forums. > > > > I am also interested in getting into quality assurance and automated > > testing using some form of a unit-testing tool for .NET developers. NUnit > > comes to mind or some other tool... > > > > I am looking forward to working with you and making the Rainbow portal the > > #1 choice for portal creations. > > > > > > Daniela Nii > > dni...@ea... > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Rainbowportal-documents mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rainbowportal-documents |
From: Mark M. <mar...@ho...> - 2004-12-21 18:20:09
|
Daniela, The installation document could really use an overhaul if you are interested. |
From: Graziano P. <gra...@du...> - 2004-12-21 15:26:43
|
aloha Daniela! welcome on board! i added u to the documentation team and to the devel team ... so u can be updated to the news coming from the rainbowbrains :-) both teams read this as a kind of introduction email so .... aloha to hawaii!! ciao! RAINBOW TEAM Graziano Poretti Rainbow Product Manager Due Metri s.a.s. gra...@du... tel: ++39 0184 42163 Signature powered by Plaxo Want a signature like this? Add me to your address book... ----- Original Message ----- From: "Daniela Nii" <dni...@ea...> To: <hr...@ra...> Sent: Friday, December 17, 2004 7:50 PM Subject: Interested in helping out with docs and qa > Aloha dear Rainbow team, > > My name is Daniela Nii and I am a Software Engineer with over 12 years of > extensive system software and object-oriented development experience > covering product support, software systems engineering, testing and > quality assurance and intra/internet applications. My roots are in > Smalltalk (was with Digitalk (later ParcPlace-Digitalk) for 6 years) and > Java and for the last two years I've been busy getting up to speed with > .NET (C#). For the last 5 years I've been a software consultant based in > Hawaii and I am keeping myself busy with local projects and a few long > distance projects in Switzerland. > > Recently the requests for portals have gone up pretty drastically, so that > I have been researching possible portal frameworks that I could use for my > consulting work. I've decided to go with your Rainbow portal and would > like to provide you with feedback as well as contributions in areas that I > will be using through my consulting work. > > At this point I would like to start out in the documentation area because > as a newbie to the Rainbow portal I will be relying heavily on the > existing documentation, and as I've noticed, on the support forums. > > I am also interested in getting into quality assurance and automated > testing using some form of a unit-testing tool for .NET developers. NUnit > comes to mind or some other tool... > > I am looking forward to working with you and making the Rainbow portal the > #1 choice for portal creations. > > > Daniela Nii > dni...@ea... > |
From: John C. <jc...@jb...> - 2004-06-16 16:05:10
|
I would like to Document Rainbow modules by placing them each on a on = it's own webpage with some CMS controlled documentation for each module = that way the help can be built iteratively on the rainbow website. Then = we can build the hyperlinks into the admin function of choosing the = modules and the modules themselves. What do you think? John Caro Jewelry By Design 2932 Prince William Pkwy Woodbridge, VA 22192 703-580-8880 |
From: Dave W. <wwa...@kc...> - 2003-10-03 19:55:12
|
BTW, the Wiki will run great in an IFrame module. Set it to a pretty large height - the maximum I think is 2000 by default or I edited mine to slightly larger to accommodate really large docs without having two sets of scroll bars appear. Set the width to 100%. Hide the title and it would look pretty seamless on the main rainbow site IMO. -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of Dave Wakefield Sent: Friday, October 03, 2003 2:45 PM To: Rainbow Documents Listserver Subject: [Rainbowportal-documents] Rainbow Open Wiki Site As per the discussion on this thread: http://www.rainbowportal.net/AspNetForums/ShowPost.aspx?PostID=3422 I set up a Rainbow Wiki at: http://rainbow.sstsinc.com <http://rainbow.sstsinc.com/> I'll start putting my graphics and themes documentation on here and that may give people a feel for its potential. Note: The domain names "rainbowdocs" or "rainbowportaldocs" are currently available. If the Wiki seems to catch on, I can register one of those and point them at this site. Let me know what you think. |
From: Dave W. <wwa...@kc...> - 2003-10-03 19:45:54
|
As per the discussion on this thread: http://www.rainbowportal.net/AspNetForums/ShowPost.aspx?PostID=3422 I set up a Rainbow Wiki at: http://rainbow.sstsinc.com <http://rainbow.sstsinc.com/> I'll start putting my graphics and themes documentation on here and that may give people a feel for its potential. Note: The domain names "rainbowdocs" or "rainbowportaldocs" are currently available. If the Wiki seems to catch on, I can register one of those and point them at this site. Let me know what you think. |
From: Graziano P. <gra...@du...> - 2003-09-19 20:01:09
|
hi Nate at the moment there are no fixed procedures for this. in my opinion this group should fix these procedures (may be thinking to a kind of QA system), but as we are starting ... in my opinion the best (and quickest) way to start is to generate a new item on the rainbowportal (a doc module) where all of us can upload documentation. i think that we should work on a kind of index too, quite simple but, we should manage a html page where to put ... categories, short description, may be a link to the document... i'm going to generate it now .. i will post so soon url, account, pwd to manage it thnx ----- Graziano Poretti http://www.rainbowportal.net <http://www.rainbowportal.net/> - http://www.duemetri.com <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 Nate Hekman Inviato: giovedi 18 settembre 2003 17.10 A: rai...@li... Oggetto: [Rainbowportal-documents] where to post documentation? I'm in the process of writing a simple how-to for programmers wanting to write their own Rainbow modules. The work in progress is currently at http://nate-helen.hekman.net/Rainbow%20How%20To.doc. What's the procedure for making this available on the rainbowportal.net site? Should it be approved by someone first? Is there already a section of the web site where this would logically fit? Can I post it myself somehow or do I need to ask someone else to? Once it's posted can I continue to edit and expand it? Nate Hekman Calgary, Alberta, Canada |
From: Graziano P. <gra...@du...> - 2003-09-19 19:56:06
|
hi i need to know the account u used in the rainbow portal so i can give u the permissions to handle the documentation section. ... asap pls ... 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 ciò non autorizzato, sono severamente proibiti. Nel caso in cui si riceva il messaggio per errore è 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. |
From: Nate H. <he...@ge...> - 2003-09-18 15:10:54
|
I'm in the process of writing a simple how-to for programmers wanting to write their own Rainbow modules. The work in progress is currently at http://nate-helen.hekman.net/Rainbow%20How%20To.doc. What's the procedure for making this available on the rainbowportal.net site? Should it be approved by someone first? Is there already a section of the web site where this would logically fit? Can I post it myself somehow or do I need to ask someone else to? Once it's posted can I continue to edit and expand it? =20 =20 Nate Hekman Calgary, Alberta, Canada =20 |
From: Graziano P. <gra...@du...> - 2003-09-09 11:05:02
|
hi to all as there are some new entries who want to spend their time improving documentation, we built this new list for documentation only. no code here, just on line demos, documents and related stuffs welcome to all ----- 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 ciò non autorizzato, sono severamente proibiti. Nel caso in cui si riceva il messaggio per errore è 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. |