in reply to Re: RFC: Monastery Markup Renderer
in thread RFC: Monastery Markup Renderer

*Do not pre-fill code, paragraphs, etc
*Is there any point to checking whether the required modules are installed? Once you hit the actual 'use', won't the code die anyway?
Would you elaborate more? as I think I am not totally aware of the technical meaning of pre-fill. Also the second point, I don't know whether it suffices to work without checking the existence of modules first, I was notified of this by ssandv but in brevity and I could not understand the purport technically. I would however want to make a list of wishlists collected from the interaction I receive on this node and they'd all hold equal importance to me.

For the read more tags I thought I would have the user not worry about double-quoting themselves in case they thought they wanted to double-quote, but I do not see this as much of a difference hence I am removing them double-quotes from the readmore tags

The reason why paragraphs can not be inserted the cursor is because it would not be clean to have paragraphs tags overlapping, suppose you wanted to add some more text to describe something in a particular paragraph, you would lose track of where that paragraph is had they been overlapping and the tag filling up where the cursor is

I have these couple of serious bugs with the listing however, whenever you hit the list button, it creates a different instance of the list-type to choose from, the second issue is that, in numbered lists, I could not treat different lists as discontiguous entities, hence, if you have used numbered list to have written this replay this way to me, you would not get the lists numbered from 1 for every time, like the numbering of a new list starts at the end of the number for the previous last list item.

I'd land at POD once this code catches real fire, I see that I haven't received the response I expected however, and now that this node is getting covered up by new nodes is kinda of difficult to garner more response,however, I tried "POD"ing but it felt like getting me off the topic since It requires viewing and testing on its own too, this is why I'd land at it later.

Tk is easier than I thought it would be, As for the many variables names, I know, for most of them, you can just work without declarations, as in $main->Button()->pack and that is it without specifying a variable as $button to hold the button name, for some other variables, you'd need to use them other places hence you need to assign them to variables. I have done it this way to be able to follow what is going on and what each button has for example by looking at the variable holding its method calls instead of digging through the code to establish what this certain part or that other part is all about

Finally, thanks and looking forward to more interaction with you

Would still compare my little ugly code to GrandFather's grand code, thanks for finding where it resides, I would come back to your question soon as I can afford.


Excellence is an Endeavor of Persistence. Chance Favors a Prepared Mind.

Replies are listed 'Best First'.
Re^3: RFC: Monastery Markup Renderer
by toolic (Bishop) on Sep 17, 2009 at 20:10 UTC
    Here is what I mean by 'pre-fill'. Currently, when I click on your 'PARAGRAPH' button, it gives me this:
    <p> enter some lines of text </p>

    I think it is unnecessary to give me the text 'enter some lines of text'. I know that I have to enter text. And now I have to select all that text and over-write it. I am too Lazy for all that. The same goes for 'code' tags and list tags.

    The reason why paragraphs can not be inserted the cursor is because it would not be clean to have paragraphs tags overlapping
    Are you aware that the ending 'p' tag is not required? I never use </p> when I'm composing a node. Here is what my node would look like with 2 paragraphs:
    <p>1st paragraph <p>2nd one

    So, all I'd like when I hit your 'PARAGRAPH' button is the following:

    <p>

    But it's easier to write POD than all those commented-out lines. It's as simple as:

    =pod This is a program that simulates some of the tasks of posting and prev +iewing a node at PerlMonks. I thought of making such a program for the following reasons: + 01-Practice the Tk module to a decent level or mastery. + 02-Make a GUI that could enable Perl newbies to post nodes quicker +without using some of the deprecated tags like <pre> and. =cut
    There's nothing to test. And it's a for-free manpage which you or anyone can view:
    perldoc renderer.pl