in reply to Re^6: Making Perl Monks a better place for newbies (and others)
in thread Making Perl Monks a better place for newbies (and others)

Legacy code and mass of data in old format
  • Comment on Re^7: Making Perl Monks a better place for newbies (and others)

Replies are listed 'Best First'.
Re^8: Making Perl Monks a better place for newbies (and others)
by PerlGuy(Tom) (Acolyte) on Feb 01, 2020 at 19:54 UTC
    I thought of that, but, such a change would not alter anything already rendered and posted on the site. I don't think.

    Workarounds, like a template might have to be changed, or might no longer be necessary. But nothing already on the forum would be altered.

    I can't see how anyway.

    Tom
[reply]

      That's because you have no clue how it works.

      Posts are rendered into "real" html at page display time by the Engine, which expects the node source content to be in our special su{b|per}set of html.

      We now have well over one million nodes in this format in the database.

      No transformation is done to user-posted content at input time.

      Ponder that for a while. Then please provide your ideas. The challenge is not insurmountable, but one must begin from an informed position.

[reply]
        > Then please provide your ideas

        --> Wikisyntax for the Monastery

        heavily tested by several monks, has only minor issues.

        based on regexes, hence language agnostic.

[reply]
      A reply falls below the community's threshold of quality. You may see it by logging in.
Re^8: Making Perl Monks a better place for newbies (and others)
by Anonymous Monk on Feb 01, 2020 at 19:33 UTC
    Its got nothing to do with that
[reply]
      With what?

      Or/and: What does it have to do with?

      I've written some basic message board programs, going back to the 90's. I would think not having basic functionality, such as rendering basic text with paragraphs,, would be intolerable.

      I can live with it I guess, I'm just puzzled why we have to, or why anyone would want to.

      Tom
[reply]
        I downloaded all the Everything Engine files from SourceForge and poked around a bit.

        I opened up first what appears to be the most recent build available.

        It contains: 

        package Everything::HTML;

######################################################################
+#######
#
#    Everything::HTML.pm
#
#    Copyright 1999,2000 Everything Development Company
#
#        A module for the HTML stuff in Everything.  This
#        takes care of CGI, cookies, and the basic HTML
#        front end.
#
######################################################################
+#######

use strict;
use Everything;
use Everything::MAIL;
use CGI;
use CGI::Carp qw(fatalsToBrowser);

        [download]

        I, of course, have no way of knowing if this has been changed or updated on PerlMonks to use something other than CGI.pm but the majority of older Perl programs did. Apparently the Everything Engine is no different.

        I never did like CGI.pm. Too bloated for the simple message board scripts I wrote.

        Also I wanted more control. It was easier just to write my own code from scratch for that.

        But, if it is still what PerlMonks has running on the back-end for handling CGI, some scripts,
        possibly some versions of CGI.pm use something like $value =~ s/\n/ /g; replacing the newline character with whitespace, globally. So instead of converting to HTML the return is converted to a space.

        Instead, do something like $value =~ s/\n/<br \/>\n/g;

        Tom

[reply]
[d/l]
[select]
          A reply falls below the community's threshold of quality. You may see it by logging in.

In Section Perl Monks Discussion