[CWB] CWB and CQPweb installation steps + Latest version

Hardie, Andrew a.hardie at lancaster.ac.uk
Fri Apr 29 13:17:31 CEST 2022


The most up to date versions are those in the development trunk of the repo. You can get these using Subversion. Explained here:

https://cwb.sourceforge.io/devs.php   (under "svn access for developers")

the specific commands you need are

svn co http://svn.code.sf.net/p/cwb/code/cwb/trunk cwb
svn co http://svn.code.sf.net/p/cwb/code/gui/cqpweb/trunk cqpweb

The former contains files README and INSTALL which explain how to install.

The latter contains (under "doc") a copy of the CQPweb manual that can also be found here (https://cwb.sourceforge.io/documentation.php); early chapters of that doc cover installation step by step.

If you have specific queries about the contents of those three files, you can email them to the list - I will clarify whatever is confusing.

NB: sometimes the very most recent version will be "unstable", ie things may break while we are midway through improvements.

CQPweb 3.3.x (the version in the dev trunk) is officially unstable, but in fact, most things work fine and you shouldn't have problems with it (there are some things in distribution and subcorpus manipulation that are broken from 3.2 and still giving me a headache; once they're fixed, 3.3. will be stable)

CWB 3.4.x is likewise officially only a preparation for the stable 3.5, but in practice it is already stable and is the best version to use.

best

Andrew.



From: cwb-bounces at sslmit.unibo.it <cwb-bounces at sslmit.unibo.it> On Behalf Of raisi
Sent: 29 April 2022 11:52
To: cwb at sslmit.unibo.it
Subject: [CWB] CWB and CQPweb installation steps + Latest version

Dear Andrew,
in corpus workbench documentation I did not find a clear step installation of CWB and CQPweb, the second there are a lot of versions produced, I would like to have the latest version for CWB and CQPweb, could you please guide me on the above questions as soon as possible?

BR
raisi

On Fri, Apr 29, 2022 at 12:00 PM <cwb-request at sslmit.unibo.it<mailto:cwb-request at sslmit.unibo.it>> wrote:
Send CWB mailing list submissions to
        cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>

To subscribe or unsubscribe via the World Wide Web, visit
        http://liste.sslmit.unibo.it/mailman/listinfo/cwb<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fliste.sslmit.unibo.it%2Fmailman%2Flistinfo%2Fcwb&data=05%7C01%7Chardiea%40live.lancs.ac.uk%7C536d50f10cb04774238708da29ce6547%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637868264894248872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NUb%2FZ0MYsEzkuSYEsnssvgqlh9lgas6R7vNdi1tWjk0%3D&reserved=0>
or, via email, send a message with subject or body 'help' to
        cwb-request at sslmit.unibo.it<mailto:cwb-request at sslmit.unibo.it>

You can reach the person managing the list at
        cwb-owner at sslmit.unibo.it<mailto:cwb-owner at sslmit.unibo.it>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CWB digest..."


Today's Topics:

   1. Re: Skins for cqpweb (Hardie, Andrew)


----------------------------------------------------------------------

Message: 1
Date: Fri, 29 Apr 2022 02:43:41 +0000
From: "Hardie, Andrew" <a.hardie at lancaster.ac.uk<mailto:a.hardie at lancaster.ac.uk>>
To: Open source development of the Corpus WorkBench
        <cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>>
Subject: Re: [CWB] Skins for cqpweb
Message-ID:
        <LO4P265MB348576D6E3277E3E2549208DCBFC9 at LO4P265MB3485.GBRP265.PROD.OUTLOOK.COM<mailto:LO4P265MB348576D6E3277E3E2549208DCBFC9 at LO4P265MB3485.GBRP265.PROD.OUTLOOK.COM>>

Content-Type: text/plain; charset="iso-8859-2"

Hi Graham, and everybody,

The CorCenCC interface isn't based on CQPweb or CWB at all; instead it uses a relational database system which encompasses their data collection records as well as accessing the corpus. See section 3.5 to 3.7, esp. fig 4, of the paper

Knight, D., Loizides, F., Neale, S., Anthony, L. and Spasi?, I. (2020). Developing computational infrastructure for the CorCenCC corpus - the National Corpus of Contemporary Welsh. Language Resources and Evaluation (LREV).

available here:

