From ati.ozgur at gmail.com Fri Feb 10 03:06:37 2006 From: ati.ozgur at gmail.com (Atilla Ozgur) Date: Fri, 10 Feb 2006 10:06:37 +0200 Subject: [Wtr-core] Regular Expression Tutorial Message-ID: It seems that a lot of new watir users do not know regular expressions. I wrote a simple regular expression tutorial for input validation. I think I will have a time to convert it to ruby syntax with watir examples. Where should I put it? From bret at pettichord.com Fri Feb 10 10:53:38 2006 From: bret at pettichord.com (Bret Pettichord) Date: Fri, 10 Feb 2006 09:53:38 -0600 Subject: [Wtr-core] Regular Expression Tutorial In-Reply-To: References: Message-ID: Good question. I think the answer should be on the wiki. But which wiki? My understanding is that the current wiki is the mediawiki wiki at watir.net. So you should put it there. But this raises two issues. 1. The old wiki at rubyforge needs to be taken down so people stop posting there. We also need to harvest any non-spam updates made there in the past couple months. 2. I think we are also moving to wanting to use confluence at openqa.org (i still plan to move the watir project there and in particular would like to get SVN set up there in the next week or two.) Does this sound right? Sy? Bret On 2/10/06, Atilla Ozgur wrote: > > It seems that a lot of new watir users do not know regular expressions. > > I wrote a simple regular expression tutorial for input validation. I > think I will have a time to convert it to ruby syntax with watir > examples. Where should I put it? > > _______________________________________________ > Wtr-core mailing list > Wtr-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-core > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060210/e3e0b032/attachment.htm From bret at pettichord.com Sun Feb 12 17:29:52 2006 From: bret at pettichord.com (Bret Pettichord) Date: Sun, 12 Feb 2006 16:29:52 -0600 Subject: [Wtr-core] Checkout? In-Reply-To: <010d01c62e61$fbefa5d0$6801a8c0@Koko> References: <010d01c62e61$fbefa5d0$6801a8c0@Koko> Message-ID: Michael Bolton has offered to clean up some of the inconsistencies in the coding style of Watir, and had some specific questions. I'm sharing my response to him with the rest of you. On 2/10/06, Michael Bolton wrote: > > Would you like me to de-CamelCase watir.rb? Some other files? Would you > like me to deprecate camelCased methods by doing this? > > def OldFunction(foo, bar) > puts "OldFunction is deprecated; please use old_function instead." > old_function(foo, bar) > end > > old_function(foo, bar) > ... > end No. Take a look at camel_case.rb to see how it is done with "alias". When you do this you have to distinguish between code that is in the public interface to Watir and code that is not. If it isn't then it doesn't need to be in camel_case.rb. We've already de-camelcased most of the original camelcase methods. But the unit tests have not been updated to use the new names. To the extent that the unit tests are often the primary technical documentation for how to use Watir, this is is a problem as it only propigates > or would you like me to simply work on the internals, and not the > externals? Taking care of the internals is easier. Although even then, you can run into unexpected trouble. One of the problems with using a dynamic language is that when you change the symbol names, you can't depend on your linker to ensure you've updated all the references. Instead you have to depend on your tests. And we have sufficient unit tests for most areas of Watir, but the main hole we have is in unit tests for our show and display and to_s methods. I do recall that i made a name change that affected this code at one point had later had bugs reported by users because of references i hadn't updated. So i've avoided cleaning up this code further. Actually, my intent is to deprecate the original show_foo methods in favor of foos.show (e.g. tables.show instead of show_tables). The Elements#show code is cleaner to begin with. The main thing holding up this deprecation is that we still need elements.show (to replace show_all_forms) and frames.show and forms.show and maybe a couple of others (not sure about the table elements, e.g.). I've also been planning to formally announce the deprecation of these old interfaces for a while, but want to do that with a clear method for letting people know what they might be using that might be deprecated. OR, would you like me to write a filter that searches and replaces all of > the instances of camel-cased Watir symbols that I can find, such that > people > can update their own source files? I think this would be hard and in any case i think the alias commands would be the place for this. > Would you like me to include symbols in the cleanup? I don't know what this means. I must say that the most exasperating aspect of using Watir has been all > those little instances where I have to remember that it's > > some_function(:beforeText, 'argh!') > > instead of > > some_function(:before_text, 'ahhh!') This has already been fixed. There are no code references to "beforeText" in watir.rb in head -- you'll only find them in camel_case.rb and some unit tests. And in the doc strings for several of the methods. Sigh. I'm actually unsure on how to correct this documentation. It could simply be corrected, but there is a lot of duplication of what amounts to the same information, and thus it flies in the face of the DRY principle. When these doc strings were first written, these methods were mostly hard-wired separately into each kind of element. But now they have almost all be refactored into methods of Element class, and we have a general mechanism that allows any Element method to be used as a attribute for the factory methods (i.e. methods like IE#button). Does any one have any suggestions? On my last project, that inconsistency made me feel like I was being pecked > to death by ducks. I also find this inconsistency annoying, and appreciate your offer to help weed it out. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060212/9f9d7446/attachment.htm From mb at michaelbolton.net Tue Feb 14 04:14:10 2006 From: mb at michaelbolton.net (Michael Bolton) Date: Tue, 14 Feb 2006 04:14:10 -0500 Subject: [Wtr-core] Checkout? In-Reply-To: Message-ID: <007b01c63147$1aff3610$6e01a8c0@Koko> Brett:> Actually, my intent is to deprecate the original show_foo methods in favor of foos.show (e.g. tables.show instead of show_tables). Bravo. Would you like me to include symbols in the cleanup? I don't know what this means. The example is just below. I must say that the most exasperating aspect of using Watir has been all those little instances where I have to remember that it's some_function(:beforeText, 'argh!') instead of some_function(:before_text, 'ahhh!') This has already been fixed. There are no code references to "beforeText" in watir.rb in head -- you'll only find them in camel_case.rb and some unit tests. And in the doc strings for several of the methods. Sigh. That I can fix. I'm actually unsure on how to correct this documentation. It could simply be corrected, but there is a lot of duplication of what amounts to the same information, and thus it flies in the face of the DRY principle. DRY is a heuristic, isn't it? I see forcing people to look for documentation in two places as kinda forcing them to repeat themselves, in a way. ---Michael B. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060214/1aa009c5/attachment-0001.htm From tobias at qualityforge.com Wed Feb 15 10:46:53 2006 From: tobias at qualityforge.com (Quality Forge) Date: Wed, 15 Feb 2006 07:46:53 -0800 (PST) Subject: [Wtr-core] SpySmth & WATIR In-Reply-To: Message-ID: <20060215154653.56700.qmail@web31804.mail.mud.yahoo.com> Bret, It seems to have been hard for us to sync up, and I was tied up all last week+ with Agile2006 reviews. There is also no other input yet on this thread, so I propose the following. I do a first rev of the WATIR-specific tool, it will show the same HTML as before, but offer a button on the popup to allow adding the element as a WATIR command to a script. The script will be written to on the fly, so at any point it can be opened in a text editor. I'll provide more detail, and maybe questions here as I progess. I'll also remove a lot of superflous stuff (Windows object inspection, and much of the UI - giving it a new WATIR look). Please note that progress on this will probably be slow right now, as I am fitting this in between other things. Tobias Bret Pettichord wrote: ok, sounds good. On 1/26/06, Quality Forge wrote: Brett, Sorry for the delayed response - got caught up with other stuff. A Skype session would be good, and I'd be free for that next week. Given that no one else has responded so far, it may be just the two of us, but once we agree on a date/time we can announce it here and make the session open. The times you give are generally fine, I suggest Wednesday at 7pm Central (5pm West coast). Tobias Bret Pettichord < bret at pettichord.com> wrote: One thing i could do would be to do an evening Skype call. We did this a while ago to sync up with the WET folks. It's a free and easy way to set up a conference call and include anyone anywhere in the world. For me, i could do it Mon, Tues or Weds evenings, say between 7 pm and 11 pm US Central time. Bret On 1/17/06, tobias at qualityforge.com wrote: Hi Chris, and others, I'd appreciate it if one or more people on this list would call me. My cell is 650-303-7572. I'd like to discuss requirements for a WATIR (WATIR/Selenium?! ) version of SpySmith. I have a number of ideas of what I think this tool should be - maybe an actual Ruby script creator... - but want to run those ideas by a couple of people before proceeding. Alternatively, you can respond by email to wtr-core, so others can comment, expand, etc. Hope to hear some ideas. What do you need? In the absence of anything specific, I'll go ahead and implement something, and we can use that as the basis for something better. Tobias ----- Original Message ---- From: Chris McMahon To: wtr-core at rubyforge.org Cc: Quality Forge < tobias at qualityforge.com> Sent: Wednesday, January 11, 2006 11:14:32 AM Subject: Re: [Wtr-core] SpySmth & WATIR > BTW, my team is actually using Selenium right now. I think there would be > equal interest in making SpySmith support the Selenium syntax. I'm also a > contributor to that project. Let me know if you'd like me to introduce you > to others on that team. (Don't worry, i plan to get them using Watir too > soon.) I'll go ahead and mention that I'm going to be teaching the first non-Pettichord-led Scripting For Testers class at STAREast in May, and SpySmith plays a pretty big role in that course. -Chris _______________________________________________ Wtr-core mailing list Wtr-core at rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-core _______________________________________________ Wtr-core mailing list Wtr-core at rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-core _______________________________________________ Wtr-core mailing list Wtr-core at rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-core _______________________________________________ Wtr-core mailing list Wtr-core at rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-core -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060215/719848cc/attachment.htm From bret at pettichord.com Thu Feb 16 01:17:10 2006 From: bret at pettichord.com (Bret Pettichord) Date: Thu, 16 Feb 2006 00:17:10 -0600 Subject: [Wtr-core] SpySmth & WATIR In-Reply-To: <20060215154653.56700.qmail@web31804.mail.mud.yahoo.com> References: <20060215154653.56700.qmail@web31804.mail.mud.yahoo.com> Message-ID: Sounds like a good plan to me. Appreciate your support for Watir. On 2/15/06, Quality Forge wrote: > > Bret, > > It seems to have been hard for us to sync up, and I was tied up all > last week+ with Agile2006 reviews. There is also no other input yet on this > thread, so I propose the following. > > I do a first rev of the WATIR-specific tool, it will show the same HTML as > before, but offer a button on the popup to allow adding the element as a > WATIR command to a script. The script will be written to on the fly, so at > any point it can be opened in a text editor. I'll provide more detail, and > maybe questions here as I progess. > > I'll also remove a lot of superflous stuff (Windows object inspection, and > much of the UI - giving it a new WATIR look). > > Please note that progress on this will probably be slow right now, as I am > fitting this in between other things. > > Tobias > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060216/12e560da/attachment.htm From bret at pettichord.com Fri Feb 17 00:11:30 2006 From: bret at pettichord.com (Bret Pettichord) Date: Thu, 16 Feb 2006 23:11:30 -0600 Subject: [Wtr-core] Checkout? In-Reply-To: <00af01c63155$e24f8040$6e01a8c0@Koko> References: <00af01c63155$e24f8040$6e01a8c0@Koko> Message-ID: Michael, Your patch looks good. I've commited your changes. Thanks for the contribution. If you send me your rubyforge userid, i'll give you commit privileges. I also strongly suggest you subscribe to the wtr-cvs-auto list. Your doc updates are, IMHO, an improvement and i don't think it is prolix. I also like the idea of writing more top-level doc, rather than putting lots of repetition in each of the methods. I can see places where i might make additions or small changes, but that doesn't have to happen right away. I also suggest that you "test" your changes by running the build-rdoc.batscript. You should also look at that. I seem to recall that i need to add some def* methods to it, and it may also need further updates. It's not long and you should understand what it does. I've also felt like we could use more cross-linking in our rdocs. Bret On 2/14/06, Michael Bolton wrote: > > I've attached a patch file and a copy of WATIR.RB, so that if the former > is screwed up, the latter may be useful. The ONLY thing that I changed > was the first swot of documentation at the top of the file, so please ignore > the other differences. > > Does this fill the bill? Does it represent an improvement? Is it too > prolix? I'd like to upgrade it further by including more examples, but > that's for another night; then I'll get down to revising the docs on > specific functions. > > ---Michael B. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060216/e0d747c9/attachment.htm From bret at pettichord.com Wed Feb 22 11:01:51 2006 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 22 Feb 2006 10:01:51 -0600 Subject: [Wtr-core] Get an Account on OpenQA.org Message-ID: I am working on the long-delayed move of Watir to OpenQA.org. Anyone involved with this project needs to have an account on OpenQA. Without this, you can't commit code and you can't enter bug reports. Nor can you have any assigned to you. If you are planning to stay involved in the project, please go to OpenQA and set up an account. Then email it to me so that i can assign you equivalent rights on the new project site. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060222/720a265c/attachment.htm From jeff at dark-light.com Wed Feb 22 11:24:17 2006 From: jeff at dark-light.com (jeff@dark-light.com) Date: Wed, 22 Feb 2006 11:24:17 -0500 Subject: [Wtr-core] Get an Account on OpenQA.org Message-ID: <29448566.7751140625457788.JavaMail.servlet@perfora> Bret, Just setup my account ... Username : jeffwood Email address: jeff at dark-light.com ... hope you're having a great day. j. From mb at michaelbolton.net Thu Feb 23 11:21:49 2006 From: mb at michaelbolton.net (Michael Bolton) Date: Thu, 23 Feb 2006 11:21:49 -0500 Subject: [Wtr-core] Get an Account on OpenQA.org In-Reply-To: Message-ID: <012001c63895$4170ec80$6901a8c0@Koko> My account name is... "Michael Bolton" ---Michael B. _____ From: wtr-core-bounces at rubyforge.org [mailto:wtr-core-bounces at rubyforge.org] On Behalf Of Bret Pettichord Sent: February 22, 2006 11:02 AM To: wtr-core at rubyforge.org Cc: Patrick Lightbody; Patrick Lightbody Subject: [Wtr-core] Get an Account on OpenQA.org I am working on the long-delayed move of Watir to OpenQA.org. Anyone involved with this project needs to have an account on OpenQA. Without this, you can't commit code and you can't enter bug reports. Nor can you have any assigned to you. If you are planning to stay involved in the project, please go to OpenQA and set up an account. Then email it to me so that i can assign you equivalent rights on the new project site. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060223/5ab2d3f2/attachment-0001.htm From bret at pettichord.com Sun Feb 26 17:38:13 2006 From: bret at pettichord.com (Bret Pettichord) Date: Sun, 26 Feb 2006 16:38:13 -0600 Subject: [Wtr-core] New Watir Repository and a Question about IEController and Scripting101 Message-ID: We have successfully migrated the WTR source repository from Rubyforge.orgto OpenQA.org. In the process we have also moved from CVS to SVN. The entire commit history has moved to the new repo, so no information has been lost. Information on accessing the new repository: http://openqa.org/watir/cvs.action To use this, developers will need to use SVN. Please let me know if you need help or advice with installation. I use TortoiseSVN and Subeclipse (for Eclipse). We are still in the process of getting the Watir committers set up on OpenQA. But anonymous access should work now. No one should be committing code to the Rubyforge.org CVS repository. We need to decide whether to freeze this or delete it. My preference would be to freeze it. However, there are two other project in WTR besides Watir: IEController and Scripting101. I need the project leads (Chris Morris and Chris McMahon) to let me know what they want to do here. It was easier to move the entire repo over to OpenQA than to just pick out the Watir project. But we can delete these projects from OpenQA if their owners would rather maintain them going forward on Rubyforge. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060226/81b70fb5/attachment.htm From bpettichord at gmail.com Sun Feb 26 18:22:38 2006 From: bpettichord at gmail.com (Bret Pettichord) Date: Sun, 26 Feb 2006 17:22:38 -0600 Subject: [Wtr-core] Our new wiki - Confluence on OpenQA.org Message-ID: I am dying to spend more time writing documentation and less time answering emails. The reality is that we are getting more and more questions that would be solved if we had better documentation and updated FAQ's. But where do i put it? We have two new wiki's and we need to decide which one we are going to use. We have the MediaWiki at Watir.net and the Confluence wiki at OpenQa.org. I've been uncertain myself, as both of these are good wikis that i've used before and both are clearly superior to the wiki we've been using at Rubyforge.org. One factor in favor of the MediaWiki is that our content has already been migrated. A factor in favor of Confluence has been that it uses the same usernames as we are using for bugtracking and code commits. But i've just realized one more thing that i think tips the balance in favor of Confluence. A frequent request has been to have a place for users to share examples and libraries and such for Watir. We've been including them in the Watir library directly but these are of mixed quality and users don't realize this. Confluence supports attachments, so it would be easy to post examples or sample libraries to a Wiki Page. And this is something that we wouldn't have to control access to, as we do the Watir library itself. So i am proposing that we move to Confluence. Please let me know whether you agree to this move or not. (Another thing that would be help our support for our users would be getting out a new release, since many of the problems people are seeing are actually fixed in trunk/head. I'm working on it...) Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060226/d80c76df/attachment.htm From sy1234 at gmail.com Sun Feb 26 20:29:16 2006 From: sy1234 at gmail.com (Sy Ali) Date: Sun, 26 Feb 2006 20:29:16 -0500 Subject: [Wtr-core] Our new wiki - Confluence on OpenQA.org In-Reply-To: References: Message-ID: <1e55af990602261729i1f31376eu62c79685e111710a@mail.gmail.com> On 2/26/06, Bret Pettichord wrote: > We have two new wiki's and we need to decide which one we are going to use. > We have the MediaWiki at Watir.net and the Confluence wiki at OpenQa.org. > I've been uncertain myself, as both of these are good wikis that i've used > before and both are clearly superior to the wiki we've been using at > Rubyforge.org. One factor in favor of the MediaWiki is that our content has > already been migrated. A factor in favor of Confluence has been that it uses > the same usernames as we are using for bugtracking and code commits. It wasn't hard to migrate everything, because MediaWiki was designed to replace the old wiki, and the syntax is nearly the same. It was a lot of copying-and-pasting. I don't know anything about confluence, so I can't comment there.. but there wasn't an intimidating amount of data to migrate. > A frequent request has been to have a place for users to share examples and > libraries and such for Watir. We've been including them in the Watir library > directly but these are of mixed quality and users don't realize this. > Confluence supports attachments, so it would be easy to post examples or > sample libraries to a Wiki Page. And this is something that we wouldn't have > to control access to, as we do the Watir library itself. Why ever would you put such things as attachments? Why not have your code inline as text or in sub-pages? When enabled in the config, a sub-page is as easy as creating [[/sub page name]], saving, following the link to edit that page and pasting the code in

