Export menu is a bit of a mess. (Mockups)

[Carl Simpson]

The menu items in the export menu are a bit ugly and hard to use, I think.
There's everything, all at once, and it's badly grouped and poorly labelled.

First, a note on terminology. "Export" is a bad word to use in menus. How
is "exporting" to Flickr related to "exporting" to another computer? How
are both of those related to the common practice of "exporting to PDF" or
"Exporting to HTML"?

When referring to putting data online with a web service, I recommend using
the verb "upload". When transferring data between physical entities like
computers and IM contacts, I recommend "send". iPods have always used the
word "sync".

Now, a note on things I didn't understand from what I saw, and so did not
include in these mockups.

What "Export to HTML" does I don't know. If it outputs an HTML document,
then I'd have a menu item that says "Embed into an HTML document…". If not,
you'll have to come up with something for it, if you like these ideas
othewise. I didn't include an entry for it in these mockups, because I
didn't want to suggest something silly, but it would probably go in after
"send to", since it appears not to have anything to do with transferring
files from one location to another, unlike all of the other options in this
menu.

Everything else is included in these mockups! Now, I only hope you like
them.

[Aurélien Gâteau]

Hi Carl,

Thanks for the time you spent on these mockups.

Post by Carl Simpson
The menu items in the export menu are a bit ugly and hard to use, I think.
There's everything, all at once, and it's badly grouped and poorly labelled.
First, a note on terminology. "Export" is a bad word to use in menus. How
is "exporting" to Flickr related to "exporting" to another computer? How
are both of those related to the common practice of "exporting to PDF" or
"Exporting to HTML"?
When referring to putting data online with a web service, I recommend using
the verb "upload". When transferring data between physical entities like
computers and IM contacts, I recommend "send". iPods have always used the
word "sync".

There is an important technical limitation you need to be aware of: the
Export menu is populated by plugins, which are shared between Gwenview,
digiKam and a few other applications. As such, Gwenview does not control
the content of the items which are going to be displayed in this menu.
This makes it difficult to implement the menu layout you suggest.

To get the labels of the plugins fixed, you need to contact the plugin
authors. You can reach them on the KDE Imaging mailing list, which you
can find here:

https://mail.kde.org/mailman/listinfo/kde-imaging

Post by Carl Simpson
Now, a note on things I didn't understand from what I saw, and so did not
include in these mockups.
What "Export to HTML" does I don't know. If it outputs an HTML document,
then I'd have a menu item that says "Embed into an HTML document…". If not,
you'll have to come up with something for it, if you like these ideas
othewise.

There is no such concept of "embedding" images in an HTML document. What
this plugin does is producing a set of HTML files which let you browse
through your images. You can then upload these files on a static web
server or burn them on a cd or dvd.


Regarding the simplification of the menu you propose with the "Set
default upload service" dialog: In an attempt to simplify
sharing/exporting contents, upcoming Gwenview (part of KDE SC 4.6) comes
with a "Share" toolbar button. You can learn more about it here:

http://agateau.wordpress.com/2010/11/19/easily-share-images-with-gwenview/

Aurélien

[Carl Simpson]

I appreciate the time taken to reply to this. When I can muster the energy,
I'll contact that mailing list you supplied with suggestions for plugin
names, to see if there's any agreement with my thoughts there.

The sharing toolbar button is cool, and I really like that "last used"
thing. Very clever idea.

In the meantime, if nothing else can be done, can't you at least display
them in alphabetical order? ^-^;;

Post by Aurélien Gâteau
Hi Carl,
Thanks for the time you spent on these mockups.

Post by Carl Simpson
The menu items in the export menu are a bit ugly and hard to use, I

think.

Post by Carl Simpson
There's everything, all at once, and it's badly grouped and poorly

labelled.

Post by Carl Simpson
First, a note on terminology. "Export" is a bad word to use in menus.

How

Post by Carl Simpson
is "exporting" to Flickr related to "exporting" to another computer? How
are both of those related to the common practice of "exporting to PDF" or
"Exporting to HTML"?
When referring to putting data online with a web service, I recommend

using

Post by Carl Simpson
the verb "upload". When transferring data between physical entities like
computers and IM contacts, I recommend "send". iPods have always used

the

Post by Carl Simpson
word "sync".

