Dizkus

Hi there,
First I'm sorry for my English, because I'm from Poland :D
I write comment module based on Ns-Comments.
Now I rename this module for Comments Ex. Instalation is very easy - only replace files in modules/Ns-Comments or modules/Comments. This module is better at EZComments. Why?
:arrow: Template engine for modyfication comment design
:arrow: Reply to comments now is not a link, but now is comment with blockquote
:arrow: Better permission system
:arrow: Quick reply form on bottom comments
:arrow: Avatars with nick and other info in comment (compatible with Avatar 1.0 module)
:arrow: I deleted not important inputs in top (sort, moderating etc)
:arrow: Only admin can write comment with HTML, user cant usign tags (but I will add bbcode hack)
:arrow: Instalation is very easy (replace files) and this module is fully compatible with table nuke_comments
:arrow: And much more
Newest version is RC2 (beta), but I ended finally version and later I will write version 2.0 for PostNuke 0.8
This module is better at EZComments, so this module can be a standard comment module in PostNuke 0.8.
This is demo in my site:
http://www.underflip.pl/Bag-Of-Suck-nowy-film-Enjoia-id176.html
This is download link:
http://post-nuke.pl/modules.php?op=modload&name=Downloads&file=index&req=getit&lid=2260
This is support topic:
http://post-nuke.pl/index.php?module=pnForum&func=viewtopic&topic=10426&highlight=Ns-Comments%20Ex

I will make a support page (www.ex.bilsoftware.com) in english language.

I'm waiting for You comments :)

OH NOOOOOOOOOOOOOOOOOOOOOOOOOO,

I think you better search the Internet before doing much work for nothing.

If you download the last version of EZComments from the cvs you can see that these things are always in.

Sorry, but therefor I don't have understanding.

... and I think your modul will never come into .8 as standard

--
Petzi-Juist :: ... welcome to my digital world ...

It's true - I haven't new version EZComments (but I saw this), but EZComments have hard instalation and Ez must convert database. My module is fully compatible :) If any user have standard Ns-Comments and much comments module and he allow guest commenting, then convert guest comments to EZComments replaced admin name. This is stupid. EZComments instalation is very stupid. And if any user have much comments then he can very easy upgrade comment module with old comments (and guest comments).

First test this module.

not realy,...
just upload, regenerate, activate the modul...
and activate it for the module you want to use...
no problem.

--
Petzi-Juist :: ... welcome to my digital world ...

Sorry to say this but PostNuke will drop the comments module in favor of EZComments.

The release of yet another Comments module does not help much to improve PostNuke...

--
Teamwork is everyone doing what I say.
Final Fantasy Corner

I don't see it being a waste of time, it's good to have choice and I'm sure each module will accept a different line of feature requests to appease different needs.

However, PostNuke has announced EZComments as the standard comments module for .8 in the Road Map allready.

--
Under Construction!

And we have EMPTY comments module with not comments counter in news template
Why user must editing news module files and convert comments? :twisted:

I know. Standard Ns-Comments module is silly, but I refresh this project :) EZComments isn't standard module in PN 0.750 and 0.761 and olders.

I do see this as a waste of time.

Instead of helping to improve a existing module everyone is reinventing the wheel. It's not only this additional comments module but also so many others.
If you need a example just take a look into the NOC and count the xinha editors that are developed at this moment.

Then ask yourself the following questions:
How many of them will be discontinued and dropped in the near future?
How much developer time has been wasted? ...


Diversity and the ability to chose between different solutions for a problem are nice concepts but at the moment PostNuke needs to gather more speed in its development if it does not want to loose the race against other opensource CMS.

You can't gain speed by spending ressources on the development of several almost identical soloutions for ONE problem...


Even much larger opensource CMS with a long history of "one customer, one special solution" development have have changed their attitude and started major colaboration and concentration efforts.

--
Teamwork is everyone doing what I say.
Final Fantasy Corner

Silly post. You don't understand. Where is future? WHERE? PostNuke 0.8 is only PostNuke 0.761 with better Xanthia and modules not from PostNuke authors. This is ... no comment. Future will be a new engine and better modules. PN 0.8 is in PAST. Where are all announced news? Nothing new...
You all waste of time, in place of develop PostNuke you are adding to PN 0.8 old modules.
Probably I finish at PostNuke and convert site to my CMS or Xaraya, because PostNuke, thank you, "developers", stay in space. Regards :]
There is no other comment modules apart from EZComments and Ns-Comments, therefore you don't tell me, that this haven't any sense.

LOL your sig on that post is amusing... I definatly see your point with the NOC

--
Under Construction!

hmm this was in response to Chasms last post, missed BatSk8 post. But in response to that...

I'm sorry that you don't understand PostNuke that well to be citing .8 as .76 with third party mods (makes me question your understanding of opensource actually), but considering your limited amount of postings, your constant reference to NS- anything (any PN with NS mods is considered insecure and in need of upgrading), and your reference to the devs as out in space, I don't really see you qualified to comment on it's future.

--
Under Construction!

My intention was to show you comment module, but now I see you reaction :)

Best regards and goodbye :)

edit
I understand this, but my seeing point is: PostNuke is developing back. Thats all.

Presenting a new module by bashing another one without even knowing it's current state of development seems to be a strange concept as far as my opinion is concerned.

The project needs more developers but it needs even more and better colaboration than it has now.
There are way to many double, triple maybe even quadrupel projects at the NOC - an nobody knows how many additional double projects are developed outside the NOC.

Way to much effort is put into the implementation of the very same functions by different groups.
What does this mean?
Large amounts of developer time are wasted by implemeting the same things twice or even more often.
It becomes less likely that the development goals are reached.
It becomes more likely that the development of one or more of the additional implementations is canceled. (ie, other implementations are better, other implementations get choosen to become core or near core modules)
Consequently it also becomes more likely that the developer of a discontinued module leaves the project.

Nobody wants that - but still it happens.

The only way to change this is at the very beginning of the process. Stop re-inventing things and start to coperate with those that are already working on a solution.

--
Teamwork is everyone doing what I say.
Final Fantasy Corner

alot easier said than done. . .

i applaud the efforts, as redundant and counter productive as they might seem, it is srill efforts, and i feel if it helps one person, a module serves its purpose.

This is an interesting question which you are not quite able to substantiate right now. The points you mentioned in favour of your module show that you do not know the recent version of EZComments at all. It has almost everything you mentioned plus a lot more.

And in addition its not very clever to get on the scene out of the blue saying that your module is better than a competetive product. You should let the users decide this. Some will like your comments module, some won't. EZComments is designed to replace the original Comments module in future versions of PN so for us the decision is easy.

BTW, virtual your module is a hack - it replaces a core module using its database structure. Doing this means the user needs to take care when updating his PostNuke installation.

Frank

--
"He is not dangerous, he just wants to play...."