[CWB] CQPWeb Custom GUII
Stephen Barrett
Stephen.Barrett at glasgow.ac.uk
Fri May 10 16:16:21 CEST 2013
Hi all,
Many thanks indeed for your very helpful feedback re: a custom GUI. I will keep the list posted on how things develop.
(Apologies if this message appears out-of-thread, as I'm new and couldn't figure out how to access the thread again. Any tips much appreciated!)
Stevie
-----Original Message-----
From: cwb-bounces at sslmit.unibo.it [mailto:cwb-bounces at sslmit.unibo.it] On Behalf Of cwb-request at sslmit.unibo.it
Sent: 10 May 2013 11:00
To: cwb at sslmit.unibo.it
Subject: CWB Digest, Vol 77, Issue 1
Send CWB mailing list submissions to
cwb at sslmit.unibo.it
To subscribe or unsubscribe via the World Wide Web, visit
http://devel.sslmit.unibo.it/mailman/listinfo/cwb
or, via email, send a message with subject or body 'help' to
cwb-request at sslmit.unibo.it
You can reach the person managing the list at
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. CQPWeb Custom GUII (Stephen Barrett)
2. Re: CQPWeb Custom GUII (Hardie, Andrew)
3. Re: CQPWeb Custom GUII (Pavel Vond?i?ka)
4. Re: CQPWeb Custom GUII (Hardie, Andrew)
5. Re: CQPWeb Custom GUII (Stefan Evert)
----------------------------------------------------------------------
Message: 1
Date: Thu, 9 May 2013 11:22:27 +0100
From: Stephen Barrett <Stephen.Barrett at glasgow.ac.uk>
To: "cwb at sslmit.unibo.it" <cwb at sslmit.unibo.it>
Subject: [CWB] CQPWeb Custom GUII
Message-ID:
<1E74325F1E320E4FAAEB051976822A0D3BFDFBD561 at CMS03.campus.gla.ac.uk>
Content-Type: text/plain; charset="us-ascii"
Hi,
We've been experimenting with CQPWeb for use with our corpora and find it a really powerful solution.
What we would like to do is customise the GUI quite heavily to provide for an interface for different user groups while at the same time allowing for any further upgrades to the code that might come along in the future. Given the code that we're running at the moment (3.0) we have a couple of questions:
The HTML output uses tables and ideally we would like to make extensive use of CSS, ideally with divs, etc. Is this something that will change in new builds of the software? If it isn't on the roadmap at the moment is it something you would consider?
Will there be any further development of the PHP, to make further use of object-oriented code, for example?
We are very happy to work on making the above changes but would like them to benefit the community at large where possible while also retaining compatibility with any further developments.
Thanks
Stevie
------------------------------
Message: 2
Date: Thu, 9 May 2013 11:04:00 +0000
From: "Hardie, Andrew" <a.hardie at lancaster.ac.uk>
To: Open source development of the Corpus WorkBench
<cwb at sslmit.unibo.it>
Subject: Re: [CWB] CQPWeb Custom GUII
Message-ID:
<28078EC3FBF1B940A3EF3D0D19BE351D1B06B3 at EX-0-MB1.lancs.local>
Content-Type: text/plain; charset="us-ascii"
hi Stevie,
> Is this something that will change in new builds of the software?
No.
> If it isn't on the roadmap at the moment is it something you would consider?
No.
The rationale for the above is that given limited development time, and a huge TODO list of requested improvements/additional analysis functions (see the website), I will be focused on functionality and not on appearance. A full redesign of the HTML structure is therefore not on the cards.
> Will there be any further development of the PHP, to make further use of object-oriented code, for example?
No.
(1) The PHP code certainly will *change* but only as a consequence of improving functionality, as per above.
(2) I personally prefer function-oriented design to object-oriented for nearly all purposes (the interfaces to child processes are an exception). I am a C programmer at heart!
If you want to use a substantially different GUI (or GUIs), and/or to structure the software according to different design principles, then I would suggest that your best option is to write a separate piece of front-end software and use vanilla CQPweb as the back-end engine.
Currently, this is not very easy since the front-end needs to parse the HTML generated by CQPweb. However, among the many high-priority things on the TODO list is the creation of an API for programmatic access via HTTP to CQPweb that would allow clients in any language, on a server or in a browser, to access the system. Once this is in place you could write a front-end GUI around it to meet your precise requirements pretty easily.
(I'd also be interested to know - anyone feel free to chip in here - for this programmatic access, what data format is best these days? My instinct is for plain-text, but XML and JSON are also options).
best
Andrew.
-----Original Message-----
From: cwb-bounces at sslmit.unibo.it [mailto:cwb-bounces at sslmit.unibo.it] On Behalf Of Stephen Barrett
Sent: 09 May 2013 11:22
To: cwb at sslmit.unibo.it
Subject: [CWB] CQPWeb Custom GUII
Hi,
We've been experimenting with CQPWeb for use with our corpora and find it a really powerful solution.
What we would like to do is customise the GUI quite heavily to provide for an interface for different user groups while at the same time allowing for any further upgrades to the code that might come along in the future. Given the code that we're running at the moment (3.0) we have a couple of questions:
The HTML output uses tables and ideally we would like to make extensive use of CSS, ideally with divs, etc. Is this something that will change in new builds of the software? If it isn't on the roadmap at the moment is it something you would consider?
Will there be any further development of the PHP, to make further use of object-oriented code, for example?
We are very happy to work on making the above changes but would like them to benefit the community at large where possible while also retaining compatibility with any further developments.
Thanks
Stevie
_______________________________________________
CWB mailing list
CWB at sslmit.unibo.it
http://devel.sslmit.unibo.it/mailman/listinfo/cwb
------------------------------
Message: 3
Date: Thu, 09 May 2013 13:26:01 +0200
From: Pavel Vond?i?ka <Pavel.Vondricka at ff.cuni.cz>
To: Open source development of the Corpus WorkBench
<cwb at sslmit.unibo.it>
Subject: Re: [CWB] CQPWeb Custom GUII
Message-ID: <1378357.KTbvrizH0n at platyz>
Content-Type: text/plain; charset="us-ascii"
Hi,
I am just in the process of developing a completely new GUI on top of CWB.
Actually it has ambitions to be able to use different back-end engines, not just CWB, and even at the same time. And it contains also a server application layer (Python) with a database and a (wanna-be-)general API (based on JSON, by the way) and a separate javascipt based (qooxdoo toolkit) GUI.
At the moment it can only queue asynchronous queries (both for monolingual and parallel corpora), show the concordances in tabs, sort the results if desired, and show some basic distribution charts. Nothing more. Next I want to implement at least some basic sub-corpora management (for fine-grained text selection, etc.).
We still have to discuss at the institute, whether this is exactly the way to take or not. But some kind of new GUI is definitely on the program - the question is only the exact design.
Best regards,
Pavel
> hi Stevie,
>
> > Is this something that will change in new builds of the software?
>
> No.
>
> > If it isn't on the roadmap at the moment is it something you would
> > consider?
> No.
>
> The rationale for the above is that given limited development time,
> and a huge TODO list of requested improvements/additional analysis
> functions (see the website), I will be focused on functionality and
> not on appearance. A full redesign of the HTML structure is therefore not on the cards.
> > Will there be any further development of the PHP, to make further
> > use of object-oriented code, for example?
> No.
>
> (1) The PHP code certainly will *change* but only as a consequence of
> improving functionality, as per above. (2) I personally prefer
> function-oriented design to object-oriented for nearly all purposes
> (the interfaces to child processes are an exception). I am a C
> programmer at heart!
>
> If you want to use a substantially different GUI (or GUIs), and/or to
> structure the software according to different design principles, then
> I would suggest that your best option is to write a separate piece of
> front-end software and use vanilla CQPweb as the back-end engine.
>
> Currently, this is not very easy since the front-end needs to parse
> the HTML generated by CQPweb. However, among the many high-priority
> things on the TODO list is the creation of an API for programmatic
> access via HTTP to CQPweb that would allow clients in any language, on
> a server or in a browser, to access the system. Once this is in place
> you could write a front-end GUI around it to meet your precise requirements pretty easily.
>
> (I'd also be interested to know - anyone feel free to chip in here -
> for this programmatic access, what data format is best these days? My
> instinct is for plain-text, but XML and JSON are also options).
>
> best
>
> Andrew.
>
> -----Original Message-----
> From: cwb-bounces at sslmit.unibo.it [mailto:cwb-bounces at sslmit.unibo.it]
> On Behalf Of Stephen Barrett Sent: 09 May 2013 11:22
> To: cwb at sslmit.unibo.it
> Subject: [CWB] CQPWeb Custom GUII
>
> Hi,
>
> We've been experimenting with CQPWeb for use with our corpora and find
> it a really powerful solution.
>
> What we would like to do is customise the GUI quite heavily to provide
> for an interface for different user groups while at the same time
> allowing for any further upgrades to the code that might come along in
> the future. Given the code that we're running at the moment (3.0) we
> have a couple of
> questions:
>
> The HTML output uses tables and ideally we would like to make
> extensive use of CSS, ideally with divs, etc. Is this something that
> will change in new builds of the software? If it isn't on the roadmap
> at the moment is it something you would consider?
>
> Will there be any further development of the PHP, to make further use
> of object-oriented code, for example?
>
> We are very happy to work on making the above changes but would like
> them to benefit the community at large where possible while also
> retaining compatibility with any further developments.
>
> Thanks
>
> Stevie
>
>
>
> _______________________________________________
> CWB mailing list
> CWB at sslmit.unibo.it
> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
> _______________________________________________
> CWB mailing list
> CWB at sslmit.unibo.it
> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
------------------------------
Message: 4
Date: Thu, 9 May 2013 11:55:18 +0000
From: "Hardie, Andrew" <a.hardie at lancaster.ac.uk>
To: Open source development of the Corpus WorkBench
<cwb at sslmit.unibo.it>
Subject: Re: [CWB] CQPWeb Custom GUII
Message-ID:
<28078EC3FBF1B940A3EF3D0D19BE351D1B0856 at EX-0-MB1.lancs.local>
Content-Type: text/plain; charset="us-ascii"
A little friendly competition is always to be welcomed. :)
Andrew.
-----Original Message-----
From: cwb-bounces at sslmit.unibo.it [mailto:cwb-bounces at sslmit.unibo.it] On Behalf Of Pavel Vondricka
Sent: 09 May 2013 12:26
To: Open source development of the Corpus WorkBench
Subject: Re: [CWB] CQPWeb Custom GUII
Hi,
I am just in the process of developing a completely new GUI on top of CWB.
Actually it has ambitions to be able to use different back-end engines, not just CWB, and even at the same time. And it contains also a server application layer (Python) with a database and a (wanna-be-)general API (based on JSON, by the way) and a separate javascipt based (qooxdoo toolkit) GUI.
At the moment it can only queue asynchronous queries (both for monolingual and parallel corpora), show the concordances in tabs, sort the results if desired, and show some basic distribution charts. Nothing more. Next I want to implement at least some basic sub-corpora management (for fine-grained text selection, etc.).
We still have to discuss at the institute, whether this is exactly the way to take or not. But some kind of new GUI is definitely on the program - the question is only the exact design.
Best regards,
Pavel
> hi Stevie,
>
> > Is this something that will change in new builds of the software?
>
> No.
>
> > If it isn't on the roadmap at the moment is it something you would
> > consider?
> No.
>
> The rationale for the above is that given limited development time,
> and a huge TODO list of requested improvements/additional analysis
> functions (see the website), I will be focused on functionality and
> not on appearance. A full redesign of the HTML structure is therefore not on the cards.
> > Will there be any further development of the PHP, to make further
> > use of object-oriented code, for example?
> No.
>
> (1) The PHP code certainly will *change* but only as a consequence of
> improving functionality, as per above. (2) I personally prefer
> function-oriented design to object-oriented for nearly all purposes
> (the interfaces to child processes are an exception). I am a C
> programmer at heart!
>
> If you want to use a substantially different GUI (or GUIs), and/or to
> structure the software according to different design principles, then
> I would suggest that your best option is to write a separate piece of
> front-end software and use vanilla CQPweb as the back-end engine.
>
> Currently, this is not very easy since the front-end needs to parse
> the HTML generated by CQPweb. However, among the many high-priority
> things on the TODO list is the creation of an API for programmatic
> access via HTTP to CQPweb that would allow clients in any language, on
> a server or in a browser, to access the system. Once this is in place
> you could write a front-end GUI around it to meet your precise requirements pretty easily.
>
> (I'd also be interested to know - anyone feel free to chip in here -
> for this programmatic access, what data format is best these days? My
> instinct is for plain-text, but XML and JSON are also options).
>
> best
>
> Andrew.
>
> -----Original Message-----
> From: cwb-bounces at sslmit.unibo.it [mailto:cwb-bounces at sslmit.unibo.it]
> On Behalf Of Stephen Barrett Sent: 09 May 2013 11:22
> To: cwb at sslmit.unibo.it
> Subject: [CWB] CQPWeb Custom GUII
>
> Hi,
>
> We've been experimenting with CQPWeb for use with our corpora and find
> it a really powerful solution.
>
> What we would like to do is customise the GUI quite heavily to provide
> for an interface for different user groups while at the same time
> allowing for any further upgrades to the code that might come along in
> the future. Given the code that we're running at the moment (3.0) we
> have a couple of
> questions:
>
> The HTML output uses tables and ideally we would like to make
> extensive use of CSS, ideally with divs, etc. Is this something that
> will change in new builds of the software? If it isn't on the roadmap
> at the moment is it something you would consider?
>
> Will there be any further development of the PHP, to make further use
> of object-oriented code, for example?
>
> We are very happy to work on making the above changes but would like
> them to benefit the community at large where possible while also
> retaining compatibility with any further developments.
>
> Thanks
>
> Stevie
>
>
>
> _______________________________________________
> CWB mailing list
> CWB at sslmit.unibo.it
> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
> _______________________________________________
> CWB mailing list
> CWB at sslmit.unibo.it
> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
_______________________________________________
CWB mailing list
CWB at sslmit.unibo.it
http://devel.sslmit.unibo.it/mailman/listinfo/cwb
------------------------------
Message: 5
Date: Fri, 10 May 2013 09:59:27 +0200
From: Stefan Evert <stefanML at collocations.de>
To: Open source development of the Corpus WorkBench
<cwb at sslmit.unibo.it>
Subject: Re: [CWB] CQPWeb Custom GUII
Message-ID: <F9AA2E02-9338-48E2-909F-CF16912DADAD at collocations.de>
Content-Type: text/plain; charset=us-ascii
> I am just in the process of developing a completely new GUI on top of CWB.
> Actually it has ambitions to be able to use different back-end
> engines, not just CWB, and even at the same time. And it contains also
> a server application layer (Python) with a database and a
> (wanna-be-)general API (based on JSON, by the way) and a separate javascipt based (qooxdoo toolkit) GUI.
That sounds very interesting. It's impossible to satisfy all users with a single peace of software, so some alternatives to CQPweb as the "official" GUI are definitely welcome.
Which Python API do you use to access corpora and communicate with CQP?
Best,
Stefan
------------------------------
_______________________________________________
CWB mailing list
CWB at sslmit.unibo.it
http://devel.sslmit.unibo.it/mailman/listinfo/cwb
End of CWB Digest, Vol 77, Issue 1
**********************************
More information about the CWB
mailing list