Marco van de Voort wrote:
I've seen that the vendor of the software that we use on window (dinkey)
also has linux and OS X bits. (dongling)
We didn't want to use hardware dongles - it will work out way to expensive.
Also you will be locked-in to a specific vendor (hoping they don't go out
of
Graeme Geldenhuys wrote:
Michael Van Canneyt wrote:
? OnGuard from turbopower does this. It is Object Pascal, so I don't see what
the problem with that could be ?
That is a sore point. We only found that after we did our implementation. :-(
Is the FPC+Lazarus port usable? Project status on
On Thu, Jan 21, 2010 at 11:22:22AM +0200, Graeme Geldenhuys wrote:
Besides the deployment issues, another thing that discourages me from
writing software for Linux is the virtual non existence of anti-cracking
software.
I know what you mean. We flew 1200km to the biggest Security
On Thu, Jan 21, 2010 at 12:23:17AM +0100, Mattias Gaertner wrote:
The frontend can be anything. Some GUIs shows graphical dialogs for
the questions.
Other points:
deb/rpm/ports/... repositories have some advantages:
- mirrors
- databases of all installed files
- databases of all
On 1/21/2010 02:25, Graeme Geldenhuys wrote:
zeljko wrote:
Just because WMaker is not freedesktop compliant ? ;)
And judging by the progress in recent years, a dead product.
if a product has fulfilled its goals, what progress is there to be made? ;)
updates/upgrades simply for
Graeme Geldenhuys wrote:
George Lober wrote:
that is easy to use by the average joe computer user whatever the
platform is. It is an idea to cater to the end user and the software
developer, and not some OSS or other status quo.
Considering what the task is, it is understandable a large
On Thu, 21 Jan 2010 08:44:21 +0200
Graeme Geldenhuys graemeg.li...@gmail.com wrote:
Mattias Gaertner wrote:
* have other customization options during the install. Not easily
at least. I have seen a handful of .deb packages that prompt for
a Yes/No question, but that's about
George Lober wrote:
The few that caught my eye were very basic, and not workable with closed
source commercial software.
http://developer.berlios.de/projects/fixinst/
http://autopackage.org/
We looked at projects like AutoPackage (I really liked this one),
ZeroInstall, etc... All
On Thu, Jan 21, 2010 at 11:22:22AM +0200, Graeme Geldenhuys wrote:
George Lober wrote:
[...]
Besides the deployment issues, another thing that discourages me from
writing software for Linux is the virtual non existence of anti-cracking
software.
I know what you mean. We flew 1200km to
On Thu, 21 Jan 2010, Graeme Geldenhuys wrote:
George Lober wrote:
The few that caught my eye were very basic, and not workable with closed
source commercial software.
http://developer.berlios.de/projects/fixinst/
http://autopackage.org/
We looked at projects like AutoPackage (I
Michael Van Canneyt wrote:
? OnGuard from turbopower does this. It is Object Pascal, so I don't see what
the problem with that could be ?
That is a sore point. We only found that after we did our implementation. :-(
Is the FPC+Lazarus port usable? Project status on wiki says beta, but so
On Thu, Jan 21, 2010 at 09:25:03AM +0200, Graeme Geldenhuys wrote:
zeljko wrote:
Just because WMaker is not freedesktop compliant ? ;)
And?
And judging by the progress in recent years, a dead product.
We mostly have it on servers yes. But I don't see why the installer wouldn't
be used to
On Thu, Jan 21, 2010 at 01:24:04AM +0200, Graeme Geldenhuys wrote:
(it might be wise to check out in how far these named programs are shared
linked)
True, those mentioned (and ones like ATI and Nvida drivers) tend to be
more on the commercial side of things. But then again, our company
Marco van de Voort wrote:
The point that I was trying to make, is that they are cross-distro exactly
because of that (being mostly statically linked).
OK. In our case, all our products and required features (encryption, xml
support, etc) are all compiled into the executable. So we simply need
Marco van de Voort wrote:
And judging by the progress in recent years, a dead product.
We mostly have it on servers yes. But I don't see why the installer wouldn't
be used to deploy a serverside product, with some GUI component as config
app.
Still, I wouldn't only support kde/gnome.
Graeme Geldenhuys schrieb:
On 20/01/2010, Jonathan wrote:
The is no frame work under Windows for the menu, just files thats
why you have silly company's listing there program under there
name.
I haven't looked at that code in a while, but our old Delphi programs
created there own icons.
Hans-Peter Diettrich wrote:
To find out whether to use there or their, try to replace it by my
Excellent, thanks. Afrikaans is so much simpler than English.
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
--
Graeme Geldenhuys wrote:
George Lober wrote:
The few that caught my eye were very basic, and not workable with closed
source commercial software.
http://developer.berlios.de/projects/fixinst/
http://autopackage.org/
We looked at projects like AutoPackage (I really liked this
On Thu, Jan 21, 2010 at 01:30:31PM +0100, zeljko wrote:
On Thursday 21 January 2010 11:08, Marco van de Voort wrote:
On Thu, Jan 21, 2010 at 09:25:03AM +0200, Graeme Geldenhuys wrote:
zeljko wrote:
Just because WMaker is not freedesktop compliant ? ;)
And?
And no default way
Hi,
Our company projects requires a flexible and easy to use setup program to
work on various Linux distros as well as Windows. Mac support will probably
come in a year or two, because currently our applications are only
available on Linux and Windows, so that is the platforms we are focusing on.
On Wed, 20 Jan 2010, Graeme Geldenhuys wrote:
Hi,
* Notification of hard drive space available and how much will be used by
selected features.
* different internal archive options: gzip, lzma, zip, tar.gz etc...
This might prove difficult. on linux, only .tar.gz is guaranteed to be
20.01.2010 15:06, Graeme Geldenhuys wrote:
We are primarily targeting deployment of Free Pascal based applications,
but the setup engine should be flexible enough to handle any type of
application (we hope). :)
We will probably release the setup and setup builder as Open Source
software once
Michael Van Canneyt wrote:
* different internal archive options: gzip, lzma, zip, tar.gz etc...
This might prove difficult. on linux, only .tar.gz is guaranteed to be
supported. If you want any of the others, you'll have to deploy the
uncompression engine as well.
Do don't plan on relying
Graeme Geldenhuys wrote:
So what feature do you require in a setup that we did not think of? What's
your wish list?
What I also forgot to mention are a few more features.
* Splash/Banner/Logo image support. If no image is
available, the setup GUI window adjust itself accordingly.
*
Paul Ishenin wrote:
My wish list - port innosetup (http://www.jrsoftware.org/isinfo.php)
which is written in delphi and is opensource project. We are using it
for lazarus windows installs.
I know about inno setup, but never used it before. We didn't want to port
something because we wanted
Graeme Geldenhuys graemeg.li...@gmail.com wrote:
Anyway, I would like to know what features your guys (as developers)
would like to see in a setup program.
I can think of the one additional feature:
* Checking dependencies. There is no such problem in fpGUI apps
since the only dependency is X
Vladimir Zhirov wrote:
* Checking dependencies. There is no such problem in fpGUI apps
since the only dependency is X :) But Lazarus apps can be stuck to
specific GTK/QT version(s).
That is exactly why the setup program is written with fpGUI. So even tiny
lite linux distros or even embedded
On Wed, 20 Jan 2010, Graeme Geldenhuys wrote:
Vladimir Zhirov wrote:
The clients we are targeting are all newcomers to Linux. They are used to
Windows with simply double clicking a setup.exe file. This is our goal for
Linux to - no opening of command prompts and typing (unless you are an
Michael Van Canneyt mich...@freepascal.org wrote:
On Wed, 20 Jan 2010, Graeme Geldenhuys wrote:
Vladimir Zhirov wrote:
The clients we are targeting are all newcomers to Linux. They are
used to Windows with simply double clicking a setup.exe file. This
is our goal for Linux to -
Sorry, I got my mails messed up, so here is the missing part:
Graeme Geldenhuys wrote:
I want to double click, then click next, next and finish -
and be done with it. :)
Well, then one more feature request :)
* Automated install procedure. It could be a command line option to
take a
Vladimir Zhirov wrote:
* Automated install procedure. It could be a command line option to
take a text/xml/ini file with setup options and do not require user
to press any buttons or type filesystem paths.
Yes we are considering the usual /silent or --silent parameter option, and
a option
Graeme,
I am sorry to tell you but your project is doomed to failure with the
requirements you listed.
In the end you will have a system that almost works, or works in 85% of the
cases, and you will be frustrated yourself.
Your idea is not new. Other people have banged their heads to wall as
Hans-Peter Diettrich wrote:
Support for user languages and countries.
That comes standard with all fpGUI applications. Currently we have
translations for 8 languages (af, de, en, es, fr, it, pt, ru).
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
On Wed, Jan 20, 2010 at 10:49:29AM +0200, Graeme Geldenhuys wrote:
[...Inno Setup...]
I know about inno setup, but never used it before. We didn't want to port
something because we wanted to think out-of-the-box and build it from the
ground up with cross-platform support in mind. Trying to
Juha Manninen wrote:
I am sorry to tell you but your project is doomed to failure with the
requirements you listed.
With that attitude, ALL developers would be out of business and we wouldn't
have things like Linux, OpenOffice or any open source projects for that
matter. :-) I gather your
stop...@muenster.de wrote:
I'd recommend to use the same syntax as inno-setup.
By that you mean the *.iss file?
eg: lazarus/tools/install/win/lazarus.iss
* fully documented
:-) Our setup.xml is already full documented (yeah, programmers that
document. WTF??) and the elements used are
Hi!
* we use recommended *.desktop and *.directory files for menu items
Do you mean there is a standard way for that for all window managers? Ok then,
I didn't know. There are tens of different window managers around.
Does RPM support dependency checks? Last time I used RedHat (years ago)
On Wed, Jan 20, 2010 at 12:31 PM, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
Does RPM support dependency checks? Last time I used RedHat (years ago) it
did not.
RPM surely always did support dependency checks. Some packages have
different names across distributions, which ruins the
Juha Manninen wrote:
* we use recommended *.desktop and *.directory files for menu items
Do you mean there is a standard way for that for all window managers? Ok
then,
I didn't know. There are tens of different window managers around.
Yes, there is a standard. Most (still active in
Felipe Monteiro de Carvalho wrote:
RPM surely always did support dependency checks. Some packages have
Not in the days I used RedHat. I'm talking long ago, from Redhat 5.0 to
about 8.1. :-)
I've just been spoilt with Ubuntu. I guess it's time I start trying out
other distros again. Slackware
On Wed, 20 Jan 2010 17:25:58 +0200
Graeme Geldenhuys graemeg.li...@gmail.com wrote:
Juha Manninen wrote:
* we use recommended *.desktop and *.directory files for menu items
Do you mean there is a standard way for that for all window managers? Ok
then,
I didn't know. There are tens
On Wed, Jan 20, 2010 at 04:41:48PM +0200, Graeme Geldenhuys wrote:
stop...@muenster.de wrote:
I'd recommend to use the same syntax as inno-setup.
By that you mean the *.iss file?
eg: lazarus/tools/install/win/lazarus.iss
Exactly.
* fully documented
:-) Our setup.xml is
- Vincent Snijders vsnijd...@vodafonevast.nl wrote:
But from the maintainer of fpgui which doesn't use an existing,
familiar
to the user widget set, another way (one kind of installer that runs
on
all systems, but does not match an existing packaging system) does not
surprise me
Please stop this flamewar, nobody is forced to use Graemes code.
His only intention was to get some feedback and tell us about his ideas,
thats how OSS works.
bye,
Stefan
--
Absender:
stop...@muenster.de escreveu:
Please stop this flamewar, nobody is forced to use Graemes code.
His only intention was to get some feedback and tell us about his ideas,
thats how OSS works.
+ 1
Keep going Graeme !
Luiz
--
___
Lazarus mailing
On Wed, Jan 20, 2010 at 10:06:55AM +0200, Graeme Geldenhuys wrote:
already implemented or at least went through the brain storming and design
idea phase. Here is our requirements and ideas we came up with:
* Linux distro independent setup. Against the normal methods, we do not
want to
On 20/01/2010, Mattias Gaertner nc-gaert...@netcologne.de wrote:
There seems to be a misunderstanding.
Both deb and rpm have package dependency resolution, but neither
downloads them automatically.
You must use tools like apt-get for debs and yum for rpms or even
Ah, so the RPM guys were
On 20/01/2010, Felipe Monteiro de Carvalho
felipemonteiro.carva...@gmail.com wrote:
Maybe you used it in the wrong way.
The rpm utility doesn't solve the dependencies, it's like the dpkg
utility from Debian.
Thanks. Mattias explained that I had a misunderstanding of how things
work.
- stop...@muenster.de wrote:
Please stop this flamewar, nobody is forced to use Graemes code.
His only intention was to get some feedback and tell us about his
ideas,
thats how OSS works.
Another way OSS works is that you're not our mommy.
Okay, here's some feedback: Use a
On 20/01/2010, stop...@muenster.de stop...@muenster.de wrote:
OK, I thought you are still in the early stages of evaluation.
No, we have had the setup tool on the table for some time, we just
did have time to implement everything yet. That's my task now.
Concerning XML:
From my point of
On 20/01/2010, Vincent Snijders vsnijd...@vodafonevast.nl wrote:
It is editable in the text editor. But also by IS-Tool, which is more like
an IDE for inno setup scripts.
I took a second look at the lazarus.iss file to see how install
features/options and there relationships are mapped in the
On 20/01/2010, Vincent Snijders vsnijd...@vodafonevast.nl wrote:
To bad, the ideal setup creator would get a setup.xml and compile it to
.rpm, .deb, windows installer, .dmg with Mac OS X package, etc.
Kind of like the Lazarus idea, one source for many OS/widget set
combinations.
Good
On 20/01/2010, stop...@muenster.de stop...@muenster.de wrote:
Please stop this flamewar, nobody is forced to use Graemes code.
Thanks Stefan. I always take what Vincent says with a pinch of salt.
We have some understanding that everything goes except on Fridays, and
I think I saw a smiley face
On Thu, 21 Jan 2010 00:56:06 +0200
Graeme Geldenhuys graemeg.li...@gmail.com wrote:
On 20/01/2010, Vincent Snijders vsnijd...@vodafonevast.nl wrote:
To bad, the ideal setup creator would get a setup.xml and compile it to
.rpm, .deb, windows installer, .dmg with Mac OS X package, etc.
On 20/01/2010, Marco van de Voort mar...@stack.nl wrote:
(it might be wise to check out in how far these named programs are shared
linked)
True, those mentioned (and ones like ATI and Nvida drivers) tend to be
more on the commercial side of things. But then again, our company
products are
On 20/01/2010, Jonathan wrote:
The is no frame work under Windows for the menu, just files thats why you
have silly company's listing there program under there name.
I haven't looked at that code in a while, but our old Delphi programs
created there own icons. I can't remember if it was
On 1/20/2010 17:15, Phil Hess wrote:
- stop...@muenster.de wrote:
Please stop this flamewar, nobody is forced to use Graemes code.
His only intention was to get some feedback and tell us about his
ideas,
thats how OSS works.
Another way OSS works is that you're not our mommy.
and
On 1/20/2010 17:18, Graeme Geldenhuys wrote:
On 20/01/2010, stop...@muenster.destop...@muenster.de wrote:
OK, I thought you are still in the early stages of evaluation.
No, we have had the setup tool on the table for some time, we just
did have time to implement everything yet. That's my
- waldo kitty wkitt...@windstream.net wrote:
Another way OSS works is that you're not our mommy.
and the other way around... we're not your mommy, either... the main
thing to
remember about OSS is there is no :( in OSS ;)
Waldo, I have no idea what that means. Hope it's
21.01.2010 8:06, Phil Hess wrote:
Part of this is probably related to the evolution of Lazarus more and more into
the best tool for developing Linux apps (which is great) but maybe less and
less the best tool for other platforms. And sure, that's no problem either, if
that's the direction
- Paul Ishenin i...@kmiac.ru wrote:
21.01.2010 8:06, Phil Hess wrote:
Part of this is probably related to the evolution of Lazarus more
and more into the best tool for developing Linux apps (which is great)
but maybe less and less the best tool for other platforms. And sure,
that's
Phil Hess wrote:
- waldo kitty wkitt...@windstream.net wrote:
Another way OSS works is that you're not our mommy.
and the other way around... we're not your mommy, either... the main
thing to
remember about OSS is there is no :( in OSS ;)
Waldo, I have no idea what
On 1/20/2010 20:06, Phil Hess wrote:
- waldo kittywkitt...@windstream.net wrote:
Another way OSS works is that you're not our mommy.
and the other way around... we're not your mommy, either... the main
thing to
remember about OSS is there is no :( in OSS ;)
Waldo, I have no idea
Graeme Geldenhuys schreef:
On 20/01/2010, Vincent Snijders vsnijd...@vodafonevast.nl wrote:
It is editable in the text editor. But also by IS-Tool, which is more like
an IDE for inno setup scripts.
I took a second look at the lazarus.iss file to see how install
features/options and there
Mattias Gaertner wrote:
* have other customization options during the install. Not easily
at least. I have seen a handful of .deb packages that prompt for
a Yes/No question, but that's about it. Most prompted in a console
window (ugly) and one or two prompted in a GTK2 dialog
Phil Hess wrote:
- LCL with Qt widgetset (if you don't mind the overhead: OOP LCL -- OOP
widgetset -- non-OOP QtIntf library -- OOP Qt (C++) -- Cocoa).
All of these are acceptable native solutions,
Very interesting Phil. You have no problems with Qt and even call it
native, yet fpGUI
Phil Hess wrote:
Many of the ideas expressed here seem to start with Linux and end with Linux.
Probably because Linux is becoming a more attractive platform than all
others for desktop applications. Also maybe because Lazarus IDE is simply
the best tool for the job - hands down!
So live with
George Lober wrote:
that is easy to use by the average joe computer user whatever the
platform is. It is an idea to cater to the end user and the software
developer, and not some OSS or other status quo.
Considering what the task is, it is understandable a large focus is on
the Linux
zeljko wrote:
Just because WMaker is not freedesktop compliant ? ;)
And judging by the progress in recent years, a dead product.
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
--
waldo kitty wrote:
s/did have/did not have/ ??
Correct. :-) I was typing while being half asleep.
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
--
___
Lazarus mailing
70 matches
Mail list logo
