On Friday 23 October 2009 20:17:12 Toshio Kuratomi wrote:
> On Fri, Oct 23, 2009 at 08:03:02PM +0200, Martin Bacovsky wrote:
> > On Friday 23 October 2009 17:51:16 you wrote:
> > > On Fri, Oct 23, 2009 at 04:46:36PM +0200, Martin Bacovsky wrote:
> > > > On Thursday 22 October 2009 16:33:06 you wrote:
> > > > > I like this concept.  How does it relate to tagging?
> > > > > * As a replacement for tagging
> > > > > * As a separate feature from tagging
> > > > > * In addition to tagging where some output utilizes both tags and
> > > > > actions
> > > >
> > > > I was thinking of replacing current tags, because I'm affraid users
> > > > will be confused by two kinds of tags. On the other hand I would keep
> > > > categories imported from .desktop files (readonly/searchonly).
> > >
> > > So I think we might be committed to having freeform tags for its use as
> > > a comps replacement and grouping mechanism. I'm not 100% sure though.
> > > There is overlap::
> > >
> > > python-openssl
> >
> > As python-openssl is not an application, this is rather hypothetical, but
> > I get your point.
> 
> Well, that could be part of the issue -- actions may be a great mapping for
> applications.  But tags are also for non-applications.
> 
> > > Also, how do we get the users to only enter actions(verbs) and not
> > > nouns when supplying new actions for a package?
> >
> > I'll start from here.  The form for action tag input should look like
> > this: "I use this application to ________________ and give it *****
> > stars." I hope it makes majority of users to fill it properly. I would
> > also expect users to fill actions like "secure connection" or "encrypt
> > data".
> >
> > Whole Application Database is targeted mainly to common users. This
> > concept was designed with that in mind. So Action is something I use my
> > computer (application) for i.e. write document, edit photos, play music
> > etc. Task is the same thing with the difference that I need more steps to
> > get it done. In other words Task is just container for Actions and is not
> > connected with application.
> >
> > The other way around, if I had such Task "Write programs in python that
> > can communicate with network services over SSL" I would it rather expect
> > to contain actions such as "edit sourcecode", "run commandline
> > application" and so on.
> >
> > Also if didn't choose the right names for entities I'm talking about
> > (Action, Task, ActionTag,..), feel free to suggest better ones.
> >
> > Anyway, the example with tags would apply for any application too, and it
> > seems we would loose usefull information  by removing freeform tags. The
> > question is how to effectively combine these two. Don't you think it may
> > be confusing/contarproductive to have two types of tags?
> 
> Yeah I agree we might be better off having both and figuring out UI that
> makes it less confusing.
> 
> I think that tagging is a superset of actions in some ways.  If I operate
>  on tags, I can't see a time where I wouldn't want to include actions when
>  figuring out the results.  OTOH, when I'm looking for actions, I probably
>  wouldn't be interested in the non-action tags.
> 
> Do actions and tasks seem like a mostly browse functionality?  Or a mostly
> search functionality to you?
> 
> -Toshio
> 

I would like to have actions visible on application page. Tasks are rather 
search functionality.
I'll  try to update the mockup and let you know.

Martin

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Reply via email to