There is an important technical limitation you need to be aware of: the
Export menu is populated by plugins, which are shared between Gwenview,
digiKam and a few other applications. As such, Gwenview does not control
the content of the items which are going to be displayed in this menu.
This makes it difficult to implement the menu layout you suggest.
To get the labels of the plugins fixed, you need to contact the plugin
authors. You can reach them on the KDE Imaging mailing list, which you
https://mail.kde.org/mailman/listinfo/kde-imaging

Post by Carl Simpson
Now, a note on things I didn't understand from what I saw, and so did not
include in these mockups.
What "Export to HTML" does I don't know. If it outputs an HTML document,
then I'd have a menu item that says "Embed into an HTML document…". If

not,

Post by Carl Simpson
you'll have to come up with something for it, if you like these ideas
othewise.

There is no such concept of "embedding" images in an HTML document. What
this plugin does is producing a set of HTML files which let you browse
through your images. You can then upload these files on a static web
server or burn them on a cd or dvd.
Regarding the simplification of the menu you propose with the "Set
default upload service" dialog: In an attempt to simplify
sharing/exporting contents, upcoming Gwenview (part of KDE SC 4.6) comes
http://agateau.wordpress.com/2010/11/19/easily-share-images-with-gwenview/
Aurélien
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Gwenview-general mailing list
https://lists.sourceforge.net/lists/listinfo/gwenview-general

[a***@public.gmane.org]

Post by Carl Simpson
I appreciate the time taken to reply to this. When I can muster the
energy, I'll contact that mailing list you supplied with suggestions for
plugin names, to see if there's any agreement with my thoughts there.
The sharing toolbar button is cool, and I really like that "last used"
thing. Very clever idea.
In the meantime, if nothing else can be done, can't you at least display
them in alphabetical order? ^-^;;

Good point! Just implemented it. Should be in KDE SC 4.6.1.

Aurélien

[todd rme]

Post by a***@public.gmane.org

I appreciate the time taken to reply to this.  When I can muster the
energy, I'll contact that mailing list you supplied with suggestions for
plugin names, to see if there's any agreement with my thoughts there.
The sharing toolbar button is cool, and I really like that "last used"
thing.  Very clever idea.
In the meantime, if nothing else can be done, can't you at least display
them in alphabetical order?  ^-^;;

Good point! Just implemented it. Should be in KDE SC 4.6.1.
Aurélien

Personally I think it would be more convenient if they were all
converted to KIO slaves, but that would be more work.

-Todd

[Aurélien Gâteau]

Post by todd rme
Personally I think it would be more convenient if they were all
converted to KIO slaves, but that would be more work.

That would be quite nice, indeed.

Aurélien

[todd rme]

Post by Aurélien Gâteau

Post by todd rme
Personally I think it would be more convenient if they were all
converted to KIO slaves, but that would be more work.

That would be quite nice, indeed.
Aurélien

Would this be a good GSOC project? Port all the website kipi plugins
to kio slaves?

-Todd

[Aurélien Gâteau]

Post by todd rme

Post by Aurélien Gâteau

Post by todd rme
Personally I think it would be more convenient if they were all
converted to KIO slaves, but that would be more work.

That would be quite nice, indeed.
Aurélien

Would this be a good GSOC project? Port all the website kipi plugins
to kio slaves?

It would definitely be great, yes!

Aurélien

[todd rme]

Post by Aurélien Gâteau

Post by Aurélien Gâteau

Post by todd rme
Personally I think it would be more convenient if they were all
converted to KIO slaves, but that would be more work.

That would be quite nice, indeed.
Aurélien

Would this be a good GSOC project?  Port all the website kipi plugins
to kio slaves?

It would definitely be great, yes!
Aurélien

Do you know who would mentor it and how I could get in touch with
him/her/them? Or would you be the mentor?

-Todd

[Aurélien Gâteau]

Post by todd rme

Post by Aurélien Gâteau

Post by todd rme

Post by Aurélien Gâteau

Post by todd rme
Personally I think it would be more convenient if they were all
converted to KIO slaves, but that would be more work.

That would be quite nice, indeed.
Aurélien

Would this be a good GSOC project? Port all the website kipi plugins
to kio slaves?

It would definitely be great, yes!
Aurélien

Do you know who would mentor it and how I could get in touch with
him/her/them? Or would you be the mentor?

I am not the author of the export plugins so I can't be the mentor.

I suggest you contact the KIPI plugin developers on the kde-imaging mailing
list. Most of them are digiKam developers and the digiKam project has already
mentored a few GSoC students so they are used to it.

Aurélien