Geshi Plugin

[George Wilson]

Hey guys,

There was a question asked on the Joomla SO a few days ago about the Geshi Plugin (http://joomla.stackexchange.com/questions/631/geshi-shows-no-syntax-colors-with-joomla-3-3). I know when we removed it from core we committed to maintaining it standalone for the rest of the J3.x series. However I can't find it anywhere in order to try and test it (tried main Joomla, joomla extensions + joomla projects repo's on github)

Anyone know what happened to it. Or if the fact it was supposed to be supported has ended?

Kind Regards,

George

[Matt Thomas]

Hi George,

I'm on mobile ATM and can't check, but there may be clues at https://groups.google.com/forum/m/?hl=en-GB#!searchin/joomla-dev-cms/Removing$20geshi/joomla-dev-cms/LGTn46SotMM

Hope that helps!

Matt Thomas
203.632.9322
http://betweenbrain.com/

Sent from mobile. Please pardon any typos or brevity.

--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
To post to this group, send email to joomla-...@googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.

[Nick Savov]

Hi George,

Unfortunately, it's not being maintained anywhere in Joomla as far as I'm
aware.

If you want to test out what that user is experiencing, grab a copy of
Joomla 3.0 then update it to Joomla 3.3. That's probably the quickest
method.

Kind regards,
Nick

> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! CMS Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to joomla-dev-cm...@googlegroups.com.

> To post to this group, send an email to joomla-...@googlegroups.com.

[Leo Lammerink]

Nick, it's not unfortunately..... It was left with very good reasons...
One for sure hardly anybody knew what it was doing (I did not know for a
long time for instance) nor did any ( and I say 'any !') of our clients
as we are aware of and we had only ("") a few ... (7.5 K over past
years) I honestly stil don't know exactly what this was suppose to do
after 14 years Joomla but that says probably more about me than the
plugin (?) - no need to answer that: "rhetoric" - ;)

Leo

[Nick Savov]

"Unfortunately" for that user. You're right though, hardly anyone used it
or knew how to use it :)

Cheers,
Nick

[Level Ten Solutions]

Best Regards
M M Rahman Maqsood

Creator of GoReserva: http://hotelbookingsoft.com/

[George Wilson]

But at the same time it was halfway through the 3.x series and if you read the tracker it went with the promise we'd maintain it for the rest of 3.x (for b/c if nothing else).

Anyhow thanks for the update Nick - useful to know anyhow

Kind Regards,

George

[Nick Savov]

Looks like Rouven was going to maintain it independently:
https://github.com/realityking/Joomla-GeSHi

I'd say report the issue in there and call him up on the offer :)

Kind regards,
Nick

>> >> email to joomla-dev-cm...@googlegroups.com <javascript:>.

>> >> To post to this group, send an email to

>> joomla-...@googlegroups.com<javascript:>.

[Rouven Weßling]

I've been summoned?

Note that this repository was a proof of concept, that the GeSHi plug-in can easily be extraced, back when I proposed removing it from Joomla. There used to be an (empty) repository in the joomla organization where it was supposed to end up in, unfortunately I as the 3.0 release dragged out I became too busy to keep up and couldn't do it anymore.

If there's an interest from the project to maintain it I'd be happy to help setting up the repository with a subsplit, but I don't have the bandwidth for ongoing maintenance.

Best regards

Rouven

[George Wilson]

On Friday, May 16, 2014 4:39:34 PM UTC+1, Rouven Weßling wrote:

I've been summoned?

Haha sorry :P

 

Note that this repository was a proof of concept, that the GeSHi plug-in can easily be extracted, back when I proposed removing it from Joomla. There used to be an (empty) repository in the joomla organization where it was supposed to end up in, unfortunately I as the 3.0 release dragged out I became too busy to keep up and couldn't do it anymore.

I dunno if there's interest per say :P It was just because I came across the stackexchange thing I was wondering. It may even be a bug in his system - I dunno. I just couldn't find much about what we'd planned to do with it 

 

If there's an interest from the project to maintain it I'd be happy to help setting up the repository with a subsplit, but I don't have the bandwidth for ongoing maintenance.

Or maybe in the joomla-extensions repo? I dunno. It depends if the PLT want to maintain it I guess for the 3.x series?

Thanks for posting anyhow Rouven :)

Kind Regards,

George

[Michael Babker]

It can easily be dumped into the extensions repo.  If there's folks interested in maintaining and using it, it isn't that difficult to get it installable or add maintainers.

--

You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.

To post to this group, send email to joomla-...@googlegroups.com.

Visit this group at http://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.

--
- Michael

Please pardon any errors, this message was sent from my iPhone.

[Leo Lammerink]

As mentioned before and multiple times confirmed (also by PLT-members!).... Who cares about Geshi/GeSHi (however you write it?) Nobody (general Joomla users)  knows its functionality or needs it  so let's please drop it for once and for all?

Complete waste of efforts

Leo

[George Wilson]

But if it was removed in the 3.x series then for b/c we should maintain it. As was even specified in the tracker. Everyone keeps moaning about how we loose users. How are we supposed to keep users when we keep throwing users out by saying "only the majority do x"

