Wiki Cabinet template

[Generic Eric]

I have a suggestion that would make reviewing completed projects easier.  If everyone could include the start date, and finish date, and a link to their project thread, well, that would be great.  Here is an example:

Project Type:
Construction Method:
Monitor Type:
Interface Type:
Special Controls:
OS:
Front End:
Start date:
Completion date:
Project thread:


Thanks for considering. 

[PL1]

Thanks for bringing up the subject, GE.   

All the recently-added examples should already have a link to the build thread. (sometimes to a homepage)

I like the idea of adding a line for the FE.   

Instead of
  Start date:
  Completion date:

How about
  Build date(s):

This makes it easier when only some of the date info is known. (Besides, do specific dates matter on a build from years ago?)

As long as we can at least ball-park it to the nearest year, that's enough to add it to the correct section of the "Builds (by year)" Examples page.

The Upright Examples page is just too overwhelming (600+ cabs  ) to go through each one individually at this time, so I've been adding new and updating older ones from "Builds (by year)" in Upright Examples with larger thumbnails to indicate which ones on that page have been reviewed and updated.

If anyone knows a particular build from "Upright" that would help round out "Builds (by year)", please feel free to update/add it.

Since we're talking about updating the template, should "Interface Type:" be changed to "Encoder Type:"?

Project Type:
Construction Method:
Monitor Type:
Encoder Type:            Interface Type:
Special Controls:
OS:
Front End:
Build Date(s):              Start date:
                                  Completion date:
Project Thread: (or Build Thread: ?)

Scott

[Generic Eric]

Well, I've counted  over 100 examples that were finished in the last year, I've got about 4 pages to go through.   Unfortunately, not everyone made a formal  declaration of complete or finished, so I've come to that conclusion manually by going through each thread.

Regarding the FE entry  that was copy pasta from an example.

Interface type works better.

[PL1]

Interface type works better.

Encoder is the more common term, but it's less effort to leave it as Interface.   

Are you actually planning on adding every one of those 100+ builds to the wiki examples??!!??   

Seems like a smaller sample size (maybe 10-20% with a focus on innovative/unique features) could make it easier for both the editor and the readers.


Scott

[Generic Eric]

Interface type works better.

Encoder is the more common term, but it's less effort to leave it as Interface.   

Now that I am on the PC, not the phone, hopefully I can manage typing better.  I suggested interface, because sometimes a keyboard is hacked.  *shrug* Either way, both get the message across.

Interface type works better.

Are you actually planning on adding every one of those 100+ builds to the wiki examples??!!??   

Seems like a smaller sample size (maybe 10-20% with a focus on innovative/unique features) could make it easier for both the editor and the readers.

Scott

Point taken.  I am thinning the herd in my review of projects.  Not everyone is HOF/UCA worthy, but I didn't do my review last year and didn't make any nominations.  Lots of the projects appear unfinished when looking at their thread, but some were just a marquee or sideart away from being complete according to their thread.   

[PL1]

Interface type works better.

Encoder is the more common term, but it's less effort to leave it as Interface.   

Now that I am on the PC, not the phone, hopefully I can manage typing better.  I suggested interface, because sometimes a keyboard is hacked.  *shrug* Either way, both get the message across.

a hacked keyboard or gamepad is still an encoder.   
[/nitpicking]


Scott

[Generic Eric]

Interface type works better.

Encoder is the more common term, but it's less effort to leave it as Interface.   

Now that I am on the PC, not the phone, hopefully I can manage typing better.  I suggested interface, because sometimes a keyboard is hacked.  *shrug* Either way, both get the message across.

a hacked keyboard or gamepad is still an encoder.   
[/nitpicking]


Scott

   lets go with encoder than. 

[PL1]

How about the dates?

One line or two?

"Project Thread:" or "Build Thread:"?

Project Type:
Construction Method:
Monitor Type:
Encoder Type:
Special Controls:
OS:
Front End:
Build Date(s):              Start date:
                                  Completion date:
Project Thread: (or Build Thread: ?)

Scott

[Generic Eric]

How about the dates?

One line or two?

"Project Thread:" or "Build Thread:"?

Project Type:
Construction Method:
Monitor Type:
Encoder Type:
Special Controls:
OS:
Front End:
Build Date(s):              Start date:
                                  Completion date:
Project Thread: (or Build Thread: ?)

Scott

I like the idea of having both, even if they are on the same line.   

[PL1]

Does that mean that "Build Date(s):" works, or do you think that separate "Start date:" and "Completion date:" lines are needed?

Also, which is better: "Project Thread:" or "Build Thread:"?


Scott

[Generic Eric]

Does that mean that "Build Date(s):" works, or do you think that separate "Start date:" and "Completion date:" lines are needed?

Also, which is better: "Project Thread:" or "Build Thread:"?


Scott

Dates on a line are fine.

"Project Announcement thread" may help point the submitter to the project forum.

[PL1]

"Project Announcement thread" may help point the submitter to the project forum.

That's why I started using "Build Thread:" which encourages linking to the forums instead of "Homepage:" which implies a page that it is hosted at another domain.   

Adding "Announcement" to "Project Thread:" seems unnecessary IMHO since:
  1. They didn't just announce it, they finished the build, and
  2. The link is probably going to take them to that sub-forum anyway.

"Project Thread:" or "Build Thread:"?


Scott

[PL1]

Anyone have any other suggestions before we start updating the wiki build pages?

Project Type:
Construction Method:
Monitor Type:
Encoder Type:
Special Controls:
OS:
Front End:
Build Date(s):
Build Thread:  or  Project Thread:  ?

Scott

[PL1]

One other thing to consider.

Both Americans and Europeans frequently visit the forums.

This could cause confusion over whether 01/10/13 means January 10th or October first of 2013.

To avoid confusion and keep the date entries a standard length, I suggest that we use a date format ike this for the Build Date(s):

  01 Oct 2013

Any objections/alternatives? (October 01, 2013?)


Scott

[Louis Tully]

.

[PL1]

Is there a "tag" or icon that can be applied to a thread here on the forum once the project is finished? I sometimes see new threads with an icon to the left and think if that field can be applied to the search function, finding finished/completed projects would be a lot easier.

The first column icons tell you if you posted in the thread, # of replies (15 or less, >15, or >25), whether it contains a poll, is locked, or is stickied.

The second column "Message icon:" is selectable by each poster, like CheffoJeffo did here with the icon.

Not sure how to make the Message icons searchable or even if it is possible to do.   

Might be easier if you find a suitable tagging mod/plugin over at the SMF forums and suggest it to Saint.

Either way, it's going to require Admin action that we lowly Mods can not do. ('cuz we'd probably break the whole site worse than Tapatalk is broken now  )


Scott