Message: previous - next
Month: February 2014

Re: [trinity-devel] R: [trinity-devel] KXMLedit is MISSING from TDE - Slavek can you convert/add?

From: "E. Liddell" <ejlddll@...>
Date: Sun, 23 Feb 2014 07:28:53 -0500
On Sun, 23 Feb 2014 07:07:38 +0000 (GMT)
Michele Calgaro <michele.calgaro@...> wrote:

> Actually a good XML editor is a very useful tool and something that TDE has been lacking so far. KXMLEditor will fill that void.
> I favor David's suggestion. If I am looking for an editor I either look in "Editor" or "Development", but definitely it wouldn't come 
>natural to look into "File". If I can't the editor there, then I use the "menu search" field to locate where the editor was installed.
> Having all general editors (text, hex and XML) in the same menu (utilities -> editor) is a reasonable idea and given that the number 
>of editors is not that big, I don't see the "editor" menu becoming over busy.
> Other people opinions are welcomed too, since it seems there is a little of disagreement on this matter.

I think Development, rather than Editors, is likely the most appropriate place.
IMHO, Darrell is right about things like KHexEdit confusing non-technical
users (who may also not grasp how to rearrange the menu), but File is also
a rather odd location.  Also, if we throw that menu subsection open to
non-text editors, it starts to sound like it should also be the place for the
menu editor and image editors and video editors and . . . well, really,
where does it end?

Development, on the other hand, is one of the locations a technical person
will look in first for that sort of software, and a non-technical person will
probably ignore that submenu altogether.

Part of the problem is that "utilities" seems to have historically been used 
as a bit of a dumping ground category.  It might benefit from a close 
re-examination of exactly what's been filed there.  I just don't know if
now is the best time to do it.

With respect to the menu structure in general, we have three forces
pulling in different directions:  the desire to keep the menu logically 
arranged (where not everyone agrees on what's logical), the desire not
to overload any given menu, and the historical structure of the packages.
KHexEdit is exactly the type of application most likely to end up getting
used as a rope in that tug-of-war.  I'm less worried about KXMLEditor,
because it isn't part of a core package and isn't likely to be installed by
people who don't know what it's for.

As for Scribus--before we get too carried away, make sure that the last
QT3 version had fixed that weird bug where the mouse cursor and text in
the main work area didn't share the same positioning data.  That used to
make it almost unusable.

E. Liddell