public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Mark required input fields with a star
Date: Sat, 27 Jun 2015 12:45:52 +0200	[thread overview]
Message-ID: <1435401952.13892.88.camel@ipfire.org> (raw)
In-Reply-To: <op.x0votcdrcahio0@honk.fritz.box>

[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]

Alright. The first two TODOs are easy. There is a variable called $blob
which is defined a couple of lines above. You would need to change the
if statement so that it checks for "net" and that should do the job I
guess.

The other huge blocks need to be cut in two pieces. Usually they use
something that looks like this:

print <<END;
   ABC
   DEF
   123
END

This will simply print everything between the print statement and END.
It will stop when ever there is a line with just "END" in it.

So you could cut that in two parts:

print <<END;
   ABC
   DEF
END

if ($something) {
	print "123\n";
}

That is basically it.

I am not entirely sure if that answers all your questions, so feel free
to ask back if there is anything else you would like to know :)

-Michael

On Sat, 2015-06-27 at 09:37 +0200, Larsen wrote:
> On Thu, 25 Jun 2015 12:28:51 +0200, Alexander Marx <alexander.marx(a)oab.de>  
> wrote:
> 
> >>>>> On Thu, 2015-06-04 at 23:46 +0200, Larsen wrote:
> >>>>>> PS: Need help with the TODOs in that patch as I am now web developer
> >>>>>> and where I don´t know how to use an if-clause.
> >>>>> As these are in the ovpnmain.cgi (as far as I have seen) you should  
> >>>>> get
> >>>>> in touch with Alex when he is back from holiday. That will be towards
> >>>>> the end of next week.
> >>>> Should not be related to ovpnmain.cgi. I just don´t have the  
> >>>> experience
> >>>> how to combine html-code and if-clauses here. Any dev might be able to
> >>>> give a hint here.
> > Hi
> > All "HTML" Files are the cgi files within /srv/web/ipfire/cgi-bin.
> > These Files are CGI's which means it can be any programming language.
> > The IPFire CGI's are usually written in perl. So one can easily use perl  
> > if-clauses.
> > When it comes to the output part you also use Perl code to "print" the  
> > htmlcode.
> 
> Yes, I know where to change it, but I don´t know how exactly to combine  
> perl code and HTML.
> Please have a look at the parts marked with TODO here:
> http://patchwork.ipfire.org/patch/15/
> 
> In other places, there is a huge "print" part where perl gives out HTML in  
> one block. Here however, I need to use perl inside one of those blocks.
> 
> 
> Lars

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-06-27 10:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 21:31 Larsen
2015-06-04 21:46 ` Larsen
2015-06-05 14:45   ` Michael Tremer
2015-06-05 14:43 ` Michael Tremer
2015-06-07 10:05   ` Larsen
2015-06-24 22:28     ` Larsen
2015-06-25 10:05       ` Michael Tremer
2015-06-25 10:28         ` Alexander Marx
2015-06-27  7:37           ` Larsen
2015-06-27 10:45             ` Michael Tremer [this message]
2015-06-28 20:21               ` Larsen
2015-06-29 12:55             ` Alexander Marx
2015-08-22 20:43 Larsen
2015-08-26 15:34 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1435401952.13892.88.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox