From bernhard at intevation.de Mon Nov 13 12:15:29 2006 From: bernhard at intevation.de (Bernhard Reiter) Date: Mon, 13 Nov 2006 18:15:29 +0100 Subject: [Weft QDA users] weft-qda on Mandriva (2006.0), incl. wxruby 0.6 and gcc 4.0 problem Message-ID: <200611131815.33681.bernhard@intevation.de> Dear All, try to get weft-qda-1.0.1 to run on GNU/Linux Mandriva, I ran into problems with a newer g++ compiler. A "dirty" install package for Mandriva 2006.0 (i586) can be found at https://ftp.intevation.de/users/bernhard/weft-qda-20060mdk/ . I am pasting in the analysis part below. Maybe this is helpful for somebody. There is no warantee, your milage might vary, it might break things. My suggestion for weft-qda development is to port to wxruby2 if possible or help to fix wxruby 0.6, otherwise it will be hard for somebody to get weft-qda to run. I cannot say if newer gcc version will make it better. Using 4.0.3 to build wxruby (without recompiling wxGTK which was build with gcc 4.0.1) did not help. Maybe gcc 4.1.x will behave differently, I cannot say. Regards, Bernhard ps.: Please copy me on relevant replies, I might not be permanently subscribed to the list. Background or how and why was this dirty build produced? ----------------------------------- The first approach is: Installing the packages that come with Mandriva main and contrib. Install ruby's PageTemplates and build wxruby 0.6.0. Trying to run any wxruby application, e.g. ruby wxruby-0.6-src/samples/controls/controls.rb there is an error: [..]src/wxruby.so: undefined symbol: _ZTV12wxRbListCtrl - [..]/src/wxruby.so (LoadError) The error was reported on Fedora with gcc 4 as well, but the developers do not want to fix it. http://rubyforge.org/tracker/index.php?func=detail&aid=2153&group_id=35&atid= 218 Thesis: There is a difference between older g++ compilers and version 4.0. Constructive proof: Fortunately Mandriva has a package for an old version of gcc as well. Install: gcc3.3-cpp-3.3.6-2mdk gcc3.3-c++-3.3.6-2mdk gcc3.3-3.3.6-2mdk Recompile wxruby with g++-3.3.6. This alone produces more errors, probably because the binaries are incompatible. So rebuild wxGTK-2.4.2 as well and then rebuild wxruby again. To do this additionally install: libgtk+1.2-devel-1.2.10-41mdk export CC=gcc-3.3.6 export CXX=g++-3.3.6 #set LD_LIBRARY_PATH and PATH accordingly before # building wxruby This build also has wx/html/htmlproc.h copied to the right place and the removal lines deactivated in extconf.rb. -- Managing Director - Owner, www.intevation.net (Free Software Company) Germany Coordinator, fsfeurope.org (Non-Profit Org for Free Software) www.kolab-konsortium.com (Email/Groupware Solution, Professional Service) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://rubyforge.org/pipermail/weft-qda-users/attachments/20061113/403390b5/attachment.bin From alex at pressure.to Mon Nov 13 15:33:42 2006 From: alex at pressure.to (Alex Fenton) Date: Mon, 13 Nov 2006 20:33:42 +0000 Subject: [Weft QDA users] weft-qda on Mandriva (2006.0), incl. wxruby 0.6 and gcc 4.0 problem In-Reply-To: <200611131815.33681.bernhard@intevation.de> References: <200611131815.33681.bernhard@intevation.de> Message-ID: <4558D6A6.5000607@pressure.to> Hi Bernhard Thank you for your message and for trying Weft. > A "dirty" install package for Mandriva 2006.0 (i586) > can be found at https://ftp.intevation.de/users/bernhard/weft-qda-20060mdk/ . > I am pasting in the analysis part below. > This is useful - sorry you had such a job getting it to work. > My suggestion for weft-qda development is to port to wxruby2 if possible or > help to fix wxruby 0.6, otherwise it will be hard for somebody > to get weft-qda to run. > You are right that wxruby 0.6.0 is now old and doesn't work well with modern Linux distros (b/c it requires old WxWidgets version, old GTK version and old gcc). weft qda + wxruby2 will be very good - when wxruby2 is finished. It will look a lot better on Linux, work on OS X, support multi-lingual projects, and offer a more professional and usable interface on all platforms(eg a better way of working with the 'Documents and Categories' window). Unfortunately wxruby2 is not yet quite stable enough to use for Weft QDA. One of the main reasons I haven't released a newer version of Weft QDA is to spend time contributing to wxruby2. We are making a lot of progress. The good news is that a lot of great features have already been added to Weft QDA - editable documents, stored 'live' searches and queries, document attributes, nicer icons, scripting. I am wondering about whether to release an intermediate version of Weft QDA that has some of these features. The downside is that it will take some time away from working on other things, and will mean users having to upgrade their projects twice. But maybe the perfect is the enemy of the good ... what do users on this list think? > I cannot say if newer gcc version will make it better. > Using 4.0.3 to build wxruby For info - wxruby2 works perfectly with gcc 4. I think it's unlikely that anyone will fix wxruby 0.6.0 so that it works with that version though. Thanks again Alex From 042045003 at fudan.edu.cn Mon Nov 13 21:16:17 2006 From: 042045003 at fudan.edu.cn (=?GB2312?B?u8bI2bnz?=) Date: Tue, 14 Nov 2006 10:16:17 +0800 Subject: [Weft QDA users] weft-qda on Mandriva (2006.0), incl. wxruby 0.6 and gcc 4.0 problem References: <200611131815.33681.bernhard@intevation.de> <4558D6A6.5000607@pressure.to> Message-ID: <200611141016177969146@fudan.edu.cn> ======= 2006-11-14 04:25:54 ????????======= >Hi Bernhard >Thank you for your message and for trying Weft. >> A "dirty" install package for Mandriva 2006.0 (i586) >> can be found at https://ftp.intevation.de/users/bernhard/weft-qda-20060mdk/ . >> I am pasting in the analysis part below. >> >This is useful - sorry you had such a job getting it to work. > >> My suggestion for weft-qda development is to port to wxruby2 if possible or >> help to fix wxruby 0.6, otherwise it will be hard for somebody >> to get weft-qda to run. >> >You are right that wxruby 0.6.0 is now old and doesn't work well with >modern Linux distros (b/c it requires old WxWidgets version, old GTK >version and old gcc). > >weft qda + wxruby2 will be very good - when wxruby2 is finished. It will >look a lot better on Linux, work on OS X, support multi-lingual >projects, This is a very good news, and I am looking forward that Weft QDA will support multi-linguage. >and offer a more professional and usable interface on all >platforms(eg a better way of working with the 'Documents and Categories' >window). Unfortunately wxruby2 is not yet quite stable enough to use for >Weft QDA. > >One of the main reasons I haven't released a newer version of Weft QDA >is to spend time contributing to wxruby2. We are making a lot of progress. > >The good news is that a lot of great features have already been added to >Weft QDA - editable documents, stored 'live' searches and queries, >document attributes, nicer icons, scripting. > >I am wondering about whether to release an intermediate version of Weft >QDA that has some of these features. The downside is that it will take >some time away from working on other things, and will mean users having >to upgrade their projects twice. But maybe the perfect is the enemy of >the good ... what do users on this list think? If releasing an intermediate version will not take you lots of time, I would prefer to support the idea. I think releaseing new version regularly is a sign of active development, and it is a way to keep the user community active. I am willing to hear the different views of the lister:) >> I cannot say if newer gcc version will make it better. >> Using 4.0.3 to build wxruby >For info - wxruby2 works perfectly with gcc 4. I think it's unlikely >that anyone will fix wxruby 0.6.0 so that it works with that version though. > >Thanks again >Alex >_______________________________________________ >weft-qda-users mailing list >weft-qda-users at rubyforge.org >http://rubyforge.org/mailman/listinfo/weft-qda-users = = = = = = = = = = = = = = = = = = = = ??? 2006-11-14 ------ Deparment of Sociology Fudan University,Shanghai,China PRC My current Email: ronggui.huang at gmail.com From bernhard at intevation.de Tue Nov 14 04:33:46 2006 From: bernhard at intevation.de (Bernhard Reiter) Date: Tue, 14 Nov 2006 10:33:46 +0100 Subject: [Weft QDA users] weft-qda on Mandriva (2006.0), incl. wxruby 0.6 and gcc 4.0 problem In-Reply-To: <200611141016177969146@fudan.edu.cn> References: <200611131815.33681.bernhard@intevation.de> <4558D6A6.5000607@pressure.to> <200611141016177969146@fudan.edu.cn> Message-ID: <200611141033.50744.bernhard@intevation.de> Hi Alex! Hi Huang! On Tuesday 14 November 2006 03:16, ??? wrote: > ======= 2006-11-14 04:25:54 ????????======= > >> A "dirty" install package for Mandriva 2006.0 (i586) > >> can be found at > >> https://ftp.intevation.de/users/bernhard/weft-qda-20060mdk/ . I am > >> pasting in the analysis part below. > > > >This is useful - sorry you had such a job getting it to work. I have quite a bit of experience getting software to work, but I expect that more people out of the potential user group will have major trouble. BTW: I am unsure if the HTML export works in my build. > >> My suggestion for weft-qda development is to port to wxruby2 if possible > >> or help to fix wxruby 0.6, otherwise it will be hard for somebody > >> to get weft-qda to run. > >The good news is that a lot of great features have already been added to > >Weft QDA - editable documents, stored 'live' searches and queries, > >document attributes, nicer icons, scripting. > > > >I am wondering about whether to release an intermediate version of Weft > >QDA that has some of these features. The downside is that it will take > >some time away from working on other things, and will mean users having > >to upgrade their projects twice. But maybe the perfect is the enemy of > >the good ... what do users on this list think? > > If releasing an intermediate version will not take you lots of time, I > would prefer to support the idea. I agree that an intermediate version can be helpful if the effort is reasonable. > >> I cannot say if newer gcc version will make it better. > >> Using 4.0.3 to build wxruby > > > >For info - wxruby2 works perfectly with gcc 4. I think it's unlikely > >that anyone will fix wxruby 0.6.0 so that it works with that version > > though. For weft-qda it would be helpful, the fix cannot be hard for someone that is into wxruby development, so my suggestion is to publish a patch for it as many GNU/Linux distributions contain older versions of wxWidgets and GTK still, so deployment of weft-qda would be much easier if wxruby would be fixed in this regard. Best Regards, Bernhard -- Managing Director - Owner, www.intevation.net (Free Software Company) Germany Coordinator, fsfeurope.org (Non-Profit Org for Free Software) www.kolab-konsortium.com (Email/Groupware Solution, Professional Service) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://rubyforge.org/pipermail/weft-qda-users/attachments/20061114/54e5d6db/attachment.bin From christophe.lejeune at ulg.ac.be Tue Nov 14 05:46:25 2006 From: christophe.lejeune at ulg.ac.be (Christophe Lejeune) Date: Tue, 14 Nov 2006 11:46:25 +0100 Subject: [Weft QDA users] pool on an intermediate release Message-ID: <45599E81.7050909@ulg.ac.be> Dear list members, I also agree: an intermediate version would be very appreciated. Anyway, I am also sensible to the fact that such a release could be very time-consuming activity for Alex... The double-upgrade issue is also a question that have to be addressed. A solution would (perhaps) reside in labelling the intermediate version as a "transition" or "intermediate" release. Users would be warned and could then choose whether they prefer to upgrade their projects twice or to wait for next release. I have in mind something like (but less complicated than) Debian system. In Debian, packages crosses -at less- two stages (called 'unstable' and 'testing') before being released as stable versions... and "mean" users are advised to use only 'stable' releases. My 2 cents Christophe -- Christophe Lejeune Qualitative Sociology http://analyses.ishs.ulg.ac.be/ From Roberta_Goldman at mhri.org Tue Nov 14 09:44:20 2006 From: Roberta_Goldman at mhri.org (Roberta_Goldman) Date: Tue, 14 Nov 2006 09:44:20 -0500 Subject: [Weft QDA users] merging two halves of a project Message-ID: <4559D644.4040004@mhri.org> Dear Alex and users of Weft - I have used other ethnographic software programs previously and was delighted to use Weft in my current project as its simplicity to learn was important for the people working with me. One feature that would be helpful for my current and other large projects is the ability to merge two halves of a project after two individuals have each completed coding a different half of the transcripts. That would allow running reports on the entire project rather than separately for each half. Is this a feature that is possible and I missed that information in the manual? If not, is there some way around this problem that I could use? I apologize if this question is redundent - I posted it previously but am new to using list serves and did not see a response in the digest. Thank you for your help, Roberta -- Roberta E. Goldman, Ph.D. Cl. Associate Professor of Family Medicine Brown University Center for Primary Care and Prevention Memorial Hospital of Rhode Island 111 Brewster Street Pawtucket, RI 02860 Tel: 401-729-2924 Fax: 401-729-2494 roberta_goldman at mhri.org From alex at pressure.to Thu Nov 16 04:29:19 2006 From: alex at pressure.to (Alex Fenton) Date: Thu, 16 Nov 2006 09:29:19 +0000 Subject: [Weft QDA users] merging two halves of a project In-Reply-To: <4559D644.4040004@mhri.org> References: <4559D644.4040004@mhri.org> Message-ID: <455C2F6F.3070903@pressure.to> Hi Roberta Hi Roberta Thanks for your email; I'm glad your team are finding Weft usable and useful. Roberta_Goldman wrote: > One feature that would be helpful for my current and other large > projects is the ability to merge two halves of a project after two > individuals have each completed coding a different half of the > transcripts. There isn't such a feature at present in Weft. The current version 1.0 only really supports one person working on a project at a time. But it's a feature I think is useful and feasible - I'm interested in pursuing this as I also have a number of projects coming up where we might want to do this. A 'merge' could work in a couple of ways - perhaps you could tell me how you like to work. Here's a few ideas - I'm interested in what other people think of these too, for the purposes of an interim Weft 2 release... - Are the individual coders working on different documents, using the same set of categories or 'codebook'? In which case you might want simply to join the documents and coding together. - Or are they working on the same documents, using the same codebook - and if so, are you interested in a metric of inter-coder reliability? - Or are they working on the same documents, evolving their own analytic frame? If so, how would the categories from different projects sit alongside each other? - Would it be helpful to enable people to work on the same project simultaneously from different workstations, even from different sites - I have prototyped this feature, and am wondering if it's worth developing further? > If not, is there > some way around this problem that I could use? > I'm not sure I can think of one for now, other that copying and pasting or combining exported text in a word processor. Thanks again for your interest Alex From 042045003 at fudan.edu.cn Thu Nov 16 08:43:49 2006 From: 042045003 at fudan.edu.cn (=?GB2312?B?u8bI2bnz?=) Date: Thu, 16 Nov 2006 21:43:49 +0800 Subject: [Weft QDA users] merging two halves of a project References: <4559D644.4040004@mhri.org> <455C2F6F.3070903@pressure.to> Message-ID: <200611162143496876555@fudan.edu.cn> ======= 2006-11-16 19:32:57 ????????======= >Hi Roberta >Hi Roberta > >Thanks for your email; I'm glad your team are finding Weft usable and >useful. > >Roberta_Goldman wrote: >> One feature that would be helpful for my current and other large >> projects is the ability to merge two halves of a project after two >> individuals have each completed coding a different half of the >> transcripts. >There isn't such a feature at present in Weft. The current version 1.0 >only really supports one person working on a project at a time. But it's >a feature I think is useful and feasible - I'm interested in pursuing >this as I also have a number of projects coming up where we might want >to do this. > >A 'merge' could work in a couple of ways - perhaps you could tell me how >you like to work. Here's a few ideas - I'm interested in what other >people think of these too, for the purposes of an interim Weft 2 release... > >- Are the individual coders working on different documents, using the >same set of categories or 'codebook'? In which case you might want >simply to join the documents and coding together. > >- Or are they working on the same documents, using the same codebook - >and if so, are you interested in a metric of inter-coder reliability? > >- Or are they working on the same documents, evolving their own analytic >frame? If so, how would the categories from different projects sit >alongside each other? > >- Would it be helpful to enable people to work on the same project >simultaneously from different workstations, even from different sites - >I have prototyped this feature, and am wondering if it's worth >developing further? >> If not, is there >> some way around this problem that I could use? >> >I'm not sure I can think of one for now, other that copying and pasting >or combining exported text in a word processor. Is it much easier for Openoffice format rather than MS word processor? After all, the odt format is an open standard. >Thanks again for your interest >Alex > >_______________________________________________ >weft-qda-users mailing list >weft-qda-users at rubyforge.org >http://rubyforge.org/mailman/listinfo/weft-qda-users = = = = = = = = = = = = = = = = = = = = ??? 2006-11-16 ------ Deparment of Sociology Fudan University,Shanghai,China PRC My current Email: ronggui.huang at gmail.com From maurizio.teli at gmail.com Fri Nov 17 14:06:27 2006 From: maurizio.teli at gmail.com (Maurizio Teli) Date: Fri, 17 Nov 2006 20:06:27 +0100 Subject: [Weft QDA users] Weft-QDA under Linux In-Reply-To: References: Message-ID: <1163790387.6485.2.camel@localhost> This is the output with Ubuntu 6.06 Dapper: $ ruby /usr/bin/weft-qda.rb /usr/lib/ruby/gems/1.8/gems/weft-qda-1.0.1/lib/weft/backend/sqlite/database.rb:8: uninitialized constant SQLite::Database (NameError) from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /usr/lib/ruby/gems/1.8/gems/weft-qda-1.0.1/lib/weft/backend/sqlite.rb:16 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /usr/lib/ruby/gems/1.8/gems/weft-qda-1.0.1/lib/weft/backend.rb:3 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /usr/lib/ruby/gems/1.8/gems/weft-qda-1.0.1/lib/weft.rb:18 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /usr/local/lib/site_ruby/1.8/rubygems.rb:229:in `activate' from /usr/local/lib/site_ruby/1.8/rubygems.rb:228:in `activate' from /usr/local/lib/site_ruby/1.8/rubygems.rb:66:in `active_gem_with_options' from /usr/local/lib/site_ruby/1.8/rubygems.rb:59:in `require_gem' from /usr/bin/weft-qda.rb:17 Any idea?!? Thanks Maurizio Maurizio Il giorno mar, 14/11/2006 alle 05.46 -0500, weft-qda-users-request at rubyforge.org ha scritto: > Re: Weft-QDA under Linux From bernhard at intevation.de Sat Nov 18 05:34:41 2006 From: bernhard at intevation.de (Bernhard Reiter) Date: Sat, 18 Nov 2006 11:34:41 +0100 Subject: [Weft QDA users] export does not work (1.0.1 on GNU/Linux Mandriva) Message-ID: <20061118103441.GA32283@intevation.de> Hi Alex, Hi everybody, here is the next technical difficulty with weft-qda: Export to HTML (or txt) does not work. I have identified and fixed one problem of the code when using PageTemplate 2.2.3. Still it does not work. My notes are following. As rubyforge was done in the last hour or so I could not check if thre are already issue reports or a new version in a code repository. Thanks in advance, Bernhard 20061118 Bernhard Trying to export something with weft-qda results into: /usr/lib/ruby/gems/1.8/gems/PageTemplate-2.2.3/lib/PageTemplate/parser.rb:237:in `initialize': undefined method `compact' for "/opt/weft-qda-20060mdk/weft_qda-1 .0.1/share/templates":String (NoMethodError) from /usr/lib/ruby/gems/1.8/gems/PageTemplate-2.2.3/lib/PageTemplate/par ser.rb:542:in `new' from /usr/lib/ruby/gems/1.8/gems/PageTemplate-2.2.3/lib/PageTemplate/par ser.rb:542:in `initialize' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/filters/templates.rb :43:in `new' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/filters/templates.rb :43:in `write' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui.rb:370:in `on_ export' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui.rb:369:in `ope n' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui.rb:369:in `on_ export' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui.rb:367:in `bus y' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui.rb:367:in `on_ export' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui.rb:141:in `cre ate_menus' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui.rb:140:in `add _item' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui/workarea.rb:33 0:in `call' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui.rb:53:in `main _loop' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/wxgui.rb:53:in `main _loop' from /opt/weft-qda-20060mdk/weft_qda-1.0.1/weft-qda.rb:60 Examination shows that parser.rb expect a hash to use .compact on, but @args seems to contain a string. Hypothesis: The infection happens in /opt/weft-qda-20060mdk/weft_qda-1.0.1/lib/weft/filters/templates.rb:43 tpl = PageTemplate::Parser.new('source' => CommentStrippingFileSource, 'include_paths' => TEMPLATES_DIR, 'preprocessor' => ExtendedPreprocessor ) as 'include_paths' will be interpreted as hash directly in /usr/lib/ruby/gems/1.8/gems/PageTemplate-2.2.3/lib/PageTemplate/parser.rb:237 def initialize(args = {}) @args = args if @args['include_paths'] @paths = @args['include_paths'] elsif @args['include_path'] @paths = [ @args['include_path'] ] Constructive proof: Try with 'include_path' => TEMPLATES_DIR, Now HTML export works, but the files itself do not contain contents. Might be a different version of PageTemplate. :/ There is another minor issue: The file name endings to get two dots ending up like "document-README..html". -- Professional Service for Free Software (intevation.net) The FreeGIS Project (freegis.org) FSFE (fsfeurope.org) From bernhard at intevation.de Mon Nov 20 04:02:12 2006 From: bernhard at intevation.de (Bernhard Reiter) Date: Mon, 20 Nov 2006 10:02:12 +0100 Subject: [Weft QDA users] Weft-QDA under Linux In-Reply-To: <1163790387.6485.2.camel@localhost> References: <1163790387.6485.2.camel@localhost> Message-ID: <200611201002.13335.bernhard@intevation.de> On Friday 17 November 2006 20:06, Maurizio Teli wrote: > Any idea?!? Which version of sqlite are you using, I believe I saw that several are available, maybe you have the wrong one. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://rubyforge.org/pipermail/weft-qda-users/attachments/20061120/59cb10b0/attachment.bin From alex at pressure.to Tue Nov 21 17:51:22 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 21 Nov 2006 22:51:22 +0000 Subject: [Weft QDA users] poll on an intermediate release In-Reply-To: <45599E81.7050909@ulg.ac.be> References: <45599E81.7050909@ulg.ac.be> Message-ID: <456382EA.8080302@pressure.to> Christophe Lejeune wrote: > Dear list members, > > I also agree: an intermediate version would be very appreciated. > Thanks all for your views. I think it is good practice for me to turn a release out soon anyway, so you can comment on how the new features are working, and where to go next, and track down bugs. It'll be a series of 'development' releases, like the old 0.9.x series of weft. So - I will make a call in a month or so's time. If wxruby2 is looking far enough along, then I'll use that. Otherwise, it'll have to be an intermediate release based on wxruby 0.6.0 > Anyway, I am also sensible to the fact that such a release could be very > time-consuming activity for Alex... > I really don't mind putting time into the software. It's just frustrating when that time goes to working round old, buggy software like wxruby 0.6.0, instead of developing usability, new features and improving documentation. Unfortunately the latter option (intermediate) is not going to improve the installation problems for people on Linux. But I don't know how to fix the old version of wxruby, and I don't think it's a useful way to spend limited time if I did. Perhaps if someone who's persevered through the pain is prepared to offer a wxruby.so binary for Linux weft-qda could be offered as a bundle or distro package for Linux. Please contact me off list... > The double-upgrade issue is also a question that have to be addressed. Hopefully this might not be such an issue. I'm planning to make the upgrading process force making a backup of the old version, to reduce the risk of data loss. alex From alex at pressure.to Tue Nov 21 17:55:34 2006 From: alex at pressure.to (Alex Fenton) Date: Tue, 21 Nov 2006 22:55:34 +0000 Subject: [Weft QDA users] merging two halves of a project In-Reply-To: <200611162143496876555@fudan.edu.cn> References: <4559D644.4040004@mhri.org> <455C2F6F.3070903@pressure.to> <200611162143496876555@fudan.edu.cn> Message-ID: <456383E6.6060809@pressure.to> ??? wrote: >> I'm not sure I can think of one for now, other that copying and pasting >> or combining exported text in a word processor. >> > > Is it much easier for Openoffice format rather than MS word processor? > After all, the odt format is an open standard. > I was just thinking of using simple cut and paste, which should work with a variety of word-processors and other desktop applications. But you're right that the OpenOffice odt format is an open standard, and could be supported as an export format. It's XML based, and any new version of Weft is going to support XML import (Transcriber) and export features. Feel free to submit a feature request for ODT - but I think I would be inclined to give higher priority to ensuring that more generic formats eg HTML, text, XML work properly. alex