David Gamey wrote:
> Basically the formatting and language/task recognition aren't coupled in the
> RC Wiki. This means we can have a heading, like Icon/Unicon with subheadings
> for the differences. It gets rid of the reference/redirect, duplication,
> and keeps the two languages together. It also means that the tasks
> complete/incomplete pages will reflect what's been don for Unicon and Icon
> separately. This shouldn't be a problem because if you follow a link to XYZ
> task unimplemented in Unicon and there is Icon code for it you'll see it very
> clearly.
>
> Thoughts?
When I look at a task to see solutions, I scan down the list of
languages on the left. If I'm looking for Unicon, I'd
expect it to be list between VB and Unix Pipes. Would that
still be the case? If I were a novice looking for Unicon
solutions I might not pick it up if it were in the I's (especially
if the list of languages gets much longer!).
I don't suppose we could get away with naming it "Unicon/Icon"? :)
--
Steve Wampler {[email protected]}
The gods that smiled upon your birth are laughing now. -- fortune cookie
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
