Panic over. Today I took a random meander around some of the snippets of
code I have collected over the last few years and actually managed to
assemble a GUI.
I now have a simple window with two pull down menus and three buttons.
Not exactly high tech but it will do the job perfectly for now.
So how do you set a program up to accessed from anywhere as you would
expect to be able to use it?
On 03/05/15 12:01, Alan Pope wrote:
It will be rejected if you do.
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/
Correct, my software is ready to roll, it is simply a case of knowing
where to install it to make it accessible. Should no better suggestions
be put forward I shall attempt to submit your solution and see if it
gets accepted.
On 03/05/15 21:50, Colin Law wrote:
I thought you had got over the
On 3 May 2015 at 20:55, Gareth France gareth.fra...@cliftonts.co.uk wrote:
My brain still hurts from figuring out everything I have done so far. I'd
rather not have to start again if I can at all help it. As you say there
will be a correct way to do this and I would hope that being pointed to
There is no point in botching it to make it work as that's not really an
instruction I can expect anyone downloading it to have to follow.
Will the packaging moderators be happy with me installing to /usr/local?
On 03/05/15 11:33, Simon Greenwood wrote:
Your immediate fix is to run 'export
On 3 May 2015 at 10:47, Gareth France gareth.fra...@cliftonts.co.uk wrote:
With a little help from Paul Sladen I got it sorted thanks. My only issue
now is that the installed package only runs if you call it using the full
path /opt/cliftontestsuite/primetest. Just typing primetest an any
The packaging tutorial ends with:
Basic DOs and Dont's for packaging for Commercial Applications
DOs
Please use /opt/application_name/ as your application root directory
I have no idea if it is in $PATH but this is a stock install and I need
this to just work on a stock install.
On
On 02/05/15 22:30, Gareth France wrote:
Ok, I am really, really needing some help here. I have resolved all the
issues one by one, except for an issue with the format. It is set to 3.0
(quilt) but I keep getting this error:
Gareth Just over a year ago, I had a go at making a Debian Sword
On 3 May 2015 at 12:01, Alan Pope a...@popey.com wrote:
On 3 May 2015 at 11:36, Gareth France gareth.fra...@cliftonts.co.uk wrote:
There is no point in botching it to make it work as that's not really an
instruction I can expect anyone downloading it to have to follow.
Will the packaging
With a little help from Paul Sladen I got it sorted thanks. My only
issue now is that the installed package only runs if you call it using
the full path /opt/cliftontestsuite/primetest. Just typing primetest an
any random location does not work. Is this by design or have I screwed up?
On
On 3 May 2015 at 10:55, Gareth France gareth.fra...@cliftonts.co.uk wrote:
The packaging tutorial ends with:
Basic DOs and Dont's for packaging for Commercial Applications
DOs
Please use /opt/application_name/ as your application root directory
I have no idea if it is in $PATH but this
On 3 May 2015 at 11:36, Gareth France gareth.fra...@cliftonts.co.uk wrote:
There is no point in botching it to make it work as that's not really an
instruction I can expect anyone downloading it to have to follow.
Will the packaging moderators be happy with me installing to /usr/local?
It
On 3 May 2015 at 12:44, Gareth France gareth.fra...@cliftonts.co.uk wrote:
So how do you set a program up to accessed from anywhere as you would expect
to be able to use it?
Well, typically applications that are submitted via that means are
shipped with a graphical user interface, an icon and
As most people are now well aware I'm desperate to be able to work out
GUI programming, but it does not seem to be my fate. There must be a
correct way to submit a commercial command line only program. It is
virtually useless if each user must be taught to use the full path each
time.
On
On 03/05/15 20:04, Gareth France wrote:
As most people are now well aware I'm desperate to be able to work out
GUI programming, but it does not seem to be my fate. There must be a
correct way to submit a commercial command line only program. It is
virtually useless if each user must be taught to
My brain still hurts from figuring out everything I have done so far.
I'd rather not have to start again if I can at all help it. As you say
there will be a correct way to do this and I would hope that being
pointed to that correct way I would be able to do so with the tools I am
already
debian/source/format:3.0 (quilt)
debian/cliftontestsuite.install:primetest /opt/cliftontestsuite/
On 02/05/15 21:43, Paul Sladen wrote:
Please post the output of:
$ grep . debian/{source/format,*.install}
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
Ok, I am really, really needing some help here. I have resolved all the
issues one by one, except for an issue with the format. It is set to 3.0
(quilt) but I keep getting this error:
dpkg-source: warning: no source format specified in
debian/source/format, see dpkg-source(1)
The format is
On Sat, 2 May 2015, Gareth France wrote:
debian/source/format
debian/cliftontestsuite.install
Please post the output of:
$ grep . debian/{source/format,*.install}
-Paul
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 2 May 2015, Gareth France wrote:
debian/source/format:3.0 (quilt)
I've run a few experiments trying variations like weird DOS line
endings, extra lines/newlines and so forth but I can't reproduce
the error message that you are seeing.
On 28 April 2015 at 09:17, Gareth France gareth.fra...@cliftonts.co.uk wrote:
I must apologise that I have limited time to look at this, usually at the
end of the day when I'm not at my best anyway. I've just performed debbuild
on it and taken some time to scrutinise the output. It does seem to
All the reading in the world isn't going to change the issues which to
the best of my ability appear to be correct. The format file in
debian/source contains:
3.0 (quilt)
Which as far as I can see is correct.
On 28/04/15 09:32, Alan Pope wrote:
Honestly, read the documentation. You have
On 28 April 2015 at 08:22, Gareth France gareth.fra...@cliftonts.co.uk wrote:
If it were clear how to do this then I would most certainly have done so. In
practice I may have or I may have not. I have followed as much of the
process as makes sense.
Please don't top post, thanks.
Are you
On 28 Apr 2015 08:22, Gareth France gareth.fra...@cliftonts.co.uk wrote:
If it were clear how to do this then I would most certainly have done so.
In practice I may have or I may have not. I have followed as much of the
process as makes sense.
It's incredibly unprofessional to upload software
If it were clear how to do this then I would most certainly have done
so. In practice I may have or I may have not. I have followed as much of
the process as makes sense.
On 28/04/15 08:19, Alan Pope wrote:
The idea is that you test the package yourself before submission rather
than use the
On 27 Apr 2015 20:35, Gareth France gareth.fra...@cliftonts.co.uk wrote:
I have just submitted my program. What has been so frustrating for me is
that I know it is a simple process once you have done it. I'm certain I've
got it wrong but I should be able to deal with that thanks to feedback from
I'm saying that the guide steps you through packaging one example where
the work has already been done. Applying that to a fresh project is
impossible as it skips important steps that you need to know. It is not
possible for someone who has not done this before to follow the guide!
No I have
I must apologise that I have limited time to look at this, usually at
the end of the day when I'm not at my best anyway. I've just performed
debbuild on it and taken some time to scrutinise the output. It does
seem to be experiencing some issues, though I'm a bit stumped as to what
to do next:
On Sat, 25 Apr 2015 23:46:18 +0100
Gareth France gareth.fra...@cliftonts.co.uk wrote:
I have written some software I would like to publish in Ubuntu.
Following the official guides I can create their demo program which
simply prints 'hello world' on the screen. Unsurprisingly I'm looking
to
I didn't think you could package commercial pay for software that way.
On 27/04/15 09:21, Dave Morley wrote:
If it's just command line I would suggest just using a ppa on launchpad
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
So how do you explain the likes of get-iplayer?
I would love to develop a gui app but it is physically impossible and
nobody seems willing to help me with that.
On 27/04/15 11:29, Dave Morley wrote:
On Mon, 27 Apr 2015 11:18:36 +0100
Gareth France gareth.fra...@cliftonts.co.uk wrote:
I
On Mon, 27 Apr 2015 11:18:36 +0100
Gareth France gareth.fra...@cliftonts.co.uk wrote:
I didn't think you could package commercial pay for software that way.
On 27/04/15 09:21, Dave Morley wrote:
If it's just command line I would suggest just using a ppa on
launchpad
Ah not commercial
I have just submitted my program. What has been so frustrating for me is
that I know it is a simple process once you have done it. I'm certain
I've got it wrong but I should be able to deal with that thanks to
feedback from the submission process.
--
ubuntu-uk@lists.ubuntu.com
On 27 April 2015 at 11:47, Gareth France gareth.fra...@cliftonts.co.uk wrote:
So how do you explain the likes of get-iplayer?
That's not a commercial app in the store, it's a free software
application packaged up in the standard ubuntu repository.
I would love to develop a gui app but it is
On 27 April 2015 at 12:57, Gareth France gareth.fra...@cliftonts.co.uk wrote:
Alan, I have tried to work out the process of creating a GUI and it's so
alien from what I know to be programming. The SDK will generate an empty
package for me but then what??? I've followed the tutorials and ended
Probably worth starting from the beginning and stopping when it gets
difficult and ask for help at that point.
Ok, load the SDK, open a new project. Now I'm stuck. I just don't get
any aspect of the concept of graphical programming.
I really do think the only way I'm going to get it is to have
On 27 April 2015 at 13:37, Gareth France gareth.fra...@cliftonts.co.uk wrote:
Ok, load the SDK, open a new project. Now I'm stuck. I just don't get any
aspect of the concept of graphical programming.
I really do think the only way I'm going to get it is to have some time face
to face with
Alan, I have tried to work out the process of creating a GUI and it's so
alien from what I know to be programming. The SDK will generate an empty
package for me but then what??? I've followed the tutorials and ended up
with something that's almost working and absolutely no understanding of
how
On Mon, 27 Apr 2015 13:37:31 +0100
Gareth France gareth.fra...@cliftonts.co.uk wrote:
Probably worth starting from the beginning and stopping when it gets
difficult and ask for help at that point.
Ok, load the SDK, open a new project. Now I'm stuck. I just don't get
any aspect of the
On 27/04/15 13:50, Dave Morley wrote:
If it is a cli tool you can create an application launcher that calls
terminal and then opens the cli app but that is not recommended,
however it is not impossible and takes longer to review.
As for the gui guide follow the many examples on
This is a good place to start. I've been through this tutorial,
written by someone else, and it worked. It really clearly steps
through every bit of the process. It's good for QML applications which
are mobile focussed, less good for legacy type desktop applications
though.
My program needs
On 27 April 2015 at 14:25, Gareth France gareth.fra...@cliftonts.co.uk wrote:
This is a good place to start. I've been through this tutorial,
written by someone else, and it worked. It really clearly steps
through every bit of the process. It's good for QML applications which
are mobile
On 27/04/15 14:36, Andy Partington wrote:
Documenting is the way forward! I do it to everything I do now, my
memory sucks!!! I just bullet point each procedure I do and expand as
and where necessary after I've worked it out.
I agree with you and have already tried that. I think sometimes the
On 27 April 2015 at 17:17, Gareth France gareth.fra...@cliftonts.co.uk wrote:
Could anyone suggest what I am supposed to put for copyright and licensing
if I'm doing a commercial project?
By commercial I wonder if you mean proprietary?
Either way, take a look at the copyright file you get
On 27/04/15 13:50, Dave Morley wrote:
You need to read up on creating a debian package.
https://developer.ubuntu.com/en/publish/other-forms-of-submitting-apps/packaging-commercial-apps-part-1-get-set-up-overview-of-debian-packaging/
Yes I do mean proprietary. I'm building this software as a product for
my business, I have chosen to go down the proprietary route and charge
for the program as if course it does need to make a profit. I am open to
any suggestions as to how I could monetise my product better in line
with the
When following the guides for submitting it talks you through setting up
your system, then the content of the various files. Then it steps you
through downloading, compiling and submitting the hello program. However
it states that hello uses the autoconf build system, but doesn't tell
you
I have written some software I would like to publish in Ubuntu.
Following the official guides I can create their demo program which
simply prints 'hello world' on the screen. Unsurprisingly I'm looking to
do much more than that! However the guides miss out a lot of important
information and
48 matches
Mail list logo
