|
»
»
The proverbial watch icon
|
View:
New views
18 Messages
—
Rating Filter:
Alert me
|
 |
The proverbial watch icon
by alain_desilets
::
Rate this Message:
I got responses from about a dozen folks. As I feared, no one icon pair
is 100% clear. Here are things that came out fairly clearly. == 1. None of the icons is good at clearly conveying ACTION == When you ask folks what ACTION will happen when you click on a given icon, there is typically a 50-50 split between those who think watches will be turned on, and those who think they will be turned off. The one exception is Icon 7, the eye with a green plus sign, which everyone interprets as meaning that watches will be turned on. == 2. All icons are pretty good at clearly conveying STATE == When you ask folks what STATE a particular icon represents, they are typically unanimous in their response. == 3. None of the icons are good a conveying STATE and ACTION that are consisten with each other === The unanimous STATE interpretation of an icon is always the opposite of the ACTION interpretation that was chosen by the majority (if there was a majority). == What to do? == Here's what I propose to do. Use icons to convey informattion about the STATE of watches (since at least, STATE is interpreted consistently by users), and use some other more explicit form of feedback to convey information about ACTION. For now, info about ACTION will be conveyed via the yello info box that pops up when you leave the mouse over the icon. It will say something more explicit like: Watches are <b>ON</b>. Click on icon to turn them <b>OFF</b> but eventually, I would like to make it so that, when you click on the icon, you see a pop-up menu like this: X Turn Watches <b>ON</b> Turn Watches <b>OFF</b> where the X represents a check mark indicating which of the two options are currently active. I don't know if we have a way in Tiki to support this kind of pop-up window, but if so, please guide me to where I can find it. For now, i will go with the info pop-up approach. Note that the pop-up menu will mean an additional click for the user. In this case, I think it's warranted because: (i) the watch icon is causing lots of confusion, partly because of the STATE/ACTION contradiction, but also because final confirmation may be sloww to come (you only know that the traces are indeed on when you get your first change notificaion) (ii) setting watches on is not as frequent an action as, say, editing a page. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by Rick Sapir-3
::
Rate this Message:
Just my opinion, but I expect buttons in a button bar to perform an action.
> >Here's what I propose to do. > >Use icons to convey informattion about the STATE of watches (since at >least, STATE is interpreted consistently by users), and use some other >more explicit form of feedback to convey information about ACTION. I disagree. I think the icon should continue to convey the ACTION. The STATE can *easily* be inferred based on the action. For example, if the action is "Start watching this page." then the current status is obviously "not watching." >For now, info about ACTION will be conveyed via the yello info box that >pops up when you leave the mouse over the icon. This text is controlled by the TITLE element of the <A> tag. I *think* this behavior may vary, depending on the browser & platform. In some instances the ALT text of the IMG (which is *inside* the <A> tag) is displayed instead of the link's title. AFAIK, this *is not* controlled by TIki. If it is truly this confusing, why not simply remove the icon completely and use a simple drop list (like we do for backlinks) with two options: - Watch this page. (i.e., the current state is "not watching") - Stop watching this page (i.e., the current state is "watching") Just my $0.02. -R --- Greetings from Sanford, NC, USA! ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by Marc Laporte-3
::
Rate this Message:
Thank you for being so thorough!
Usability issues can be so intangible. Real-world observation and surveys are so useful. Once guidelines are set, devs will be happy to have something to follow. And over time, we can harmonize the whole app, as has been done for tables, pagination, etc. Best regards, M ;-) On Thu, Nov 5, 2009 at 5:45 AM, Desilets, Alain <Alain.Desilets@...> wrote: > I got responses from about a dozen folks. As I feared, no one icon pair > is 100% clear. Here are things that came out fairly clearly. > > == 1. None of the icons is good at clearly conveying ACTION == > > When you ask folks what ACTION will happen when you click on a given > icon, there is typically a 50-50 split between those who think watches > will be turned on, and those who think they will be turned off. The one > exception is Icon 7, the eye with a green plus sign, which everyone > interprets as meaning that watches will be turned on. > > == 2. All icons are pretty good at clearly conveying STATE == > > When you ask folks what STATE a particular icon represents, they are > typically unanimous in their response. > > == 3. None of the icons are good a conveying STATE and ACTION that are > consisten with each other === > > The unanimous STATE interpretation of an icon is always the opposite of > the ACTION interpretation that was chosen by the majority (if there was > a majority). > > == What to do? == > > Here's what I propose to do. > > Use icons to convey informattion about the STATE of watches (since at > least, STATE is interpreted consistently by users), and use some other > more explicit form of feedback to convey information about ACTION. > > For now, info about ACTION will be conveyed via the yello info box that > pops up when you leave the mouse over the icon. It will say something > more explicit like: > > Watches are <b>ON</b>. Click on icon to turn them <b>OFF</b> > > but eventually, I would like to make it so that, when you click on the > icon, you see a pop-up menu like this: > > X Turn Watches <b>ON</b> > Turn Watches <b>OFF</b> > > where the X represents a check mark indicating which of the two options > are currently active. > > I don't know if we have a way in Tiki to support this kind of pop-up > window, but if so, please guide me to where I can find it. For now, i > will go with the info pop-up approach. > > Note that the pop-up menu will mean an additional click for the user. In > this case, I think it's warranted because: > > (i) the watch icon is causing lots of confusion, partly because of the > STATE/ACTION contradiction, but also because final confirmation may be > sloww to come (you only know that the traces are indeed on when you get > your first change notificaion) > > (ii) setting watches on is not as frequent an action as, say, editing a > page. > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Tikiwiki-devel mailing list > Tikiwiki-devel@... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > -- Marc Laporte http://MarcLaporte.com http://TikiWiki.org/MarcLaporte http://AvanTech.net http://OurWiki.net ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by alain_desilets
::
Rate this Message:
> Just my opinion, but I expect buttons in a button bar to perform an
> action. Opening a menu IS an action no. There are plenty of examples of buttons that open up something which allows you to further specify the details of the action you want to happen. As I am writing this message in Outlook, I see a "To..." button. When I click on it, I get a dialog box where I can choose the addressees. That's not that different from clicking on an eye icon and getting a popup menu where I can say whether I want the traces to be on or off. > I disagree. I think the icon should continue to convey the ACTION. The STATE > can *easily* be inferred based on the action. For example, if the action is > "Start watching this page." then the current status is obviously "not > watching." I have observed many users in the course of training sessions, or in the course of starting a tiki site and supporting users by email at the beginning, and my experience contradicts what you say. Users do not find this obvious, even with the yellow info box (which, btw only shows up when you hover the mouse over the icon). Furthermore, my (admittedly very small) survey indicates that even when you tell people that the icon refers to an action (not to the state), they are confused about what action it refers too (whereas they are always clear about what state it might refer to). Hence, my recommendation that, in the case of a toggle, we use the look of the icon to convey state as opposed to action. > >For now, info about ACTION will be conveyed via the yello info box that > >pops up when you leave the mouse over the icon. > > This text is controlled by the TITLE element of the <A> tag. I *think* this > behavior may vary, depending on the browser & platform. In some instances > the ALT text of the IMG (which is *inside* the <A> tag) is displayed instead > of the link's title. AFAIK, this *is not* controlled by TIki. OK. So we need to specify the information about the button in both place. Thx for the info. > If it is truly this confusing, Believe me, it is! I have seen it many times. > why not simply remove the icon completely and > use a simple drop list (like we do for backlinks) with two options: > - Watch this page. (i.e., the current state is "not watching") > - Stop watching this page (i.e., the current state is "watching") Actually, that sounds like a good idea. But we need to be careful about not using too much real-estate. What about a short picklist with two elements: On, Off, with an eye icon right in front of it. And surround the pair with a border so that it is clear that they go together. Alain ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by Jonny Bradley-2
::
Rate this Message:
On 5 Nov 2009, at 13:39, Marc Laporte wrote: > Once guidelines are set, devs will be happy to have something to > follow. Especially if you can summarise! :) (we are talking about this for 4.1 or 5 aren't we?) jb ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by alain_desilets
::
Rate this Message:
There are two types of widgets we have been talking about.
- A widget for setting something on or off. - A widget for doing multiple selects. I have a pretty good handle on the first. Still need to try a couple of things, but when done, I will summarize. For the multiple select, I think the article that Marc pointed to is a perfect summary. We just have to choose the one we think is best. Alain -----Original Message----- From: Jonny Bradley [mailto:tw@...] Sent: Thursday, November 05, 2009 9:24 AM To: Tikiwiki developers Subject: Re: [Tikiwiki-devel] The proverbial watch icon On 5 Nov 2009, at 13:39, Marc Laporte wrote: > Once guidelines are set, devs will be happy to have something to > follow. Especially if you can summarise! :) (we are talking about this for 4.1 or 5 aren't we?) jb ------------------------------------------------------------------------ ------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by Rick Sapir-3
::
Rate this Message:
I don't see how a drop list will cost any real estate at all (other than a
few pixels for the arrow). See attached samples: eye1.gif: User is currently watching the page (as noted by the "watch is on" icon). Drop list has 2 choices, but only one is valid. The only possible action is to *stop* watching. eye1.gif: User is currently not watching the page (as noted by the "watch is off" icon). The only possible action is to *start* watching. -R --- Greetings from Sanford, NC, USA! ----- Original Message ----- From: "Desilets, Alain" <Alain.Desilets@...> To: "Rick Sapir" <rick.sapir@...>; "Tikiwiki developers" <tikiwiki-devel@...> Sent: Thursday, November 05, 2009 9:08 AM Subject: RE: [Tikiwiki-devel] The proverbial watch icon > Just my opinion, but I expect buttons in a button bar to perform an > action. Opening a menu IS an action no. There are plenty of examples of buttons that open up something which allows you to further specify the details of the action you want to happen. As I am writing this message in Outlook, I see a "To..." button. When I click on it, I get a dialog box where I can choose the addressees. That's not that different from clicking on an eye icon and getting a popup menu where I can say whether I want the traces to be on or off. > I disagree. I think the icon should continue to convey the ACTION. The STATE > can *easily* be inferred based on the action. For example, if the action is > "Start watching this page." then the current status is obviously "not > watching." I have observed many users in the course of training sessions, or in the course of starting a tiki site and supporting users by email at the beginning, and my experience contradicts what you say. Users do not find this obvious, even with the yellow info box (which, btw only shows up when you hover the mouse over the icon). Furthermore, my (admittedly very small) survey indicates that even when you tell people that the icon refers to an action (not to the state), they are confused about what action it refers too (whereas they are always clear about what state it might refer to). Hence, my recommendation that, in the case of a toggle, we use the look of the icon to convey state as opposed to action. > >For now, info about ACTION will be conveyed via the yello info box that > >pops up when you leave the mouse over the icon. > > This text is controlled by the TITLE element of the <A> tag. I *think* this > behavior may vary, depending on the browser & platform. In some instances > the ALT text of the IMG (which is *inside* the <A> tag) is displayed instead > of the link's title. AFAIK, this *is not* controlled by TIki. OK. So we need to specify the information about the button in both place. Thx for the info. > If it is truly this confusing, Believe me, it is! I have seen it many times. > why not simply remove the icon completely and > use a simple drop list (like we do for backlinks) with two options: > - Watch this page. (i.e., the current state is "not watching") > - Stop watching this page (i.e., the current state is "watching") Actually, that sounds like a good idea. But we need to be careful about not using too much real-estate. What about a short picklist with two elements: On, Off, with an eye icon right in front of it. And surround the pair with a border so that it is clear that they go together. Alain ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by alain_desilets
::
Rate this Message:
OK. I thought you meant a drop list like the one that displays English in your screenshots. These drop lists usually take as much space as the longest of the strings they contain.
I now see that you meant an icon which functions as a drop list, and has a little down pointing arrow to indicate that. I very much like it!!! In fact, it's functionally equivalent to what I was describing earlier, i.e. a button which opens a pop-up menu when you click on it. But the downward pointing triangle is an improvement because it clearly suggests that this icon is a picklist. One thing I would add, How would I go about implementing this? Is is standard HTML stuff, or would I be using some of the things that Stéphane refers to in his emails? Alain -----Original Message----- From: Rick Sapir [mailto:rick.sapir@...] Sent: Thursday, November 05, 2009 10:35 AM To: Desilets, Alain; Tikiwiki developers Subject: Re: [Tikiwiki-devel] The proverbial watch icon I don't see how a drop list will cost any real estate at all (other than a few pixels for the arrow). See attached samples: eye1.gif: User is currently watching the page (as noted by the "watch is on" icon). Drop list has 2 choices, but only one is valid. The only possible action is to *stop* watching. eye1.gif: User is currently not watching the page (as noted by the "watch is off" icon). The only possible action is to *start* watching. -R --- Greetings from Sanford, NC, USA! ----- Original Message ----- From: "Desilets, Alain" <Alain.Desilets@...> To: "Rick Sapir" <rick.sapir@...>; "Tikiwiki developers" <tikiwiki-devel@...> Sent: Thursday, November 05, 2009 9:08 AM Subject: RE: [Tikiwiki-devel] The proverbial watch icon > Just my opinion, but I expect buttons in a button bar to perform an > action. Opening a menu IS an action no. There are plenty of examples of buttons that open up something which allows you to further specify the details of the action you want to happen. As I am writing this message in Outlook, I see a "To..." button. When I click on it, I get a dialog box where I can choose the addressees. That's not that different from clicking on an eye icon and getting a popup menu where I can say whether I want the traces to be on or off. > I disagree. I think the icon should continue to convey the ACTION. The STATE > can *easily* be inferred based on the action. For example, if the action is > "Start watching this page." then the current status is obviously "not > watching." I have observed many users in the course of training sessions, or in the course of starting a tiki site and supporting users by email at the beginning, and my experience contradicts what you say. Users do not find this obvious, even with the yellow info box (which, btw only shows up when you hover the mouse over the icon). Furthermore, my (admittedly very small) survey indicates that even when you tell people that the icon refers to an action (not to the state), they are confused about what action it refers too (whereas they are always clear about what state it might refer to). Hence, my recommendation that, in the case of a toggle, we use the look of the icon to convey state as opposed to action. > >For now, info about ACTION will be conveyed via the yello info box that > >pops up when you leave the mouse over the icon. > > This text is controlled by the TITLE element of the <A> tag. I *think* this > behavior may vary, depending on the browser & platform. In some instances > the ALT text of the IMG (which is *inside* the <A> tag) is displayed instead > of the link's title. AFAIK, this *is not* controlled by TIki. OK. So we need to specify the information about the button in both place. Thx for the info. > If it is truly this confusing, Believe me, it is! I have seen it many times. > why not simply remove the icon completely and > use a simple drop list (like we do for backlinks) with two options: > - Watch this page. (i.e., the current state is "not watching") > - Stop watching this page (i.e., the current state is "watching") Actually, that sounds like a good idea. But we need to be careful about not using too much real-estate. What about a short picklist with two elements: On, Off, with an eye icon right in front of it. And surround the pair with a border so that it is clear that they go together. Alain ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by Rick Sapir-3
::
Rate this Message:
I assume we can use the same implementation that is used in File Gallery for
the pop-up drop-list for the Action (when listing file galleries). -R --- Greetings from Sanford, NC, USA! ----- Original Message ----- From: "Desilets, Alain" <Alain.Desilets@...> To: "Rick Sapir" <rick.sapir@...>; "Tikiwiki developers" <tikiwiki-devel@...> Sent: Thursday, November 05, 2009 10:49 AM Subject: RE: [Tikiwiki-devel] The proverbial watch icon OK. I thought you meant a drop list like the one that displays English in your screenshots. These drop lists usually take as much space as the longest of the strings they contain. I now see that you meant an icon which functions as a drop list, and has a little down pointing arrow to indicate that. I very much like it!!! In fact, it's functionally equivalent to what I was describing earlier, i.e. a button which opens a pop-up menu when you click on it. But the downward pointing triangle is an improvement because it clearly suggests that this icon is a picklist. One thing I would add, How would I go about implementing this? Is is standard HTML stuff, or would I be using some of the things that Stéphane refers to in his emails? Alain ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by Rick Sapir-3
::
Rate this Message:
>
>How would I go about implementing this? Is is standard HTML stuff, or would >I be using some of the things that Stéphane refers to in his emails? > Can't we reuse the same implementation that the File Gallery has? When you list galleries, the Action icon is a pop-up/droplist menu. -R --- Greetings from Sanford, NC, USA! ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by luci aka luciash d' being
::
Rate this Message:
hi,
sorry, i don't see the icon samples in the docx :( luci On 11/05/2009 11:45 AM, Desilets, Alain wrote: > I got responses from about a dozen folks. As I feared, no one icon pair > is 100% clear. Here are things that came out fairly clearly. > > == 1. None of the icons is good at clearly conveying ACTION == > > When you ask folks what ACTION will happen when you click on a given > icon, there is typically a 50-50 split between those who think watches > will be turned on, and those who think they will be turned off. The one > exception is Icon 7, the eye with a green plus sign, which everyone > interprets as meaning that watches will be turned on. > > == 2. All icons are pretty good at clearly conveying STATE == > > When you ask folks what STATE a particular icon represents, they are > typically unanimous in their response. > > == 3. None of the icons are good a conveying STATE and ACTION that are > consisten with each other === > > The unanimous STATE interpretation of an icon is always the opposite of > the ACTION interpretation that was chosen by the majority (if there was > a majority). > > == What to do? == > > Here's what I propose to do. > > Use icons to convey informattion about the STATE of watches (since at > least, STATE is interpreted consistently by users), and use some other > more explicit form of feedback to convey information about ACTION. > > For now, info about ACTION will be conveyed via the yello info box that > pops up when you leave the mouse over the icon. It will say something > more explicit like: > > Watches are <b>ON</b>. Click on icon to turn them <b>OFF</b> > > but eventually, I would like to make it so that, when you click on the > icon, you see a pop-up menu like this: > > X Turn Watches <b>ON</b> > Turn Watches <b>OFF</b> > > where the X represents a check mark indicating which of the two options > are currently active. > > I don't know if we have a way in Tiki to support this kind of pop-up > window, but if so, please guide me to where I can find it. For now, i > will go with the info pop-up approach. > > Note that the pop-up menu will mean an additional click for the user. In > this case, I think it's warranted because: > > (i) the watch icon is causing lots of confusion, partly because of the > STATE/ACTION contradiction, but also because final confirmation may be > sloww to come (you only know that the traces are indeed on when you get > your first change notificaion) > > (ii) setting watches on is not as frequent an action as, say, editing a > page. > > > > ------------------------------------------- > > Modern Hosting PIPNI - http://www.pipni.cz/ > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > ------------------------------------------------------------------------ > > _______________________________________________ > Tikiwiki-devel mailing list > Tikiwiki-devel@... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: The proverbial watch icon
by Marc Laporte-3
::
Rate this Message:
Everyone:
We are about to decide. Last chance to express opinons: http://dev.tikiwiki.org/WatchIcon Thanks! M ;-) On Thu, Nov 5, 2009 at 3:02 PM, luci aka luciash d' being <sf@...> wrote: > hi, > > sorry, i don't see the icon samples in the docx :( > > luci > > > On 11/05/2009 11:45 AM, Desilets, Alain wrote: >> I got responses from about a dozen folks. As I feared, no one icon pair >> is 100% clear. Here are things that came out fairly clearly. >> >> == 1. None of the icons is good at clearly conveying ACTION == >> >> When you ask folks what ACTION will happen when you click on a given >> icon, there is typically a 50-50 split between those who think watches >> will be turned on, and those who think they will be turned off. The one >> exception is Icon 7, the eye with a green plus sign, which everyone >> interprets as meaning that watches will be turned on. >> >> == 2. All icons are pretty good at clearly conveying STATE == >> >> When you ask folks what STATE a particular icon represents, they are >> typically unanimous in their response. >> >> == 3. None of the icons are good a conveying STATE and ACTION that are >> consisten with each other === >> >> The unanimous STATE interpretation of an icon is always the opposite of >> the ACTION interpretation that was chosen by the majority (if there was >> a majority). >> >> == What to do? == >> >> Here's what I propose to do. >> >> Use icons to convey informattion about the STATE of watches (since at >> least, STATE is interpreted consistently by users), and use some other >> more explicit form of feedback to convey information about ACTION. >> >> For now, info about ACTION will be conveyed via the yello info box that >> pops up when you leave the mouse over the icon. It will say something >> more explicit like: >> >> Watches are <b>ON</b>. Click on icon to turn them <b>OFF</b> >> >> but eventually, I would like to make it so that, when you click on the >> icon, you see a pop-up menu like this: >> >> X Turn Watches <b>ON</b> >> Turn Watches <b>OFF</b> >> >> where the X represents a check mark indicating which of the two options >> are currently active. >> >> I don't know if we have a way in Tiki to support this kind of pop-up >> window, but if so, please guide me to where I can find it. For now, i >> will go with the info pop-up approach. >> >> Note that the pop-up menu will mean an additional click for the user. In >> this case, I think it's warranted because: >> >> (i) the watch icon is causing lots of confusion, partly because of the >> STATE/ACTION contradiction, but also because final confirmation may be >> sloww to come (you only know that the traces are indeed on when you get >> your first change notificaion) >> >> (ii) setting watches on is not as frequent an action as, say, editing a >> page. >> >> >> >> ------------------------------------------- >> >> Modern Hosting PIPNI - http://www.pipni.cz/ >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Tikiwiki-devel mailing list >> Tikiwiki-devel@... >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >> > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Tikiwiki-devel mailing list > Tikiwiki-devel@... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > -- Marc Laporte http://MarcLaporte.com http://TikiWiki.org/MarcLaporte http://AvanTech.net http://OurWiki.net ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Dogfood Question
by Eric Kelner, P.E.
::
Rate this Message:
Hi All:
I just read the Watch Icon discussion and have a question. Why isn't the comments feature being used? Everyone is just editing the wiki page. It seems that the comment feature would be the best way to capture the discussion, then you could rank ideas by scoring the comments. Since it's a discussion by tiki developers, it's interesting that it isn't used. Just an observation. BTW, how about using the "poll" feature to vote on User Watch proposals? Eric Eric Kelner, P.E. Vice President Letton-Hall Group 210-372-0830 (Office) 210-875-6277 (Cell) www.letton-hall.com ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: Dogfood Question
by alain_desilets
::
Rate this Message:
Could have done it that way. Personally, I find comments are mostly good
to allow users to rapidly post casual comments on a page. Alain -----Original Message----- From: Eric Kelner, P.E. [mailto:kelner@...] Sent: Thursday, December 17, 2009 1:34 PM To: Tikiwiki developers Subject: [Tikiwiki-devel] Dogfood Question Hi All: I just read the Watch Icon discussion and have a question. Why isn't the comments feature being used? Everyone is just editing the wiki page. It seems that the comment feature would be the best way to capture the discussion, then you could rank ideas by scoring the comments. Since it's a discussion by tiki developers, it's interesting that it isn't used. Just an observation. BTW, how about using the "poll" feature to vote on User Watch proposals? Eric Eric Kelner, P.E. Vice President Letton-Hall Group 210-372-0830 (Office) 210-875-6277 (Cell) www.letton-hall.com ------------------------------------------------------------------------ ------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
|
|
|
Re: Dogfood Question
by regis.barondeau
::
Rate this Message:
I like this idea Erik. As you said, we could turn it into a hybrid event, on site and online, webminar style. May be backed by a special section in doc to create a case study/training repository. I also think linking it to TikiFest could be a good think. Exchanges between users, admins and dev can theoretically create value, even it is not always easy to mix the cultures.
I was not available a lot this year for Tiki do to my thesis writing, it should be better for the first half of 2010 and I would like to contribute to those events. Régis On 2009-12-18, at 12:01 PM, Eric Kelner, P.E. wrote: > Good comments. In general, I'm wondering if the developer community > dogfood experience is different than the "regular" users' and admins' > experiences. I suppose it is, since developers are far more familiar > with the code. Has there ever been a Tikifest focused on applications, > rather than development? I'd like to learn how others are implementing > the tool. I'd also like to learn some admin tricks. I'm probably > missing a lot of good stuff. I recall seeing a brief user's > presentation at a Tikifest awhile back, but I'm thinking it might be > worth a one-day user's symposium or roundtable, maybe on the front-end > of a Tikifest. Participants could post discussion questions/topics (on > a wiki page, of course) ahead of time. Users/Admins could give brief > (15 minute) overviews of their sites, followed by discussion for, say 45 > minutes, providing a lot of discussion time. Being on the front end of > a Tikifest, it may also stimulate developer discussion. If the concept > were to catch on, I can envision possible on-line interactive training > sessions and Q/A for new users as well. > > Off the top of my head, here's a possible agenda. Ideally, each > application would be completely different in its approach. > > 8:00 - Opening and Introductions > 8:15-9:30 - Discussion/User Questions > 9:30-9:45 - Tiki Application #1 Presentation > 9:45-10:30 - Discuss Application #1 > 10:30-10:45 - Break > 10:45-11:00 - Tiki Application #2 Presentation > 11:00-11:45 - Discuss Application #2 > 11:45-1:00 - Lunch > 1:00-2:30 - Admin Tips, Tricks and Techniques > 2:30-2:45 - Tiki Application #3 Presentation > 2:45-3:30 - Discuss Application #3 > 3:30-3:45 - Break > 3:45-4:00 - Tiki Application #4 Presentation > 4:00-4:45 - Discuss Application #4 > 4:45-5:00 - Closing Remarks/Adjourn > 5:30 - Happy Hour (Can't forget this!) > > I know user groups aren't a new idea. This one came to my mind as > something that seems to be missing. We could call it "TUG." I'd be > happy to take the lead if there's interest. If it's already happening > in one form or another, please let me know who the lead is. It also > wouldn't necessarily have to be done in coordination with a Tikifest - > that just seems convenient. > > Eric Kelner, P.E. > Vice President > Letton-Hall Group > 210-372-0830 (Office) > 210-875-6277 (Cell) > www.letton-hall.com > > > > Gary Cunningham-Lee wrote: >> I like the idea of doing the discussion within the wiki page itself, >> but often it isn't easy to see who said what and when they said it. >> (Probably people rely on the page history to keep track of >> contributions.) I suppose people work out some methods of formatting >> the page if this is important to see in-page (even something impromptu >> like how it was done at the doc.tw.o Editorial Board pages). >> >> Somebody asked in irc about if Tiki had in-page signatures like >> Mediawiki does. Apparently the author/editor can add a little syntax >> and then his/her name, the edit time, and some other info will be >> pasted in as text. It'd be good if Tiki had this also. And I was >> thinking it'd be interesting to think about taking this another step >> and maybe have something like a highlight background color on the >> person's contribution on mouseover, or meta information in a popup or >> something. Just hover around the page and see creation info >> colorfully. The downside would be no appearance of it when printed. >> >> -- Gary >> >> Desilets, Alain wrote: >>> Could have done it that way. Personally, I find comments are mostly good >>> to allow users to rapidly post casual comments on a page. >>> Alain >>> >>> -----Original Message----- >>> From: Eric Kelner, P.E. [mailto:kelner@...] Sent: >>> Thursday, December 17, 2009 1:34 PM >>> To: Tikiwiki developers >>> Subject: [Tikiwiki-devel] Dogfood Question >>> >>> Hi All: >>> >>> I just read the Watch Icon discussion and have a question. Why isn't >>> the comments feature being used? Everyone is just editing the wiki >>> page. It seems that the comment feature would be the best way to >>> capture the discussion, then you could rank ideas by scoring the >>> comments. Since it's a discussion by tiki developers, it's >>> interesting that it isn't used. Just an observation. >>> >>> BTW, how about using the "poll" feature to vote on User Watch >>> proposals? >>> >>> Eric >>> >>> Eric Kelner, P.E. >>> Vice President >>> Letton-Hall Group >>> 210-372-0830 (Office) >>> 210-875-6277 (Cell) >>> >>> www.letton-hall.com >>> >>> >>> >>> ------------------------------------------------------------------------ >>> ------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Tikiwiki-devel mailing list >>> Tikiwiki-devel@... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >>> >>> ------------------------------------------------------------------------------ >>> >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast >>> and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Tikiwiki-devel mailing list >>> Tikiwiki-devel@... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >>> >>> ------------------------------------------------------------------------ >>> >>> >>> No virus found in this incoming message. >>> Checked by AVG - www.avg.com Version: 9.0.716 / Virus Database: >>> 270.14.112/2571 - Release Date: 12/18/09 04:40:00 >>> >>> >> >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Tikiwiki-devel mailing list > Tikiwiki-devel@... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: Dogfood Question
by alain_desilets
::
Rate this Message:
What a great idea Eric!
Alain -----Original Message----- From: Eric Kelner, P.E. [mailto:kelner@...] Sent: Friday, December 18, 2009 12:02 PM To: Gary Cunningham-Lee Cc: Tikiwiki developers Subject: Re: [Tikiwiki-devel] Dogfood Question Good comments. In general, I'm wondering if the developer community dogfood experience is different than the "regular" users' and admins' experiences. I suppose it is, since developers are far more familiar with the code. Has there ever been a Tikifest focused on applications, rather than development? I'd like to learn how others are implementing the tool. I'd also like to learn some admin tricks. I'm probably missing a lot of good stuff. I recall seeing a brief user's presentation at a Tikifest awhile back, but I'm thinking it might be worth a one-day user's symposium or roundtable, maybe on the front-end of a Tikifest. Participants could post discussion questions/topics (on a wiki page, of course) ahead of time. Users/Admins could give brief (15 minute) overviews of their sites, followed by discussion for, say 45 minutes, providing a lot of discussion time. Being on the front end of a Tikifest, it may also stimulate developer discussion. If the concept were to catch on, I can envision possible on-line interactive training sessions and Q/A for new users as well. Off the top of my head, here's a possible agenda. Ideally, each application would be completely different in its approach. 8:00 - Opening and Introductions 8:15-9:30 - Discussion/User Questions 9:30-9:45 - Tiki Application #1 Presentation 9:45-10:30 - Discuss Application #1 10:30-10:45 - Break 10:45-11:00 - Tiki Application #2 Presentation 11:00-11:45 - Discuss Application #2 11:45-1:00 - Lunch 1:00-2:30 - Admin Tips, Tricks and Techniques 2:30-2:45 - Tiki Application #3 Presentation 2:45-3:30 - Discuss Application #3 3:30-3:45 - Break 3:45-4:00 - Tiki Application #4 Presentation 4:00-4:45 - Discuss Application #4 4:45-5:00 - Closing Remarks/Adjourn 5:30 - Happy Hour (Can't forget this!) I know user groups aren't a new idea. This one came to my mind as something that seems to be missing. We could call it "TUG." I'd be happy to take the lead if there's interest. If it's already happening in one form or another, please let me know who the lead is. It also wouldn't necessarily have to be done in coordination with a Tikifest - that just seems convenient. Eric Kelner, P.E. Vice President Letton-Hall Group 210-372-0830 (Office) 210-875-6277 (Cell) www.letton-hall.com Gary Cunningham-Lee wrote: > I like the idea of doing the discussion within the wiki page itself, > but often it isn't easy to see who said what and when they said it. > (Probably people rely on the page history to keep track of > contributions.) I suppose people work out some methods of formatting > the page if this is important to see in-page (even something impromptu > like how it was done at the doc.tw.o Editorial Board pages). > > Somebody asked in irc about if Tiki had in-page signatures like > Mediawiki does. Apparently the author/editor can add a little syntax > and then his/her name, the edit time, and some other info will be > pasted in as text. It'd be good if Tiki had this also. And I was > thinking it'd be interesting to think about taking this another step > and maybe have something like a highlight background color on the > person's contribution on mouseover, or meta information in a popup or > something. Just hover around the page and see creation info > colorfully. The downside would be no appearance of it when printed. > > -- Gary > > Desilets, Alain wrote: >> Could have done it that way. Personally, I find comments are mostly >> to allow users to rapidly post casual comments on a page. >> Alain >> >> -----Original Message----- >> From: Eric Kelner, P.E. [mailto:kelner@...] Sent: >> Thursday, December 17, 2009 1:34 PM >> To: Tikiwiki developers >> Subject: [Tikiwiki-devel] Dogfood Question >> >> Hi All: >> >> I just read the Watch Icon discussion and have a question. Why isn't >> the comments feature being used? Everyone is just editing the wiki >> page. It seems that the comment feature would be the best way to >> capture the discussion, then you could rank ideas by scoring the >> comments. Since it's a discussion by tiki developers, it's >> interesting that it isn't used. Just an observation. >> >> BTW, how about using the "poll" feature to vote on User Watch >> proposals? >> >> Eric >> >> Eric Kelner, P.E. >> Vice President >> Letton-Hall Group >> 210-372-0830 (Office) >> 210-875-6277 (Cell) >> >> www.letton-hall.com >> >> >> >> >> ------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Tikiwiki-devel mailing list >> Tikiwiki-devel@... >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >> >> ------------------------------------------------------------------------ ------ >> >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast >> and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Tikiwiki-devel mailing list >> Tikiwiki-devel@... >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >> >> >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com Version: 9.0.716 / Virus Database: >> 270.14.112/2571 - Release Date: 12/18/09 04:40:00 >> >> > > ------------------------------------------------------------------------ ------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: Dogfood Question
by gary_c
::
Rate this Message:
I've thought for a long time that we're really missing information about
how to take the next steps after Tiki is installed and initially configured. One area that would be good to collect/share information about is how to get various layouts within a wiki page, how to place headings, images and text so it looks like a nice HTML page, how to make columns, how to use plugins (more details, with live examples and discussions, etc.). This would supplement doc.tw.o, which is, I think, best limited to reference and basic getting-started information. New people also ask things like when should I use a wiki page and when an article, things on that level. Well, I thought mods.tikiwiki.org would be good for this, if it could be a Tiki installation, in the sense of continuing from where the basics of doc.tw.o leave off. This kind of information overlaps some of what I've done at themes.tw.o (like http://themes.tikiwiki.org/Floated%20box%20demo) but would also get into use cases, and so there's also the connection with Profiles. Anyway, one way or the other, the more this kind of information can be provided, the more new people will see what Tiki is capable of, etc. And it'd be a good place for contribution from experienced users who aren't developers, since it's about using the software and not about the code. -- Gary Desilets, Alain wrote: > What a great idea Eric! > > Alain > > -----Original Message----- > From: Eric Kelner, P.E. [mailto:kelner@...] > Sent: Friday, December 18, 2009 12:02 PM > To: Gary Cunningham-Lee > Cc: Tikiwiki developers > Subject: Re: [Tikiwiki-devel] Dogfood Question > > Good comments. In general, I'm wondering if the developer community > dogfood experience is different than the "regular" users' and admins' > experiences. I suppose it is, since developers are far more familiar > with the code. Has there ever been a Tikifest focused on applications, > rather than development? I'd like to learn how others are implementing > the tool. I'd also like to learn some admin tricks. I'm probably > missing a lot of good stuff. I recall seeing a brief user's > presentation at a Tikifest awhile back, but I'm thinking it might be > worth a one-day user's symposium or roundtable, maybe on the front-end > of a Tikifest. Participants could post discussion questions/topics (on > a wiki page, of course) ahead of time. Users/Admins could give brief > (15 minute) overviews of their sites, followed by discussion for, say 45 > > minutes, providing a lot of discussion time. Being on the front end of > a Tikifest, it may also stimulate developer discussion. If the concept > were to catch on, I can envision possible on-line interactive training > sessions and Q/A for new users as well. > > Off the top of my head, here's a possible agenda. Ideally, each > application would be completely different in its approach. > > 8:00 - Opening and Introductions > 8:15-9:30 - Discussion/User Questions > 9:30-9:45 - Tiki Application #1 Presentation > 9:45-10:30 - Discuss Application #1 > 10:30-10:45 - Break > 10:45-11:00 - Tiki Application #2 Presentation > 11:00-11:45 - Discuss Application #2 > 11:45-1:00 - Lunch > 1:00-2:30 - Admin Tips, Tricks and Techniques > 2:30-2:45 - Tiki Application #3 Presentation > 2:45-3:30 - Discuss Application #3 > 3:30-3:45 - Break > 3:45-4:00 - Tiki Application #4 Presentation > 4:00-4:45 - Discuss Application #4 > 4:45-5:00 - Closing Remarks/Adjourn > 5:30 - Happy Hour (Can't forget this!) > > I know user groups aren't a new idea. This one came to my mind as > something that seems to be missing. We could call it "TUG." I'd be > happy to take the lead if there's interest. If it's already happening > in one form or another, please let me know who the lead is. It also > wouldn't necessarily have to be done in coordination with a Tikifest - > that just seems convenient. > > Eric Kelner, P.E. > Vice President > Letton-Hall Group > 210-372-0830 (Office) > 210-875-6277 (Cell) > www.letton-hall.com > > > > Gary Cunningham-Lee wrote: >> I like the idea of doing the discussion within the wiki page itself, >> but often it isn't easy to see who said what and when they said it. >> (Probably people rely on the page history to keep track of >> contributions.) I suppose people work out some methods of formatting >> the page if this is important to see in-page (even something impromptu > >> like how it was done at the doc.tw.o Editorial Board pages). >> >> Somebody asked in irc about if Tiki had in-page signatures like >> Mediawiki does. Apparently the author/editor can add a little syntax >> and then his/her name, the edit time, and some other info will be >> pasted in as text. It'd be good if Tiki had this also. And I was >> thinking it'd be interesting to think about taking this another step >> and maybe have something like a highlight background color on the >> person's contribution on mouseover, or meta information in a popup or >> something. Just hover around the page and see creation info >> colorfully. The downside would be no appearance of it when printed. >> >> -- Gary >> >> Desilets, Alain wrote: >>> Could have done it that way. Personally, I find comments are mostly > good >>> to allow users to rapidly post casual comments on a page. >>> Alain >>> >>> -----Original Message----- >>> From: Eric Kelner, P.E. [mailto:kelner@...] Sent: >>> Thursday, December 17, 2009 1:34 PM >>> To: Tikiwiki developers >>> Subject: [Tikiwiki-devel] Dogfood Question >>> >>> Hi All: >>> >>> I just read the Watch Icon discussion and have a question. Why isn't > >>> the comments feature being used? Everyone is just editing the wiki >>> page. It seems that the comment feature would be the best way to >>> capture the discussion, then you could rank ideas by scoring the >>> comments. Since it's a discussion by tiki developers, it's >>> interesting that it isn't used. Just an observation. >>> >>> BTW, how about using the "poll" feature to vote on User Watch >>> proposals? >>> >>> Eric >>> >>> Eric Kelner, P.E. >>> Vice President >>> Letton-Hall Group >>> 210-372-0830 (Office) >>> 210-875-6277 (Cell) >>> >>> www.letton-hall.com >>> >>> >>> >>> > ------------------------------------------------------------------------ >>> ------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast > and >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Tikiwiki-devel mailing list >>> Tikiwiki-devel@... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >>> >>> > ------------------------------------------------------------------------ > ------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast >>> and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Tikiwiki-devel mailing list >>> Tikiwiki-devel@... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >>> >>> > ------------------------------------------------------------------------ >>> >>> No virus found in this incoming message. >>> Checked by AVG - www.avg.com Version: 9.0.716 / Virus Database: >>> 270.14.112/2571 - Release Date: 12/18/09 04:40:00 >>> >>> >> > > ------------------------------------------------------------------------ > ------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Tikiwiki-devel mailing list > Tikiwiki-devel@... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Tikiwiki-devel mailing list > Tikiwiki-devel@... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.717 / Virus Database: 270.14.114/2574 - Release Date: 12/19/09 04:38:00 > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
Watches icon survey.docx (27K) 
| Free embeddable forum powered by Nabble | Forum Help |