tags. Links to this new page's parent are automatic and this new page has its own discussion tab for easy conversation. MediaWiki has an extension to colour code, although I couldn't get it working for Ruby because I didn't have the colouration information for that language. Mediawiki also supports uploads. There's no concept of attaching to a particular page.. any upload is available to be linked to from anywhere. Also, every upload is hosted on yet another page.. so it can be collaborated on and discussed. > So i am proposing that we move to Confluence. Please let me know whether you > agree to this move or not. I say go with confluence because it's a profesional application maintained on and by the same host as the rest of your services. I'm not willing to learn yet another markup language to do more than help with the initial migration though. From christopher.mcmahon at gmail.com Mon Feb 27 02:11:14 2006 From: christopher.mcmahon at gmail.com (Chris McMahon) Date: Mon, 27 Feb 2006 01:11:14 -0600 Subject: [Wtr-core] Hedging for the moment. Re: New Watir Repository and a Question about IEController and Scripting101 Message-ID: <72799cd70602262311k67ccd1eas3aaca131c035b3a7@mail.gmail.com> > However, there are two other project in WTR besides Watir: IEController and > Scripting101. I need the project leads (Chris Morris and Chris McMahon) to > let me know what they want to do here. It was easier to move the entire repo > over to OpenQA than to just pick out the Watir project. But we can delete > these projects from OpenQA if their owners would rather maintain them going > forward on Rubyforge. Life has been a little crazed in recent weeks, but I'll be paying attention to the Scripting materials in the very near future, so I'll have an informed opinion in the next week or so. -Chris (McMahon) From chrismo at clabs.org Mon Feb 27 09:54:36 2006 From: chrismo at clabs.org (Chris Morris) Date: Mon, 27 Feb 2006 08:54:36 -0600 Subject: [Wtr-core] New Watir Repository and a Question about IEController and Scripting101 In-Reply-To: References: Message-ID: <440312AC.7080008@clabs.org> Bret Pettichord wrote: > However, there are two other project in WTR besides Watir: > IEController and Scripting101. I need the project leads (Chris Morris > and Chris McMahon) to let me know what they want to do here. It was > easier to move the entire repo over to OpenQA than to just pick out > the Watir project. But we can delete these projects from OpenQA if > their owners would rather maintain them going forward on Rubyforge. The licensing for IEController allows you to include it or not at your own convenience -- I probably wouldn't maintain future code stuffs at OpenQA, but it's very unlikely I'd do much more with it as-is anyway. So, whatever works for you Bret is fine with me. -- Chris http://clabs.org/blogki From bret at pettichord.com Mon Feb 27 18:12:25 2006 From: bret at pettichord.com (Bret Pettichord) Date: Mon, 27 Feb 2006 17:12:25 -0600 Subject: [Wtr-core] Watir Development In-Reply-To: <7a754c960602271235g716008a8mcd51d5dde6ea2a4d@mail.gmail.com> References: <7a754c960602271235g716008a8mcd51d5dde6ea2a4d@mail.gmail.com> Message-ID: Chris, Right now we have a backlog of stuff in the trackers that need to be fixed. We also have several issues that have been acknowledged as problems or good ideas to fix in the mailing lists, but someone needs to put them on our task list. We've just set up a new bug tracking system, Jira at OpenQA.org, but we don't have anything there. It would be great if someone were to create Jira Issues for the stuff on the Rubyforge.org trackers. It would be enough to transfer skeleton information and then just include a link to the original for the description. Let me know whether you want to help organize or issues list or if you want to work one of the issues. If you are going to work on code, you should know that we recently moved our source base to SVN on OpenQA.org. Please send a patch file containing your changes. Any code changes should be accompanied by unit tests. Thanks for offering to help. Bret On 2/27/06, Chris Schmechel wrote: > > > Bret, > > I'd be interested in helping with the Watir core development. What tasks > and/or areas do you need help? > > Thanks again, > > Chris Schmechel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060227/f9982fa9/attachment.htm From bret at pettichord.com Mon Feb 27 18:21:57 2006 From: bret at pettichord.com (Bret Pettichord) Date: Mon, 27 Feb 2006 17:21:57 -0600 Subject: [Wtr-core] Our new wiki - Confluence on OpenQA.org In-Reply-To: <1e55af990602261729i1f31376eu62c79685e111710a@mail.gmail.com> References: <1e55af990602261729i1f31376eu62c79685e111710a@mail.gmail.com> Message-ID: Sy, Thanks for your understanding. For short bits of code, i agree that i would rather see it inline than as an attachment. Attachments become more attractive as the files become longer, or especially if there are several files, say a library and it's unit tests. Attachments can be zip files or patch files also. Another good thing about attachments is that they can word document or excel files or other things like that. There was one page in the wiki that was delivered as a word document and then i had to convert it to wiki form. That is manual work and formatting was lost in the process, so having attachments can definitely be an advantage. Both mediawiki and confluence support discussions. On mediawiki, the discussion page is like a wiki page. On Confluence it is more like a blog or a comment thread. Bret On 2/26/06, Sy Ali wrote: > > On 2/26/06, Bret Pettichord wrote: > > We have two new wiki's and we need to decide which one we are going to > use. > > We have the MediaWiki at Watir.net and the Confluence wiki at OpenQa.org > . > > I've been uncertain myself, as both of these are good wikis that i've > used > > before and both are clearly superior to the wiki we've been using at > > Rubyforge.org. One factor in favor of the MediaWiki is that our content > has > > already been migrated. A factor in favor of Confluence has been that it > uses > > the same usernames as we are using for bugtracking and code commits. > > It wasn't hard to migrate everything, because MediaWiki was designed > to replace the old wiki, and the syntax is nearly the same. It was a > lot of copying-and-pasting. I don't know anything about confluence, > so I can't comment there.. but there wasn't an intimidating amount of > data to migrate. > > > > A frequent request has been to have a place for users to share examples > and > > libraries and such for Watir. We've been including them in the Watir > library > > directly but these are of mixed quality and users don't realize this. > > Confluence supports attachments, so it would be easy to post examples or > > sample libraries to a Wiki Page. And this is something that we wouldn't > have > > to control access to, as we do the Watir library itself. > > Why ever would you put such things as attachments? Why not have your > code inline as text or in sub-pages? > > When enabled in the config, a sub-page is as easy as creating [[/sub > page name]], saving, following the link to edit that page and pasting > the code in

