Subcategories Additions

[orware]

Wilco mentioned the subcategories additions on the Joomla.org article
about the recent dev summit and when I talked to him about it earlier
he mentioned that it was something that was already completed, it just
needed to be committed. Any additional word on this?

It's probably not the highest of priorities, but since I had done a
bit of work on this earlier in the year it is a topic I'm pretty
interested in and I would like to check out the implementation.

[Louis Landry]

It is entirely likely that this won't be added before the first alpha of 1.6.  It is something that will be done in concert with reworking com_content to be modern and consistent with the current way we are building extensions.  The implementation is using a nested set model with a pre-order tree traversal lookup method.  http://dev.mysql.com/tech-resources/articles/hierarchical-data.html is a great primer to thinking about how the data is stored.

- Louis

--
Development Coordinator
Joomla! ... because open source matters.
http://www.joomla.org

[Ercan Özkaya]

Is there any need for work in this area or is it completed? For the
last weeks I've been thinking about a base category component that
uses a hybrid model which is using nested sets primarily but also
keeps a parent field in the table so that it's still possible to use
adjacency model.

If needed, instead of writing it for 1.5 I can help for 1.6.

Ercan

On 27 Jan, 05:32, Louis Landry <louis.lan...@joomla.org> wrote:
> It is entirely likely that this won't be added before the first alpha of
> 1.6.  It is something that will be done in concert with reworking
> com_content to be modern and consistent with the current way we are building
> extensions.  The implementation is using a nested set model with a pre-order

> tree traversal lookup method.http://dev.mysql.com/tech-resources/articles/hierarchical-data.htmlis a

[Rob Schley]

Ercan,

That is actually how it works. The nested set model allows for fast traversal of the tree and proper ordering when pulling down the tree whereas the adjacency model allow for an easier to understand data-model. We have several implementations sitting around and we were just going to pull one and adapt it to com_categories. If you want to help out with that, I'm sure we can get you started with some code.

Best,

Rob

[Ercan Özkaya]

Sure Rob. It would be nice to have some code to work on if there is an
already written implementation. I'm gonna wait for your code and also
study a bit more about nested sets.

Thanks,
Ercan

On Jan 28, 1:25 am, Rob Schley <rob.sch...@community.joomla.org>
wrote:

> Ercan,
> That is actually how it works. The nested set model allows for fast
> traversal of the tree and proper ordering when pulling down the tree whereas
> the adjacency model allow for an easier to understand data-model. We have
> several implementations sitting around and we were just going to pull one
> and adapt it to com_categories. If you want to help out with that, I'm sure
> we can get you started with some code.
>
> Best,
> Rob
>

[orware]

Just some additional resources on this topic that have been mentioned
elsewhere:

Joe Celko's Trees and Hierarchies in SQL for Smarties (recommended by
Andrew on the jxtended forums):
http://www.amazon.com/Hierarchies-Smarties-Kaufmann-Management-Systems/dp/1558609202

http://www.dbmsmag.com/9603d06.html
http://threebit.net/tutorials/nestedset/tutorial1.html
http://en.wikipedia.org/wiki/Nested_set_model

In addition to the implementations in jxtended Magazine/Catalog,

-Omar

[Wilco Jansen]

Hi Omar,

Very nice!

Suggest that you indeed link to Rob, and see what the plans can be of making this one happen. Just can't wait ;-)

Regards, Wilco

[Ercan Özkaya]

Here is an idea for components to control their sections properly:

First our category component would implement default parameters like
maximum depth (defaults to unlimited) or delete behavior (deleting all
childs or promoting childs) etc.

Then if the current section starts with com_ (like com_weblinks), a
parameter group of that specific component (maybe called categories)
is merged into category parameters and stored in a helper class.

This would allow 3rd parties to use a flat category list if they want
as it's the case in 1.5 while it allows others to have more control
over com_categories.

Thoughts?

On Feb 4, 8:37 pm, Wilco Jansen <jansen.wi...@gmail.com> wrote:
> Hi Omar,
>
> Very nice!
>
> Suggest that you indeed link to Rob, and see what the plans can be of making
> this one happen. Just can't wait ;-)
>
> Regards, Wilco
>
> On Wed, Feb 4, 2009 at 6:02 PM, orware <orw...@gmail.com> wrote:
>
> > Just some additional resources on this topic that have been mentioned
> > elsewhere:
>
> > Joe Celko's Trees and Hierarchies in SQL for Smarties (recommended by
> > Andrew on the jxtended forums):
>

> >http://www.amazon.com/Hierarchies-Smarties-Kaufmann-Management-System...

[Hannes Papenberg]

Hi guys,
I've started with an implementation for this myself. I'm removing
sections altogether and adding some of the work Enno did in the GSoC
2007 for hardlinked, nested sets. Currently I have the table scheme
changed and the sample data fixed. Also, com_content currently shows the
basic stuff again, without the section view. I've got an idea on how to
manage the URLs and com_categories presents you with a nice view of the
categories. I hope to get the big issues straigthened out till friday,
as well as branching the common functions into a library. Hopefully I
will be able to fix the smaller stuff over the weekend and also refactor
the other components using categories.

I'll share that code as soon as I feel confident to make it public. Stay
tuned here on this channel... ;-)

Hannes

Ercan Özkaya schrieb: