Hi You''re warmly invited to try and comment on the first initial preview of Weft QDA 2. == WARNING = This is very much an alpha release. It definitely shouldn''t be used for real projects. There''s no guarantee that projects will be capable of being opened in future releases. == DOWNLOADING & INSTALLING = http://rubyforge.org/frs/?group_id=665&release_id=21324 Windows users: download the .exe file and run the installer; you should then have a shortcut in your Start menu Mac users: download the .dmg file and open it up; copy the WeftQDA to your Applications folder Linux and other source users: download the .tar.gz file and unpack it. You will need ruby, a few system libraries, and several ruby gems installed. The README.txt file runs through the requirements. It''s a few steps, but should be straightforward. Then do ruby -rubygems weft-qda.rb to run Weft QDA. == WHAT''S NEW = Pretty much everything. It should look familiar, and tries to retain an emphasis on simplicity and ease of use, but internally it''s been almost completely rewritten. Major new features include: * Supports multi-lingual projects (save documents files for import in UTF-8 encoding) * Native on Mac OS X * More modern visual appearance * Interface can be translated into different languages * Documents can be edited after importing, whilst retaining coding * Annotations can be applied to passages of text * Attributes can be applied to whole documents * Searches, queries and code reviews are saved to the database and results updated live * Printing * Autosaving to recover from crashes * Smaller project file size Note that internally the file format is different to Weft QDA 1.0, so at the moment, it''s not possible to open Weft 1.0 qdp files in this release. This is partly deliberate to avoid damaging existing projects. == WHAT''S LEFT TO DO = First, a few things left to match up to Weft QDA 1.0 * Interface for Queries * Interface for CodeReviews * Update documentation Then, remaining features I''d like to add: * More import/export formats - XML (hypertopic, QuDeX, QDIF), possibly PDF, RTF * Colour theming of application icons * Custom-highlighting colours for Categories * Convert project from Weft QDA v1.0 * Scripting * Collaborative net-based working * Image documents (possibly sound & video...) * Integrated help Plus your suggestions... == PROBLEMS, BUGS, FEATURE REQUESTS = If you''re having problems installing or running the software, please use the mailing list. If you find bugs - you probably will - please file them on the bug tracker: http://rubyforge.org/tracker/?atid=2625&group_id=665&func=browse If you would like to request a feature, either discuss it on this mailing list, or use the feature request: http://rubyforge.org/tracker/?atid=2628&group_id=665&func=browse Please use the tracker if possible; it helps ensure that everything is followed up. You don''t have to register to use it, but if you register you will receive feedback on the bug/feature. Lastly, thanks all for your continued interest in Weft QDA. cheers alex
Alex Fenton wrote:> Mac users: download the .dmg file and open it up; copy the WeftQDA to > your Applications folder >Apparently the Mac build isn''t running right. I don''t have access to a second Mac to test on, so I''d like to hear from anyone with OS X 10.4 or 10.5 who''d be willing to collaborate on getting this to work. It would only involve a bit of emailing back and forth and trying out applications until we get one that works. Please drop me an email if interested. thanks alex
Alex, I will happily help, if I can. I was the one who originally posted the bug report (anonymously). But my knowledge of OS X and its unix underpinnings is not all that deep. Lindsay Alex Fenton wrote:> Alex Fenton wrote: > >> Mac users: download the .dmg file and open it up; copy the WeftQDA to >> your Applications folder >> >> > > Apparently the Mac build isn''t running right. I don''t have access to a > second Mac to test on, so I''d like to hear from anyone with OS X 10.4 or > 10.5 who''d be willing to collaborate on getting this to work. > > It would only involve a bit of emailing back and forth and trying out > applications until we get one that works. Please drop me an email if > interested. > > thanks > alex > > > _______________________________________________ > weft-qda-users mailing list > weft-qda-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/weft-qda-users >
Lindsay Stirton wrote:> I will happily help, if I can. I was the one who originally posted the > bug report (anonymously). But my knowledge of OS X and its unix > underpinnings is not all that deep. >Thanks for the kind offer. I should have said no technical knowledge required. I think I know what the problem is; it''s a matter of verifying when it''s resolved, which I can''t do on a single machine. I will drop you a line off-list to follow-up. If there are others out there willing to help, it''d still be useful to hear from you - I would like to test on both 10.4 and 10.5 thanks alex
Realy great... I just take a look on the new features and the previous ones and we will have a good software to propose for anybody how want to work with something else than NVivo, Atlas-ti or other. An idea, if you decide to work on integretion of video or audio, maybe it could be an idea to continue de developpement of Transana. It is suppose to be open source, but the developper decide to request payment for the download (500$). So, if WeftQDA want to go on this way, maybe we just can take the source code of a previous version and legally go over the transana project with integreting some modules of Transana in Weft. OK, I''m not a programmer, so I don''t know if it is possible to do that, but if we can do it... wow. Have a great day... and thanks Alex for your great work... Jean-Fran?ois Dragon 2008/4/18 Alex Fenton <alex at pressure.to>:> Hi > > You''re warmly invited to try and comment on the first initial preview of > Weft QDA 2. > > == WARNING => > This is very much an alpha release. It definitely shouldn''t be used for > real projects. There''s no guarantee that projects will be capable of > being opened in future releases. > > == DOWNLOADING & INSTALLING => > http://rubyforge.org/frs/?group_id=665&release_id=21324 > > Windows users: download the .exe file and run the installer; you should > then have a shortcut in your Start menu > > Mac users: download the .dmg file and open it up; copy the WeftQDA to > your Applications folder > > Linux and other source users: download the .tar.gz file and unpack it. > You will need ruby, a few system libraries, and several ruby gems > installed. The README.txt file runs through the requirements. It''s a few > steps, but should be straightforward. Then do ruby -rubygems weft-qda.rb > to run Weft QDA. > > == WHAT''S NEW => > Pretty much everything. It should look familiar, and tries to retain an > emphasis on simplicity and ease of use, but internally it''s been almost > completely rewritten. Major new features include: > > * Supports multi-lingual projects (save documents files for import in > UTF-8 encoding) > * Native on Mac OS X > * More modern visual appearance > * Interface can be translated into different languages > * Documents can be edited after importing, whilst retaining coding > * Annotations can be applied to passages of text > * Attributes can be applied to whole documents > * Searches, queries and code reviews are saved to the database and > results updated live > * Printing > * Autosaving to recover from crashes > * Smaller project file size > > Note that internally the file format is different to Weft QDA 1.0, so at > the moment, it''s not possible to open Weft 1.0 qdp files in this > release. This is partly deliberate to avoid damaging existing projects. > > == WHAT''S LEFT TO DO => > First, a few things left to match up to Weft QDA 1.0 > > * Interface for Queries > * Interface for CodeReviews > * Update documentation > > Then, remaining features I''d like to add: > > * More import/export formats - XML (hypertopic, QuDeX, QDIF), possibly > PDF, RTF > * Colour theming of application icons > * Custom-highlighting colours for Categories > * Convert project from Weft QDA v1.0 > * Scripting > * Collaborative net-based working > * Image documents (possibly sound & video...) > * Integrated help > > Plus your suggestions... > > == PROBLEMS, BUGS, FEATURE REQUESTS => > If you''re having problems installing or running the software, please use > the mailing list. > > If you find bugs - you probably will - please file them on the bug > tracker: > http://rubyforge.org/tracker/?atid=2625&group_id=665&func=browse > > If you would like to request a feature, either discuss it on this > mailing list, or use the feature request: > http://rubyforge.org/tracker/?atid=2628&group_id=665&func=browse > > Please use the tracker if possible; it helps ensure that everything is > followed up. You don''t have to register to use it, but if you register > you will receive feedback on the bug/feature. > > Lastly, thanks all for your continued interest in Weft QDA. > > cheers > alex > > > > > _______________________________________________ > weft-qda-users mailing list > weft-qda-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/weft-qda-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/weft-qda-users/attachments/20080418/70d40dc7/attachment.html
Alex Fenton wrote:> Apparently the Mac build isn''t running right. I don''t have access to a > second Mac to test on, so I''d like to hear from anyone with OS X 10.4 or > 10.5 who''d be willing to collaborate on getting this to work.Just a note to say that it''s now working on 10.5 - thanks to Lindsay for help with this. An updated .dmg file is now available on the download page if you wish to try this version of Weft QDA on Mac. alex
I''ve checked importing text in Spanish and Catalan languages, but i couldn''t import them. I also tried to open a previous project in Spanish but I couldn''t. El program gives a problem of encoding. In English It worked fine to import data. I tried alto to assign attributes to documents and it worked fine. A very nice feature. I like the new graphical aspects. Jordi En/na Alex Fenton ha escrit:> Hi > > You''re warmly invited to try and comment on the first initial preview of > Weft QDA 2. > > == WARNING => > This is very much an alpha release. It definitely shouldn''t be used for > real projects. There''s no guarantee that projects will be capable of > being opened in future releases. > > == DOWNLOADING & INSTALLING => > http://rubyforge.org/frs/?group_id=665&release_id=21324 > > Windows users: download the .exe file and run the installer; you should > then have a shortcut in your Start menu > > Mac users: download the .dmg file and open it up; copy the WeftQDA to > your Applications folder > > Linux and other source users: download the .tar.gz file and unpack it. > You will need ruby, a few system libraries, and several ruby gems > installed. The README.txt file runs through the requirements. It''s a few > steps, but should be straightforward. Then do ruby -rubygems weft-qda.rb > to run Weft QDA. > > == WHAT''S NEW => > Pretty much everything. It should look familiar, and tries to retain an > emphasis on simplicity and ease of use, but internally it''s been almost > completely rewritten. Major new features include: > > * Supports multi-lingual projects (save documents files for import in > UTF-8 encoding) > * Native on Mac OS X > * More modern visual appearance > * Interface can be translated into different languages > * Documents can be edited after importing, whilst retaining coding > * Annotations can be applied to passages of text > * Attributes can be applied to whole documents > * Searches, queries and code reviews are saved to the database and > results updated live > * Printing > * Autosaving to recover from crashes > * Smaller project file size > > Note that internally the file format is different to Weft QDA 1.0, so at > the moment, it''s not possible to open Weft 1.0 qdp files in this > release. This is partly deliberate to avoid damaging existing projects. > > == WHAT''S LEFT TO DO => > First, a few things left to match up to Weft QDA 1.0 > > * Interface for Queries > * Interface for CodeReviews > * Update documentation > > Then, remaining features I''d like to add: > > * More import/export formats - XML (hypertopic, QuDeX, QDIF), possibly > PDF, RTF > * Colour theming of application icons > * Custom-highlighting colours for Categories > * Convert project from Weft QDA v1.0 > * Scripting > * Collaborative net-based working > * Image documents (possibly sound & video...) > * Integrated help > > Plus your suggestions... > > == PROBLEMS, BUGS, FEATURE REQUESTS => > If you''re having problems installing or running the software, please use > the mailing list. > > If you find bugs - you probably will - please file them on the bug tracker: > http://rubyforge.org/tracker/?atid=2625&group_id=665&func=browse > > If you would like to request a feature, either discuss it on this > mailing list, or use the feature request: > http://rubyforge.org/tracker/?atid=2628&group_id=665&func=browse > > Please use the tracker if possible; it helps ensure that everything is > followed up. You don''t have to register to use it, but if you register > you will receive feedback on the bug/feature. > > Lastly, thanks all for your continued interest in Weft QDA. > > cheers > alex > > > > > _______________________________________________ > weft-qda-users mailing list > weft-qda-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/weft-qda-users > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/weft-qda-users/attachments/20080421/be50769d/attachment-0001.html
Jordi - Thanks for trying it out. Jordi L?pez wrote:> I''ve checked importing text in Spanish and Catalan languages, but i > couldn''t import them. I also tried to open a previous project in > Spanish but I couldn''t. El program gives a problem of encoding.To deal with multilingual projects, the program has to be more careful about encodings (which are different ways to store characters in text files). For Spanish or Catalan, I would try importing again. In the dialog where you choose the files, there is an option at the bottom "Files of type:". Choose "Plain Text Files (ISO-8859-1)" instead of "Plain Text Files (UTF-8)". Then choose the files you were using before. If that doesn''t work, please let me know. You could then ensure that your text files are saved in UTF-8. If you open them in a word processor, and choose "Save As" "Plain Text File", it should give you an option to choose encoding. Select "Unicode (UTF-8)" or "UTF-8". Then import those files into Weft. btw, previous Weft v1.0 projects won''t open - the file format is different. When 2.0 is ready there will be an option to import old projects.> In English It worked fine to import data. I tried alto to assign > attributes to documents and it worked fine. A very nice feature. I > like the new graphical aspects.Thanks. In the next release you will be able to use attributes in queries - so "find text coded by category XXX which has attribute YYY". alex
Alex, I followed your instructions and I could import Spanish docs in Weft QDA1.9. It worked fine and accents were in their place. Thanks, Alex. Jordi En/na Alex Fenton ha escrit:> Jordi - Thanks for trying it out. > > Jordi L?pez wrote: > >> I''ve checked importing text in Spanish and Catalan languages, but i >> couldn''t import them. I also tried to open a previous project in >> Spanish but I couldn''t. El program gives a problem of encoding. >> > To deal with multilingual projects, the program has to be more careful > about encodings (which are different ways to store characters in text > files). > > For Spanish or Catalan, I would try importing again. In the dialog where > you choose the files, there is an option at the bottom "Files of type:". > Choose "Plain Text Files (ISO-8859-1)" instead of "Plain Text Files > (UTF-8)". Then choose the files you were using before. > > If that doesn''t work, please let me know. You could then ensure that > your text files are saved in UTF-8. If you open them in a word > processor, and choose "Save As" "Plain Text File", it should give you an > option to choose encoding. Select "Unicode (UTF-8)" or "UTF-8". Then > import those files into Weft. > > btw, previous Weft v1.0 projects won''t open - the file format is > different. When 2.0 is ready there will be an option to import old projects. > >> In English It worked fine to import data. I tried alto to assign >> attributes to documents and it worked fine. A very nice feature. I >> like the new graphical aspects. >> > Thanks. In the next release you will be able to use attributes in > queries - so "find text coded by category XXX which has attribute YYY". > > alex > _______________________________________________ > weft-qda-users mailing list > weft-qda-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/weft-qda-users > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/weft-qda-users/attachments/20080421/c97af46d/attachment.html
Hi! Have done some testing with swedish documents, in both utf-8 and iso8859-1 coding, and found no problems with them. - importing works well - coding works well - retrieving and viewing codes work well Also tried with categories using swedish characters (a code called "externa akt?rer") - worked well. Unmarking - ok. Deleting documents - ok. Inserting memo - ok BUT: when doing this, and clicking on OK on the note, I am retured to the top of the text document, not to the insert point. Found that the dropdown box that displays "recently used categories" displayed mulitple instances of categories, when I had used one category several times. And an idea: I would like to see all categories used in the present document there. As of now, when I re-open a coded document, this box is empty (as no codes have been used this session). (this is a feature request) One problem (maybe not to be expected to work?) - attempting to restore a backup, after a crash, again crashed weft. Would you need the output from this? Finally, I am not sure how the attribute function is to work... ? Maybe too early? My system is Ubuntu Gutsy. And somewhat off the point: why is Weft not GPL''d? Just curious. Great work, Alex! Keep it up, and hope I can be of help somewhere along the line... Magnus Alex Fenton skrev:> Hi > > You''re warmly invited to try and comment on the first initial preview of > Weft QDA 2. > > == WARNING => > This is very much an alpha release. It definitely shouldn''t be used for > real projects. There''s no guarantee that projects will be capable of > being opened in future releases. > > == DOWNLOADING & INSTALLING => > http://rubyforge.org/frs/?group_id=665&release_id=21324 > > Windows users: download the .exe file and run the installer; you should > then have a shortcut in your Start menu > > Mac users: download the .dmg file and open it up; copy the WeftQDA to > your Applications folder > > Linux and other source users: download the .tar.gz file and unpack it. > You will need ruby, a few system libraries, and several ruby gems > installed. The README.txt file runs through the requirements. It''s a few > steps, but should be straightforward. Then do ruby -rubygems weft-qda.rb > to run Weft QDA. > > == WHAT''S NEW => > Pretty much everything. It should look familiar, and tries to retain an > emphasis on simplicity and ease of use, but internally it''s been almost > completely rewritten. Major new features include: > > * Supports multi-lingual projects (save documents files for import in > UTF-8 encoding) > * Native on Mac OS X > * More modern visual appearance > * Interface can be translated into different languages > * Documents can be edited after importing, whilst retaining coding > * Annotations can be applied to passages of text > * Attributes can be applied to whole documents > * Searches, queries and code reviews are saved to the database and > results updated live > * Printing > * Autosaving to recover from crashes > * Smaller project file size > > Note that internally the file format is different to Weft QDA 1.0, so at > the moment, it''s not possible to open Weft 1.0 qdp files in this > release. This is partly deliberate to avoid damaging existing projects. > > == WHAT''S LEFT TO DO => > First, a few things left to match up to Weft QDA 1.0 > > * Interface for Queries > * Interface for CodeReviews > * Update documentation > > Then, remaining features I''d like to add: > > * More import/export formats - XML (hypertopic, QuDeX, QDIF), possibly > PDF, RTF > * Colour theming of application icons > * Custom-highlighting colours for Categories > * Convert project from Weft QDA v1.0 > * Scripting > * Collaborative net-based working > * Image documents (possibly sound & video...) > * Integrated help > > Plus your suggestions... > > == PROBLEMS, BUGS, FEATURE REQUESTS => > If you''re having problems installing or running the software, please use > the mailing list. > > If you find bugs - you probably will - please file them on the bug tracker: > http://rubyforge.org/tracker/?atid=2625&group_id=665&func=browse > > If you would like to request a feature, either discuss it on this > mailing list, or use the feature request: > http://rubyforge.org/tracker/?atid=2628&group_id=665&func=browse > > Please use the tracker if possible; it helps ensure that everything is > followed up. You don''t have to register to use it, but if you register > you will receive feedback on the bug/feature. > > Lastly, thanks all for your continued interest in Weft QDA. > > cheers > alex > > > > > _______________________________________________ > weft-qda-users mailing list > weft-qda-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/weft-qda-users >
Magnus Larsson wrote:> Have done some testing with swedish documents, in both utf-8 and > iso8859-1 coding, and found no problems with them. >Great, thanks for encouragement and time trying this out. Briefly in response:> BUT: when doing this, and clicking on OK on the note, I am retured to > the top of the text document, not to the insert point. >I''ll fix that.> And an idea: I would like to see all categories used in > the present document there. As of now, when I re-open a coded document, > this box is empty (as no codes have been used this session). (this is a > feature request) >Sounds sensible, I can add that.> One problem (maybe not to be expected to work?) - attempting to restore > a backup, after a crash, again crashed weft. Would you need the output > from this? >No, I''m seeing the same thing now> Finally, I am not sure how the attribute function is to work... ? Maybe > too early? >It should work at the moment - you create an attribute (eg ''sex'') then create values for it (eg ''male'', ''female''). Then you can file documents under those attributes. But the point of it will be clearer when Query is working again.> And somewhat off the point: why is Weft not GPL''d? Just curious. >I just liked a "Public Domain" licence better, at the time, because it completely disavowed proprietorial rights. best alex