OSDev.org

a wisiwig wiki ? weird idea. It tooks 10x longer to get the "edit" thing and it even crashed my web browser (mozilla/linux) while trying to edit again.

All those word-like additionnal functions (free font selection, etc) will make it even harder to keep a consistent "look and feel" (which is, imho, one of the strongest advantage of wikis against html).

The wiki 'formatting' is hardly something bad (still imvho) and it rather _speeds_ edition than slowing it down, if you see what i mean

Honnestly, the only thing that could make me advocate for a switch to another wiki would be in-place diagram edition (so that i no longer need to do ascii art here and there)

They use this one http://sourceforge.net/projects/itools-htmlarea/ see the CVS because no releases... . Here the load is fast, the first time no, but one time I get the js files is more fast. Using FF here.

Perhaps somethings in the editor are configurable.. I supose. Is js then for example perhaps will be posible to only allow certain types of formats you see there exist heading1, heading2, etc....

I supose is a good idea . I think it "saves" the content like html, but what if we get the code, and instead of use the save, we write a little js that will format the html like is required by normal wikis , I let the idea there .

To put it simple; I think it's just stupid.
Wikiformatting is simple enough for anyone, and works great.
As Pype said word-like functions will only make pages look inconsistent because everyone prefer different fonts. Also, stupid word-like functions put in hands of ?creative? people make pages look like ****.

Pype, which diagrams do you mean? Graphviz-style?
I use Trac (integrated issue-tracker, wiki and subversion-browser), whose wiki is easily extendable. I wrote a small plugin that lets me write an inline dot-block (graphviz instructions) that's rendered to an image when viewed.
Maybe it's possible to extend phpwiki in the same way?
This applies to other diagrams which may be rendered from text aswell.

I very much prefer current wiki editing methodics, since they make for clean & maintainable pages. What I've seen in feature creep with word processors is that they all (wysiwyg ones) seem to develop the concept of "grouping" styles for easy adjustment, and then screw that up very badly. You end up with a document that's unmaintainable.

Please, keep it text-based.

ok, Apart is not a easy task .


If the problem is let the guys access diferent formats, provide the necesary formats... no access to colors...

Sure this script work only for newer IE and FF... and also the output *is* html, in the submit, for example you can put a convert.php that will handle the necesary format like a wiki like, also I have watched some "defects" in the script, perhaps in a later version they will be "cleaned". Only keep the mind open.

You use editors for word like files? or html pages? or you do all the formatting with a plain text editor???

rea: I've done a fair amount of webdesign and I ALWAYS use a notepad equivalent. I find that wysiwig generates code filled with unnessecary rubbish and i can get more control over code layout on my own.

Also for the wiki, the emphasis is on content not layout. The wiki language should stay as it is, maybe add a [ code ] tag (haven't used it for a while so this might already exist). And then whoever owns the wiki can just use stylesheets to define what different blocks should look like...

Is the merger with bonafide still happening etc.? I've been helping a bit with the new cms for over there but don't really know what's going on...

Pete

What's the proper etiquette for updating entries? I've been using the network boot feature of grub to improve my build/test time and thought that would be a good entry to add, but don't want to blindly start editing pages if the owner prefers a bit more control over the content.

BTW, thanks for the FAQ, it's been a great help. I've played around with writing my OS before but the learning curve had been a bit too steep for a few hours a week project. The FAQ here and the Bona Fide website have really pulled together the relevant info into a nice little package.

After reading though the archives I was tempted to post a "Can I write an OS in Javascript" thread, but then sobered up.

Eddie

well, if you want to add your 2 cents to the FAQ, the common way to do is to add it as a sort of "comment" as <spaces><two single quotes> <your text> -- <YourName><two single quotes> If you want to provide a more complete contribution, just edit things as you think they should do and open a thread on the forum to request for comments ... (pointing to that thread from the wikipage may sometimes be a good idea too) Solar and I at least periodically watch the "last change" and we'll check out what you did anyway

Just make sure you have signed in with a name that more or less reflects your login on the forum so that we can more easily track who thinks what and that we can optionnally discuss the issue with you if we happen to disagree

Pete wrote: rea: I've done a fair amount of webdesign and I ALWAYS use a notepad equivalent. I find that wysiwig generates code filled with unnessecary rubbish and i can get more control over code layout on my own.

Same for me ;D Notepad equivalents are the most powerful tools to create a website ;D

Just a heads up for the powers-that-be: I've added a new BareBones example for higher-half kernels:

http://www.osdev.org/osfaq2/index.php/H ... ion=browse

It's tested in my environment at least (Cygwin, GNU cross-compiler, nasm, run in VMWare). Feel free to work your editorial magic on it as necessary.

I added a brief description on network booting to Grub, but just realized I used my real name for the wiki login, EddieMcCreary, sorry if this causes any problems.

In case somebody cares, I create my own pages with a tool called Rewaster (which I haven't released) which works with two ideas:

Block level markup is done with a combination of starting characters, indentation, and empty lines. Basicly, more identation puts a block on an inner level, while less indentation gets it back out. Empty line terminates a block, unless it was terminated anyway by less indentation. For example:
On inline level another form of markup exists. It is actually a generic macro-system (with enough power for building non-terminating macro-expansions), but in reality that's just an implementation detail.

The real point is: [tt]/:word[/tt] comes out as italic, and [tt]/:{segment of italic words with one *:{bold} word}[/tt]. That is, macroname followed by : followed by a word or a {}-delimited cluster expands into a macrocall which generates XHTML. And it's impossible to get stuff nested improperly in the output. Any extra {} are ignored with a warning, and if foo: is not a proper macro name then it's left as it is..

Multiple arguments are handled by currying as in $link:{Google}{http://www.google.com}. I'm happy with my system so far, and it's easy to extend it by just adding new macros. The one feature lacking is that conditional macro-expansion is not possible. Would have to add that at some point.

Finally, I also do --- to em-dash, -- to en-dash, `` and '' to start/end quotation (and with nested quotations alternates single and double quotes), ... to ellipsis and a few similar expansion in order to get more pleasing typography without any extra effort.

. From pass days to today I can access the FAQ, it say "Forbidden" is this a random thing? and I have the "luke" to try access in those moments.

Most likely an IP block-ban. As the Wiki is plagued by rogue editing (the traditional pr0n link list...), df / Chris keep "known bad" IP blocks banned. Sometimes the innocent get caught together with the guilty; best contact df / Chris by PM and sort it out.

i havnt changed the ip ban list in a long long time, since its all getting ready to move... mr xism is/was testing and trying to get it setup on osdever...