tags. Links to this new page's parent are > automatic and this new page has its own discussion tab for easy > conversation. > > MediaWiki has an extension to colour code, although I couldn't get it > working for Ruby because I didn't have the colouration information for > that language. > > Mediawiki also supports uploads. There's no concept of attaching to a > particular page.. any upload is available to be linked to from > anywhere. Also, every upload is hosted on yet another page.. so it > can be collaborated on and discussed. > > > > So i am proposing that we move to Confluence. Please let me know whether > you > > agree to this move or not. > > I say go with confluence because it's a profesional application > maintained on and by the same host as the rest of your services. I'm > not willing to learn yet another markup language to do more than help > with the initial migration though. > > _______________________________________________ > Wtr-core mailing list > Wtr-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-core > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20060227/4ada32d2/attachment-0001.htm From christopher.mcmahon at gmail.com Tue Feb 28 22:14:02 2006 From: christopher.mcmahon at gmail.com (Chris McMahon) Date: Tue, 28 Feb 2006 21:14:02 -0600 Subject: [Wtr-core] just out of curiosity: Vista? Message-ID: <72799cd70602281914x5c8c68feuc7791cc0c6911497@mail.gmail.com> Is anyone thinking about/looking into Watir vs. Windows Vista and IE7? I was surfing the announcements today, and just wondered if IE7 is on anyone's agenda. -Chris From paul.rogers at shaw.ca Tue Feb 28 22:18:17 2006 From: paul.rogers at shaw.ca (Paul Rogers) Date: Tue, 28 Feb 2006 20:18:17 -0700 Subject: [Wtr-core] just out of curiosity: Vista? Message-ID: <3ee77873eed2ec.3eed2ec3ee7787@shaw.ca> ive been following some blogs about it. I am too scared to install it on any of my pcs though Paul ----- Original Message ----- From: Chris McMahon Date: Tuesday, February 28, 2006 8:14 pm Subject: [Wtr-core] just out of curiosity: Vista? > Is anyone thinking about/looking into Watir vs. Windows Vista and IE7? > I was surfing the announcements today, and just wondered if IE7 > is on > anyone's agenda. > -Chris > > _______________________________________________ > Wtr-core mailing list > Wtr-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-core > From christopher.mcmahon at gmail.com Tue Feb 28 22:59:25 2006 From: christopher.mcmahon at gmail.com (Chris McMahon) Date: Tue, 28 Feb 2006 21:59:25 -0600 Subject: [Wtr-core] just out of curiosity: Vista? In-Reply-To: <3ee77873eed2ec.3eed2ec3ee7787@shaw.ca> References: <3ee77873eed2ec.3eed2ec3ee7787@shaw.ca> Message-ID: <72799cd70602281959w5177bbecta2f44e293862ab43@mail.gmail.com> That's a funny thing. I just spent US $1299 of my (frightened) parents' money on an Intel iMac for them and I wasn't scared at all. :) -C On 2/28/06, Paul Rogers wrote: > ive been following some blogs about it. I am too scared to install it on any of my pcs though > > Paul > > ----- Original Message ----- > From: Chris McMahon > Date: Tuesday, February 28, 2006 8:14 pm > Subject: [Wtr-core] just out of curiosity: Vista? > > > Is anyone thinking about/looking into Watir vs. Windows Vista and IE7? > > I was surfing the announcements today, and just wondered if IE7 > > is on > > anyone's agenda. > > -Chris > > > > _______________________________________________ > > Wtr-core mailing list > > Wtr-core at rubyforge.org > > http://rubyforge.org/mailman/listinfo/wtr-core > > > > _______________________________________________ > Wtr-core mailing list > Wtr-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-core >