User talk:A Witt

From Sonikmatter

better algorithm tables

hey, guys, take a look at this table I came up with for Algorithm10:

	↓			↓	↓					↓			↓
block1		→	block2		→	block3		→	block4		→	block5		→

I think our problems with fixing the look of algorithms is complete. the key is a table that is 15 columns wide. starting with the 2nd column, every 3rd column has an unfixed width, with every other column being 5px. sort of:
5px <none> 5px 5px <none> 5px 5px etc...

secondly, using multiple border styles per cell is possible.

What do you guys think of building each table for the algorithms using this style? I think it's a lot more efficient than the other way, and alot easier to read. No more kurzweil "spacer.gif" file. As far as building wiring for triplemode layers, here's Alg44:

	↓			↓			↓			↓			↓
block1		→	block2		→	block3		→	block4		→	block5

Here is alg70:

	↓				↓	↓					↓			↓
block1		→		block2		→	block3		→	block4		→	block5

chuck
---

Just so you know, we can easily capture "real" screen images with VP as JPG, TIFF, etc. See Capturing_Screens

Warp

Puppeteer and AWitt didn't want to use jpg's because they use alot of bandwidth and are slow, compared to how fast Wiki Tables load. I originally suggested we just post images from the manual, but they said that it would be better to do tables, because a) you're not using copyrighted stuff from kurzweil, and b) you can make everything link to its respective page.

chuck

I can make this so easy and quick using templates for the cells and rows.

So, a template for the top row where all you have to type is | {{atr}}

template for ↓ {{adar}} (it looks like one isn't needed for →, if it is I'll do it)

Then 11 templates for the various borders and a colspan, so you have (where (ab:) stands for algorithm borders)...

{{ab:a|2}}	allborders | colspan 2
{{ab:l|3}}	left | colspan 3
{{ab:lt|2}}	left-top | colspan 2
{{ab:ltr|2}}	left-top-right | colspan 2
{{ab:t|2}}	top | colspan 2
{{ab:tr|4}}	top-right | colspan 4
{{ab:r}}	right | no colspan
{{ab:lb}}	left-bottom | no colspan
{{ab:lbr}}	left-bottom-right | no colspan
{{ab:b|2}}	bottom | colspan 2
{{ab:br}}	bottom-right | no colspan

So this line:

| colspan=5 style="border-left:1px solid blue; border-bottom:1px solid blue; border-right:1px solid blue;"

becomes

| {{ab:lbr|5}}

the wiki for alg70 would end up looking like:

