Notices

Working beautifully here, thanks!

Yep, working.

works like charm, thanks
As for extras-devel, the problem is that some people put very unstable code in devel (which is fine) and some leave very mature code in devel for a long time. So for the end user it is hard to guess whether they should use a devel version of some app or not. As far as Ansela is concerned those that use devel should be ready to accept some breakage and be happy to help out solving the bugs. Else use the testing version imho.

WAW!! fantastic!!! greetings from Colombia and THANK YOU LOSTINMIRKWOOD!!!

Oh man, if you were a woman I'd give you the biggest kiss for this... xD Thank you thank you for a great app!!!!!

10 votes. It's go for extras! Click that promote button! Click it!

Wow, Well it seems that We have the votes to get to EXTRAS, 14 as of right now. [link]
Please Vote Up or Down as you see fit, especially after reading the contents of this post. Otherwise I think the promotion will occur on June-27th.

Two points to discuss with you, my awesome users:
First, My Extras-Checklist and List of Known Bugs for your perusal:

Extras-Checklist
1. [X] Bug database exist.
2. [X] Licensing ok.
3. [X] No illegal/dubious content.
4. [X] Working provided features.
see Additional comments.
5. [X] No missing announced features.
see Additional comments.
6. [X] Optification ok. (12K usage)
7. [X] No performance problems.
Significant CPU usage when applying a filter AS EXPECTED.
8. [X] No power management issues.
9. [X] No known security risks.


Known Bugs
There are currently a few minor bugs in the current version (v0.9-5) they are being posted to bugzilla, I believe that none of there are critical blockers and we should go ahead with the release.

1:MMC Checkbox Persistance [link]
The Memory Card/Onboard Storage check-box setting does not persist over sessions.
Result: Repeatable, Annoying

2:Portrait Crop Transposed [link]
Crop functionality of portrait photos is transposed from what is desired. clicking the adjacent crop slider based on the rotation of the image will give you correct results.
Result: Repeatable, Addressable, Annoying

