The Joomla! People Portal ™

Hey, I think this extension do this job: http://extensions.joomla.org/extensions/news-production/content-submission/6260

I think this relates to the task at hand. Is there a reason that we need to be running SQL queries at all? Would it be possible to have a method which would take in an array of parameters and generate the underlying code appropriately? Meaning, inconsistencies of SQL implementation, other dialects (I see Doctrine refers to DQL), etc. For example, the code might work like this: $db = &JFactory::getDBO(); $db->setQuery(array("table" => "content", "category" => 10, "order" => "id")); and for example, in the implementation, if ($params["order"]) { $query .= "ORDER BY " . $params["order"]; } Just a thought.

What are the chances that we can discuss the overall direction we want to take Joomla in terms of thin/fat core *before* discussing whether a particular component should go in? IMO it would be better to leave this out of the core, keeping the installation package thin. Comments should be a core-team maintained extension, but not actually packaged with the core. The web developer would be able to install the comments extension in a click via the extension manager. Thoughts?

Hi Julio, I have developed an entity based workflow for one of my component. I adopt it from KnowledgeTree. I choose this type of workflow instead of Activity based as it is easier. I think we can start by this type of workflow. In this work flow we have an object (entity), this object has its state which will change a long the process. When an object stays in one state, it can transit from this state to one of available states. The transition defined with target state, and of course, transition guards. The transition guards are the trigger that will allow an object to make a transition or not. States 1 Draft 2. On Approval 3. Rejected 4. Cancelled 5. Published Transitions 1. Submit target: On Approval 2. Cancel target: Cancelled 3. Reject target: Rejected 4. Approve target: Published State Transitions (From state and transition) From State Transition Transition Guards [trigger] Draft Submit Owner Role Draft Cancel Owner Role On Approval Published Approver Role On Approval Rejected Approver Role On Approval Cancel Owner In my development, transition is action attach with toolbar button. The system will show available buttons to user depending on object state and user 's role (permission, object condition etc). Then user can click on desire button to bring object to desired state. The transition Guards are plugin in the system making it extensible. For each transition, all guards must be true to move on. All we have to do is to make a core api to be called by Joomla! extensions and a component used to manage workflow configurations.

Agreeing with @odino as usual, and want to add that distributing dead components with Joomla is also something that needs to stop. From com_content and all the way down to com_contacts… When I install Joomla, the step that takes the most time is uninstalling all the dead weight that comes with it.