phatch-dev team mailing list archive

[Juho Vepsäläinen <bebraw@xxxxxxxxx>]

Hi,

2009/9/7 Stani <spe.stani.be@xxxxxxxxx>:
> The good thing about Igor is that he is not a developer (except of
> course for the excellent icons ;-)), but an end user from the first
> hour. So he thinks more like a designer. Besides graphic profesionals,
> the target audience for Phatch also includes for whom programs like
> Gimp, Fusion 6 or Photoshop are too difficult. So we should keep the
> organisation of actions as simple as possible. The tags should be the
> best organisation of the *current* actions. Juho, I really appreciate
> your ambition with Phatch, but I prefer not to add categories/tags
> with only entrance or todo items. This feels a bit like an "under
> construction homepage". Of course Phatch is in constant evolution and
> will continue to grow, but that doesn't mean we shouldn't present
> Phatch as a polished release.

The point was to show how to possibly ~extend~ the structure. When it
comes to categorization, each application has its own way.

Note that I was thinking more in terms of Python packages/modules
(treelike hierarchy). For me the point of categorization is to split
things up level by level from abstract to concrete. I don't think
three levels (high level concept, possible middle level, low level) in
a category tree is too much. In my view it's much worse to have a huge
root level with many categories without any subcategorization. In this
case you lose some vital information about the structure.

It's possible to use a shallow structure in practice and tag some
action to say "decor" and "filter". This way when you do a search on
these terms you obviously get some filter that can be used for
decoration (ie. border and such). Or on more general search you just
might want to see all filters, generators or whatever.

Note that the structure does ~not~ constraint the user interface in
any meaningful manner. You can put the actions in menus, have nice
folders for them, use tagging etc. It's generic in that way.

Sincerely,
Juho Vepsäläinen

>
> So I feel Juho that your logic is more based on the content of the
> actions. I prefer more to see the best organisation of the current
> actions. This means a limited set of tags with a roughly equal
> distribution of actions. I think Igors setup is a good base for this.
> Only I feel that there might be some overlap. For example I would put
> the transform filters also under transform. Filters is a very generic
> name, so if some filters relate to specific categories already present
> in Phatch we should also link them there. Otherwise filters feels for
> me too much like the "left overs".
>
> Juho and Igor, thanks a lot for your input! I'm curious for Nadia's reaction.
>
> Best regards,
>
> Stani
>
> On Mon, Sep 7, 2009 at 9:26 AM, Admiror Design
> Studio<admirorns@xxxxxxxxx> wrote:
>> @Juho Vepsäläinen
>>
>> You make very nice organisation of actions. I only dislike Input, FIle and
>> Output categories. I think these actions can be put under File category.
>> Lesser number of categories will be more ease to use than bigger number.
>>
>> Filters can be organise with category droplist system:
>>
>> File (link)
>> Transform (link)
>> Color (link)
>> -----------------------
>> Filters
>>    Blur (link)
>>    Noise (link)
>>    Distort (link)
>> ------------------------
>> Plugins (link)
>>
>>
>> Tagging system Phatch currently is using is great, because it is possible to
>> have action which user wont be sure where to search. But again, if a lot of
>> actions belong to more than 1 category, than is questionable need for
>> categories because everything can be found everywhere. Having actions in
>> more than one category should be avoid if possible, and be used only for
>> special cases.
>>
>> Regards,
>> Igor Kekeljevic
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~phatch-dev
>> Post to     : phatch-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~phatch-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
>
> --
> Phatch Photo Batch Processor - http://photobatch.stani.be
> SPE Python IDE - http://pythonide.stani.be
>
> _______________________________________________
> Mailing list: https://launchpad.net/~phatch-dev
> Post to     : phatch-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~phatch-dev
> More help   : https://help.launchpad.net/ListHelp
>