Re: [midgard] Midgard Question: creating links

2000-01-10 Thread Henri Bergius

On 10 Jan, Emiliano Heyns wrote:
 (varname:u);
   mark up varname as URL. If $varname =
 "http://www.midgard-project.org/" then (varname:u);
   would expand to a
 href="http://www.midgard-project.org/"http://www.midgard-project.org//a

Actually, the :u formatting means that the variable
will be printed in URL-encoded format. This means
that "Network Security RD" becomes "Network%20Security%20R%26D"
(just an example from page I was working on). This
is useful for passing text strings as GET or Midgard
Active page arguments.

 (varname:f);
   mark up formatted text. Empty lines will be replaced with P will
 automatically, and you
   can include HTML markup in [...] delimiters (anything between those
 will be passed unchanged
   with the [ and ] removed. It does a great lot more but for the life
 of me I can't find
   the markup parser.

There is also :F which makes all paragraphs shorter than 10
words without period a H2-level headline and lines beginning
with a dash into unnumbered listings.

My experience is that almost all of Web content will fit
nicely in these rules, especially as you can embed HTML
code into it as needed.

 Emile

/Bergie

-- 
-- Henri Bergius -- +358 40 525 1334 -- [EMAIL PROTECTED] --
   http://www.iki.fi/Henri.Bergius


--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org

To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]



Re: [midgard] Midgard Question: creating links

2000-01-10 Thread Emiliano Heyns

Henri Bergius wrote:
 
 On 10 Jan, Emiliano Heyns wrote:
  (varname:u);
mark up varname as URL. If $varname =
  "http://www.midgard-project.org/" then (varname:u);
would expand to a
  href="http://www.midgard-project.org/"http://www.midgard-project.org//a
 
 Actually, the :u formatting means that the variable
 will be printed in URL-encoded format. This means
 that "Network Security RD" becomes "Network%20Security%20R%26D"
 (just an example from page I was working on). This
 is useful for passing text strings as GET or Midgard
 Active page arguments.

Correct, my bad. I just located the parser, and I'll try to write a
little
something about its workings.

Emile

--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org

To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]



Re: [midgard] Midgard Question: creating links

2000-01-10 Thread Emiliano Heyns

Alexander Bokovoy wrote:

 I don't look yet into 2.0 alpha sources about parser code but was it changed
 into module structure like other things did?

Not in the version that is now in CVS, although that will naturally not
necesarily be as up to date as the code that Jukka is still working on.

 If so, it is very good, I'd like
 to add some LaTeX-like formating after 1.2.6 will be released to make life
 easier for scientific applications of Midgard. Current implementation of parser
 has some limitations in extension scheme (you'll need to rewrite parser at
 least in two or three places in different packages), so modularizing it would
 be great. Actually, I've already have LaTeX-like formatting done in PHP using
 regular expressions and possibly support for PCRE in the text parser would be
 useful. I mean that text formating modules could use generalized API for
 accessing PCRE library like it is done with DB support.

Seems like you allready put some thought in this. I would welcome this
concept,
so if you have ideas on this API I'd gladly discuss the remifications.

 Then creating parsers
 would be more efficient (it could be relatively simple to create parser for
 Word-like format, as those apps already done in Perl and C). Thus, we could
 achieve the same feature set that proprietary systems (like NPS) sell for
 thousands of dollars. Especially it would be great if those parsers could be
 dynamically loaded (hence, optimisation for memory footprint will be very
 effective). Also real document flow is impossible without those things.

Hmm, nice. But the current parser does all it's work in memory; I'm not
sure
I'd want to serve many Word documents like this concurrently. If we want
to
use this we may want to have a way to circumvent this.

Emile

--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org

To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]