>> but now that you bring this on Windows I have
>> remembered PortableApps at www.portableapps.com I have tested with people
...
> This could be very good. Thanks for this link.
A PortableApps version of Leo would be very cool and emminently
usable, but it's not likely to be an easy path. They do
On Tue, Aug 31, 2010 at 10:55 PM, Offray Vladimir Luna Cárdenas
> but now that you bring this on Windows I have
> remembered PortableApps at www.portableapps.com I have tested with people
> not fluent with computers and this is dead easy for them. I think that there
> is even a portable app creato
Hi,
El 16/08/10 21:53, Sam Hartsfield escribió:
On Aug 16, 2:37 pm, Terry Brown wrote:
Sure, if that was what it takes, it's not feasible. My thought was to set up python,
leo, and Qt in a single directory - the directory would then be installed by the
"leo" installer, so that you end up
On Aug 31, 12:06 pm, "Edward K. Ream" wrote:
> I doubt a1 will happen this Friday--there have been just too many
> interesting distractions. However, we aren't that far away from a1.
> Perhaps in 5 to 10 days.
I've been wondering myself exactly how to set reasonable schedules.
Setting priorit
On Aug 14, 11:09 am, "Edward K. Ream" wrote:
> 1. The best possible docs for newbies...
> 2. The best possible installer for newbies.
It may not be completely obvious, but these are still my
priorities :-)
I doubt a1 will happen this Friday--there have been just too many
interesting distract
On Fri, Aug 27, 2010 at 5:25 PM, Paul Moore wrote:
> 1. Python version. I don't typically have multiple Python versions on
> my PC, and I generally upgrade fairly rapidly to the latest version.
> So for me, right now, an installer which required Python 2.6 would be
> a pain
The installer will pr
On 17 August 2010 15:14, Edward K. Ream wrote:
> I don't mind thinking of Leo in that way, but I'm not going to package
> Python with Leo.
OK, fair enough. However, some things need to be sorted out in that case:
1. Python version. I don't typically have multiple Python versions on
my PC, and I
On Fri, Aug 27, 2010 at 11:51 AM, Todd Mars wrote:
> Proper thing to do is run Python installer and run QT installer if
> user says to, from the Leo installer first.
I don't believe that the Leo installer should download other
installers, so the question is, which installers should Leo's
installe
Proper thing to do is run Python installer and run QT installer if
user says to, from the Leo installer first.
In either case if the user installs Leo, and Python and QT are
installed, it should work. It does not now.
(my new Win7 install did not a few days ago)
Just takes a bit of work that's all,
On Tue, Aug 17, 2010 at 8:59 PM, Steve Allen wrote:
> Leo installation doesn't seem to be an issue with Linux (at least with
> Ubuntu which I'm familiar with), so I won't comment on Linux
> installations.
>
> However, on the subject of Windows and Mac installations (and
> subsequent execution), ar
Leo installation doesn't seem to be an issue with Linux (at least with
Ubuntu which I'm familiar with), so I won't comment on Linux
installations.
However, on the subject of Windows and Mac installations (and
subsequent execution), are there insurmountable barriers to
creating .EXE and .DMG files?
> I don't mind thinking of Leo in that way, but I'm not going to package
> Python with Leo.
For anybody who does decide to pick up the challenge of improving the
installer:
It is perfectly reasonable for a new user to get the message "Sorry,
python not found, go get it from ..." and to stop insta
On Tue, Aug 17, 2010 at 9:31 AM, Edward K. Ream wrote:
> I am not going to do this, and I shall reject any patches that do this.
I might consider a patch from somebody with 5+ years as a full-time
developer of installers, who not only showed how the patch was
developed and tested, but also prese
On Tue, Aug 17, 2010 at 1:04 AM, taa, Leo Newbie wrote:
>>My thought was to set up python, leo, and Qt in a single directory - the
>>directory would then be installed by the "leo" installer, so that you end
>>up with leo and its private copies of python/qt in c:\program
>>files\leo\leo or somesuch
On Mon, Aug 16, 2010 at 9:53 PM, Sam Hartsfield wrote:
> On Aug 16, 2:37 pm, Terry Brown wrote:
>> Sure, if that was what it takes, it's not feasible. My thought was to set
>> up python, leo, and Qt in a single directory - the directory would then be
>> installed by the "leo" installer, so tha
On Mon, Aug 16, 2010 at 1:37 PM, Terry Brown wrote:
> My thought was to set up python, leo, and Qt in a single directory - the
> directory would then be installed by the "leo" installer, so that you end up
> with leo and its private copies of python/qt in c:\program files\leo\leo or
> somesuch
On Mon, Aug 16, 2010 at 1:34 PM, Seth Johnson wrote:
> On Mon, Aug 16, 2010 at 12:02 PM, Edward K. Ream wrote:
>>
>> Installing Python and PyQt along with Leo does not seem like a
>> reasonable goal, but perhaps there is a plugin that would allow the
>> Leo installer to chain to other installers.
>My thought was to set up python, leo, and Qt in a single directory - the
>directory would then be installed by the "leo" installer, so that you end
>up with leo and its private copies of python/qt in c:\program
>files\leo\leo or somesuch. Dumb, inelegant, and the lowest possible
>barrier to the L
On Aug 16, 2:37 pm, Terry Brown wrote:
> Sure, if that was what it takes, it's not feasible. My thought was to set up
> python, leo, and Qt in a single directory - the directory would then be
> installed by the "leo" installer, so that you end up with leo and its private
> copies of python/qt
On Mon, 16 Aug 2010 12:55:47 -0500
"Edward K. Ream" wrote:
> On Sun, Aug 15, 2010 at 8:55 PM, Terry Brown wrote:
>
>
> > Although it may clash with the philosophy of the NSIS installer, what about
> > including Python [and qt] in the .exe installer?
>
> I see no good way of avoiding using th
On Mon, Aug 16, 2010 at 12:02 PM, Edward K. Ream wrote:
>
> Installing Python and PyQt along with Leo does not seem like a
> reasonable goal, but perhaps there is a plugin that would allow the
> Leo installer to chain to other installers...
Hmm, isn't Leo really closely allied with Python? Why w
On Aug 15, 6:33 pm, "Edward K. Ream" wrote:
> By far the easiest approach will be to improve Leo's present NSIS
> installer.
Indeed it is. Using the NSIS compiler is likely to be 100 times
easier than using any other tool.
I have made a good start in improving the install script. For
exampl
On Sun, Aug 15, 2010 at 8:55 PM, Terry Brown wrote:
> Although it may clash with the philosophy of the NSIS installer, what about
> including Python [and qt] in the .exe installer?
I see no good way of avoiding using the "official" installers.
The Python installer is extremely complex: take
On Sun, 15 Aug 2010 21:54:52 -0500
Terry Brown wrote:
> Hmm, just trying to install leo in win 7 64bit in VirtualBox. First attempt,
> python2.7-64bit + pyqt - failed, I think because of 32/64 bit. Will try all
> 32 bit downloads.
Ok, win 7 64bit in VirtualBox, 32 bit python 2.7 and pyqt 4.7
Hmm, just trying to install leo in win 7 64bit in VirtualBox. First attempt,
python2.7-64bit + pyqt - failed, I think because of 32/64 bit. Will try all 32
bit downloads.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, s
On Sun, 15 Aug 2010 18:33:41 -0500
"Edward K. Ream" wrote:
> On Sat, Aug 14, 2010 at 11:09 AM, Edward K. Ream wrote:
>
> > 2. The best possible installer for newbies.
>
> I've made a quick review of the process of creating Windows
> installers. It isn't pretty.
>
> By far the easiest approac
On Sat, Aug 14, 2010 at 11:09 AM, Edward K. Ream wrote:
> 2. The best possible installer for newbies.
I've made a quick review of the process of creating Windows
installers. It isn't pretty.
By far the easiest approach will be to improve Leo's present NSIS
installer. The other ways are either
On Aug 14, 11:09 am, "Edward K. Ream" wrote:
> 2. The best possible installer for newbies.
Creating .msi files is "interesting".
Googling "open software msi installers" I found
http://www.advancedinstaller.com/.
It has several versions, including a freeware version that I am about
to explore
On Aug 14, 11:21 am, "Edward K. Ream" wrote:
> Haven't found the installer sources on svn. Still looking...
Here they are: /python/trunk/Tools/msi
/python/trunk/Tools/buildbot/buildmsi.bat
http://svn.python.org/view/python/trunk/Tools/buildbot/buildmsi.bat?revision=76534&view=markup
/python/t
On Aug 14, 11:09 am, "Edward K. Ream" wrote:
> With this new view, my plan is to become somebody who can build a
> respectable installer, if not an installer guru. Python has a
> respectable installer, which should be on view because Python is open
> source. Studying how Python does it might
My response on a related topic today got me thinking about the
installer. As soon as did so, it became obvious that the big picture
for Leo is to attract new users. Duh!
That being so, it again became obvious that the following is the *one
and only* possible priority list for me:
1. The best po
31 matches
Mail list logo
