On 03/25/2013 02:55 PM, Ryo Anazawa wrote:
Hi all,
Thanks for maintaining CGI::Application.
I'll release yet another CGI::Application plugin,
CGI::Application::Plugin::Header, on CPAN soon.
I've taken a second look at this, and have some more feedback on it.
- The docs open by
On 03/25/2013 05:04 PM, Ron Savage wrote:
Hi Ryo
Why on earth do you use a '-' prefix on parameters?
While I wouldn't use the - prefix in documentation or otherwise
promote it, I could see silently or quietly *supporting* it, if one one
of your objectives is to be CGI.pm-compatible.
He
I've now made some edits that I believe should disable edit access to
the old wiki. I've asked David Kaufman at Erlbaum.net to reload Apache
for us so that they can take effect.
It will remove the edit button from every page, and will prevent a
direct POST to the edit processing run mode from
On 01/17/2013 01:26 PM, Brian Wightman wrote:
Ok, I don't plan on plan wack-a-mole with this bozo.
Any other easy-to-implement LARTs available until things are fully
transferred to the new wiki?
Maybe we could put the old wiki in read-only mode?
I have not looked into this, but it doesn't
On 11/21/2012 07:46 PM, Ron Savage wrote:
Hi Mark
On 22/11/12 01:25, Mark Stosberg wrote:
What I have now is for Moose and a bit project-specific, but I plan to
make CPAN-ready Moo-based variants at some point.
Just for record, you can't use a BUILD sub with Moo. I'm just trying
What I have now is for Moose and a bit project-specific, but I plan to
make CPAN-ready Moo-based variants at some point.
Would you support Moo /and/ Moose variants long term? I wouldn't bother
myself.
Or are you saying the public versions would use Moo?
I doubt it. We'd like to switch
I am planning to change CGI::Snapp's base class from Hash::FieldHash to
Moos (sic).
I would definitely support using one of the Moose-compatible projects. I
am thinking of moving PSGI::Application from Any::Moose to Moo.
I looked at 'Moos' a bit as well. I factored in that Moo has quickly
Ron,
Thanks for all the feedback. Follow-ups are below.
* query() is now req() and new(QUERY=...) is now
new(REQUEST=...)
I'd go with request(). I see no need to introduce an abbreviation.
For reference:
Catalyst uses both request() and req()
Mojolicious uses only req()
Dancer
On 11/06/2012 12:27 PM, Kurt Lidl wrote:
On 11/6/2012 12:24 PM, Mark Stosberg wrote:
* Hash keys for new() must now be upper-case now.
Ridiculous. Lower case hash keys are the norm throughout Perl.
Upper case is SHOUTING.
I agree that lower case hash keys are the norm and upper case hash
On 11/06/2012 01:55 PM, Giannis Economou wrote:
On 6/11/2012 8:36 μμ, Mark Stosberg wrote:
On 11/06/2012 12:27 PM, Kurt Lidl wrote:
On 11/6/2012 12:24 PM, Mark Stosberg wrote:
* Hash keys for new() must now be upper-case now.
Ridiculous. Lower case hash keys are the norm throughout Perl
Brett, I think this existing functionality would provide what you want:
PSGI::Application-new_hook('authorization');
PSGI::Application-add_callback('authorization', \callback);
Kind of, but what it doesn't allow me to do is affect the order in
which the lifecycle hooks are executed. I
As previously announced here, I've been working on a significant update
to CGI::Application focused on Mouse/Moose and PSGI, and also breaking
backwards compatibility in some cases.
What I've published now is in a fairly complete, stable state. Docs are
there are tests are passing.
Still, not
On 11/02/2012 01:37 PM, Brian Wightman wrote:
CGI::Application page http://cgi-app.org/index.cgi?MVC edited by
MidLifeXis
I have been starting to migrate some of the 'simpler' pages from
erlbaum.netto github. Please take a look at the few changes I have
made, as I am
contemplating writing
Thanks for the feedback, Ron and Brian.
Is there any thought (or even value) to migrating the current data into the
git wiki history? Given sufficient tuits (and the original data - can be
after the cutover is done), I would be willing to help with submitting a
pull request on this.
I
euclid: lib/cgi-bin % setenv DEBUG 1
euclid: lib/cgi-bin % ./sascgi 'SASFILE=getlist1.sasLISTS=1ITEMS=20'
I understand why this error occurs, but not how to fix it, at either the
perl or OS level.
WHY: It seems that in my current ubuntu precise release, /bin/sh
has been replaced by
Start over the wiki using a new platform.
It's due for a refresh anyway. I'm sure a lot of the content should
use a review for updates, purging and adding, and the design is stale
now as well.
Are you thinking of a pre-existing system?
Yes. There are a number of options now.
The
On 10/25/2012 05:58 PM, Ron Savage wrote:
Hi Mark
On 26/10/12 02:01, Mark Stosberg wrote:
On 10/25/2012 10:51 AM, Brian Wightman wrote:
Are we able to block this username (I know it won't be very effective) from
doing any type of updates? Perhaps just bit-bucketing them or blacklisting
On 10/25/2012 10:51 AM, Brian Wightman wrote:
Are we able to block this username (I know it won't be very effective) from
doing any type of updates? Perhaps just bit-bucketing them or blacklisting
the IP for a period of time?
I believe we have, or can have, root access on the server where the
The company I co-founded has posted a job opening for a Perl/JavaScript
contract developer. Telecommute applications are welcome:
http://www.summersault.com/about/careers/position-perl-javascript-developer/
The position could include helping us update the project to incorporate
more PSGI and
On 10/15/2012 08:42 AM, Mike Tonks wrote:
Another issue that has come up along the way is using $ENV
While this is fine under apache it doesn't seem to work with PSGI.
You are correct that PSGI uses $env, not %ENV.
A common occurence is using $ENV{REMOTE_ADDR} for a user IP Address,
but
On 10/12/2012 09:06 AM, Mike Tonks wrote:
I've been doing some more testing and it seems to work really well.
Serving up big files quite happily, and fast!
A few additional thoughts...
The PSGI spec allows 2 useful options:
1) The subref callback as originally suggested
2) Return a
This is as far as I've got. Can anyone help / advise? Maybe patching
CAP::Stream is the way to go - I suppose it should be possible to
detect the running environment and 'do the right thing'.
Mike,
My reading of the spec is that you can return a callback instead of a
body, and the Plack
On 09/15/2012 05:00 PM, Jiří Pavlovský wrote:
On 15.9.2012 3:22, Mark Stosberg wrote:
Regarding performance, I recently benchmarked accessor generation time
for Moo vs Mouse vs Moose vs manual accessors (what CGI::App uses) and
raw hashes. In a persistent environment like you are using Moose
Bill--
I've sort of taken my own path to create web apps, and while it works for me,
I've gotten some blowback for it a few times over the years, but I really
don't mind that, so I'll explain it.
I have a small demo Note Pad app at www.raspberryperl.com:
app -
I know that you're right according to common practice, so I have to
admit it made me laugh reading that this morning for that very reason.
But... in my (weak) defense, in chapter three, page 119, of Lincoln's
book, The official guide to programming with CGI.pm is the Advanced
Trick that
So the fix isn't good enough. I think line 422 should be
unless ( ref $e $e-isa('Exception::Class::Base') ) {
Thanks Michael.
I've now released 3.12 which incorporates this fix from you, as well as
a test fix from Graham TerMarsch.
Mark
# CGI::Application community mailing
This job posting from Energy Fundamentals is specifically looking for a
Senior Perl Developer with experience with CGI::Application.
The position is Zurich, but telecommuting is an option for candidates in
the EU. Details here:
http://jobs.perl.org/job/16384
Mark
# CGI::Application
Bill,
Thanks for feedback. Responses are below.
On 09/02/2012 01:46 PM, Bill Stephenson wrote:
Hi Mark,
Nice to hear you're going to move forward with the CAP project.
After reading your comments about CGI.pm, and comments from others
here, I'm left wondering about a few things. If
Brett,
Thanks for the feedback.
- A ::Compat addition that allows people to keep using a maximal
amount of the old API if they need to. (Including a certain amount of
plugins)
Or maybe just do something like how perl5 turns on new version based
features (e.g., use CGI::Application
- Uses Any::Moose / Mouse. I endorse the Moose API and Mouse brings
much of that API to lower resource environments, like the CGI
environment where CGI::Application has always performed well.
This is tricky. Why is the env low-resourced? And if it is, what's wrong
with targeting
Richard,
Thanks for the feedback.
But since C::A first appeared we now have newer frameworks like
Catalyst, Mojo, and the more recent Dancer (also in the process of
being rewritten to embrace the Moose API). Given that Ron has already
forked C::A I wonder if there is any point embarking on
On 08/31/2012 03:46 AM, Michael Lackhoff wrote:
On 31.08.2012 04:21 Mark Stosberg wrote:
You can find the bug queue for it here:
https://rt.cpan.org/Dist/Display.html?Name=CGI-Application-Dispatch
some months ago I wrote a message to this list with the problem of bug
#78552
Subject
Hello everyone,
A few bugs have piled up on the queue for CGI::Application::Dispatch,
and help would be appreciated seeing that they are all addressed.
You can find the bug queue for it here:
https://rt.cpan.org/Dist/Display.html?Name=CGI-Application-Dispatch
The related Github repo is
I started writing my own fork over a year ago in hopes of having
something to share around the time for YAPC 2011. While I needed to put
that on hold for a while, It's now on the verge of the initial release.
Here are the key points I have mind for the update I'll be publishing
soon:
- A
Hello Everyone.
I'll start with a apology about not being as present as I intended.
Messages from this list were not coming directly to my Inbox for some
time, and it took me longer than I wanted to get that addressed.
Starting today, messages should be going back in my Inbox again, and I
will
On 02/19/2012 04:39 PM, Ron Savage wrote:
Hi Folks
Firstly, the code:
===8===
#!/usr/bin/env perl
use feature 'say';
use CGI;
use CGI::Simple;
# --
say 'CGI: ', CGI - new - redirect;
say 'CGI::Simple: ', CGI::Simple - new - redirect;
===8===
Then the output:
Does any of this affect the mailing list, since it uses lists.erlbaum.net?
As you observe, that appears to be hosted separately.
Mark
# CGI::Application community mailing list
####
## To unsubscribe, or
On 12/18/2011 08:14 PM, Ron Savage wrote:
Hi Folks
Is anyone using Chrome's Javascript [1]?
Or heard of anyone using it?
[1] http://code.google.com/p/v8/
We've used it to support running jshint/jslint over a code base on the
server side, via node.js.
Mark
# CGI::Application
...that makes a lot of sense, so maybe we should get the new wiki
set up, with an initial draft of topology, layout, etc, and then migrate
the content across. It doesn't sound like this would take long if we
split up the tasks between a few of us and we have windows in
diaries.
Mark co:
The cgi-app.org domain has been been moved from GoDaddy to Namecheap. I
missed updating the GoDaddy name servers in advance, and the site is
unavailable at the moment while I correct that.
If you need to find the content in the meantime, it is available at at:
http://cgiapp.erlbaum.net/
I
Tim Appnel has proposed adding REST tunneling to
CGI::Application::Dispatch dispatcher.
We discussed this some on-list in the past and found that REST tunneling
is also in Jaldhar's REST plugin.
Although I'm a fan of small core with heavy use of plugins, this kind if
REST handling strikes me as
On 09/09/2011 03:40 AM, Nicholas Bamber wrote:
At line 5 there is use Try:Tiny rather than use Try::Tiny.
Nicholas,
3.06 has now been pushed to CPAN with this fix, with credit to you.
Thanks.
Mark
# CGI::Application community mailing list
##
On 08/07/2011 10:32 AM, Emmanuel Seyman wrote:
* Jerry Kaidor [07/08/2011 16:02] :
Does Wiki editing require a captcha? If not, maybe it should. Automated
spam will stop when you require that a human being enter it. Because that
costs the spammers money.
See the previous discussion on
On 07/05/2011 02:29 AM, Nicholas Bamber wrote:
The latest release of CGI::Session appears to be unauthorized. I can
find it at http://search.cpan.org/~markstos/CGI-Session-4.45/ but ifyou
click on permalink it disappears.
Thanks for the note.
I've now uploaded to 4.46 to address this issue.
Module dependency minimum versions are one of the areas that has become a
really irritating part of using CPAN for me. If an author *knows* they need
some minimum version of something else, maybe because previous versions
lacked a feature they need, then I'm all for including the version. I'd
On 06/24/2011 02:31 PM, Nicholas Bamber wrote:
Mark,
Thanks for keeping on top of CGI::Application. I am puzzled that
Build.PL for CGI::Application::Dispatch mentions CGI::PSGI version 1,
which seems not to exist. Both this version and the previous worked fine
anyway, so this is more
On 06/21/2011 09:16 AM, Mark Stosberg wrote:
The new CGI::Application::Dispatch 3.0 release is failing some
PSGI-related tests on most-but-not-all platforms:
http://www.cpantesters.org/distro/C/CGI-Application-Dispatch.html#CGI-Application-Dispatch-3.00
3.01 was released last night, which
The new CGI::Application::Dispatch 3.0 release is failing some
PSGI-related tests on most-but-not-all platforms:
http://www.cpantesters.org/distro/C/CGI-Application-Dispatch.html#CGI-Application-Dispatch-3.00
Help would be welcome looking into those. I'll try to get to them in the
next 48 hours
On 06/14/2011 10:00 PM, silent wrote:
Hi, list
can I do displaying form and validate form only in one run mode ?
It is not designed for this.
# run mod
sub register {
if ( GET request ) {
#display form
}elsif ( POST requst ) {
#validate
}
}
To put
After a long incubation period, perhaps too long, CGI::Application has
been updated today with native PSGI support in the core module as well
as PSGI-native dispatcher.
The changes since the last stable versions for each module are included
below. You can now find and review on the new MetaCPAN
On 05/14/2011 02:20 AM, Joshua Miller wrote:
Is there a reason the home page can be modified by anyone sans-registration
and sans-approval?
No good reason. Does anyone want to be the wiki admin and see about
making that change with the current software, or moving us to a
better/newer wiki
CGI::Application::Dispatch::PSGI gives any CGI script using CGI::App
access to PSGI's amazing capabilities. It's what I use for every CGI
script, nowadays.
Ron,
Could you test the Github version of CAD::PSGI if you haven't already?
As part of re-implementing it better, it should be a little
On 05/11/2011 10:16 PM, Jaldhar H. Vyas wrote:
On Wed, 11 May 2011, Mark Stosberg wrote:
Jaldhar,
Could point out specifically where your auto-tunneling feature is in the
plugin?
Oops. The tunneling code is actually in REST::Utils which C::A::P::REST
depends on. Here is the POD from
Some of us here have been bitten by CGI.pm's behavior under mod_rewrite,
which is common to use with CGI::Application::Dispatch.
This test illustrates the issue:
###
use Test::More;
use CGI;
print CGI: $CGI::VERSION\n;
%ENV = (
# These two are always set
'SCRIPT_NAME' =
I know I keep tooting my own horn but all this and more is already present
in CGI-Application-Plugin-REST.
Jaldhar,
Could point out specifically where your auto-tunneling feature is in the
plugin? You may want to add the keyword tunneling somewhere in the
docs near where you document that
On 05/11/2011 07:47 PM, Ron Savage wrote:
Hi Tim
Just glancing at the code:
If you call lc at line 399, surely the check 2 lines down should be for
'post', not 'POST'?
Or am I missing something?
It looks like you are looking at the line 399 that shows up on the
side of the patch for
On 03/11/2011 11:20 PM, Ron Savage wrote:
Hi James
On Fri, 2011-03-11 at 19:58 -0800, James.Q.L wrote:
Thanks for reporting it on RT.
I think C::A::D should respect C::A's start_mode. If no rm is defined in
C::A::D rules, the start_mode in the dispatched module should be used.
A
Plack eliminates the start-up time of each invocation, as does any other
persistent environment (Fast CGI, mod_perl, ...):
Plack only eliminates the start-up time if you choose a persistent
backend, including a Plack server. Plack still allows you to run scripts
as a CGI.
If you choose to run
On 12/18/2010 06:37 PM, Nicholas Bamber wrote:
I notice that a 4.43 o CGI::Session has been released. That should get
into Debian in due course. Reviewing the Debian bug list I noticed this:
Session file not being written for driver:File; serializer:Storable
I recently researched and tested all of the URI percent-encoding
solutions for Perl (including CGI.pm and CGI::Simple, which are commonly
used with CGI::Application), and thought you might be interested in the
result:
http://mark.stosberg.com/blog/2010/11/percent-encoding-uris-in-perl.html
a previous thread is below.
Mark
On 02/12/2010 12:23 PM, Mark Stosberg wrote:
I have been following the development of PSGI and Plack closely [1], and I
recommend that CGI::Application provide first-class support for the PSGI
protocol.
1. http://plackperl.org/
PSGI is a port
o Off-list msgs to me have revealed deep disquiet and frustration over
Mark's handling of a number of projects, including CGI::Session
I welcome feedback about projects I manage on list and directly from
those who would like to share it.
Mark
# CGI::Application community mailing
On 11/26/2010 04:07 PM, Gurunandan R. Bhat wrote:
Hi,
I am moving my application to work under CA::Dispatch and using
mod_rewrite to hide the dispatch script (index.cgi) from the URL.
I am using rewrite rules .htaccess copy-pasted (without change) from the
CA::Dispatch man page and I am
Hello,
Thanks to those of you that alerted me that cgi-app.org is down. I
passed this information on to Jesse Erlbaum yesterday, and he replied
that he is actively working on a fix. I expect it will available again
soon. I'm sorry for the inconvenience.
Mark
# CGI::Application
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark StosbergPrincipal Developer
m...@summersault.com Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
# CGI::Application community mailing list
On Tue, 2 Mar 2010 13:38:15 -0500
Mark Stosberg m...@summersault.com wrote:
On Thu, 25 Feb 2010 17:51:40 -0600
P Kishor punk.k...@gmail.com wrote:
following Mark Stosberg's email about PSGI, I decided to poke around a
bit more, and landed up with Dancer. Color me very impressed
http://search.cpan.org/~miyagawa/Plack-0.99_05/lib/Plack/Handler/CGI.pm
Did you mean Plack::Server::CGI?
No. The ::Server name space has been deprecated in favor of the ::Handler
name space:
http://github.com/miyagawa/Plack/blob/master/lib/Plack/Server/CGI.pm
Mark
#
To keep this process moving along, I would like add the comment period will
last for one week, until February 19th.
I've also uploaded a developer release with the proposed change to CPAN
to give it some broader exposure.
Mark
On Fri, 12 Feb 2010 12:23:55 -0500
Mark Stosberg m
but as long as it
maintains backwards compat. (which I think it does) it sounds like a
good step forward.
Thanks for the feedback. There are no plans to break backwards-compatibility as
part of this.
It's a relatively small change in the amount of code added.
Mark
--
Also, would it be true to say that using PSGI is one way to do it, and
another way is to use things like:
o Net::FastCGI
o AnyEvent::FCGI
o FCGI
o FCGI::Async
o FCGI::Client
o FCGI::EV
For instance, I've just downloaded FCGI::Async, and in the examples/ dir
I found exec-cgi.fcgi, which
It remains to be seen if I will be able to make it to YAPC::NA, so I
will probably not be able to speak on our framework. Lets see if we can
get a few people who really want to speak, and pair them up with others
here who have the knowledge, but don't want to speak.
I am interested in
I have been following the development of PSGI and Plack closely [1], and I
recommend that CGI::Application provide first-class support for the PSGI
protocol.
1. http://plackperl.org/
PSGI is a port of the WSGI protocol used by Python, which has already proven
successful in that language
I believe what Mark is referring to is Stinki -- the Simple TItaNium wiKI
which I mentioned to him at YAPC-NA last year. I began renovating
CGI::Wiki::Simple which Lyle found on CPAN. And then I got distracted and
forgot about it. So today I put it up on github, you may find it at
Yes, MT4 is not a wiki, but do we really need a wiki for now?
I find wiki's great for collaborative editting because of their very
low bar for contribution.
Classically, MT4's model is that of a blog, but because it offers
multiple users to contribute, and offers an extensive amount of
The idea was that the 315 subscribers to this mailing list are the only
people in the world with the slightest motivation to delete spam from
the wiki and, since its not a terribly thriving, active wiki, even we
members of the cgiapp community don't visit it all that much.
So my hope
On Wed, 11 Nov 2009 02:30:21 +
r...@savage.net.au wrote:
Hi Mark
Quoting Mark Stosberg m...@summersault.com:
To proceed, I'd like to hear at least a small chorus of voices
claiming that the they use
the die_on_bad_params feature.
I always use it, since in testing I want
On Sat, 07 Nov 2009 10:48:02 +0530
Gurunandan R. Bhat g...@informationmatters.in wrote:
Hi,
Is CGI::Application::PSGI available? The link from the Plack website
gives a 404.
Are you referring to this link?
http://search.cpan.org/dist/CGI-Application-PSGI
It works now. Miyagawa wrote
On Sat, 07 Nov 2009 10:48:02 +0530
Gurunandan R. Bhat g...@informationmatters.in wrote:
Hi,
Is CGI::Application::PSGI available? The link from the Plack website
gives a 404.
Are you referring to this link?
http://search.cpan.org/dist/CGI-Application-PSGI
It works now. Miyagawa wrote
I don't know how many people use die_on_bad_params, so I don't
know how worth it it is to modify the core.
I have never used die_on_bad_params with HTML::Template. At least
two of the mostly-API-compatible projects choose not to support enabling the
option:
HTML::Template::Compiled has the
that others can use
it and help maintain the browser matching over time.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark StosbergPrincipal Developer
m...@summersault.com Summersault, LLC
765-939-9301 ext 202 database driven websites
from?
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark StosbergPrincipal Developer
m...@summersault.com Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
# CGI
On Sat, 17 Oct 2009 10:47:05 +0200
Alex cap...@gmx.de wrote:
Dear all!
I recently polluated another cpan root namespace by including a test
application in a dist. That's bad. I wonder if there isn't a test namespace
in the CGI::Application namespace itself. So anyone releasing a plugin with
On Thu, 3 Sep 2009 14:37:20 -0700
Mark Fuller azful...@gmail.com wrote:
On Thu, Sep 3, 2009 at 1:56 PM, Mark Rajcokmraj...@gmail.com wrote:
When I think of CGI::App though, I don't think of onions or leaves...
I agree. The proposed logos are very nice. But, I don't get the
connection to
::Authorization in this
situation? Should I expect CAP::Auth to work out-of-the-box with
CA::Dispatch?
I think these tools should be work together. In fact, I think I'm using
them together myself.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark StosbergPrincipal
On Mon, 03 Aug 2009 14:54:10 -0700
a...@spatialsystems.org wrote:
I have a textarea field to evaluate and peg errors line by line. So
if line 2 and line 5 are invalid, I want to note that as two different
errors.
It is normal for fields to have more than one constraint, with the possiblity
See what is going on -- C::A::P::Routes correctly thinks the runmode
is ‘mainpage’ as per the URL. However, $self-get_current_runmode()
returns ‘welcome’ in cgiapp_prerun(), and as a result, the mainpage is
not protected. Now, it could be that C::A::P::Routes is firing *after*
my
On Thu, 30 Jul 2009 01:20:14 -0400
David Kaufman da...@gigawatt.com wrote:
Hi Mark,
Mark Stosberg wrote:
[...] the wiki is currently returning a technical error page. I've notified
Jesse about this now, and when I have am able to remember my password on
that
machine again, I may
Thanks to everyone who gave input on the mailing list possibilities. I
particularly want to thank Jesse Erlbaum for his gracious list hosting over the
years, and Lyle Hopkins for pro-actively allowing us to explore another
alternative.
The official mailing list will be staying here for now,
On Thu, 23 Jul 2009 12:37:37 -0400
Mark Stosberg m...@summersault.com wrote:
sub html_tmpl_class { 'HTML::Template::Compiled' }
But: how do I replace the html_tmpl_class() in the calling app? I don't get
how I call the init hook. I guess (at least I hope) it's something very
simple
.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark StosbergPrincipal Developer
m...@summersault.com Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
# CGI::Application
On Tue, 14 Jul 2009 10:11:57 -0700
Stephen Carville stephen.carvi...@gmail.com wrote:
Whilst searching for something else I came across this
http://www.appcelerator.com/
IANAL so I have no idea of this affects your use of Titanium as a name.
This Titanium came after our use of Titanium
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark StosbergPrincipal Developer
m...@summersault.com Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
# CGI::Application community mailing list
Mark Stosberg wrote:
Could someone who is more UTF-8 savvy than myself peer review this simple
UTF-8
patch for CGI::Application for me?
http://rt.cpan.org/Public/Bug/Display.html?id=46513
You can comment through the ticket or here.
Mark
You may find this thread
Could someone who is more UTF-8 savvy than myself peer review this simple UTF-8
patch for CGI::Application for me?
http://rt.cpan.org/Public/Bug/Display.html?id=46513
You can comment through the ticket or here.
Mark
--
http://mark.stosberg.com/
# CGI::Application community
I'm planning to release a simple update to CGI::Application soon and wanted to
allow for some feedback first.
Relatively recently, the 'html_tmpl_class()' class method was added, as a way
to more easily specify an alternative to HTML::Template. Because of the simple
original implemenation, this
On Wed, 24 Jun 2009 18:10:48 +1000
Ron Savage r...@savage.net.au wrote:
Hi Mark
As I clicked on your link to Strign::Dirify, but the attachment had been
scrubbed!
http://www.sixapart.com/pipermail/mtos-dev/2008-December/002249.html
It's still linked to from there as attachment.bin. I
On Wed, 24 Jun 2009 13:34:06 +0530
Gurunandan R. Bhat g...@informationmatters.in wrote:
Thats great news.
I checked out from Git but could not find references or use of
CGI::Application anywhere in the source.
Has development begun?
The work done so far has been planning work linked to from
Today Melody was announced as a fork of the perl-based Movable Type
platform. I have been advising the project in part because some of the
other group members are interested in refactoring this fork so that it
uses CGI::Application and possibly some plugins.
Through my blog post I provide some
On Fri, 5 Jun 2009 15:16:43 -0400
Nathaniel Smith n...@summersault.com wrote:
Greetings,
I have uploaded a plugin that provides lightweight query validation using
Params::Validate. The release on CPAN is stable and tested but has not seen
production use. Any and all feedback or review
A couple of years ago there was discussion about a PDF plugin that
Evan Zacks was working on.
Evan, are you still out there? Any updates on this plugin progress:
http://www.mail-archive.com/cgiapp@lists.erlbaum.net/msg04186.html
Mark
# CGI::Application community mailing list
1 - 100 of 715 matches
Mail list logo