Frankly I've never used Geshi nor do I plan to in my own projects. But it's about maintaining Joomla's image.

--
You received this message because you are subscribed to a topic in the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/joomla-dev-cms/k7g9b3Yi68Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to joomla-dev-cm...@googlegroups.com.

[Matt Thomas]

I agree with George that it's the right thing to do and we can facilitate that happening. It will take those that care about Geshi to come forward to help maintain it, but let's at least give them that chance.

Best,

Matt Thomas

203.632.9322
http://betweenbrain.com/

[Sergio Manzi]

I agree that b/c is very important, but what if seldom used (and probably rarely updated) extensions were unbundled from the main distribution and made available in an "add-on package"?

[piotr_cz]

What about using CodeMirror in read-only mode?

To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cms+unsubscribe@googlegroups.com.
To post to this group, send email to joomla-dev-cms@googlegroups.com.

[Sergio Manzi]

Sorry, but I'm afraid I don't get your sense of humor...

On 2014-05-16 22:42, piotr_cz wrote:

[Nikolai Plath]

I don't think that this was a joke... actually, like piotr_cz, I was also thinking about CodeMirror as an alternative to Geshi. Makes perfect sense, and I believe that people in need of code highlighting already have found their solution...

What I really would like to see is that extensions like Geshi, CodeMirror etc. which are clearly optional, are maintained in separate repositories and are then merged as a complete package when it's time for a release.

I think if more extensions would be separated and maintained **officially**, there would be people willing to maintain those.
The com_weblinks component is a good start, but I think there should be some more promotion.
Maybe also include com_banners...

Please create as much official repositories as possible and strip out extensions that have no or few "dependencies"

Regards,
Nikolai

[Sergio Manzi]

Hi Nikolai! I totally agree with you, and the two extensions you
mentioned are exactly the ones I was thinking of. Personally I never
used com_contact neither, so as far as regards myself, that too could be
unbundled, but I really don't know if it is too much integrated with the
CMS to be easily feasible. Anyway, the idea of a lightweight Joomla!
without all the fuss is something I really like.

As far as taking Piotr words as a joke, maybe I've misunderstood, but I
was thinking he was joking when he talked about using Codemirror in
"read-only mode", which doesn't makes much sense for an "editor". It
comes to my mind, now, that maybe he was thinking about just having the
highlighting features of Codemirror, without its (innervating)
auto-complete feature. I apologize if I misunderstood!

O.T., but personally I always use "Editor: none" and if I need to check
syntax, with highlighting, I copy-paste to Notepad++

Regards,
Sergio

[Nikolai Plath]

Hi Sergio,
well that's what Geshi is about: "A syntax highlighting library thingy".
It's not an editor, so the idea would be to use only the syntax
highlighting feature from CodeMirror as a replacement since it is
currently included in the Joomla! CMS.

A little off topic.. I did an editor plugin a while back that integrates
the EditArea editor. The page is in german but the code speaks for
itself ;)
http://www.joomla-wiki.de/dokumentation/Joomla!_Programmierung/Programmierung/Plugins/Editoren

More On topic, I think once we set up a build system and several
extension repositories, things will get clearer so a BIG :+1: @wilsonge
for bringing this up ;)

[jms]

For B/C reasons, Geshi is not deleted when updating Joomla! as you can see in
ROOT/administrator/components/com_admin/script.php

For the same reason, we decided to keep its language strings in the French language pack. I have not tested all packs for them.

The problem of "decoupling extensions" (see Weblinks debate) can't really be solved until a formal decision is taken by PLT/OSM on a firm policy.

2 solutions:

1. They are fully considered as "Core supported" and therefore their packs have to be presented at J install time as Optional installs, —NOT as a category in JED as proposed somewhere else— because new users would not know they exist and it would only fit the loud supporters of a "small Joomla", not the majority of Joomla users.
If updated, they should show in the extension Update.
The packs should contain ALL core languages files (or, as we have issues with that right now, the language files should be kept in core and core lang packs).

2. Core does not formally support them, but only volunteers (including for translation). Core TTs stop adding the lang files in their core packs. They are proposed wherever it is decided. They basically become 3pd extensions… Not B/C.

If solution 2 is decided, then it should only be done in 4.0 imho.

A decision has also to be taken concerning what should be "decoupled", after a discussion.

regards
JM

[Sergio Manzi]

As I *think* (but I can be really wrong) that Joomla! 4 will not happen
any day soon, you have a +1 vote from me for an interim "solution 1",
but, as you stated, a broader discussion is needed and maybe a new topic
should be opened focused on the possibility of a "lightweight/small
Joomla! CMS + Joomla! extension pack(s)".
Probably the PLT should "sponsor" such a discussion and possibly use 3.5
(or even 3.4...) as the target revision for this "unbundling".

As far as language packs regards, I think they should follow the
organization of the CMS, i.e. a "core language pack" + one (or several)
"extension language pack(s) "

