Talk:Plugin: Difference between revisions

From TotalcmdWiki
Jump to navigation Jump to search
m (Call out to plugin authors perhaps?)
(Forced TOC. Removed category Wiki discussions.)
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__FORCETOC__
== Plugins list? ==
--[[User:Fenixproductions|Fenixproductions]] 2 Sept 2008
I've created different plugins list and I am thinking about adding it to wiki.
What does anybody think about it?
Would it be better to create completely new page with listing or add proper tables to plugins types pages (Content, Packer, ...)?
PS. List can be seen here:
http://fenixproductions.aspnet.pl/TCplugslist.aspx
The fields which might be included are: Plugin name, filename, download...
I can provide CSV file to anyone with some ideas ;)
----
:--[[User:White|White]] 17:53, 3 September 2008 (EDT)
:I recommend the following:
:* Create new pages for list of content plugins, list of packer plugins, etc. That way the existing pages [[Content plugin]], [[Packer plugin]], etc. can explain the plugin type and the lists are on seperate pages. Since the plugin types are quite different from each other use seperate lists for each plugin type rather than one long list. That will also help to keep the page size down.
:* Like the Wikipedia guidelines, start the title with "List of". So in this case "List of content plugins", "List of packer plugins", etc. This works well in practice. It is easily distinguishable among the pages explaining the subjects of the lists and among category pages. Following this guideline will also help to guess a name of a page and go directly to a page by entering the name "List of .." in the searchbox and clicking the Go button.
:* Like the Wikipedia guidelines, do not use big tables but use a simple bulleted list instead and place details on a seperate page for each entry. Big tables are hard to maintain and many people won't understand how it works. It is likely to become a mess. Also users generally do not need detailed information of all plugins at once. More likely users need only detailed information of one plugin at a time. Details on seperate pages can be displayed in a uniform way by using a template to display them.
:* Alfabetically sort the list (on name) for easy access.
:* Do not include direct download links. Wikis are not very well suited for download links. Since everybody can edit the links, it's easy to point a download link to malware. Instead mention the homepage of the author (on the details page). This makes it much harder for bad people to fool people.
:See also [[Wincmd.ini]] and my suggestion on the talk page [[Talk:Wincmd.ini#Suggestion for a different approach]]
:Contact me if you want me to help (either on this discussion page, on [[User_talk:White|my user talk page]] or by using the [http://ghisler.ch/board/profile.php?mode=email&u=1956 e-mail button on my forum profile page]).
== Call out to plugin authors perhaps? ==
Tell them to add their plugins when they reach mature versions themselves? Or is this thought as an official-only list?
--[[User:AlleyKat|AlleyKat]] 18:54, 23 Oct 2005 (EST)
----
:Here could anyone announce plugin who want's to.
:[[User:Sheepdog|Sheepdog]] 24. October 2005 08:46 (GMT)
== (WCX),(WFX),(WLX) and (WDX) in the headlines of the existing pages ==
--[[User:Stance|Stance]] 13:51, 23 May 2005 (EST) Hello, I would like to have shown:(WCX),(WFX),(WLX) and (WDX) in the headlines of the existing pages.<br>
--[[User:Stance|Stance]] 13:51, 23 May 2005 (EST) Hello, I would like to have shown:(WCX),(WFX),(WLX) and (WDX) in the headlines of the existing pages.<br>
Don´t know if it´s possible to change titles without changes the links.<br>
Don´t know if it´s possible to change titles without changes the links.<br>
It is not so important, but for a reader maybe better. Kind regards, Stance.
It is not so important, but for a reader maybe better. Kind regards, Stance.


== Call out to plugin authors perhaps? ==
----
 
:If you use the 'move' or 'Verschieben' Tab in the head of the line you could rename the page and Wiki would create a redirect on the old page.


Tell them to add their plugins when they reach mature versions themselves? Or is this thought as an official-only list?
:Thus each links ends up in the new page.


--[[User:AlleyKat|AlleyKat]] 18:54, 23 Oct 2005 (EST)
:[[User:Sheepdog|Sheepdog]] 24. October 2005 08:46 (GMT)

Latest revision as of 12:17, 14 October 2009


Plugins list?

--Fenixproductions 2 Sept 2008

I've created different plugins list and I am thinking about adding it to wiki. What does anybody think about it?

Would it be better to create completely new page with listing or add proper tables to plugins types pages (Content, Packer, ...)?

PS. List can be seen here: http://fenixproductions.aspnet.pl/TCplugslist.aspx

The fields which might be included are: Plugin name, filename, download... I can provide CSV file to anyone with some ideas ;)


--White 17:53, 3 September 2008 (EDT)
I recommend the following:
  • Create new pages for list of content plugins, list of packer plugins, etc. That way the existing pages Content plugin, Packer plugin, etc. can explain the plugin type and the lists are on seperate pages. Since the plugin types are quite different from each other use seperate lists for each plugin type rather than one long list. That will also help to keep the page size down.
  • Like the Wikipedia guidelines, start the title with "List of". So in this case "List of content plugins", "List of packer plugins", etc. This works well in practice. It is easily distinguishable among the pages explaining the subjects of the lists and among category pages. Following this guideline will also help to guess a name of a page and go directly to a page by entering the name "List of .." in the searchbox and clicking the Go button.
  • Like the Wikipedia guidelines, do not use big tables but use a simple bulleted list instead and place details on a seperate page for each entry. Big tables are hard to maintain and many people won't understand how it works. It is likely to become a mess. Also users generally do not need detailed information of all plugins at once. More likely users need only detailed information of one plugin at a time. Details on seperate pages can be displayed in a uniform way by using a template to display them.
  • Alfabetically sort the list (on name) for easy access.
  • Do not include direct download links. Wikis are not very well suited for download links. Since everybody can edit the links, it's easy to point a download link to malware. Instead mention the homepage of the author (on the details page). This makes it much harder for bad people to fool people.
See also Wincmd.ini and my suggestion on the talk page Talk:Wincmd.ini#Suggestion for a different approach
Contact me if you want me to help (either on this discussion page, on my user talk page or by using the e-mail button on my forum profile page).

Call out to plugin authors perhaps?

Tell them to add their plugins when they reach mature versions themselves? Or is this thought as an official-only list?

--AlleyKat 18:54, 23 Oct 2005 (EST)


Here could anyone announce plugin who want's to.
Sheepdog 24. October 2005 08:46 (GMT)

(WCX),(WFX),(WLX) and (WDX) in the headlines of the existing pages

--Stance 13:51, 23 May 2005 (EST) Hello, I would like to have shown:(WCX),(WFX),(WLX) and (WDX) in the headlines of the existing pages.
Don´t know if it´s possible to change titles without changes the links.
It is not so important, but for a reader maybe better. Kind regards, Stance.


If you use the 'move' or 'Verschieben' Tab in the head of the line you could rename the page and Wiki would create a redirect on the old page.
Thus each links ends up in the new page.
Sheepdog 24. October 2005 08:46 (GMT)