From kde-kimageshop Tue Aug 28 11:03:58 2012 From: Simon Legrand Date: Tue, 28 Aug 2012 11:03:58 +0000 To: kde-kimageshop Subject: Re: Choosing Krita's most annoying bugs and most sought after features Message-Id: X-MARC-Message: https://marc.info/?l=kde-kimageshop&m=134615184803286 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============7703569184180925506==" --===============7703569184180925506== Content-Type: multipart/alternative; boundary=bcaec50162d32bc24a04c851663b --bcaec50162d32bc24a04c851663b Content-Type: text/plain; charset=ISO-8859-1 On Tue, Aug 28, 2012 at 11:07 AM, Boudewijn Rempt wrote: > On Tuesday 28 August 2012 Aug, Simon Legrand wrote: > > I personally would order them this way: > > > > 1- typographic text tool > > 2- overview docker > > 3- open image browser/flipbook > > > > The browser is a great idea, although dolphin is already very powerful! > > Could digikam be useful there? Maybe a digikam bridge? I love that > > software. As far as the flipbook aspect of it I think it may be tough > doing > > both in one tool, especially considering that Krita may be used for > fixing > > a few frames but I doubt it would be used to load and fix a full shot. We > > already have pretty robust tools for flip-booking. > > > > DJV_viewer (Open source, perfect for home use) : > http://djv.sourceforge.net/ > > RV (Industry standard, this is what almost all big studios use) : > > http://www.tweaksoftware.com/products/rv > > FrameCycler (Used to be industry standard) : http://www.iridas.com/ > > > > Should you want to move ahead with writing a flipbook of your own I would > > recommend RV as an initial guideline for UI and functionality. > > Interesting links! I was suggesting the flipbook/browser plugin more as a > way to get multiple images open in krita for easy switching -- i.e., a kind > of extended tabbing interface. > Aaaahhh right! In this case I would put it at 2nd place. (mainly because I know many people are waiting for the text tool). > > For the text tool, we'd really need to first investigate what artists need > out of it and then find a way to get the resources to implement it > properly. I doubt that the artistic text tool will give us a proper base to > work from (and the same for the multiline text tool, which is really geared > towards producing text in paragraphs.) > > -- > Boudewijn Rempt > http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl > _______________________________________________ > kimageshop mailing list > kimageshop@kde.org > https://mail.kde.org/mailman/listinfo/kimageshop > -- Simon Legrand http://slegrand.blogspot.com/ --bcaec50162d32bc24a04c851663b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Aug 28, 2012 at 11:07 AM, Boudew= ijn Rempt <boud@valdyas.org> wrote:
On Tuesday 28 August 2012 Aug, Simon Legrand wrote:
> I personally would order them this way:
>
> 1- typographic text tool
> 2- overview docker
> 3- open image browser/flipbook
>
> The browser is a great idea, although dolphin is already very powerful= !
> Could digikam be useful there? Maybe a digikam bridge? I love that
> software. As far as the flipbook aspect of it I think it may be tough = doing
> both in one tool, especially considering that Krita may be used for fi= xing
> a few frames but I doubt it would be used to load and fix a full shot.= We
> already have pretty robust tools for flip-booking.
>
> DJV_viewer (Open source, perfect for home use) : http://djv.sourceforge.net/
> RV (Industry standard, this is what almost all big studios use) :
> http://www.tweaksoftware.com/products/rv
> FrameCycler (Used to be industry standard) : =A0http://www.iridas.com/
>
> Should you want to move ahead with writing a flipbook of your own I wo= uld
> recommend RV as an initial guideline for UI and functionality.

Interesting links! I was suggesting the flipbook/browser plugin more = as a way to get multiple images open in krita for easy switching -- i.e., a= kind of extended tabbing interface.

Aaaahhh right! In this case I would put it at 2nd place. (mainly because I = know many people are waiting for the text tool).
=A0

For the text tool, we'd really need to first investigate what artists n= eed out of it and then find a way to get the resources to implement it prop= erly. I doubt that the artistic text tool will give us a proper base to wor= k from (and the same for the multiline text tool, which is really geared to= wards producing text in paragraphs.)

--
Boudewijn Rempt
http://www.valdyas.org= , http://www.krita.o= rg, http://w= ww.boudewijnrempt.nl
_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop



--
= Simon Legrand
http://slegrand.= blogspot.com/
--bcaec50162d32bc24a04c851663b-- --===============7703569184180925506== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kimageshop mailing list kimageshop@kde.org https://mail.kde.org/mailman/listinfo/kimageshop --===============7703569184180925506==--