https://www.researchgate.net/publication/343299269_Developing_computational_infrastructure_for_the_CorCenCC_corpus_The_National_Corpus_of_Contemporary_Welsh<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.researchgate.net%2Fpublication%2F343299269_Developing_computational_infrastructure_for_the_CorCenCC_corpus_The_National_Corpus_of_Contemporary_Welsh&data=05%7C01%7Chardiea%40live.lancs.ac.uk%7C536d50f10cb04774238708da29ce6547%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637868264894248872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4Cpah19iL3hvnMMYmYs9ECybhnzxkRiLJTFJaE456xE%3D&reserved=0>

As they say there:

"The main reasons for creating a bespoke interface rather than re-using an existing solution such as CQPweb (Hardie 2012) were the requirements to tailor its functionality to the specific metadata of the CorCenCC corpus and its prospective users, and so it could be integrated with a bespoke pedagogic toolkit."

My aim, via my push on plugins and the API over the last few years, is that, in future, people will be able to achieve this level of customisation without starting from scratch. Part of the point of CQPweb as a whole to help others avoid having to create the same basic web concordancer etc. over and over, but the evidence (not just from CorCenCC but from many other projects) is that this hasn't worked - people (quite rightly) have very particular requirements and if a system fails to meet just one of them, they'll start from scratch rather than adopt that existing system as a solution. Thus, the importance of customisability and extensibility. Things have improved. But overall it's not where it needs to be yet.

But on the actual topic of skins/colours...

Originally, the idea was that a skin = a CSS file. One css file contained all the formatting, so you rewrite that file as you liked to modify the appearance.

However, as the system evolved, things changed, because the basic CSS became more and more complex.

So what I did instead is parameterise the colours, and separate them from the main formatting. You can see this in the HTML at the start of any page:

        <style>

                :root {
                        --colour-layout-fg      :       #ecff6f;
                        --colour-layout-strong  :       #b9ff6f;
                        --colour-layout-contrast        :       #00ffff;
                        --colour-text-normal    :       black;
                        --colour-text-strong    :       black;
                        --colour-text-bright    :       purple;
                        --colour-text-faint     :       gray;
                        --colour-layout-bg      :       #d5d5d5;
                        --colour-layout-data2   :       #f0f0f0;
                        --colour-layout-outline :       white;
                        --colour-tooltip-frame  :       #003399;
                        --colour-tooltip-bg     :       #e6ecff;
                        --colour-tooltip-text   :       #000066;
                }


        </style>

