×

Notice

The forum is in read only mode.
Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: [SOLVED] CComment support for component Seblod CCK

[SOLVED] CComment support for component Seblod CCK 11 years 6 months ago #20860

  • Gerhard Sitzmann
  • Gerhard Sitzmann's Avatar Topic Author
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 41
  • Thank you received: 0
Hello,

I have downloaded and installed the free version 5.0rc1 of your comment system and I really like it so far.

Only problem is, that I develop most of my projects with Seblod CCK and I cannot find Seblod in the list of supported extensions.

I made a test-install of ccomments on a J!3.1.1 site with Seblod CCK latest version. Unfortunately ccomment doesn't work with Seblod content items.

Is there a way to get this to work or are you planning to offer Seblod CCK integration?

I would be more than happy to buy a subscription and use your component in future projects if it will support Seblod.

CComment support for component Seblod CCK 11 years 6 months ago #20867

  • Gerhard Sitzmann
  • Gerhard Sitzmann's Avatar Topic Author
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 41
  • Thank you received: 0
Ok, I found out that ccoment relies on Mootools. I had Mootools deactivated for my template because I mostly work with JQuery. Also J!3.5 will rely on JQuery and Mootools will be deprecated.

You might want to think about redesigning your extension with that in mind.

CComment support for component Seblod CCK 11 years 5 months ago #20868

  • Daniel Dimitrov
  • Daniel Dimitrov's Avatar
  • Away
  • Administrator
  • Administrator
  • Posts: 9618
  • Karma: 155
  • Thank you received: 1081
Hey Gerhard,
I'm not the expert on Seblod, but it should work. Seblod uses the default jos_content table and our content plugin should work as expected event with the core version. Do you get any error?
The following user(s) said Thank You: Gerhard Sitzmann

CComment support for component Seblod CCK 11 years 5 months ago #20872

  • Daniel Dimitrov
  • Daniel Dimitrov's Avatar
  • Away
  • Administrator
  • Administrator
  • Posts: 9618
  • Karma: 155
  • Thank you received: 1081
I posted with out seeing your previous comment.

I've been thinking about this for the last couple of years. I think that the first few paragraphs from here sums it pretty well:
jqueryvsmootools.com/

The Mottos Say It All

If you go to the jQuery site, here's what it says at the top of the page:

jQuery is a fast and concise JavaScript Library that simplifies HTML document traversing, event handling, animating, and Ajax interactions for rapid web development. jQuery is designed to change the way that you write JavaScript.

...and if you go to MooTools, this is what you'll find:

MooTools is a compact, modular, Object-Oriented JavaScript framework designed for the intermediate to advanced JavaScript developer. It allows you to write powerful, flexible, and cross-browser code with its elegant, well documented, and coherent API.

I think this really sums it up. If you ask me (and you're reading this, so I'll assume you just have), the question isn't about which framework is better or worse. It's which one of these things above do you want to do? These two frameworks just aren't trying to do the same things. They overlap in the functionality they provide, but they are not trying to do the same things.

jQuery's description of itself talks about HTML, events, animations, Ajax, and web development. MooTools talks about object oriented-ness and writing powerful and flexible code. jQuery aspires to "change the way you write JavaScript" while MooTools is designed for the intermediate to advanced JavaScript developer.

Part of this consideration is the notion of a framework vs a toolkit. MooTools is a framework that attempts to implement JavaScript as it should be (according to MooTools' authors). The aim is to implement an API that feels like JavaScript and enhances everything; not just the DOM. jQuery is a toolkit that gives you an easy to use collection of methods in a self-contained system designed to make the DOM itself more pleasant. It just so happens that the DOM is where most people focus their effort when writing JavaScript, so in many cases, jQuery is all you need.

Most of the code you write when you write MooTools still feels like JavaScript. If you aren't interested in JavaScript as a language, then learning MooTools is going to feel like a chore. If you are interested in JavaScript and what makes it interesting, powerful, and expressive, then, personally, I think MooTools is the better choice.


That is why I'm not sure that I'll move to jquery, but we'll see :)

Cheers,
Daniel
The following user(s) said Thank You: Gerhard Sitzmann

CComment support for component Seblod CCK 11 years 5 months ago #20874

  • Gerhard Sitzmann
  • Gerhard Sitzmann's Avatar Topic Author
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 41
  • Thank you received: 0
Hi Daniel,

this is quite interesting, indeed.

I am not generally against Mootools.

But since the J! dev team has decided to move to JQuery, I want to be able to use J! without Mootools dependencies in future. Loading two JS libraries slows down page load and should be avoided where possible.

Have a nice day
gerhard

CComment support for component Seblod CCK 11 years 5 months ago #20883

  • Gerhard Sitzmann
  • Gerhard Sitzmann's Avatar Topic Author
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 41
  • Thank you received: 0
Hi Daniel,

I found out that ccomment is only working with Seblod when I set the on content prepare option to Yes and include {ccomment on} in all articles.

If I want to use it with the onContentAfterDisplay function, it doesn't work.

Do you have any idea, why this is happening?

CComment support for component Seblod CCK 11 years 5 months ago #20896

  • Daniel Dimitrov
  • Daniel Dimitrov's Avatar
  • Away
  • Administrator
  • Administrator
  • Posts: 9618
  • Karma: 155
  • Thank you received: 1081
Can I get access to your site?

CComment support for component Seblod CCK 11 years 5 months ago #20905

  • Gerhard Sitzmann
  • Gerhard Sitzmann's Avatar Topic Author
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 41
  • Thank you received: 0
Thank you for taking a look into this.

I don't see how I can PM you in the forum.

Where can I send the access details to?

[SOLVED]CComment support for component Seblod CCK 11 years 5 months ago #20954

  • Gerhard Sitzmann
  • Gerhard Sitzmann's Avatar Topic Author
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 41
  • Thank you received: 0

Gerhard Sitzmann wrote: Hi Daniel,
I found out that ccomment is only working with Seblod when I set the on content prepare option to Yes and include {ccomment on} in all articles.

If I want to use it with the onContentAfterDisplay function, it doesn't work.


Now I found that this was related to my custom template. I forgot to include
<?php echo $this->item->event->afterDisplayContent; ?>
into my template.

Now Ccomment is working fine with SEBLOD :-)

[SOLVED]CComment support for component Seblod CCK 11 years 5 months ago #20958

  • Daniel Dimitrov
  • Daniel Dimitrov's Avatar
  • Away
  • Administrator
  • Administrator
  • Posts: 9618
  • Karma: 155
  • Thank you received: 1081
That is awesome! Glad you've sorted it out and that makes one more component that ccomment works with.
  • Page:
  • 1
Time to create page: 0.172 seconds