auto-detection of the editing API - Movable Type (MT) is best
06-September-2005
-
Ecto-Api-Default
[ Download ]
(ecto-api-default.jpg
-
36.13 Kb
)
Preview
sigh...
Auto-detection of the edit API hads been a real pain for us. Clients differ in their behaviour.
And recently ecto, which used to auto-detect the preferred API and access-point for KNotes blogs, now fails. And blogjet, which used to fail, succeeds :O)
... we did not change anything I am aware of, so I suspect these are clientside changes :o{
ANYway, the worst part of not auto-detecting is that the user is not currently given a hint to specify the MT API (Movable Type). The MT API allows some clients - ed ecto - to edit the summary and extended text, pluys other goodies I think. Which makes for more useful content structuring from the editor. We're proud of the work we did implementing the serverside for the API for plone, and it did take work to support those neat MT extenseions - so this is frustrating :O)
So...
- If you are setting up remote editing for a KNotes blog, and auto-detection of preferences and API access-point does not work, please choose the MOvable Typ APi if given the choice.
- We should remember to have another look at the way we specify the MT as preferred API in our edituri text
- It seems likely that whatever is preveting ecto from noticing our preferred API might also be the culprit in preventing it from auto-detecting the API attachment
- Andin the meatnime we ought to add some text to the 'set up external editing' content to explain why the MT APi is better.
... of course, once KNotes becomes well-known by the developers of the clients, these problems start to become theirs as well as ours :O)
1 trackbacks.
- Latest trackback link:
- [Mike Malloch, KNotations], auto-detection of the editing API - Movable Type (MT) is best, 06-September-2005 08:36:31
auto-detection of the editing API - Movable Type (MT) is best
06-September-2005
-
Ecto-Api-Default
[ Download ]
(ecto-api-default.jpg
-
36.13 Kb
)
Preview
sigh...
Auto-detection of the edit API hads been a real pain for us. Clients differ in their behaviour.
And recently ecto, which used to auto-detect the preferred API and access-point for KNotes blogs, now fails. And blogjet, which used to fail, succeeds :O)
... we did not change anything I am aware of, so I suspect these are clientside changes :o{
ANYway, the worst part of not auto-detecting is that the user is not currently given a hint to specify the MT API (Movable Type). The MT API allows some clients - ed ecto - to edit the summary and extended text, pluys other goodies I think. Which makes for more useful content structuring from the editor. We're proud of the work we did implementing the serverside for the API for plone, and it did take work to support those neat MT extenseions - so this is frustrating :O)
So...
- If you are setting up remote editing for a KNotes blog, and auto-detection of preferences and API access-point does not work, please choose the MOvable Typ APi if given the choice.
- We should remember to have another look at the way we specify the MT as preferred API in our edituri text
- It seems likely that whatever is preveting ecto from noticing our preferred API might also be the culprit in preventing it from auto-detecting the API attachment
- Andin the meatnime we ought to add some text to the 'set up external editing' content to explain why the MT APi is better.
... of course, once KNotes becomes well-known by the developers of the clients, these problems start to become theirs as well as ours :O)
1 trackbacks.
- Latest trackback link:
- [Mike Malloch, KNotations], auto-detection of the editing API - Movable Type (MT) is best, 06-September-2005 08:36:31
){kind=link}