Hi Steve,

I would like to look just crazy busy at the moment.
Are you just wanting feed back on the code or testing the app and criting
the code?
On 24 Feb 2014 18:35, "Steve Teale" <steve.teale@britseyeview.com> wrote:

> On Monday, 17 February 2014 at 17:56:08 UTC, Steve Teale wrote:
>
>> On Monday, 17 February 2014 at 06:57:55 UTC, Steve Teale wrote:
>>
>>> I would love to get some feedback on both the application and the documentation
>>>
>>
> You must forgive me for harping on about this, but I am going to be persistent. Between COMPO 1 and COMPO 2, there's the best part, or more, of a man-year's work. So I won't let go lightly.
>
> Today I have posted two new .deb files (i386/amd64) on the COMPO web site - http://britseyeview.com/compo/. There's decent online documentation at the same place. The stage of operations is now QA, and since I am the author, you know that at this point, I need help ;=)
>
> The source code is also up-to-date on https://github.com/britseye/compo.
>
> Come on guys, give me an hour of your precious time.
>
> Steve
>

On Monday, 24 February 2014 at 18:08:34 UTC, Rory McGuire wrote:
> Hi Steve,
>
> I would like to look just crazy busy at the moment.
> Are you just wanting feed back on the code or testing the app and criting
> the code?

What I need most is comment on the usability and scope of the application - am I wasting my time if I continue to work on it?

If you think it's OK, then testing. It's always difficult to critically test your own application. You know how it works and what it's supposed to do, and that knowledge channels you.

I mostly know where the code is a mess, and can fix that over time. At the moment I'm sticking to the old adage - if it ain't broken, don't mend it.

Thanks
Steve

On Monday, 24 February 2014 at 16:30:43 UTC, Steve Teale wrote:
> On Monday, 17 February 2014 at 17:56:08 UTC, Steve Teale wrote:
>> On Monday, 17 February 2014 at 06:57:55 UTC, Steve Teale wrote:
>>> I would love to get some feedback on both the application and the documentation
>
> You must forgive me for harping on about this, but I am going to be persistent. Between COMPO 1 and COMPO 2, there's the best part, or more, of a man-year's work. So I won't let go lightly.
>
> Today I have posted two new .deb files (i386/amd64) on the COMPO web site - http://britseyeview.com/compo/. There's decent online documentation at the same place. The stage of operations is now QA, and since I am the author, you know that at this point, I need help ;=)
>
> The source code is also up-to-date on https://github.com/britseye/compo.
>
> Come on guys, give me an hour of your precious time.
>
> Steve

However I go about building this, I get linker errors about libusps4cb.a

Where can I find the source for this library? Or at the very least can you upload a x86_64 version?

On Wednesday, 26 February 2014 at 00:43:58 UTC, John Colvin wrote:
> On Monday, 24 February 2014 at 16:30:43 UTC, Steve Teale wrote:
>> On Monday, 17 February 2014 at 17:56:08 UTC, Steve Teale wrote:
>>> On Monday, 17 February 2014 at 06:57:55 UTC, Steve Teale wrote:
>>>> I would love to get some feedback on both the application and the documentation
>>
>> You must forgive me for harping on about this, but I am going to be persistent. Between COMPO 1 and COMPO 2, there's the best part, or more, of a man-year's work. So I won't let go lightly.
>>
>> Today I have posted two new .deb files (i386/amd64) on the COMPO web site - http://britseyeview.com/compo/. There's decent online documentation at the same place. The stage of operations is now QA, and since I am the author, you know that at this point, I need help ;=)
>>
>> The source code is also up-to-date on https://github.com/britseye/compo.
>>
>> Come on guys, give me an hour of your precious time.
>>
>> Steve
>
John,

I'm sorry. Trying to do too many things at the same time. libusps4cb is a binary provided by the US Postal Service for creating postal bar codes. They don't publish the source.

I had the .a file for COMPO1, and that still seems to work OK, but they don't do static libraries any more, so for a 64 bit build you'll need to use libusps4cb.so.  They are both in compo/lib on GitHub. The .a file is 32 bit, and the .so file 64 bit.

Steve

I will get the 32 bit .so file and regularize the situation
> However I go about building this, I get linker errors about libusps4cb.a
>
> Where can I find the source for this library? Or at the very least can you upload a x86_64 version?

Steve,

Does compo2 allow you to add effects to layers?


On Wed, Feb 26, 2014 at 10:26 AM, Steve Teale <steve.teale@britseyeview.com>wrote:

> On Wednesday, 26 February 2014 at 00:43:58 UTC, John Colvin wrote:
>
>> On Monday, 24 February 2014 at 16:30:43 UTC, Steve Teale wrote:
>>
>>> On Monday, 17 February 2014 at 17:56:08 UTC, Steve Teale wrote:
>>>
>>>> On Monday, 17 February 2014 at 06:57:55 UTC, Steve Teale wrote:
>>>>
>>>>> I would love to get some feedback on both the application and the documentation
>>>>>
>>>>
>>> You must forgive me for harping on about this, but I am going to be persistent. Between COMPO 1 and COMPO 2, there's the best part, or more, of a man-year's work. So I won't let go lightly.
>>>
>>> Today I have posted two new .deb files (i386/amd64) on the COMPO web site - http://britseyeview.com/compo/. There's decent online documentation at the same place. The stage of operations is now QA, and since I am the author, you know that at this point, I need help ;=)
>>>
>>> The source code is also up-to-date on https://github.com/britseye/compo.
>>>
>>> Come on guys, give me an hour of your precious time.
>>>
>>> Steve
>>>
>>
>>  John,
>
> I'm sorry. Trying to do too many things at the same time. libusps4cb is a binary provided by the US Postal Service for creating postal bar codes. They don't publish the source.
>
> I had the .a file for COMPO1, and that still seems to work OK, but they don't do static libraries any more, so for a 64 bit build you'll need to use libusps4cb.so.  They are both in compo/lib on GitHub. The .a file is 32 bit, and the .so file 64 bit.
>
> Steve
>
> I will get the 32 bit .so file and regularize the situation
>
>  However I go about building this, I get linker errors about libusps4cb.a
>>
>> Where can I find the source for this library? Or at the very least can you upload a x86_64 version?
>>
>
>

On Wednesday, 26 February 2014 at 08:41:29 UTC, Rory McGuire wrote:
> Steve,
>
> Does compo2 allow you to add effects to layers?
>
A composition is:

Container
   - Layer 1
   - Layer 2
   - Layer 3
   ...

The layers can be of any kind, including effects, though if they are not in a sensible order, opaque layers will hide layers underneath.

A file can be:

Composition 1
Composition 2
Layer 4
Layer 5
...

In any order.

Layers in a composition may use other compositions or stand-alone layers (e.g. Layer 4) as fill, so in that sense, yes, you can add effects to a layer as long as the layer is a closed and fillable figure. All but one of the closed figure types are fillable.

Steve

I've just had a hack at the structure of the GitHub repo.
It is now, as suggested by Iain Bucklaw, less flat. The source is in a separate directory, and I've added a package.json file at the top level so COMPO can be built with DUB.

I also updated the README file to talk about library dependencies, put both makefiles (32 and 64) in a makefiles directory, and added libusps4cb.so (see the README).

I hope it is gradually getting more civilized.

Steve