I agree that those extension language pack(s) should be offered together
the core pack and not in the JED. I'm still not sure if it would be
preferable to have a monolitic extension pack containing all the
extensions unbundled from the core or several extension packs, one for
each unbundled extension.

Sergio

On 2014-05-17 09:26, jms wrote:
> For B/C reasons, Geshi is not deleted when updating Joomla! as you can see in
> ROOT/administrator/components/com_admin/script.php
>
> For the same reason, we decided to keep its language strings in the French language pack. I have not tested all packs for them.
>
> The problem of "decoupling extensions" (see Weblinks debate) can't really be solved until a formal decision is taken by PLT/OSM on a firm policy.
>
> 2 solutions:
>

> 1. They are fully considered as "Core supported" and therefore their packs have to be presented at J install time as Optional installs, --NOT as a category in JED as proposed somewhere else-- because new users would not know they exist and it would only fit the loud supporters of a "small Joomla", not the majority of Joomla users.

> If updated, they should show in the extension Update.
> The packs should contain ALL core languages files (or, as we have issues with that right now, the language files should be kept in core and core lang packs).
>

> 2. Core does not formally support them, but only volunteers (including for translation). Core TTs stop adding the lang files in their core packs. They are proposed wherever it is decided. They basically become 3pd extensions... Not B/C.

[Sergio Manzi]

Errata corrige:

"I agree that those extension language pack(s)..."

[Matt Thomas]

For anyone interested in continuing the conversation about a slim core and decoupling extensions, there is a Distribution Working Group, located at
https://github.com/joomla-cms/start-here, open to everyone. There has been quite a few good conversations there already. Hope to see you there.

Best,

Matt Thomas
203.632.9322
http://betweenbrain.com/

Sent from mobile. Please pardon any typos or brevity.

--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.

To post to this group, send an email to joomla-...@googlegroups.com.

[Sergio Manzi]

That's perfect, Matt!

See you there! (just let me the time to read what has already been
told...) :-)

Regards,
Sergio

[Sergio Manzi]

Actually... there is *a lot* to read there and some very different "philosophical attitudes", from the "let's just get rid of what is obsolete and/or rarely used" and have this delivered quickly (something I'm inclined to favor) to more radical stances like "let's have different distributions, from a minimal, tiny, one devoid of even com_content and com_users to a plenty-of-things one (and while we are that let's also revamp the installer)".

I think I have to make my mind up...

[George Wilson]

So back to original subject RE: Geshi can we have a PLT decision about whether we should bung it into the joomla-extensions repo to continue support as in the tracker?

Kind Regards,

George

--
You received this message because you are subscribed to a topic in the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/joomla-dev-cms/k7g9b3Yi68Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to joomla-dev-cm...@googlegroups.com.

To post to this group, send email to joomla-...@googlegroups.com.

[piotr_cz]

http://codemirror.net/doc/manual.html#option_readOnly

It may not be as lightweight as geshi, but it's actively maintained and already available in Joomla for some time.

[Sergio Manzi]

Hello Piotr,

first of all, again my apologies for having misunderstood your statement as a joke.

I've never used Geshi, but, as I see it, it is a syntax highlighter plugin to be used together with "Editor: none".

On the other hand, Codemirror (which I used for a while) is an editor itself, but, according to the documentation you pointed to, when used in readOnly mode becomes a "lister" with syntax highlighting (readOnly: This disables editing of the editor content by the user). I fail to see how this can be useful in the context of editing Joomla! content.

Regards,
Sergio

[Rouven Weßling]

> Am 17.05.2014 um 23:28 schrieb Sergio Manzi <s...@smz.it>:
>
> I've never used Geshi, but, as I see it, it is a syntax highlighter plugin to be used together with "Editor: none".

That's incorrect. The Joomla GeSHi plug-in is used to to format code snippets inside articles or other content, it has nothing to do with editing.

This is also the reason many people wanted to see it leave the main repository, it's only useful for a small subset of Joomla sites.

Best regards
Rouven

[Sergio Manzi]

OMG! I was *badly* wrong! Sorry to everybody... :-(

[Matt Thomas]

https://github.com/joomla-extensions/Joomla-GeSHi :-)

It's future now depends on Pull Requests.

Best,

Matt Thomas

203.632.9322
http://betweenbrain.com/

[jms]

Please take example on the languagecode system plugin concerning language files.
You need an en-GB folder inside the language folder and changes in the xml to fit

Also, this does not solve the languages issue as discussed in the weblinks thread.
Would Geshi be a "core supported" extension or not?

Regards

JM

> --
> You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.

[Bakual]

I'd prefer the term "community supported" :)

[Matt Thomas]

What you currently find at https://github.com/joomla-extensions/Joomla-GeSHi is a forked copy of what Rouven was maintaining. The code hasn't been touched since Sept 7, 2012. I'm not sure what you mean by core supported, but this repo was created to allow members of the community the opportunity to maintain this extension that was removed from core. Time will tell the level of interest there is in maintaining it.

Best,

Matt Thomas
203.632.9322
http://betweenbrain.com/

Sent from mobile. Please pardon any typos or brevity.

I'd prefer the term "community supported" :)