The work-state buttons sound like a great idea - should streamline the process (and save screen real-estate).<br><br>Having brightness/contrast independent for shadow/highlights is basically a modification of the curve. Perhaps it would be suitable to have those sliders accompanied by the curve on a specific work state, and have the curve updated to show the effect of the sliders - that way, the sliders can be used to approach a desired curve, and then the curve tweaked as needed. Just a thought.<br>
<br>Anyway, it seems like the UI will see significant changes before 2.0, and I look forward to them all!<br><br>Cheers guys<br><br>Jon<br><br><div class="gmail_quote">On Tue, Nov 10, 2009 at 7:45 AM, Klaus Post <span dir="ltr"><<a href="mailto:klauspost@gmail.com">klauspost@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Jon!<br>
<div class="im"><br>
> I've begun putting together documentation for the current stable release -<br>
> I'm probably over half way with that. I think getting that done, then<br>
> discussing it here will provide a good base for working on the documentation<br>
> for 2.0. I had the same thought about videos, they can be very useful for<br>
> quickly showing basic functionality, or explaining more complex<br>
> functionality in small sections.<br>
<br>
</div>I complely agree!<br>
<div class="im"><br>
<br>
> In terms of usability, I gave some thoughts in a previous email, such as<br>
> left clicking by default setting the white balance - this is very<br>
> unintuitive - it should certainly drag the image when zoomed, and probably<br>
> have no effect when viewing the whole image. Couldn't holding W down while<br>
> clicking set the white balance?<br>
<br>
</div>Our initial idea is to have work-state buttons, that defines the task<br>
you are currently working on.<br>
Click to set WB is of course one of these states, but so are crop,<br>
rotate, pan, etc. A simple button press to change between them and a<br>
nice icon should hopefully make it a bit more intutive.<br>
<br>
(Rather badly titled)<br>
<a href="http://bugzilla.rawstudio.org/show_bug.cgi?id=287" target="_blank">http://bugzilla.rawstudio.org/show_bug.cgi?id=287</a><br>
<div class="im"><br>
<br>
> Since then I've built and had a play with the current SVN. I like the<br>
> improved functionality, but what's going on with the super-sensitivity of<br>
> the contrast slider? I know there are bug reports about it, and suggestions<br>
> of manual text input boxes - whatever the solution, it obviously has to be<br>
> possible to fine-tune.<br>
<br>
</div>All color-adjustments are "work-in-progress", and are due to be<br>
fine-tuned before 2.0. I completely agree on contrast, and personally<br>
I cannot see a good reason for hue to be more than +-15 degrees. I<br>
would also personally like contrast to be divided into<br>
shadow/highlight contrast, since it allows far more flexibiliy.<br>
<br>
But all this is relying on the biggest missing thing before 2.0, color<br>
management. As you might have noticed, Anders has done a great deal of<br>
work to support DCP-profiles.<br>
<div class="im"><br>
> I'm not a usability expert, so what I've said above isn't gospel, but I do<br>
> know a certain amount about usability. On the whole, in terms of the rapid<br>
> and smooth workflow, prioritising images etc, Rawstudio beats most<br>
> commercial software when it comes to sorting a raw shoot for processing -<br>
> but there are these few areas (mentioned above) which let it down.<br>
<br>
</div>I think that will warm the hearts of Anders&Anders. This was what they<br>
set out to do a few years ago, and with color management, I personally<br>
think it is very useful, and as a Windows user I pray for a port every<br>
day. :)<br>
<div class="im"><br>
<br>
<br>
> Clearly there's no point writing the 2.0 documentation until things are<br>
> finalised - which is why I started with the 1.2. I'm busy for the next<br>
> couple of weeks, so probably wont have it finished until after then (as I<br>
> had hoped to). Then we can discuss what I've done and how we can apply that<br>
> to 2.0.<br>
<br>
<br>
</div>Sounds like a good plan!<br>
<div><div></div><div class="h5"><br>
><br>
> Cheers<br>
><br>
> Jon<br>
><br>
><br>
><br>
> On Tue, Nov 10, 2009 at 5:04 AM, Klaus Post <<a href="mailto:klauspost@gmail.com">klauspost@gmail.com</a>> wrote:<br>
>><br>
>> Hi!<br>
>><br>
>> Sounds great!<br>
>><br>
>> I've been pondering on doing a documentation efford on the<br>
>> sharpening/denoiser part at least, since it is pretty much in the<br>
>> state it should be for the 2.0 release, IMO at least.<br>
>><br>
>> My own thoughts were along small video tutorials, but it cannot go<br>
>> without written documentation, since it allows far more detail.<br>
>><br>
>> We have talked about some more generic UI improvements, which I feel<br>
>> should be implemented for 2.0. The main issue is to make the already<br>
>> available features more visible. We are mostly talking about exposing<br>
>> the Rightclick-menu features to buttons, so they are immediately<br>
>> visible and available to the user.<br>
>> This way, hopefully you shouldn't have to use too much space on<br>
>> explaining basic functions.<br>
>><br>
>> Other than that, there are also a bunch of Lensfun options that has to<br>
>> be displayed, and a camera settings/profile page that has to be built.<br>
>><br>
>><br>
>><br>
>> Regards, Klaus Post<br>
>><br>
>> <a href="http://www.klauspost.com" target="_blank">http://www.klauspost.com</a><br>
>><br>
>><br>
>><br>
>> On Tue, Nov 3, 2009 at 9:33 AM, Jonathan Musther <<a href="mailto:jmusther@gmail.com">jmusther@gmail.com</a>><br>
>> wrote:<br>
>> > Hi Martin,<br>
>> > Is the functionality you describe in the current development release, as<br>
>> > there aren't any RGB sliders in the 1.2 release?<br>
>> ><br>
>> > Hi Michael,<br>
>> > I would be very happy to collaborate on documentation via a wiki (or<br>
>> > some<br>
>> > other means).<br>
>> > There are clearly several different ways to approach this, but I think<br>
>> > perhaps the most important thing is that we begin actually doing it,<br>
>> > rather<br>
>> > than getting too bogged down in the technicalities. A wiki is perfectly<br>
>> > acceptable, but should be coordinated with whoever is in charge of the<br>
>> > rawstudio website, such that it can be fairly seamless and easily<br>
>> > accessible<br>
>> > for users.<br>
>> ><br>
>> > Cheers<br>
>> ><br>
>> > Jon<br>
>> ><br>
>> ><br>
>> > On Tue, Nov 3, 2009 at 9:09 PM, Martin Christensen<br>
>> > <<a href="mailto:martin.sand.christensen@gmail.com">martin.sand.christensen@gmail.com</a>> wrote:<br>
>> >><br>
>> >> >>>>> "Jonathan" == Jonathan Musther <<a href="mailto:jmusther@gmail.com">jmusther@gmail.com</a>> writes:<br>
>> >><br>
>> >> Jonathan> My name is Jon, and I'm here to volunteer to write some<br>
>> >> Jonathan> documentation.<br>
>> >><br>
>> >> Wonderful! Rawstudio could use it.<br>
>> >><br>
>> >> [...]<br>
>> >> Jonathan> - Reduce to B&W<br>
>> >> Jonathan> It would be great to be able to reduce to black and white,<br>
>> >> and<br>
>> >> Jonathan> vary the RGB being used to do so. This would allow<br>
>> >> Jonathan> photographers to, for example, produce a B&W image dominated<br>
>> >> Jonathan> by the red channel This is the equivalent of using lens<br>
>> >> Jonathan> filters, or DSLR lens filter effects.<br>
>> >><br>
>> >> This is already an option almost exactly as you describe it. Just set<br>
>> >> the saturation slider to 0 and adjust the RGB sliders to your heart's<br>
>> >> content.<br>
>> >><br>
>> >><br>
>> >> Martin<br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Rawstudio-dev mailing list<br>
>> > <a href="mailto:Rawstudio-dev@rawstudio.org">Rawstudio-dev@rawstudio.org</a><br>
>> > <a href="http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev" target="_blank">http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev</a><br>
>> ><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> Rawstudio-dev mailing list<br>
>> <a href="mailto:Rawstudio-dev@rawstudio.org">Rawstudio-dev@rawstudio.org</a><br>
>> <a href="http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev" target="_blank">http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> Rawstudio-dev mailing list<br>
> <a href="mailto:Rawstudio-dev@rawstudio.org">Rawstudio-dev@rawstudio.org</a><br>
> <a href="http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev" target="_blank">http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev</a><br>
><br>
><br>
</div></div></blockquote></div><br>