Support/Comments for Easy 2 Gallery 1.4.0-Beta 4

Quote from: outre99 at Jul 28, 2010, 01:20 AM

Also, in the meantime would you recommend a workaround way to plugin a different gallery presentation and a slideshow components?

Thanks in advance.

Like what?

I’m using jQuery Tools Scrollable component to present items in a carousel and integrate it with PrettyPhoto lightbox.

So all i need to do is to turn off any of the bundled libraries and just format the template for the images output to use the proper classes.
I also don’t need Easy2Gallery to include any javascript libraries nor make the component initialization calls. Just get me the images.

As is always the case: less is more.


Thank you.

Hi Goldsky,

as i was working through the current project and thinking about a couple of upcoming ones i realized that one of the most common cases for added images is in the context of a particular resource. For example having a News section with multiple news article resources. Any set of images would be related to a particular article. So it would be much more usable if it was possible to create a new gallery and add images while editing the news article resource. Perhaps another ManagerManager tab (similar to YAMS) for the gallery Module. Maybe the gallery title can default to the resource title and gallery name to the resource alias.
I think this workflow would feel more natural than having to go to the module to create a gallery.

By the way Sharkbait’s little snippet posted earlier in this thread to pull available galleries into a dropdown TV works like a charm.

I think that this gallery is the most functional and logically organized of all MODx galleries and would like to help. I’m ok with PHP and pretty good with html, js. I can also translate from Russian.

Let me know.
Best

outre, you’re using the RC1 version, right?
A guy from the russian forum has pointed me to the better option: http://code.google.com/p/tinymce-gallery-connection/
So, right now I’ve been working on making a new plugin for the TinyMCE.

Yes, i’m on 1.4.0 - RC1.

Is there something newer?

Just looked at TinyMCE connector.
It’s nice but it only inserts a single image into content at a time. I think it’s great for non-technical users who edit content using TinyMCE.
Unfortunately this if very limited for several reasons:
1. TinyMCE generates horrible code
2. Cannot insert a whole gallery.
3. One way interaction: an image is selected from an existing gallery and inserted into the current document. User can’t insert an image into the gallery.

What i was describing is a very different use case. A content editor is creating a new article and needs to upload several related images and link them to this article.

If you were thinking about this one (attached), then you need to wait the RC2 release for a while, and of course the bug resolving for the report I’ve make.

He Goldsky,

my last message was for the longer term.

The tab i was referring to would not be in the Plugin configuration page, but rather an additional page on any resource that had a "gallery" flag set to "true". Similar to YAMS module. When YAMS is enabled for a template it adds tabs to each resource using that template for every active language.
No i know what YAMS is doing is very different from the gallery, but the user experience should be the same. i.e. A user can create a gallery and add images to it in the context of working on a resource rather than having to open the gallery plugin, create a new gallery, and then go back to the resource and link it to the newly created gallery.

Of course this is the perfect world. For now the workflow is sufficient, and the Sharkbait’s snippet links a gallery with a resource just fine.

For me the most critical issue is to allow turning off of all the 3’rd party libraries so i can format the snippet’s output with template chunks.

Quote from: outre99 at Jul 28, 2010, 07:24 AM

I’m using jQuery Tools Scrollable component to present items in a carousel and integrate it with PrettyPhoto lightbox.
So all i need to do is to turn off any of the bundled libraries and just format the template for the images output to use the proper classes.
I also don’t need Easy2Gallery to include any javascript libraries nor make the component initialization calls. Just get me the images.
As is always the case: less is more.
Thank you.

@outre99,
do you think that editing the libs.config.easy2gallery.php is not simply enough for you?
or do you have more simple suggestion?

I looked through that file but only noticed the initial calls to the Javascript libraries, which i would like to have in a my own separate file anyway. But where in the libs config would I setup the actual classes of the images or wrapper divs?

My thought for simplification would be to do something very similar to what Ditto does. i.e. have a template chunk that would format what easy2 snippet returns. The template would include the proper classes for whatever gallery or lightbox to use. And the site author would include the proper libraries and make the JS initialization calls in a way they want. For example i have a separate js_init.js file that initializes all of the JS components present on a page. Since i prefer to control what libraries are being included on a page and in what order i find it a bit frustrating that easy2 messes with my carefully crafted page head.

I think it would be cleaner and simpler to keep the module and snippet completely agnostic to what JavaScript libraries are being used. So there would be no need to have all of those library configurations in the libs file. Actually there would be no need for the libs.config file at all. The module and snippet are just there to find and return proper images, then a chunk would be used to format what is being returned.

Now i understand that some less technical users would prefer to have everything included, but i think that goes against the MODx’s primary focus of providing power and flexibility of a programming framework rather than being WISYWIG CMS. For those folks example template chunks and initialization calls could be provided for whatever JS gallery or lightbox they want to use either by you or by others in the community. This will remove the burden of keeping up with all of the new libraries from you.

Just my 2 cents worth.

Let me know if i can help in any way.