[dev] Fwd: Re: AJAX Framework changes

[Ralf Lang]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I hate to bring this up again, but I think there *is* a break here
> that would prevent current x.0 applications from working correctly
> on 4.1. For instance, I just tried to use my local Hermes install,
> I am now completely unable to get it to load the dynamic view
> because it is still looking for the 'mode' session setting that was
> removed/changed for 4.1. This is exactly the type of issue I was
> trying to avoid by moving the view determination out of the
> application's scope into Core. Yes, Hermes isn't yet released for
> H4, but the method it used for determining the view to load is
> identical to the method Kronolith and Imp used.
> 
> There is also the loss of functionality I described in my other
> email regarding the ability to explicitly ask for the traditional
> vs dynamic view for each application, but that discussion I'll
> leave for the other thread.
> 
> These type of changes, IMO, should require a major version bump.

It may sound naive but isn't there a feasible way to make pre-4.1
applications use their ways and methods of determining ajax or not
independently of 4.1 added features / changed
"classic"/default/now-standard way of displaying menu?

It doesn't matter much to me personally because we won't use horde 4.1
without upgrading the official apps. If something proprietary break,
well, this might sell support contracts.

Pre 4.1 ajax apps assume that all 4.0 methods they use are still in
place (although they might be deprecated and issue warnings), and do
something which is equivalent at least I think.



- -- 
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang at b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8sRI8ACgkQCs1dsHJ/X7Df7QCglhtzPDR+3XjekJt1IakNNL05
xYIAn1p9tGhBXKEGU51D6El806vfu8tO
=3HwL
-----END PGP SIGNATURE-----