The short of it is that the client wants less clicks to upload, add text, and save an image.
Images have a caption and credit fields. Here is what the client is experiencing starting from the content node:
1. Click Create
2. click browse
3. search computer files for desired photo
4. click photo to populate “Choose file” and “name” fields
5. click a “parent” where to store the photo
6. click “create”
7. click “select” to add it to the post
8. click “edit”
9. add caption info
10. add credit info
11. click "save icon” to save caption and credit
12. click save and publish icon to post.
I've gone through and this is exactly what needs to happen. The default media type is already set to Image. There is no getting around this. But the client wants to reduce this by 5 clicks.
Me immediate thought is to hack DAMP or add some js to trigger some clicks here and there....
Here is all I can think of but it's really hacky.
Since DAMP is in an an iframe in an Umbraco modal div I'm thinking of the following:
Hmm it's hard to reduce clicks. If the user wouldn't have to add extra info that would already reduce it, but I can understand that won't work unless the caption and credit info is on the content node instead of the media node. I don't use the creat option of DAMP a lot. Instead I use a custom version of the Multiple File Upload package. I first create all media in the media section and than use DAMP to select it.
Yeah there's not really a way to streamline this. They will be uploading a dozen articles per day with any number of images. The media tree is going to get huge very quickly...so finding the images after they upload them may be more hassle for them.
Do you think triggering those clicks using js is an ok idea? Personally I think it's a bit hacky but I cant really think of anything else.
It might be a bit hacky, but sometimes that's the only solution. I've done a couple of things like that in DAMP already ;-). For example in DigibizPickerScripts.js there is a script which opens the first node when selecting media:
if (!isCreateTree) {
//Wait for 100 miliseconds because the Umbraco tree might not be loaded yet.
setTimeout(
function () {
//Find the top node and click it to show the allowed media items of the top node in the centre.
leftCol.find("a").first().click();
}, 100);
}
As you can see that's also a bit hacking, but I didn't know how else to do it. So go ahead :).
You could have made it "slightly less hacky" by using setinterval. Then check if the dom element exists before either triggering the click, or waiting again.
Client asking for 5 less clicks
The short of it is that the client wants less clicks to upload, add text, and save an image.
Images have a caption and credit fields. Here is what the client is experiencing starting from the content node:
1. Click Create
2. click browse
3. search computer files for desired photo
4. click photo to populate “Choose file” and “name” fields
5. click a “parent” where to store the photo
6. click “create”
7. click “select” to add it to the post
8. click “edit”
9. add caption info
10. add credit info
11. click "save icon” to save caption and credit
12. click save and publish icon to post.
I've gone through and this is exactly what needs to happen. The default media type is already set to Image. There is no getting around this. But the client wants to reduce this by 5 clicks.
Me immediate thought is to hack DAMP or add some js to trigger some clicks here and there....
Here is all I can think of but it's really hacky.
Since DAMP is in an an iframe in an Umbraco modal div I'm thinking of the following:
DAMP loads this page in an iframe:
/umbraco/plugins/DigibizAdvancedMediaPicker/CreateMediaItem.aspx
When it loads I can trigger a click on #body_UploadField which will launch the browse dialog
On click of "create" I can trigger a click of "select"
Then on close of the modal, I can trigger a click on edit
Then on click of the save button I can trigger a click of the save button in the content panel. Might have to add a publish button there too.
That's 4 clicks saved. But it's HACKY!!!
Can anyone can think of better ways to reduce clicks?
I've considered the desktop media uploader but I'm not sure if that is going to be good for them as they want less steps.
ps. I hate how pasting into here changes fonts
Yes please - any ideas to reduce clicks?
Hmm it's hard to reduce clicks. If the user wouldn't have to add extra info that would already reduce it, but I can understand that won't work unless the caption and credit info is on the content node instead of the media node. I don't use the creat option of DAMP a lot. Instead I use a custom version of the Multiple File Upload package. I first create all media in the media section and than use DAMP to select it.
Jeroen
Yeah there's not really a way to streamline this. They will be uploading a dozen articles per day with any number of images. The media tree is going to get huge very quickly...so finding the images after they upload them may be more hassle for them.
Do you think triggering those clicks using js is an ok idea? Personally I think it's a bit hacky but I cant really think of anything else.
It might be a bit hacky, but sometimes that's the only solution. I've done a couple of things like that in DAMP already ;-). For example in DigibizPickerScripts.js there is a script which opens the first node when selecting media:
if (!isCreateTree) { //Wait for 100 miliseconds because the Umbraco tree might not be loaded yet. setTimeout( function () { //Find the top node and click it to show the allowed media items of the top node in the centre. leftCol.find("a").first().click(); }, 100); }As you can see that's also a bit hacking, but I didn't know how else to do it. So go ahead :).
Jeroen
You could have made it "slightly less hacky" by using setinterval. Then check if the dom element exists before either triggering the click, or waiting again.
:)
Frost, it looks like plan A is the way to go.
Hi Anthony,
Did you succeeded in creating less clicks? Would like to see the result :).
Jeroen
It was for Frost's project.
I'm curious too :)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.