User talk:Orderud
From Wikibooks, the open-content textbooks collection
Contents |
[edit] Computing Bookshelves
Hey Orderud, I don't think we need to merge the three book shelves. Here's what an ideal organization would be:
- Computer Science -- the more "math-like" stuff you would get in college
- Programming -- language guides, library tutorials, programming tips and recipies
- IT -- about computer programs, using them, set up of networks, so long as you aren't writing much "code"
That's just my two cents, but the differences between CS and IT are so great that they shouldn't belong on the same shelf. --MShonle 18:42, 9 October 2005 (UTC)
- There's a reply for you on my user page. --MShonle 22:16, 9 October 2005 (UTC)
[edit] Programming:MS Visual Studio
Hello there Orderud,
What is your view on moving all C++ content from Programming:MS Visual Studio to Programming:C plus plus this is already a Win32 and MFC section there if the content in the future gets to big a separate book can be created to keep it as I see now it consists only on some wikipedia links and a single module also consider that in the C++ book it will get more visibility and probably more contributions, if not consider at least on using transclusion for content that relates only to C++ (non Visual Studio dependent)--Panic 18:45, 16 October 2005 (UTC)
- Sounds like a good suggestion. Feel free to move the content as you please :) --Orderud 19:34, 16 October 2005 (UTC)
-
- Txs, new location of the content is [Using Static Libraries], if you have more just add to it's parent...--Panic 04:45, 17 October 2005 (UTC)
[edit]
Can you provide a motive for the page moves of the library sections (I've read the comments) and they don't make sense, since it was evolving toward the other side of the spectrum, (it's been implement across the book, so retracing it would require a major restructure) we do sacrifice clarity of path to enable easier navigability (better that using navigational aids and templates), even what you said on the comment is incorrect, since C++ (and C also) "programs" will consists of one or more translation units that are compiled separately, this results in separated object files are then linked together to produce an executable file. Keeping the navigational structure intact is very important and rational on this case (I have fixed the one I know, broke the book structure and the print version), if you agree with the concept, can you see if you can undo the moves and correction of paths ? --Panic (talk) 18:04, 5 January 2009 (UTC)
We can use redirects also to improve path visibility if you think it is important, I was going to experiment with those to enable more logical navigation but I'm going from start to end (in relation to the TOC), another example of the use of this navigational structure that is still incomplete is on the /Code/ this will slowly extend to the rest of the book see C++ Programming/Code/Style Conventions/Documentation... --Panic (talk) 18:06, 5 January 2009 (UTC)
- Sorry for breaking the book structure. I'm not that experienced when it comes to wikibook editing, and have no idea about book structure and how print versions are built. My intention was only to make the module paths more intuitive. Especially, I found the /Compiler/Linker/Libraries/ path structure very strange, and therefore moved some modules beneath /Libraries/ instead. As for navigation, I don't see any prev or next links or a navigation bar anywhere to navigate between the modules. How are users supposed to navigate through the book? --Orderud (talk) 00:06, 6 January 2009 (UTC)
- No big problem, so far I only detected that break and you fixed most of the links and didn't tag the redirects for deletion (so they are virtual placeholders) for the previous content. As for prev and next I the first part of the book addresses it by including references to those section that are relevant (you corrected some of those links they are labeled as something Section, and I also used old Wikipedia (were possible and on scope) to local book pages that cover the issues as for the navigation one must use the ones provided by the strange paths (like the example I gave above C++ Programming/Code/Style Conventions/Documentation or use the category link Category:C++ Programming (that will show all pages of the book, this is not as great as using a navigational template, but come close and is easier to maintain, especially if we move pages about, the normal way people navigate book is to use the toc and the browser back or history function will cover that, the major problem is that the root page or cover page doesn't hold the real toc of the book (were clicking on C++ Programming would show the toc), there is a pending request for the administration to fix that... --Panic (talk) 00:55, 6 January 2009 (UTC)
- The book had a navigational scheme in the past but was not maintained and was voted for removal, this method can be more confusing but if you look at toc1 is easy to fallow he arrangement, and enables users not professional with templates to make changes due to the use of transclusiom... --Panic (talk) 00:57, 6 January 2009 (UTC)
