Difference between revisions of "Template talk:App"

From ArchWiki
Jump to: navigation, search
m (Condense and Links title?)
Line 46: Line 46:
  
 
:: Then what should be done, when a package like dar that returns pages of packages? Also i686 should be preferred over x86_64 for linking. As most use tend to use i686 I think and it's not about playing favorites. -- [[User:M l|M l]] 18:03, 3 December 2009 (EST)
 
:: Then what should be done, when a package like dar that returns pages of packages? Also i686 should be preferred over x86_64 for linking. As most use tend to use i686 I think and it's not about playing favorites. -- [[User:M l|M l]] 18:03, 3 December 2009 (EST)
 +
 +
::: Dar is the exception not the rule, I use x86_64 and I don't want anyone to play favorites with package listing and listing one thing over another _IS_ playing favorites. Things should be left as they are. --[[User:Keiichi|Keiichi]] 19:03, 3 December 2009 (EST)
  
 
== Condense and Links title? ==
 
== Condense and Links title? ==

Revision as of 00:03, 4 December 2009

I like it.
Trying to make the url small, so far with no results. I apparently broke the template because it shows small here, but not in articles. manolo 13:35, 13 November 2009 (EST)

Using direct links

When trying to use a direct link, it does not format correctly:

Yaourt — A Pacman frontend with more features and AUR support.

http://www.archlinux.fr/yaourt-en/ || {{yaourt}}

Yaourt — A Pacman frontend with more features and AUR support.

http://www.archlinux.fr/yaourt-en/ || Template:Package AUR


A really good example why using a direct links is needed for this template, Template:Package Official and Template:Package AUR

DAR — A full-featured command-line backup tool, short for Disk ARchive

http://dar.linux.free.fr/ || Template:Package Official

DAR — A full-featured command-line backup tool, short for Disk ARchive

http://dar.linux.free.fr/ || {{dar}}


The following works, but does not look as neat like when just showing the name of said package(but it's fine by me):

DAR — A full-featured command-line backup tool, short for Disk ARchive

http://dar.linux.free.fr/ || http://www.archlinux.org/packages/community/i686/dar/

Does not work with AUR:

Yaourt — A Pacman frontend with more features and AUR support.

http://www.archlinux.fr/yaourt-en/ || not packaged? search in AUR


Looking through some on the links on the sections that use this template in Common Apps most are similar to the dar example above. When using a direct links from http://www.archlinux.org/packages/ which link should be used? Direct links for i686 or x86_64 packages? I think direct links for i686 should be used. -- M l 15:32, 27 November 2009 (EST) Thanks

Hrm... I see the problem now. The direct AUR links contain an "=" sign. I would suggest the following:

Yaourt — A Pacman frontend with more features and AUR support.

http://www.archlinux.fr/yaourt-en/ || yaourt

Note the <tt> tags to format the output; the braces do nothing.
It's a bit more work for you, though. However, in most cases, I think the search should be used even if it returns ~10-15 results. I can see your point about dar though... that's a mess of results.
If linking to an official package directly, I would suggest the i686 package, certainly. -- pointone 15:52, 27 November 2009 (EST)
~10-15 sounds fine, but by not using direct links might confuse new users staring at a list of packages with similar names and not knowing which one too install. To avoid that might be best to use direct links. The examples above with correct direct linking should be added to their respected pages, so direct linking gets done right. I will start working on that when I get a chance. -- M l 19:13, 27 November 2009 (EST) Thanks
I am 100% against direct links to packages. There are two architectures and playing favorites is not the way to go. --Keiichi 10:45, 3 December 2009 (EST)
Then what should be done, when a package like dar that returns pages of packages? Also i686 should be preferred over x86_64 for linking. As most use tend to use i686 I think and it's not about playing favorites. -- M l 18:03, 3 December 2009 (EST)
Dar is the exception not the rule, I use x86_64 and I don't want anyone to play favorites with package listing and listing one thing over another _IS_ playing favorites. Things should be left as they are. --Keiichi 19:03, 3 December 2009 (EST)

Condense and Links title?

The current style takes three lines which does take a good deal of space. Any thoughts about doing this with two? Wiki page | description | homepage | package information.

  • Firefox - Web Browser that is faster, more secure, and customizable.
homepage | package information

--Gen2ly 21:55, 2 December 2009 (EST)

I like your proposal a lot, I vote for implementing it. --Keiichi 10:45, 3 December 2009 (EST)
I also agree, Pointone already took care of this. -- M l 18:05, 3 December 2009 (EST) Thanks