Hi,
A footnote to the conversation.
Cava Packager now has a 'non-commercial' option that requires no user
registration.
There is also special provision for use by Open Source projects. (this
does still require one time user registration but has liberal license
terms to allow the freedom of
Ok.
I feel the pain. I think you've got hold of the wrong end of the stick
slightly. The current differences between the 'free beer' subscription
plus the continued need for user login are purely down to attempting to
accommodate free use in the existing code. The user management stuff and
on
Mark Dootson writes:
> A non-commercial usage option is now available for individuals
> distributing non-commercial apps (required download version 2.0.16).
> Free as in beer.
Mark, you're breaking my heart.
Your work for the wxPerl community is invaluable and I very much
appreciate it.
CavaP
rce applications.
I wonder if keeping Cava open source (and I did not even know it
ever was open source) would really interfere with the idea of selling
it as subscription based service. That's up to Mark to decide.
Distributing wxPerl applications to nonexpert users is still a pain.
This may be
Hi,
The list is at http://groups.google.com/group/cava-packager/topics?hl=en
On 21/12/2010 20:13, perltk wrote:
What is the Cava list address ?
On 12/20/2010 9:41 PM, Mark Dootson wrote:
Hi,
As Cava Packager has been mentioned on the list a few times I'm
dropping a note to advise that Cava P
What is the Cava list address ?
On 12/20/2010 9:41 PM, Mark Dootson wrote:
Hi,
As Cava Packager has been mentioned on the list a few times I'm
dropping a note to advise that Cava Packager now supports MacOSX and
Linux in addition to Windows as promised some time ago.
A shameless plug perhap
e to encourage people to make
money using Perl even if that means closed source applications.
I wonder if keeping Cava open source (and I did not even know it
ever was open source) would really interfere with the idea of selling
it as subscription based service. That's up to Mark to decide.
tion fee to allow other people to use my free applications.
Moreover, this means that Cava is now a closed source application and I
try to avoid closed source apps as much as possible.
Distributing wxPerl applications to nonexpert users is still a pain.
This may be one of the reasons there are
On Dec 21, 2010, at 8:09 AM, Huub Peters wrote:
> On Dec 21, 2010, at 3:41 AM, Mark Dootson wrote:
>
>> Hi,
>>
>> As Cava Packager has been mentioned on the list a few times I'm dropping a
>> note to advise that Cava Packager now supports MacOSX and Linux in addition
>> to Windows as promised
On Dec 21, 2010, at 3:41 AM, Mark Dootson wrote:
> Hi,
>
> As Cava Packager has been mentioned on the list a few times I'm dropping a
> note to advise that Cava Packager now supports MacOSX and Linux in addition
> to Windows as promised some time ago.
>
> A shameless plug perhaps, but it is a
Hi,
As Cava Packager has been mentioned on the list a few times I'm dropping
a note to advise that Cava Packager now supports MacOSX and Linux in
addition to Windows as promised some time ago.
A shameless plug perhaps, but it is a cross platform application written
using wxPerl that can help
the target machine.
--
Octavian
- Original Message - From: "perltk"
To:
Sent: Tuesday, August 03, 2010 2:44 PM
Subject: Re: AW: Distributing wxPerl applications - Perlapp
The point of perlapp is that you don't even need perl installed on
machines where app runs. So
ust 03, 2010 2:44 PM
Subject: Re: AW: Distributing wxPerl applications - Perlapp
The point of perlapp is that you don't even need perl installed on
machines where app runs. So you can have a different verison(s) of perl
installed and the standalone will completely ignore them. Like PAR, it
b
ot;'Johan Vromans'"
; "'Daniel Carrera'"
Cc:
Sent: Tuesday, August 03, 2010 1:12 AM
Subject: RE: AW: Distributing wxPerl applications
On Mon, 02 Aug 2010, ademmler wrote:
hi,
I am using all of those tools and the major difference is the concept
b
f course, Strawberry has its own issues so I am trying to find the
best solution.
--
Octavian
- Original Message - From: "Jan Dubois"
To: "'Octavian Rasnita'" ; "'ademmler'"
; "'Johan Vromans'" ;
"'Daniel C
ginal Message -
From: "Jan Dubois"
To: "'Octavian Rasnita'" ; "'ademmler'"
; "'Johan Vromans'" ; "'Daniel
Carrera'"
Cc:
Sent: Tuesday, August 03, 2010 8:59 AM
Subject: RE: AW: Distributing wxPerl
Dear Jan,
I understand your whish, but I have stopped using ActiveState some
month at all and I have no simple sample.
The simple ones are working and I cant ship you my svn contents for
testing.
The biggest Problem: "cant find module . . . ." even if everything
should be in there.
I sw
Hi Octavian and the others,
Actually CavaPacker is only for Windows available. It is on the plan
to make Linux and MacOX X Versions.
There is a special Note about on the website:
NOTE: Cava Packager Professional has not yet been released. You can
download Version 1.3 of
Cava Packager fro
y
> that PDK requires ActivePerl.
>
> Isn't this true?
>
> --
> Octavian
>
> - Original Message -
> From: "Jan Dubois"
> To: "'ademmler'" ; "'Johan Vromans'"
> ; "'Daniel Carrera'"
> C
mler'" ; "'Johan Vromans'"
; "'Daniel Carrera'"
Cc:
Sent: Tuesday, August 03, 2010 1:12 AM
Subject: RE: AW: Distributing wxPerl applications
On Mon, 02 Aug 2010, ademmler wrote:
hi,
I am using all of those tools and the major difference is th
niel Carrera"
Cc:
Sent: Monday, August 02, 2010 11:39 PM
Subject: Re: AW: Distributing wxPerl applications
hi,
I am using all of those tools and the major difference is the concept
behind:
A) perl2exe never made it succsesfully for me.
B) ActiveStae perlapp I could not run wtihout Act
On Mon, 02 Aug 2010, ademmler wrote:
>
> hi,
>
> I am using all of those tools and the major difference is the concept
> behind:
>
> B) ActiveStae perlapp I could not run wtihout ActiveStae Per . . .
> (non strawberry)
Could you provide me with a sample that fails? PerlApp generally works
fine
hi Daniel,
and be aware there is traps and problems always and every where. I had
project coding a week and packaging took also a week or longer.
Especially addonig libs like libusb, image magick and so on needs
extra tweeks.
Sometimes it is easier on Mac to juts put all into the local dir
Hi Alexander,
Excellent information. Thanks!
The comment about ActiveState PerlApp is very important. I don't want
to make a program that only work with Active Perl.
>From what you say, it seems like the best option might be: (1)
Standard .deb or .rpm on Linux, (2) PAR on Mac, and (3) Cava on
Wi
hi,
I am using all of those tools and the major difference is the concept
behind:
A) perl2exe never made it succsesfully for me.
B) ActiveStae perlapp I could not run wtihout ActiveStae Per . . .
(non strawberry)
C) PAR is generating some ZIP Archive containing everything. While
launc
Hi,
I have the following experiences. different systems differnet ways how
to get the best result:
- Windows: CavaPackager (even ActiveState perlapp had problems with
wxPerl code)
- Linux: PAR
- Mac OS X: Actually some selfmade "collect modules" + AppWarpper made
by Platypus
If Cava be
Daniel Carrera writes:
> Does Cava work better than PAR? How would you compare them? What's the
> ETA for Cava to be cross-platform?
>
> I don't have any urgency. I am not a commercial developer with a deadline.
Then I suggest you repeat this question in a couple of weeks when (I
assume) the Cav
On Mon, Aug 2, 2010 at 8:03 PM, Johan Vromans wrote:
> Cava will be multi-platform soon.
>
> ActiveState PDK ('perlapp') already works nice on all platforms but is a
> commercial product. If you have seral apps to ship is may be worth
> considering.
>
> Perl 'PAR' works nice in many cases as well.
Daniel writes:
> I always use the cava packager, but my applications are for Windows
> only and it works very well. Unfortunately there is no tool like Cava
> for Linux or Mac OS (or I don't know it).
Cava will be multi-platform soon.
ActiveState PDK ('perlapp') already works nice on all platfo
y well. Unfortunately there is no tool like Cava for Linux or
> Mac OS (or I don't know it).
>
> Regards
> Daniel
>
>
>
> Von: Daniel Carrera
> An: Alessandro
> CC: wxperl-users@perl.org
> Gesendet: Montag, den 2. August 2010, 16:
l.org
Gesendet: Montag, den 2. August 2010, 16:46:44 Uhr
Betreff: Re: Distributing wxPerl applications
On Mon, Aug 2, 2010 at 3:49 PM, Alessandro
wrote:
> Hello,
> isn't http://www.cava.co.uk/ what you're looking for?
Possibly. Have you tried it? Does it work well? I am not famili
On Mon, Aug 2, 2010 at 3:49 PM, Alessandro
wrote:
> Hello,
> isn't http://www.cava.co.uk/ what you're looking for?
Possibly. Have you tried it? Does it work well? I am not familiar any
of these tools. I'm only beginning to learn about PerlApp, PAR and
Cava.
I'm sure that there are people here wh
On Mon, Aug 2, 2010 at 1:24 PM, perltk wrote:
> Yes, from my personal use/experimenting. Theres Perlapp or PAR or make an
> '.app" on OSX. The trick is including & using the wx binary libs you pacakge
> up. But it isn't going to be write once , run everywhere.
Thanks. It looks like PerlApp is p
; wxperl-users@perl.org
Gesendet: Montag, den 2. August 2010, 15:49:58 Uhr
Betreff: Re: Distributing wxPerl applications
Hello,
isn't http://www.cava.co.uk/ what you're looking for?
Alessandro
2010/8/1 Daniel Carrera
> Hello,
>
> Is it difficult to package and dis
Hello,
isn't http://www.cava.co.uk/ what you're looking for?
Alessandro
2010/8/1 Daniel Carrera
> Hello,
>
> Is it difficult to package and distribute a wxPerl application? I am
> thinking, for example, how Windows and Mac OS don't have a package
> manager with wxPerl, wxWidgets and so on, so
Yes, from my personal use/experimenting. Theres Perlapp or PAR or make
an '.app" on OSX. The trick is including & using the wx binary libs you
pacakge up. But it isn't going to be write once , run everywhere.
On 8/1/2010 3:52 PM, Daniel Carrera wrote:
Hello,
Is it difficult to package and d
Hello,
Is it difficult to package and distribute a wxPerl application? I am
thinking, for example, how Windows and Mac OS don't have a package
manager with wxPerl, wxWidgets and so on, so you have to package all
the dependencies with you. And for Linux the situation isn't much
better. Yes Linux di
37 matches
Mail list logo