(that's 3.3, it looks a bit different in 3.2)

So now, colour schemes are defined by the colour variables inserted here. This has allowed me to add a bundle of new built-in colour schemes (not chosen by me; I'm rubbish at that) quickly just by adding them to the code. See:

https://sourceforge.net/p/cwb/code/HEAD/tree/gui/cqpweb/trunk/lib/html-lib.php#l2628<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fcwb%2Fcode%2FHEAD%2Ftree%2Fgui%2Fcqpweb%2Ftrunk%2Flib%2Fhtml-lib.php%23l2628&data=05%7C01%7Chardiea%40live.lancs.ac.uk%7C536d50f10cb04774238708da29ce6547%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637868264894248872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9j5RX%2FDkA3Ziwc%2B3hXgSAiyW0mKeFc79osHNSvpZ2qo%3D&reserved=0>

Adding new colour schemes can be done by hacking that file OR using a CSS file that contains just a ":root" control like the above to specify colours, though the latter can't be set up by the interface (yet), only by directly putting the filename into the database in corpus_info.colour_scheme (or using them for the three main pages via the config file variables).

I want to add a system to dynamically control the colours in place of the use of CSS files, but as with so many other things, it's a matter of time ...

I also want to use more CSS variables so that colour-schemes can alter more behaviours (at the moment it's JUST colour).

For instance, the things that Thilo Wiertz's CSS skins for 3.2 do (which I really like by the way, they are better than most of my own efforts) wouldn't be possible in 3.3. But I'd like to make it so they are.

There are other people who've made the system look visually much better by hacking the code. See, for instance, https://corpling.uis.georgetown.edu/cqp/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcorpling.uis.georgetown.edu%2Fcqp%2F&data=05%7C01%7Chardiea%40live.lancs.ac.uk%7C536d50f10cb04774238708da29ce6547%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637868264894248872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=aF9v4NDaQNwv2peiKIKIgGh1Swrox%2FYRw0s3lIMTJM8%3D&reserved=0> (as I understand, the front page is the most-changed). The drawback is that doing that breaks upgrade paths. The aforementioned Georgetown server is at 3.2.11, for instance. Reapplying all their changes to 3.3 would be ... quite a task. I'm trying to amend the code structure to make that kind of modification easier.


Finally: If you want to change the interface completely, that is (where "is" = "will be Real Soon Now") possible too: by using the CQPwebClient as your backend, and then writing whatever frontend you want. Alas the CQPwebClient modules for different languages are nowhere near completion, and are dependent on the degree of completion of the API, of course.

best

Andrew.


-----Original Message-----
From: cwb-bounces at sslmit.unibo.it<mailto:cwb-bounces at sslmit.unibo.it> <cwb-bounces at sslmit.unibo.it<mailto:cwb-bounces at sslmit.unibo.it>> On Behalf Of Graham Ranger
Sent: 28 April 2022 14:45
To: Open source development of the Corpus WorkBench <cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>>
Subject: [CWB] Skins for cqpweb


Hello to all,
I was wondering whether there are any alternative skins or themes for cqpweb?
I think this is a recurrent question, and I believe Thilo Wiertz has developed some css which change the colour schemes
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwiertz%2Fcqpweb_css&amp;data=05%7C01%7Chardiea%40live.lancs.ac.uk%7Cd25ec0186f7b4176875d08da291e9e99%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637867509923068013%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=2AiNy4PAziPSQCDm5YQVdCogozkvkr55ZQKY%2FtzNUZA%3D&amp;reserved=0<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwiertz%2Fcqpweb_css&data=05%7C01%7Chardiea%40live.lancs.ac.uk%7C536d50f10cb04774238708da29ce6547%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637868264894248872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Vf2ptB%2B91yOqrVkYntimmu3PpuGZ5Evnge4bEg%2BtKjg%3D&reserved=0> but I was wondering if there was anything new... (I had understood, perhaps mistakenly, that the contemporary Welsh corpus was built around a cqpweb base, but with a very different interface https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcorpus.corcencc.org%2Fhome&amp;data=05%7C01%7Chardiea%40live.lancs.ac.uk%7Cd25ec0186f7b4176875d08da291e9e99%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637867509923068013%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=c6vRK76DIhuKSXQ2AzLkDX87oR9<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcorpus.corcencc.org%2Fhome&data=05%7C01%7Chardiea%40live.lancs.ac.uk%7C536d50f10cb04774238708da29ce6547%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637868264894248872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZJHoLKlq37p5R6xmB%2FAMVCtwikpsSZQ1xsDxNRch6fI%3D&reserved=0>
 cR8fKThX%2Fl2BUmJ8%3D&amp;reserved=0.)
Best,
Graham.
_______________________________________________
CWB mailing list
CWB at sslmit.unibo.it<mailto:CWB at sslmit.unibo.it>
https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fliste.sslmit.unibo.it%2Fmailman%2Flistinfo%2Fcwb&amp;data=05%7C01%7Chardiea%40live.lancs.ac.uk%7Cd25ec0186f7b4176875d08da291e9e99%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637867509923068013%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=jwlzxrSC6BUvqjuOj4AP1UWjSv78NIXYe9r3PitTy%2BM%3D&amp;reserved=0<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fliste.sslmit.unibo.it%2Fmailman%2Flistinfo%2Fcwb&data=05%7C01%7Chardiea%40live.lancs.ac.uk%7C536d50f10cb04774238708da29ce6547%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637868264894248872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NUb%2FZ0MYsEzkuSYEsnssvgqlh9lgas6R7vNdi1tWjk0%3D&reserved=0>


------------------------------

_______________________________________________
CWB mailing list
CWB at sslmit.unibo.it<mailto:CWB at sslmit.unibo.it>
http://liste.sslmit.unibo.it/mailman/listinfo/cwb<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fliste.sslmit.unibo.it%2Fmailman%2Flistinfo%2Fcwb&data=05%7C01%7Chardiea%40live.lancs.ac.uk%7C536d50f10cb04774238708da29ce6547%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637868264894405082%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=w2aEYl%2B5gMs92yjP8veCqAeucIEfSRpII%2FnAUSr7cQA%3D&reserved=0>


End of CWB Digest, Vol 181, Issue 30
************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://liste.sslmit.unibo.it/pipermail/cwb/attachments/20220429/d6d8009f/attachment-0001.html>


More information about the CWB mailing list