Your hints.jap sets rows to 99999

You can force the same behaviour by setting rows to 0 (just in case somebody generates an album with 100000+ rows).

No I don't spend all of my spare time re-reading this thread. I am just taking a short break from the 34°C temperature here in the Great White North.

Btw checking the link in the Downloads tab (and also a couple others) I get:


So I can't actually download it. Maybe it's the same that's bundled with jAlbum though? Anyway I really just have to look at the JAlbumContext class etc. (whatever else it takes) and work on implementing it - but I don't know when I'll get to this. But thought one of you ought to know that the download isn't working (though maybe I have to be logged in, I don't know).

Cheers.

There is an API to extend the type of image filters we call "Image tools" under the Edit panel. These are also filters technically speaking. But, we currently don't have an open API to extend the "effects" (i.e. filters with user interfaces that by default apply to all images). It's on the long todo list to unify these filters under the same API as they technically speaking all do the same thing - manipulate images. I guess you're looking for an extension API so you can add your own effect, right? Or do you prefer to install your filter as an "Image tool" under Edit?

What I would like is to be able to change the settings and see a live preview like you can of the Arty, Greyscale, Text effects. The reason is that one of my filters has a lot of settings and it would be great to see it without having to force rebuild an album and then look at it. This would help not only in finding better settings but it would also make it easier in general.

So yes I would like to add my own effect indeed. If the other option has a preview that would be fine too but I don't think it does? Oh actually I see it does but does it have a way to set parameters? That's the key - I would like to install it into the UI and then be able to say: I want to run this filter on this image but be able to update the parameters. Is that possible?

Thanks for the reply and any help you can provide here! Same goes to the others of course.

Oh btw is there a way to make it so that the rebuild always runs filters - that is as if it does force rebuild? Since my skin basically has filters as part of it it would be better to have the filters always be run. Thanks.

Update your defaults, make sure Settings>Advanced>Metadata>Include JAlbum widget support is off, then do Menu>File>Save as default.

I've made a lot of improvements and have added quite a few new features (skin and filters plus a new filter) but I have run into a snag that I want your thoughts on. Perhaps this goes esp to jGromit but anyone else is by all means welcome.

Old way: if the album has three directories and the first one has a subdirectory which has a subdirectory it would show something like:

Pet Photos | 1 folder

And then under that directory it would show also that there's a subdirectory. But then I thought: what if there are no images in the end? That's rather silly to show that there are directories if they're empty.

So the obvious solution was to recurse and if no images found don't include them like:

int numTotalImages = JAlbumUtilities.countCategories(ao,true).getCount(Category.image);
if (numTotalImages == 0) continue;

But since it's one directory at a time it might happen that the parent directory already found two directories and so it listed them even though one has no images.

I can think of some ways to resolve this but maybe there's a preferred method with jAlbum and that's what I'm after. To give you an idea this is from lines 77 through 140 in the attached index.htt.

Is there a preferred jAlbum method for this? Maybe there's even a reason to include empty directories? I don't know why there would be but it would also make it simpler. Then again it might even be that i'm not thinking of a much simpler solution and if I take a break and look at it again it'll be very obvious. I could believe that too.

Thanks.

The user may be building a project with many branches, and wants to set up the structure before populating it with images. He'll just be puzzled about why he's not seeing the structure he's created.

Hiding empty directories falls into the category of doing the user a "favor" that he didn't ask for. If he wants to have empty directories ignored, the core already gives him a way to do that - he can hide or exclude them with a click.