[dev] [commits] Horde branch master updated. 90c599358555c7a2525feac0f0a4a0f7e626209e

[Michael M Slusarz]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Michael M Slusarz <slusarz at horde.org>:
>
>> Quoting Jan Schneider <jan at horde.org>:
>>
>>> Zitat von Michael M Slusarz <slusarz at horde.org>:
>>>
>>>> commit 3f022fd4e266e73e451eb22db410579bb921f2e7
>>>> Author: Michael M Slusarz <slusarz at horde.org>
>>>> Date:   Fri Aug 31 15:19:58 2012 -0600
>>>>
>>>>  [mms] Anchors appear before query string in URL output.
>>>>
>>>> framework/Url/lib/Horde/Url.php          |    6 +++---
>>>> framework/Url/package.xml                |    4 ++--
>>>> framework/Url/test/Horde/Url/AddTest.php |    6 +++---
>>>> framework/Url/test/Horde/Url/RawTest.php |    4 ++--
>>>> 4 files changed, 10 insertions(+), 10 deletions(-)
>>>>
>>>> http://git.horde.org/horde-git/-/commit/3f022fd4e266e73e451eb22db410579bb921f2e7
>>>
>>> Uhm, no. http://tools.ietf.org/html/rfc3986#appendix-A
>>
>> Well... the PHP documentation itself is wrong then.  And the jquery  
>> mobile documentation.  And this means we can't use Horde_Url in  
>> smartmobile view.
>
> If that's really somewhere in the PHP documentation, then yes, that  
> would be plain wrong.
>
> The JQM is not explicit about that, but using it correctly. In the  
> JQM examples, and in the way we already pass URLs around in the  
> smartmobile applications, the query parameters are *part of the the  
> anchors". Which makes sense, because in JQM, the anchor refers to a  
> page.
> Anyway, we indeed cannot use Horde_Url for building such URLs.

We still need some way of generating smartmobile URLs in PHP code  
though.  I've implemented this by extending Horde_Url in Core  
(Horde_Core_Url_Smartmobile).  Although I think it's best if we  
namespace all Smartmobile related classes under a single parent -  
'Smartmobile' - so this will be changed to Horde_Core_Smartmobile_Url.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]