3:Non-Functioning Scalling Buttons [link]
Scaling Buttons in Crop S,M,L do not apply to the real image, so essentially do not function as advertised (they have no beneficial or harmful effect.
Result: Repeatable, Non-Functioning, Non-Breaking

4. Slider does not match Thumbnail [link]
The correlation between the sliders and the click buttons are not always one-to-one, meaning that if the applied filter value says +8, from a sudden jump from 0 by touching the slider-rail (not the slider button or the +/- orbs) the thumbnail may not register the change, but the apply button works as designed. A Second press of any control/widget, usually Re-Syncs the thumbnail.
Result: Non-Repeatable, Confusing.

5.package description needs spaces after colons and commas [link]
Packaging (Again) there seems to be a lack of spaces is the extended description after certain commas.
Result:Non-Breaking, Embarrassing

6. Application Load Invisible [link]
During the application load Ansel-A appears on the taskbar with a loading spinner, when I force a switch to full-screen the UI disappears and only reappears as Thumbnail creation starts population the photo-browser. This is seen in other python and PyQt Applications.
Result:Confusing




Sad Note
I smashed the screen of my phone, the LCD panel is cracked and colorfully-non-functioning, but the touch screen digitizer works fine. So development has stalled until that arrives and is brought in for service. Until then I'm getting by using SSH, VNC or an old LCD Panel with video out to run the tablet.
Back to using my N95, I had forgotten after all these months how finger-active symbian is and just how many finger presses to get the simplest thing to work, on average it seems like 5.
The worst thing is now I have to run facebook-app, Fring and NokiaMail all the time. I don't even remember how to update an application without going to a website and sending myself some odd sms link (I was looking for the update button, Ha); and t9 has become mind numbing after having a keyboard for 6 months. Worst of all there's no terminal, it's like a phone or something.

Dearly missing and spoiled by my N900.

Thanks for Ansel A. I really like it. It is so nice when people bring out "real" solutions to replace the "duct tape" ones that I have been using.

Some problems I've found:
1. At least for the landscape photos I've tried, the whole picture doesn't display, both in the browser, and on the image manipulation pages. The current picture seems too far to the left, cutting some of the image off, and there may be some cropping on the right too. This is particularly problematic on the cropping screen, since I can't see the left and right crop lines.
2. When "warming up" my picture by adding some red and yellow, there's something not-quite-right happening. I first adjust the cyan-red axis towards red, and then I adjust the yellow-blue axis towards yellow. It seems that the preview doesn't show correctly after adjusting the yellow, because if I adjust the red up and back down again (after adjusting the yellow), the picture looks different, even though it should look the same. (EDIT: this might be bug 10766)
3. The histogram/levels tab doesn't seem to have anything in the three graphs... Not sure if it is something I'm doing wrong?

Some feature requests:
1. There should be some way to see a quick fullscreen preview of your current edit before committing to it. There seems to be something like this in the "undo" tab, but I'm a bit nervous about what's going on, since I'm in a place all about "undoing"...
2. I would love to see an auto white balance button, as well as a couple of colour temperature presets.
3. I would love a couple of preset aspect ratios for cropping, especially for standard (at least in North America) print sizes. You know, 4x6, 5x7, 8x10, those ones.

(If you want to see a photo editing feature set that really "nails it" for the average user, take a look at Picasa.)

Anyway, thanks again for a really useful and nice looking app!

Thanks qole, I was shocked when I saw a moderator take the time and make a lengthy reply to my thread. I know you guys have enough to do, and I appreciate that. To address some of your points at length:

Yes this is a bug. It can be missing a few (1-10)verticle lines on the left side. I noticed that it only happens to landscape images with certain dimensions. The fitting algorithm seems to fail with landscape images that are between 4:3 and 1:1, "widescreen" 16:9 shots seem to fit without cropping, please post a full-resolution image (or at least the numeric resolution) that you're specifically having problems with and I'll try to see what it "breaks"

This is a architecture issue. I'll describe it here in a bit of detail so other's can see what is happening as well, sort of a code review.

I have three objects in memory that we'll call state, curPhoto and undoList and two objects in the GUI let's call them GUI.FullPhoto and GUI.Thumb.

The Last two match to what you'd think they are, but the GUI.FullPhoto is actually the full photo 5Meg Resolution scaled in Qt to fit the screen for display only, whereas the GUI.Thumb is pixel-for-pixel displayed in the editor (approx 35K, 250x? or ?x250 in order to fit landscape or portrait here lies the issue above described in point 1.).

state has in it the values that you have set in the GUI such as the location of the current photo on disk, the values of all the sliders, the selected BW conversion, orientation of the photo, etc.

curPhoto has the pixmap of the current-real-image curPhoto.Full, a thumbnail of the pixmap of the current-real-image curPhoto.Thumb, and the appropriate sizes and location of each for display in the GUI as GUI.Thumb and GUI.Full.

undoList is an ordered dictionary of curPhoto objects.

When you first select a photo from the photoBrowser a curPhoto is created and undoList[0] is populated with this object. state is reset to default (or 0) values and and the Entire GUI is updated with that state information.
(This will allow for future filters to be created and saved by the user, or as you mentioned: Warmify, might be an increase in Brightness+3, Red+3, Blue-1, Sharpness-2)

as you interact with the GUI, say by changing the Brightness slider to +1, the state object gets updated, in this case state.bright =1. This triggers an signal to regenerate the GUI.Thumb, specifically for Brightness. It'll take curPhoto.Thumbnail apply a brightness multiplier of 10% and display the results in GUI.Thumb which is a relatively fast process. (~0.1sec)
and the user can see what the change would achieve.

When the user clicks Apply, GUI.Full needs to be updated, state is passed to the appropriate filter routine based on the currently selected tab, and any non-zero changes available in that tab are applied (i.e. Brightness+1 & Contrast+4) to curPhoto.Full and saved to a new curPhoto, this curPhoto is then stored in undoList[1], The GUI.Full/Thumb are updated as described above.

Note: Undo uses the undoList[] by repopulating curPhoto back to the selected undo state.

So as the current architecture stands, If you modify the Contrast slider and then Brightness, it does not re-gen the GUI.Thumb with information on Contrast. So, if you Apply a Contrast change then Apply a Brightness change, the GUI.Full/Thumb will be updated correctly.

But as you mentioned if you change Contrast, and Change Brightness the GUI.Thumb will show the Brightness change only, But when you click, Apply it will apply all changes present in that tab (namely Both Brightness and Contrast) updating the GUI.Full and GUI.Thumb as expected.

I think that there needs to be a bit of an architecture change on my side to rectify this. Thought the outstanding problem is that settings like Brightness and Contrast are not commutative. Brightness->then->Contrast will create a final image that is different than a Contrast->then->Brightness filter.

It works before you adjust the image, afterwards, it seems that the histogram data is appended to the current values, but overflows the chart, thus you see no data and no changes. I'll look into it.
Hey, that's a great idea! Not sure how to implement that in a filter, but it seems like a fun math problem to attack.
This is what the S, M, L, buttons would do, once they are implemented.
I agree. I used Picasa and Gimp, while developing to get some of my ideas. I'd like this application to be closer to Picasa then to Photoshop. Simple tools, simple fixes, with a "bit" of user control; but not to the extent that gimp/Photoshop provides.

Thanks again for your comments and thoughts.

Tell us your facebook page so that we can friend you.