Tito is now faster with fuzzy search! :) Familiar with the file finder on emacs/vim/textmate/sublime-text? You can now type in abstract characters from the menu item to find it. appcan = Apply Canvas gablr = Gaussian Blur shgr = Show grid jgs = Jigsaw drpsh = Drop Shadow ... I'll leave the rest to your creativity and imagination :) [of course, you can still type in the name fully if you want to]
On Wed, Jun 6, 2012 at 1:39 PM, Srihari Sriraman <[email protected]>wrote: > A few more updates: > > - Works in any (all) languages supported by gimp. > - Opacity is now a preference. > - Width, Height and position are based on main window, not screen > (Tito resizes on Gimp resize). > - No more mark-up warnings in other languages. > - Code further tuned to Gimp style. > - Optimized code, removed unnecessary lines. > > A ton of thanks to Michael Muré (aka Bat`O) for his help! > > On Tue, Apr 17, 2012 at 9:01 AM, Srihari Sriraman <[email protected]>wrote: > >> Firstly, We've fixed those buffer, malloc bugs in Tito. >> >> you have an opportunity to do something good for... >>> ... 1/3 of the GIMP interaction system. >>> is that worth it? >> >> >> Making a significant contribution to 1/3rd of the interaction system >> seems like a big deal to me. >> So yes, I think its worth it. >> >> >> You can "Apply Canvas" by typing in "AC" and hitting enter. >>> > Or say "Gaussian Blur" by just "GB". >> >> >> The resolution of these 2 character inputs is done on the go. >> It should work irrespective of the language. >> I shall confirm this once I have tried this out. >> >> We tried developing the mac-like interface. It didn't work out. >> There isn't a sane way to do it in Gtk. [See Pitfalls in >> specs<http://dl.dropbox.com/u/28366148/TITO-Specifications> >> ] >> >> I think Tito is quite a cool tool to have. Even though it might not find >> an exact fit into the product vision. >> And since quite some people like Tito, my thoughts are in line with >> Aleksandar >> Kovač. >> >>> Please, let's afford ourselves some (U)ser e(X)perience with this work >> >> Tito has the potential to spur new ideas and solutions. >> >> I'll start a thread on the command system so there can be focussed >> healthy/lengthy discussions. >> >> >> >> On Sun, Apr 1, 2012 at 12:04 AM, peter sikking <[email protected]>wrote: >> >>> Srihari Sriraman wrote: >>> >>> > A command system would really boost the speed of interaction. >>> >>> now that would really depend a lot on how you design this. >>> I must admit there is a tiny opportunity to come out faster than >>> mousing the menus for a plugin without a shortcut key (ctrl-...). >>> where is comes to menu items with shortcut keys, I am not sure you >>> ever can. >>> >>> so let's see, you have an opportunity to do something good for >>> a minority part of the menu structure, which by itself forms 1/3 of the >>> GIMP interaction system. >>> >>> is that worth it? >>> >>> this of course apart form the help/explore/documentation system we >>> talked about here and on irc. I thought we had understand each other >>> during those talks. >>> >>> > We're headed there. >>> > Blender's and Rhino's systems are great, so we'll be taking inputs >>> from their design too. >>> >>> that does not sound like a confident approach to designing this >>> for GIMP. think about the whole context of GIMP, its vision and >>> its core users. all the work on the canvas. >>> >>> it starts with that realisation that you are working on what is >>> a minority part of 1/3 of GIMP's interaction. >>> >>> > Currently we're thinking of using a command syntax similar to that of >>> ImageMagick.. >>> > Would be great if we could pool in ideas regarding the command system >>> here... >>> > (Will probably start a new thread on that soon). >>> > >>> > Just to note, Tito has this handy feature. >>> > If you enter 2 letters, it matches those actions with those 2 letters >>> as the first letters of its words... >>> > Ex: >>> > You can "Apply Canvas" by typing in "AC" and hitting enter. >>> > Or say "Gaussian Blur" by just "GB". >>> >>> have you run statistic on how many clashes (same 2 or 3 letters for >>> different commands) in english? and then on to other languages, where >>> the 2 or 3 words english needs to describe something (a peculiarity) >>> is localised with a single word. >>> >>> there is 76 localisations of GIMP, I would not blame you if it can be >>> made to work for all languages apart from urdu (or something like that). >>> but if at the end it only works for 5 languages out of 76, then >>> it would of course go nowhere. >>> >>> then on to non-latin input methods, on those standard latin keyboards >>> computers are sold with. how would that be fast? >>> >>> --ps >>> >>> founder + principal interaction architect >>> man + machine interface works >>> >>> http://blog.mmiworks.net: on interaction architecture >>> >>> >>> >>> _______________________________________________ >>> gimp-developer-list mailing list >>> [email protected] >>> http://mail.gnome.org/mailman/listinfo/gimp-developer-list >>> >> >> >> >> -- >> * >> * >> *Regards, >> * >> *Srihari Sriraman >> * >> >> >> > > > -- > * > * > *Regards, > * > *Srihari Sriraman > * > > > -- * * *Regards* *Srihari Sriraman*
_______________________________________________ gimp-developer-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gimp-developer-list
