[JDEV] browsing channels in a tree

[Katz, Dov (IT)]

If you're looking for a client-side only solution (i.e. a "hack") you
can just enforce a naming convention in the room names similar to a
folder structure, and the use your client to display things
hierarchically...

i.e.

Sales.marketing
Sales.salepoints
Development.technics
Development.products
Development.lab.informatic
Etc...

Then all you need to do is parse these out on '.' and render them in the
client using some tree widget...

Obviously not an elegant solution in the face of JEP65, etc... But this
can be implemented with relative ease and little effort, not to mention
no server-side changes.

All the best,
d

-----Original Message-----
From: David Sutton [mailto:jabber at dsutton.legend.uk.com] 
Sent: Friday, September 26, 2003 4:00 AM
To: jdev at jabber.org
Subject: Re: [JDEV] browsing channels in a tree


Hi there,

  Its easy to support, just interesting in how you'd set up such data.
If its a feature that people are 
wanting, then I can look into this.

Regards,

  David

On Fri, Sep 26, 2003 at 09:34:54AM +0200, Jacek Konieczny wrote:
> On Thu, Sep 25, 2003 at 05:02:56PM -0300, Nicolas Avila wrote:
> > Hi everybody:
> >     So....
> >     I'm developing a client wich should use no User's roster.
> >     It should get from the server only the channels wich the user is

> > allowed to join
> [...]
> >     if i want to group one organization's areas i would have a tree 
> > like home
> >     sales
> >         marketing
> >         salepoints
> >     development
> >         technics
> >         products
> >         lab
> >             informatic
> >             electronic
> >             mechanic
> >     administration
> >         financial
> >         human resources
> [..]
> >  
> >     so i would need each terminal node to be a groupchat
> >     idk if this kind of structure is supported by today's jabber
protocoll
> >     i suposse if it's not and if i't not planed to there would be a 
> > way to add this....
> 
> Such structure is supported by today's jabber protocol (this can be 
> done using disco or browse), but it isn't supported by any existing 
> groupchat/conference implementation (existing clients should have no 
> problem with this). But modification to eg. mu-conference component 
> would be versy easy.
> 
> Other solution would be to use roster with hierarchy extension 
> (defined by some JEP) to store channel list - this could be 
> implemented on the client side only.
> 
> Greets,
> 	Jacek
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev

-- 
David Sutton
Email: dsutton at legend.co.uk
Jabber: peregrine at legend.net.uk
_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev


--
NOTICE: If received in error, please destroy and notify sender.  Sender does not waive confidentiality or privilege, and use is prohibited.