Hi Denis,

first i want to say thank you. Every effort taken on the Github-Wiki
pages is a big help for the community. And much more such a complex &
good written tutorial!

Now here comes the BIG sorry: I tried to quickly read through how you
could place the jQuery inside the page and thought i'd just switch to
textile syntax (right upper side), which didn't do any good. Sadly
everything got changed to the textile syntax and the complete tutorial
is broken. Further more i haven't got enough rights to revert the
changes (don't ask me why - i'll have to talk to Christian about
this). I'll be away for the next hours but fix that later. Btw: In
textile it should just add "pre" both in front and after the code
block. There also appears (sometimes) a small tutorial for the
different languages on top of the page when you edit. Maybe there's
some hint (in one word: the github wiki editing is really not the
best).

Until later,
K.

On 31 Mrz., 12:05, Denis BEURIVE <denis.beur...@gmail.com> wrote:
> Hello,
>
> I put the Perl script in a new page:
>
> https://github.com/joshuaclayton/blueprint-css/wiki/property-extractor
>
> I added a link to this page to the section "*Tools and Resources*", under
> the sub-section "*Language-specific Utilities*".
>
> I tried to create a new page for the JQuery add-on. But there is a problem
> with the JavaScript syntax : It interferes with the syntax of the WIKI. I
> tried different kinds of WIKI (mediawiki, textile,...), but the JavaScript
> code does not fit.
>
> Note : I am not an expert on WIKI. There may be a way to add some complex
> JavaScript code... but I ignore it.
>
> Do you know a way to add "brut source code"?
>
> Regards,
>
> Denis

-- 
You received this message because you are subscribed to the Google Groups 
"Blueprint CSS" group.
To post to this group, send email to blueprintcss@googlegroups.com.
To unsubscribe from this group, send email to 
blueprintcss+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/blueprintcss?hl=en.

Reply via email to