archive-org.com » ORG » W » WIKICREOLE.ORG

Total: 1035

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Talk.PEAR Text_Wiki Package
    Quick search type ahead Recent Searches Clear Talk PEAR Text Wiki Package Your trail Talk NewlineSpace Home Talk Newlines Home Talk News blogentry 070107 1 Home Talk Nyctergatis Home Talk Oddmuse Home View Page Discussion V iew A ttach I nfo Hi Michele just tested a little bit on your sandbox seems that external links without description don t work http www wikicreole org ChristophSauer 1 Feb 2007 Wow not a minor bug Thanks Christoph It should be fixed now MicheleTomaiuolo 2007 02 01 I still need some reflection before being totally convinced by multiline headings unlike list items and Wouldn t you like to at least consider the final as the heading end marker I e heading paragraph would be handled like heading paragraph YvesPiguet 2007 03 02 Yes Yves I see your point Not all elements are intuitive to use when they re multi line Probably headings aren t Moreover they should be short This is just some experimentation to put hands on Instead it certainly makes sense for list items and indented paragraphs In fact Creole supported reasons for ignoring newlines in paragraphs The same reasons stand here Michele Tomaiuolo 2007 07 02 Hello Michele I just

    Original URL path: http://wikicreole.org/wiki/Talk.PEARText_WikiPackage (2016-02-11)
    Open archived version from archive


  • Talk.Paragraphs
    the contributors Some rights reserved license BY SA Sponsored by the Wiki Symposium and the Nuveon GmbH view find Quick search type ahead Recent Searches Clear Talk Paragraphs Your trail Talk Newlines Home Talk News blogentry 070107 1 Home Talk Nyctergatis Home Talk Oddmuse Home Talk PEARText WikiPackage Home View Page Discussion V iew A ttach I nfo Should this page be merged with Linebreaks EricChartre 2007 01 03 I

    Original URL path: http://wikicreole.org/wiki/Talk.Paragraphs (2016-02-11)
    Open archived version from archive

  • Talk.Paragraphs And Line Breaks Reasoning
    1 Home Talk Nyctergatis Home Talk Oddmuse Home Talk PEARText WikiPackage Home Talk Paragraphs Home View Page Discussion V iew A ttach I nfo It s clear there is no consensus on the creole markup for linebreak but the majority of discussion favoured n br and n n as the simplest most intuitive Given this it seems extremely arbitrary to decide creole 1 0 will break with its previous standard

    Original URL path: http://wikicreole.org/wiki/Talk.ParagraphsAndLineBreaksReasoning (2016-02-11)
    Open archived version from archive

  • Talk.Patrick Michaud
    Wiki Symposium and the Nuveon GmbH view find Quick search type ahead Recent Searches Clear Talk Patrick Michaud Your trail Talk Nyctergatis Home Talk Oddmuse Home Talk PEARText WikiPackage Home Talk Paragraphs Home Talk ParagraphsAndLineBreaksReasoning Home View Page Discussion V iew A ttach I nfo Welcome to wikicreole org It s good to see more wiki developers involved I hope you will help us make Creole even better I must try the microwved grapes trick some day RadomirDopieralski 2007 01 21 Also welcome Since you re creator of PmWiki and I think originator of the right arrow link syntax I m particualrly interested in your ideas on Alternate Link Syntax Proposal Why did you introduce this syntax Did it create any problems or confusion for your users Do you still feel it s a good idea RaphLevien 2007 01 20 Yes I originated the right arrow syntax It works extremely well and my authors don t seem to have any trouble with it There are some authors who exclusively use the arrow syntax some who exclusively use the pipe syntax and some like myself who use both depending on what reads better in the markup I ve never heard from

    Original URL path: http://wikicreole.org/wiki/Talk.PatrickMichaud (2016-02-11)
    Open archived version from archive

  • Talk.Placeholder
    to a single line helps ease editting The MediaWiki example given in Placeholder could be quite off putting to wiki novices I think Another thought bout what are becoming common operations during editting Using a hash or programming camel case style identifiers would cause spell checkers to flag things that aren t ment to be changed Hmm JaredWilliams 2007 02 23 I m more concerned that there is introduced an opportunity for errors and lost data What should the wiki do when there is an unknown placeholder What if the placeholder is duplicated Data loss is possible when the user tries to move text between pages or even on the same page but in two edits he will cut the text save to see how it looks edit again and paste the text in different place There is also a possibility of accidental modification of the hash during editing either by the user himself or by the text editor line breaking autoindenting spellchecking autocompletion The main problem is that such a failure is fatal once you save even pasting the text back wont help because the placeholder is already deleted on the server Sure it s a wiki so you can probably revert to a previous version and then retry all your changes but this in truns destroys the user s work Turning the hash into an actual perfect representation of the data just compressed and base64 encoded is one solution To sum up I agree that it can be advantagues to use hashes in cases of elaborate elements especially when they can contain whitespace and normal text But at the same time this has several drawbacks making the whole editor a little less friendly and faultproof so it seems that the technique can be avoided when it s not actually necessary when the text of contained object is actually short and robust no whitespace or other things that could make it look similar to other page content RadomirDopieralski 2007 02 23 I suppose the ideal would be able to use code folding to automatically fold hide large multi line Placeholder sections Novices can safely ignore advanced users can unfold the section and edit But its pretty much impossible for HTML JS I think XUL XAML or some other tech would have to be used JaredWilliams 2007 02 23 Code folding syntax highlighting automatic indetation templates and autocompletion are elements commonly used to actually fix the language used See how C Java C programmers become bound to the IDEs they use because the code is only in part written by them the machine does most of the work But if the machine can do that work when the code is written it can as well do it when the code is parsed hence all the generated parts of code are really superfluous and serve only presentation not meaning It s better to design the markup right from the start than to patch it with additional functionalities of the editing program

    Original URL path: http://wikicreole.org/wiki/Talk.Placeholder (2016-02-11)
    Open archived version from archive

  • Talk.Placeholder Reasoning
    Sandbox Copyright C by the contributors Some rights reserved license BY SA Sponsored by the Wiki Symposium and the Nuveon GmbH view find Quick search type ahead Recent Searches Clear Talk Placeholder Reasoning Your trail Talk PEARText WikiPackage Home Talk Paragraphs Home Talk ParagraphsAndLineBreaksReasoning Home Talk PatrickMichaud Home Talk Placeholder Home View Page Discussion V iew A ttach I nfo Placeholder Reasoning is somewhat confusing to people coming into the discussion It may need some elaboration use cases and examples I did not understand the concept Note that only the reasoning pages are referenced from the Creole0 5 summary I added the link to Placeholder itself Some background information seems to be in Prototype GregorHagedorn Something strange going on with placeholders Edit page shows but View page shows It looks like something wrong with the engine because even Creole 0 1 spec is showing for placeholders I think it s very confusing to be meaning one thing but saying another It s not good for a spec Can this be fixed anytime soon MarkWharton 2007 05 03 This is indeed very strange I ll have the Creole plugin maintainer for JSPWiki look into it Thanks for heads up ChuckSmith 2007

    Original URL path: http://wikicreole.org/wiki/Talk.PlaceholderReasoning (2016-02-11)
    Open archived version from archive

  • Talk.Preformatted And Nowiki
    the loss of a mechanism to implement unformatted text containing metacharacters I find we ve used the backslash quite a bit One possibility I m considering maybe as an extension is to adapt the exclamation prefix traditionally used for making CamelCase words nowiki In Creole style I d adapt that to a double exclamation point It needs to occur at the beginning of a word delimited by whitespace to be interpreted Its scope would be to the end of the word again delimited by whitespace and would suppress all interpretation of metacharacters within that scope So for example if you want double backslash instead of linebreak you could write And to write markup that will produce that display you d write Of course I m allowed to do this in the spirit of ExtensibleByOmission but I m wondering if there s sense this kind of functionality would be generally useful either as a proposal for the core or possibly as a gently suggested extension P S I want to take this opportunity to rant against the word nowiki I see it used here primarily as a synonym for preformatted i e unformatted and monospaced but its original usage was to defeat automatic link pattern detection without the accompanying switch to monospace font Thus it seems nearly impossible to use the term without creating potential confusion about which is meant I recommend we try to consistently use the terms monospaced and unformatted to refer to the components and preformatted to refer to the combination Raph Levien 2002 02 10 I used nowiki to mean unformatted not monospaced text Personally I d like to see foo in this role and then foo as the unformatted monospaced text in Creole Extended In the absence of that markup foo can produce monospaced text if it s desirable on particular wiki This is not as important for inline markup you can t line up characters anyways because you don t know the line length So changing the font from monospace to normal or the other way around is not going to mess things There are several reasons why I m advocating for marking up inline monospaced text it s the most popular markup that is acceptable in Creole listed at wikimatrix it s used mostly for variables snippets of code etc great number of programming languages use as a comment character and comments are unlikely to appear in these snippets it mirrors the markup used for bold so we can use all the same rules and techniques used for lists bold it has no other obvious use it looks good to me What do you think RadomirDopieralski 2007 02 10 I don t understand very well what it adds wrt corrent nowiki Nowiki now serves for monospaced sequences and it leaves the content unparsed which I think is correct and desirable Mixing monospace and other markup I m not sure The only problem is when you want to escape some markup for example introducing a

    Original URL path: http://wikicreole.org/wiki/Talk.PreformattedAndNowiki (2016-02-11)
    Open archived version from archive

  • Talk.Preformatted And Nowiki Reasoning
    leaving this to the implementers won t cause trouble monospace text isn t distinctive enough to be used as emphasis anyways then those who adopt from Creole additions can leave nowiki in normal font while those who lack the tt formatting can make nowiki monospaced Radomir Dopieralski 2007 Mar 06 I think that is somewhat dangerous It implies that parts of text may or may not have an emphasis or be distinct If Nowiki is around single characters the difference is negligable but otherwise the content author has to know in advance whether escaped text may or may not be differentiated from normal text Gregor Hagedorn 2007 03 08 They already have no emphasis if viewed entirely in monospaced font on console or cell phone Also most users are not really able to distinguish fonts on first glance maybe you can do it if you use the ugly Courier but not with DejaVu family for example which is the default on most Linux distributions So relying on emphasis using monospace font is fishy from the beginning and the markup is preserved so a more visible form of emphasis can be added substituted Radomir Dopieralski 2007 Mar 08 Quoted from the article page Triple curly brackets were chosen due to their visibility and unlikeliness to be in the code itself I d guess that I ve typed as part of code hundreds of times over the years Update Wait a moment A google code search for just showed me 120 000 matches When using google code search use to bracket what you re typing Match counts seem to vary from moment to moment when repeating the same search but afaik it never shows false positives ie I believe that A the 120 000 is about right or is an underestimate for and that B google code search remains useful for testing other proposals Anyhoo I think you should propose something else and use google s code search to test proposed solutions I just tried all obvious combinations on my US keyboard Straight doubles triples and even quadruples all showed thousands of matches So too all mixed doubles and mixed triples and quadruples that were grouped on the keyboard eg showed 20 000 matches Even crazy stuff like showed hundreds of matches RaiphMellor 2007 Apr 19 In preformatted blocks triple braces are only recognized as the end marker at the very beginning of a line Google code finds 200 matches which is probably acceptable since braces can be made meaningless to the Creole parser with a single leading space In inline nowiki triple braces could cause problems only when followed by something else which has been considered here rightfully imo as an edge case Workarounds exist such as two successive inline nowikis Your last search shows that no fix end marker is safe User selected end markers would probably make some implementations much more complicated YvesPiguet 2007 Apr 19 I can t believe the 200 number Right now a google code search

    Original URL path: http://wikicreole.org/wiki/Talk.PreformattedAndNowikiReasoning (2016-02-11)
    Open archived version from archive



  •