P.S. I remember that speed might be a problem. When you first open the
help system the compilation from markdown is going on with a
noticeable delay.
On 11/15/12, H. Hirzel wrote:
> Torsten,
>
> In August this year I loaded NBHelp into Squeak. NBHelp uses the
> mark-down syntax.
>
> Here is a des
Torsten,
In August this year I loaded NBHelp into Squeak. NBHelp uses the
mark-down syntax.
Here is a description how I did it
http://lists.squeakfoundation.org/pipermail/squeak-dev/2012-August/165587.html
(written in markdown :-) )
NBHelp uses PetitParser.
You write that you want to
On 11/12/12, Esteban Lorenzano wrote:
> +1
+1
> On Nov 12, 2012, at 9:57 PM, Tudor Girba wrote:
>
>> Hi,
>>
>> I completely agree that the PIer syntax is rather niche these days, but we
>> should not confuse the PIer syntax with the Pier model. I think that it
>> would be beneficial to capitali
It should be a pluggable design similar to current help
system so one can write in wikistyle, html, markdown, ...
But we need one default. I like Markdown too - but
do we have some lean code to parse or just transform
it to HTML.
The help system should be relative small - so it
can be delivered
>
>> Hi,
>>
>> I completely agree that the PIer syntax is rather niche these days, but we
>> should not confuse the PIer syntax with the Pier model. I think that it
>> would be beneficial to capitalize on this model (and all the infrastructure
>> built on top of it) and simply create a Markdow
+1
On Nov 12, 2012, at 9:57 PM, Tudor Girba wrote:
> Hi,
>
> I completely agree that the PIer syntax is rather niche these days, but we
> should not confuse the PIer syntax with the Pier model. I think that it would
> be beneficial to capitalize on this model (and all the infrastructure built
Hi,
I completely agree that the PIer syntax is rather niche these days, but we
should not confuse the PIer syntax with the Pier model. I think that it would
be beneficial to capitalize on this model (and all the infrastructure built on
top of it) and simply create a Markdown support.
Cheers,
D
On 2012-11-12, at 15:56, Stéphane Ducasse wrote:
> You won I put a filter markdown to thrash on my mail sadly.
?? I do not parse
> On Nov 12, 2012, at 3:11 PM, Camillo Bruni wrote:
>
It depends at which level.
Can you tag on word in markdown to have bold, italic, index?
>>
>> stef,
You won I put a filter markdown to thrash on my mail sadly.
On Nov 12, 2012, at 3:11 PM, Camillo Bruni wrote:
>>> It depends at which level.
>>> Can you tag on word in markdown to have bold, italic, index?
>
> stef, I already explained you that at least 4 times! Plus I gave you the
> solutions
>> It depends at which level.
>> Can you tag on word in markdown to have bold, italic, index?
stef, I already explained you that at least 4 times! Plus I gave you the
solutions,
the only thing I don't have is the time to complete the Markdown parser!
>> If I would not have written 350 pages of s
On 11 Nov 2012, at 17:26, Stéphane Ducasse wrote:
> On Nov 10, 2012, at 9:41 PM, Sven Van Caekenberghe wrote:
>
>> On 10 Nov 2012, at 21:33, Stéphane Ducasse wrote:
>>
3. Lets discuss how we want to describe the content "in-image"
for "serving on the web". Maybe with a "Markup to HT
Sven Van Caekenberghe-2 wrote
>> I want to use the pier syntax because I know that I can generate the
>> correct latex
>> with it for the books, and of course any kind of html and other formats.
>
> I vote for Markdown, it is more like a defacto standard.
> And you can convert Markdown into anyth
On Nov 10, 2012, at 9:41 PM, Sven Van Caekenberghe wrote:
>
> On 10 Nov 2012, at 21:33, Stéphane Ducasse wrote:
>
>>> 3. Lets discuss how we want to describe the content "in-image"
>>> for "serving on the web". Maybe with a "Markup to HTML translator"
>>> - or a "WikiStyle to HTML" like he
On 10 Nov 2012, at 21:33, Stéphane Ducasse wrote:
>> 3. Lets discuss how we want to describe the content "in-image"
>> for "serving on the web". Maybe with a "Markup to HTML translator"
>> - or a "WikiStyle to HTML" like help
>
> I want to use the pier syntax because I know that I can gen
> As you may know I wrote the current "Pharo help" implementation which
> you can access from the Help menu or via
Yes and I still would like to convince people to write special Unitests tagged
to populate the help.
> There is also no central "docu" point for someone who just downloaded
> Pha
Gorgeous!
Alexandre
On Nov 9, 2012, at 8:48 AM, Stephan Eggermont wrote:
> Here is a screenshot from one of the exercises:
>
>
> For beginners, we got feedback that there is still too much source visible in
> the exercise, but that is a small change.
>
> Stephan
--
_,.;:~^~:;._,.;:~^~:;.
Awesome!!
BTW how do you deal with text formatting?
For NativeBoost we used MarkDown to add sourceCode / method / class and
section links to the documentation. With the formatting and the webserver
the documentation would be almost perfect in my eyes!
On 2012-11-06, at 23:13, Torsten Bergmann
this is cool.
No time to fully read now but later for sure.
I would like to see how we can integrate the book chapters. This is why we
brainstormed with damien c
to see how we can use Pier format as a core format for all the doc and so that
we can generate the book (like for the seaside book).
18 matches
Mail list logo