{| border="0" width="500"

|-

| {{atr}} ||

| {{darr}} ||

| {{al:b}} ||

| {{darr}}

| {{altr:b}} | {{darr}} ||

| {{darr}} || ||

| {{darr} ||

|-

|

| {{ab:a|2}} | block 1 || →

| {{ab:a|2}} | block 2 || →

| {{ab:a|2}} | block 3 || →

| {{ab:a|2}} | block 4 || →

| {{ab:a|3}} | block 5 ||

|-

| height="10px" | ||

| {{ab:lbr|5}} | || ||

{{ab:lbr|4}} |

| width="10px" {{atr:b}} |

|-

|}

This table can be set inside of another table, like a background like this:

{| border="0" style="background: blue"

|-

|

{| border="0" width="500"

|-

| {{atr}} ||

| {{darr}} ||

| {{al:b}} ||

|}

|}

It seems like this will make it simple enough and I'll do the templates, if they aren't gonna be used then I'll just delete em after, no harm in doing them.

A Witt

what's it look like?

So, what does that end up looking like?

can you show how it compares to my tables?

chuck

so here we go...

Without templates

	↓				↓	↓					↓			↓
block1		→		block2		→	block3		→	block4		→	block5

With Templates

	↓				↓	↓					↓			↓
block1		→		block2		→	block3		→	block4		→	block5

Now just look at the difference in the code.

In this example, I just created a background then copy/pasted alg70 in

↓ ↓ ↓ ↓ ↓ block1 → block2 → block3 → block4 → block5

A Witt

Just the borders...

{{ab:a|2}}
{{ab:lt|2}}
{{ab:t}}
{{ab:ltr}}
{{ab:tr}}
{{ab:lb|2}}
{{ab:lbr|3}}
{{ab:br|2}}
{{ab:r}}

I'm noticing that the top row or {{atr}} is changing so I'll have to figure something out for that.

arrow placement

we gotta watch out about arrow placement. alg10 doesn't have arrows after the 2nd and 3rd block, because the wiring goes around those two.

{{ templatename: l=left b=bottom r=right t=top| columns }} | text to display

is that the format for the template?

chuck

fixed width columns?

can we use a fixed width column system? that way the arrows are always in the same place, and we use column width to control where the blocks are spreading to. That's what I tried to do with the table I made originally. wouldn't IM/ICQ/Y!/MSN be faster for chatting than this talk method?

chuck

I'm only on IRC for chat if you're able to get on there.

If you want to come up with a fixed column width 1st row, I will make it the {{atr}} template. The template can have the ↓ insterted by having each column numbered which will make it possible to insert the ↓ between pipes in the template... and yes this is hard to explain with non-realtime chat. Right now, the arrows are manually put into the table which means you just delete them where they aren't, like this...

	↓				↓	↓					↓			↓
block1		→		block2			block3			block4		→	block5

A Witt

IRC

Yeah, what IRC channel/server do you hang out in?

chuck

On Efnet I just made #sonik

fixed table

fixed width table:

500 = 10(5px) + 5(90px)

chuck

This is now {{atr:1}} with a setting for border incase you want to check stuff. So {{atr:1|1}} means the border will show, {{atr:1}} means no border.

A Witt

	↓				↓	↓					↓			↓
block1		→		block2			block3			block4		→	block5
		→										→				→

namespace for templates

Hey, I was thinking that all those templates I built, I have no idea how to edit any of them to go within the Kurzweil Namespace. you might want to try and see about doing that. since all the Algorithms use them, you'll need to only edit the templates. Also, whenever all of the filters are moved into the namespace, each of the templates needs to be changed to match that. Again, I don't know where the templates are stored anymore, because they don't show up when you click in the categories link.

Matkatamibakundo 13:57, 23 March 2006 (EST)

I moved the algorithms to their own category that is a sub category of Kurz, you'll see it at the top of the Kurz category page. I think the templates are automatically routed to the new page when it's moved, I'll check it.

A Witt

Templates can be put into a category by using <noinclude>[[Category:Template]]</noinclude>

Templates however are picky and I've found that putting this line at the end of any script is the best way, right at the end, no Return or spaces, like this...

the last line of text or a table.<noinclude>[[Category:Template]]</noinclude>

I assume that if it needs to be a subcategory that the only safe way to do it is...

the last line of text or a table.<noinclude>[[Category:Kurzweil]]</noinclude><noinclude>[[Category:Template]]</noinclude>

I know it seems silly but templates really are picky and if this noinclude is put in wrong it will break the template

A Witt 21:58, 5 October 2006 (EDT)

Algorithm 9

Kurzweil:Algorithm_9 is that only one that I see having trouble because the templates aren't being used for the links yet.

A Witt

I cleaned up number 9

Matkatamibakundo 17:37, 23 March 2006 (EST)

Everything else working?

A Witt

It should be, unless you find something that doesn't look right. Someone told me the tables didn't look right in Opera Browser. could be a wiki problem, and not something we can do anything about...

Matkatamibakundo 18:26, 23 March 2006 (EST)

Yeah well that isn't surprising. Fortunately Opera doesn't have as big of a following as the others. Perhaps when the wiki or Opera is updated everything will be fine. I hope that categorizing makes sense. Since basically everything has to go under the letter "K" the main Kurzweil category was getting very ugly. I was leaving the main subject (like VAST Programmer) for each sub-category in the Kurzweil category also. Now with the subcategories, since they show up at the top it should be easier to find what you're looking for. If you create a category on a page, be sure to go to that category, add [[Category:Kurzweil]] in the edit window and save it. That creates a sub-category under Kurzweil. I hope you've seen the "stub" pages. I've been creating them as I go along so that when a link goes to a page with little or nothing in it there is a message for people to add to it. There is also a stub category that shows us what articles need attention. There is a new "sonikmatter" stub page for general audio stuff (isn't kurz or logic specific) like ADAT. There is also a "Sonikmatter" category that has sub-categories for kurz and logic.

A Witt

KDFX

I went through the KDFX page and there's issues with the naming of the links, looks like something to do with the +'s and <>'s, I don't know what to rename them so please take a look.

A Witt 01:39, 24 March 2006 (EST)

yo, can you hit up the gamesurge IRC channel? My friend got his macbook pro, and we're having a hard time getting his Radium49 to show up in Logic7.2

irc.gamesurge.net #k26sonik

We've been naming the +'s as plus though I'm not sure about the <>'s. They indicate that the algorithm order can be changed.

Also, all the Vast Programmer stuff should be kept in the VP: namespace, not the Kurzweil namespace.

The Puppeteer 22:54, 28 March 2006 (EST)

K, just checking in from Vienna, I'll fix that up when I get back.

A Witt

algorithms are finished

Algorithms are done. all of them. Someone give me access to those locked tutorials on the forums!!!!!! grrrrr!!!!!

Matkatamibakundo 11:57, 5 April 2006 (EDT)