Re: Bug 1852: support creation of xmpp: field types in OGo

Hi,
[email protected] wrote: 
> On Mar 25, 2007, at 18:29, Adam Williams wrote:
> > Problem is that URLs can actually get more tricky than one ever
> > initially suspects.  IMAPS is a good example.
> 
> I don't buy this. Either your client can parse a given URL or not. In  
> the latter case he should just tell the user.

at least konqueror does understand to handle links like this:
fish://[email protected]
imaps://[email protected]
and many more, due to its kioslaves, lots of browsers do not understand 
these types at all. Providing an easy way for the user to define custom 
protocol:userid values. My last patch is an approach to keep it as simple as 
possible but flexible as possible. Maybe that catches not all cases in 
a first place, but at least adds a lot of flexibility, up to the time 
someone comes up with something more sophisticated solution ;).

And yes, I think just the url type should be able to handle all kinds of 
protocol:// link url's, and not just only http: and https: 
http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1853
And I just realized that at least ftp:// and gopher:// urls are working fine 
with firefox, but not with konqueror, but unfortunately firefox does not 
handle the kioslave protocols like fish:// or imaps://.
but thats another story.

kind regards
Sebastian

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss