Re: [Koha-devel] Bug 5401: WYSWYG for Koha News
Galen Charlton wrote:
Since TinyMCE is used by only one page, if we decide to switch to elRTE (or to something else entirely), it won't be a big deal. Has anybody done a direct comparison?
I've used TinyMCE and haven't used elRTE, but wouldn't this question get better answers if asked on koha-devel? Thanks -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Past Koha Release Manager (2.0), LMS programmer, statistician, webmaster. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha
Hi, On Sun, Nov 14, 2010 at 1:18 PM, MJ Ray <mjr@phonecoop.coop> wrote:
Galen Charlton wrote:
Since TinyMCE is used by only one page, if we decide to switch to elRTE (or to something else entirely), it won't be a big deal. Has anybody done a direct comparison?
I've used TinyMCE and haven't used elRTE, but wouldn't this question get better answers if asked on koha-devel?
As the question was stated, yes, although if it turned out that Koustubha was just unaware that Koha was already using TinyMCE, a replacement patch using it instead of elRTE may have sufficed. There is a long standing practice of discussion of individual patches on koha-commits, however, so while koha-devel is certainly a valid choice for discussing this issue, I do want to point out and remind people that some relevant discussion does take place on the koha-commits list. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
On 15 November 2010 08:12, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
On Sun, Nov 14, 2010 at 1:18 PM, MJ Ray <mjr@phonecoop.coop> wrote:
Galen Charlton wrote:
Since TinyMCE is used by only one page, if we decide to switch to elRTE (or to something else entirely), it won't be a big deal. Has anybody done a direct comparison?
I've used TinyMCE and haven't used elRTE, but wouldn't this question get better answers if asked on koha-devel?
As the question was stated, yes, although if it turned out that Koustubha was just unaware that Koha was already using TinyMCE, a replacement patch using it instead of elRTE may have sufficed.
There is a long standing practice of discussion of individual patches on koha-commits, however, so while koha-devel is certainly a valid choice for discussing this issue, I do want to point out and remind people that some relevant discussion does take place on the koha-commits list.
And on the koha-patches list too :) Chris
Hi, On Sun, Nov 14, 2010 at 2:24 PM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
And on the koha-patches list too :)
Indeed. To understand my previous email correctly, please replace every use of "koha-commits" with "koha-patches". :) Regards, Galen -- Galen Charlton gmcharlt@gmail.com
On Mon, Nov 15, 2010 at 12:42 AM, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
On Sun, Nov 14, 2010 at 1:18 PM, MJ Ray <mjr@phonecoop.coop> wrote:
Galen Charlton wrote:
Since TinyMCE is used by only one page, if we decide to switch to elRTE (or to something else entirely), it won't be a big deal. Has anybody done a direct comparison?
I've used TinyMCE and haven't used elRTE, but wouldn't this question get better answers if asked on koha-devel?
As the question was stated, yes, although if it turned out that Koustubha was just unaware that Koha was already using TinyMCE, a replacement patch using it instead of elRTE may have sufficed.
As it happens I am aware of TinyMCE being already in Koha. But try as I might I could not get it to play nice ( read - at all ) with the News page. I tried the jquery varient of TinyMCE too and no go. Also I dont like the fact that the imagemanager etc of TinyMCE are only for paid customers. elRTE worked pretty well. Had to do some tweaks to its css etc. I have cleaned up the patch. Divided it into two separate patches. One for the elRTE library and one for the Koha changes I did. Now both apply squeaky clean. Got all features like image, media insert etc working now. Attaching both the patches here. Will also upload in bugzilla. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2
Galen Charlton wrote:
There is a long standing practice of discussion of individual patches on koha-commits, however, so while koha-devel is certainly a valid choice for discussing this issue, I do want to point out and remind people that some relevant discussion does take place on the koha-commits list.
I don't like that practice because:- 1. the list description "Patches submitted to Koha" gives no indication it occurs and it's different from other projects' -commit mailing lists; 2. developers have to subscribe to receive all patches even if they're only interested in their fields of activity and the occasional discussions, contributing to information overload; 3. I think the patches are carried in only one of the web forum versions of our discussions http://koha-community.org/support/forums/ 4. usually the patches relate to a bug and email discussion isn't automatically attached to the bug report - I have started work to address this, but it's still going to have some delay between the discussion and posting to the bug report, which may mean the discussion is irrelevant by the time the bug is told; 5. most importantly, many topics are wider than a single patch, such as this one about what rich editor to adopt. Can we overcome these problems, or state clearly that wider-than-one-patch discussions should be on -devel? Thanks, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Past Koha Release Manager (2.0), LMS programmer, statistician, webmaster. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha
From the koha-commits mailing list:
This mailing list is an informational list to which commit descriptions for patches pushed to the public Koha Git repository (currently git://git.koha-community.org/koha.git) are posted. This list should not be used to discuss individual patches, as not all contributors will be subscribed to koha-commits. Instead, please use koha-devel, koha-patches, or bugs.koha.org for that purpose. Is this no longer the case? -----Oorspronkelijk bericht----- Van: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] Namens MJ Ray Verzonden: maandag 15 november 2010 11:10 Aan: Galen Charlton CC: koha-devel@lists.koha-community.org; koha-patches@lists.koha-community.org Onderwerp: [Koha-devel] Discussion of development topics, was: Bug 5401: WYSWYG for Koha News Galen Charlton wrote:
There is a long standing practice of discussion of individual patches
on koha-commits, however, so while koha-devel is certainly a valid
choice for discussing this issue, I do want to point out and remind
people that some relevant discussion does take place on the
koha-commits list.
I don't like that practice because:- 1. the list description "Patches submitted to Koha" gives no indication it occurs and it's different from other projects' -commit mailing lists; 2. developers have to subscribe to receive all patches even if they're only interested in their fields of activity and the occasional discussions, contributing to information overload; 3. I think the patches are carried in only one of the web forum versions of our discussions http://koha-community.org/support/forums/ 4. usually the patches relate to a bug and email discussion isn't automatically attached to the bug report - I have started work to address this, but it's still going to have some delay between the discussion and posting to the bug report, which may mean the discussion is irrelevant by the time the bug is told; 5. most importantly, many topics are wider than a single patch, such as this one about what rich editor to adopt. Can we overcome these problems, or state clearly that wider-than-one-patch discussions should be on -devel? Thanks, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Past Koha Release Manager (2.0), LMS programmer, statistician, webmaster. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Hi, 2010/11/15 Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>:
This mailing list is an informational list to which commit descriptions for patches pushed to the public Koha Git repository (currently git://git.koha-community.org/koha.git) are posted.
To reiterate, I mispoke. I meant koha-patches, not koha-commits. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
participants (5)
-
Chris Cormack -
Galen Charlton -
Koustubha Kale -
Marcel de Rooy -
MJ Ray