din & dout table in new wiki format

[This N°9]

here's to ported din & dout - table:

http://www.midibox.org/dokuwiki/doku.php?id=mbhp:module:dinoutpins'>http://www.midibox.org/dokuwiki/doku.php?id=mbhp:module:dinoutpins

I don't know if this is a good place to put the page, but I didn't see a better in the namespace structure. I don't know if some kind of table/lookup/list namespace would be useful.

also created the pages for din and dout, and inserted the link to dinoutpins:

http://www.midibox.org/dokuwiki/doku.php?id=mbhp:module:din

http://www.midibox.org/dokuwiki/doku.php?id=mbhp:module:dout

Is there some kind of convention when to use these dotframed boxes? I just used them to frame/pack statements and code-snippets.

[stryd_one]

here's to ported din & dout - table:

http://www.midibox.org/dokuwiki/doku.php?id=mbhp:module:dinoutpins'>http://www.midibox.org/dokuwiki/doku.php?id=mbhp:module:dinoutpins

I don't know if this is a good place to put the page, but I didn't see a better in the namespace structure. I don't know if some kind of table/lookup/list namespace would be useful.

As you know I originally thought the DIN pintable should go on the DIN page, the DOUT pintable on the DOUT page. This is one of the concepts behind the new layout, is to avoid mixed up info.... but now that I look at it, I think that having the same table on two pages would suck. I think you took the best option there.

Durisian, Is that cool with you? You've thought about this more than both of us combined ;)

also created the pages for din and dout, and inserted the link to dinoutpins:

http://www.midibox.org/dokuwiki/doku.php?id=mbhp:module:din

http://www.midibox.org/dokuwiki/doku.php?id=mbhp:module:dout

brilliant!

one thing I changed was the page name, to din_dout_pin_list. Why? because when you type any of those words in the search box, it'll show up in the shortlist :) most important was adding the 'd' to 'dout', but i added the underscores to match the similar page names

Is there some kind of convention when to use these dotframed boxes?

Good question... Would you like to suggest guidelines that you think would be smart? There are also the pretty boxes like on the current homepage, it would be good to figure out when to use them..

I just used them to frame/pack statements and code-snippets.

That didn't work out well, I have to scroll inside the boxes, to see the paragraphs. I think that for paragraphs, traditional line spacing is still best.

Code snippets should use the code tag. you can also specify the code language, so we get code highlighting :)

The examples shouldn't be there though - they would be duplicates of the examples that should be given on the application's page. That's just because it is a little different between apps.

Great work man! *High five*  8) 8) 8)

[This N°9]

This is one of the concepts behind the new layout, is to avoid mixed up info.... but now that I look at it, I think that having the same table on two pages would suck. I think you took the best option there.

I thought about this too, and I also prefer to have infos about one issue as compacts as possible. But I think the goal of having the combined table is, that you see the difference between the pin mappings of din's and dout's at one glance, I think this is worth a exception. Maybe the placement in the namespace :module is a bit weired, but I didn't see a better quick solution.

one thing I changed was the page name, to din_dout_pin_list. Why?

I wanted to avoid underscore because it looked like the new page names should try to avoid these. but what you say makes sense.

That didn't work out well, I have to scroll inside the boxes, to see the paragraphs. I think that for paragraphs, traditional line spacing is still best.

one thing is, that no parsing is done for the content of the boxes, also no automatic linebreaks. This causes the scrollbars if your screen / browser window is too small. I'll change this and use normal paragraphs.

Good question... Would you like to suggest guidelines that you think would be smart? There are also the pretty boxes like on the current homepage, it would be good to figure out when to use them..

one guideline then should be, that the content should not be too wide. If there is a way to disable the scrollbars, this would be very nice.

There are also the pretty boxes like on the current homepage

do they fit into the new layout? Maybe they are not meant to be a part of the new layout concept (graphically). What durisian says to this?

Code snippets should use the code tag

ok, I just read on the wiki-syntax page, that the code-tag is just another way to disable the parsing. I'll read some more.

[Durisian]

Durisian, Is that cool with you? You've thought about this more than both of us combined ;)

That's great - One of the aims is to have 1 place for the data. So when things change we don't end up with a jumble of old and new info.