My idea is to develop a new (simple & flexible) comment / review system based as Akocomment on bot (is it the right solution?) functionality. So through a bot you can add text at the bottom of an article.

Despite of Akocomment my idea is to use completely all Joomla power such as using the ID user in the DB and all the "hooks" of the new 1.1 environment... but in this case for avoiding any delay or misunderstanding I need links or suggestions/tips for my work.

Anyone?

you should at first take a look at the developer wiki on dev.joomla.org (the big button on top of this page labeled Developers) There are all events listed that are used in Joomla and how to use the plugin system.

well, thanx very much for your reply but my intention was to receive a more specific tip for this specific feature. We know that Akocomment isn't developped by anyone and there is a "protected" licence upon it. My intention is to start developping a new comment/review system in 1.1 in GPL with a glimpe at the Akocomment experience...

But reading the dev pages I'm a bit confused about how to well move. I don't like (as everyone, I presume) to delay my goal so I think it is more appropriate to ask for tips or a dedicated link in dev pages to study carefully or in deeper way... The problem is the time (very little), as usual and I need to use it at the best.

If you are asking about what features you should implement, I like the features that the AkoComment component has but I'd like to see the "Write Comment" link to be underneath the "Read More >>" link. Also I think the enhancement someone else made for spam protection (with the generated image) is a good idea, and it would be good to incorporate that.



I find when I'm in a situation like that, I look at exising components/modules and try to figure out how they work and then slowly build up a skeleton just as proof of concept. Then, as I learn things I keep adding features. Ok, sometimes I have to backtrack when I see that I didn't plan ahead well enough but that's how I learn about these things.

I recently just built a component (to learn about component making) that just lists some joomla core parameters from $mainframe and some other objects and uses patTemplate and has a small admin section allowing the edititng of component parameters (which is pretty useless but still, practice). It doesn't have a database interface but that's for component.

The dev documentation is useful but I find looking through the actual code gets you into more advanced functionality. The problem is that the 1.1 code still has a lot of 1.0.x code lingering around and the use of the new features is not very consistent.

HTH

Thanx for the "feature request"and about your tip... if I well understand your one is that using the new 1.1 features isn't so much "necessary" as there are too many 1.0 codes or it is difficult to use the 1.1 code only... is it right?

So about the component I need to study a working component (simple with patTemplate) and the akoComment features. Thanx for your great tips about how to work and about the "skeleton process", I like very much!

well, about the proof component.... what component have I to study, in your opinion?

PS. I wonder if it is necessary a converter package from AkoComment DB...

He means that a lot of components still use 1.0 code and have not been refactored. At the moment, the most work has been done in regards to the API.

Thank you very much Hackwar for your clarification! Now it's very clear. Any tip from you? I have in the forge the project and I'd like to start... 

Yes, indeed I meant to say that the 1.1 component code is still using a lot of 1.0 constructs and calls.

In your case, since you have to write a plugin I'd suggest to look at some of the new 1.1 plugins and how they hook into the page rendering process. As far as component code goes, your AkoComment rewrite really only has to have a component admin so look at some of the existing admin components like com_banners. The front end will be rendered in your plugin code and I'd say you could keep quite a bit of the original code and just replace some of the old style calls to the API with new style code like getting request parameters (JRequest :: getVar( 'task' )), JTemplate for patTemplates, JText for internationalisation etc...

Also, if you can make your component so that it is able to use an existing AkoComment database, that would be great.

HTH,
Robert

A guide for plugins development is available on dev.joomla.org

I'm taking into great account the last 2 posts, about the guide and above all the clear tips for starting with the right step. I like the idea to "study" com_banners on the admin basis and about the AkoComment I think that I'll have a glimpe at that but I don't think to just rewrite the system...  My idea is to project a new comment system with some features, well known in AkoComment, inside it. So starting from a stable simple but complete version...

And about the spam comment risk, personally I don't like the image feature, it's difficult to read, it isn't an accessibility option, etc. IMHO it is important to have a wall against the spam but avoiding this confusing and ugly (graphicaly too) way of prevention. I have a revolutionary idea (but very simple) for that, never used before  but I am wondering if it is efficient or not...  (another problem, so).

About the DB, I'd like to maintain the same one but for hardening the system I need at least another field for ID user... I think that an "upgrade" way such as a converter package should be necessary 

But at the moment I need to have well in mind my first step:
study the plugins guide
study the com_banners (admin)
find out a simple plugin in 1.1 for studing, too (any tip?)
study the com_content for editing/pubblishing rights

And about the request parameters, if I well understand these are the most important for my project:
JRequest :: getVar( 'task' )
JTemplate for patTemplates
JText for internationalisation
... stop?

Instead of com_securityimages, you could try the image feature from "spamfix for akobook" (find it on google). It's more subtle and less obtrusive than com_securityimages.



...Or you could add afeature to import from akocomment.

Thanx a lot mjaz - I'll take yr tips into great consideration. At the moment I'm evaluating a lot of ideas... and I've already a project in mind but before developping I need to see a stable and unmodified joomla v. 1.5 (the new 1.1 renaming version)