Always consult the official Owners Manuals first!
March 2024: all pages have been checked and are up-to-date

User talk:Yek on wheels!

From Fractal Audio Wiki
Revision as of 07:38, 4 August 2011 by Manning (talk | contribs) (→‎Official manual: reply)
Jump to navigation Jump to search

Hey have a look at this page. It's an alternate design for the Amplifier_(FX_block):_list_of_amp_types. It's not finished, but I thought I'd get your opinion before I go any further. Cheers Manning 01:44, 3 August 2011 (EDT)

Also, I had a couple of thoughts on configuration.

1 - I think having defined URL paths http://wiki.fractalaudio.com/axefx2/somepage
is better than http://wiki.fractalaudio.com/axefx2/index.php?title=somepage.

This is set in the $wgUsePathInfo parameter.

The main reason it is better is that the links look better when pasted into other places (such as the forum).

2 - Somewhere in the parameters for the default Vector Skin is the option to underline all links (which Wikipedia has as a default). Currently the Axe Wiki doesn't, which makes it really hard to tell when text has been hyperlinked. I can't actually remember where this is set.

Anyway, just some thoughts. Cheers Manning 02:01, 3 August 2011 (EDT)

PDF's and stuff

Hey, we can keep the discussion here on your page, I'll know when you have replied as your page is on my watchlist. Also, when you leave a comment type ~~~~ at the very end, that signs and dates it.

PDFs are still not supported properly by MediaWiki, and you will probably never be able to upload a PDF and search it because PDF is a commercial format and Mediawiki is open-source. Having said that, there are methods - see http://www.appropedia.org/Help:Porting_PDF_files_to_MediaWiki for a good summary.

Peaker - LOL, sorry about that. I was on auto-pilot. Thanks for double-checking.

As far as the table - it should format properly on mobile devices as I used the "wikitable" template. Standard HTML tables can go horribly wrong. That is all the information I was planning to use for the table, each line of the table can then link to a full article for each module. I'll do an example and put the link here. Cheers Manning 05:03, 3 August 2011 (EDT)

Update - I've created the first subpage (59 Bassguy). You can click to it from the temporary table. Manning 20:59, 3 August 2011 (EDT)

Official manual

On the topic of PDF's is it your plan to import the entire manual? If so, I can probably help with that as I have access to all the necessary software. (I also now have the manual as a Word document in case you want a copy).

The other necessary block of work would be wikilinking all the text. This would take some time, but it is far from impossible.

If that is the plan, then it would be good to have a naming standard to indicate it is directly from the manual eg "MAN:The Section Name". Manning 18:45, 3 August 2011 (EDT)

Hi, I already converted the current manual and integrated it into the wiki.
I split it into paragraphs and used templates to separate it from user contributions.
This allowed me to add manual content to individual topics where applicable.
I did this using the DOC I got from Matman, and the Save-To-Mediawiki feature in Libre Office (successor of OpenOffice).
Of course the layout isn't 100% the same and I didn't embed small images. The text in the templates should not be edited, as it is Fractal's.
Most pages start with a disclaimer about the manual conversion.
Oh cool. Obviously the text shouldn't be changed, but what about wikilinking - is there any problem with doing that? Also I've been working on getting the Navbar and Navbox templates working, as they make creating automatically updated tables of contents really easy. Scroll to the bottom of this page and open the "Lists by Country" - that is the navbox template. It is used through all of Wikipedia.
Going back to your first question, which PDFs are you talking about, apart from the user manual? Manning 03:17, 4 August 2011 (EDT)

Wow, Bassman amp page looks good. Lotta work man. Navbox is also cool. PDF: in fact the manual is the only one. And maybe the MFC manual too. I guess wikilinking wouldn't be a problem. Always to consider: - are the results worth the effort / do many people use it - are things still easy to manage when the manual is updated, or when you and I aren't around :) Yek 03:29, 4 August 2011 (EDT)

LOL - I've been around Wikis for a LONG time - I was involved in the original design of Mediawiki (as I was one of the original editors of Wikipedia). Doing this sort of thing is a breeze.
I've got some ideas on how to organise it a bit better. I see you've loaded the manual into templates (a VERY good idea). We should get all of the Manual templates edit-protected so that only certain people (like yourself) can edit the text. At the moment anyone can cruise on in and change things. also I can colour-code the background of the manual text so that people can easily tell what is from the manual and what isn't. Manning 03:38, 4 August 2011 (EDT)