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 abo
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,
>
>>>>
>>> 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
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
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/.
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
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 CO
. 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 st
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
Have now done a dual-boot install of Ubuntu 12.04 64 bit, and
built COMPO using that. Seems to pass limited sanity testing.
Will make a .deb file
On Saturday, 8 February 2014 at 06:03:18 UTC, Steve Teale wrote:
>
I have to take a break from developing it, and write some
documentation now.
OK, I have made some reasonably complete documentation, and that
now replaces the COMPO stuff I had on the web at
http://britseyeview.com/co
On Monday, 10 February 2014 at 07:11:17 UTC, Iain Buclaw wrote:
You mean one humungous file?
Nope. Create a directory 'compo', move all sources I. The
folder and update
the module names from 'module text' -> 'module compo.text'
Iain,
I live in fear
old British twit has been taking the mushrooms again.
> >> This is all quite beyond me! ;-)
> >>
> >> Having a quick look at the source on github. I would suggest to not
> >> have a flat module hierarchy (ie: move them all into 'compo').
> >>
>
ck look at the source on github. I would suggest to not
>> have a flat module hierarchy (ie: move them all into 'compo').
>>
>> Regards
>> Iain
>
>
> You mean one humungous file?
Nope. Create a directory 'compo', move all sources I. The folder and update
the module names from 'module text' -> 'module compo.text'
I believe Iain is suggesting you put your source code into a folder called
compo/. In Dub you would generally put the sources in Source/ then have
project files in the root of the project folder Readme and License for
example.
On Mon, Feb 10, 2014 at 7:02 AM, Steve Teale
wrote:
> On Sunday
'compo').
Regards
Iain
You mean one humungous file?
On 8 February 2014 06:03, Steve Teale wrote:
> A deb file of an early version of COMPO2 is now available at
> http://britseyeview.com/compo/.
>
> I'd appreciate some feedback from the Debian based users in the D community.
> It's not technical stuff, but it's an ex
On Sunday, 9 February 2014 at 09:36:15 UTC, Russel Winder wrote:
Steve,
I cloned your Git repository. Instead of editing your Makefile
to switch
from your file structure to mine, I created a SCons build,
using the
separate compilation approach for now. with my 64-bit build of
your
code, I am
ror: cannot implicitly convert expression
(this.po.editStack.length) of type ulong to int
polycurve.d(685): Error: cannot implicitly convert expression
(this.pcPath.length - 1LU) of type ulong to int
polycurve.d(1040): Error: cannot implicitly convert expression
(this.pcPath.length) of type ulong to
Steve,
I cloned your Git repository. Instead of editing your Makefile to switch
from your file structure to mine, I created a SCons build, using the
separate compilation approach for now. with my 64-bit build of your
code, I am seeing errors such as:
acomp.d(782): Error: cannot implicitly convert
On Sun, 2014-02-09 at 07:25 +, Steve Teale wrote:
[…]
> I have changed the naming to make it clear that it is a 32 bit
> version. However it's not clear to me whether I can build a 64
> bit version on my 32 bit system.
Should be possible if you have the 64-bit libraries, it's just a form of
On Saturday, 8 February 2014 at 17:32:05 UTC, Russel Winder wrote:
1. use the Debian package naming rules so that the version
number and
architecture are more standardly part of the name.
2. build a 64-bit amd64 package as well as a 32-bit i386
package.
I have changed the naming to make
On Sunday, 9 February 2014 at 05:48:06 UTC, Steve Teale wrote:
On Sunday, 9 February 2014 at 00:17:01 UTC, angel wrote:
Trying to build from source, I run into missing 'mainwin.d'
file.
From the git history it seems like some time ago main.d was
renamed to mainwin.d, but no mainwin.d seems to b
On Sunday, 9 February 2014 at 00:17:01 UTC, angel wrote:
Trying to build from source, I run into missing 'mainwin.d'
file.
From the git history it seems like some time ago main.d was
renamed to mainwin.d, but no mainwin.d seems to be present in
the repository.
I'll fix it.
Trying to build from source, I run into missing 'mainwin.d' file.
From the git history it seems like some time ago main.d was
renamed to mainwin.d, but no mainwin.d seems to be present in the
repository.
On Sat, 2014-02-08 at 06:03 +, Steve Teale wrote:
> A deb file of an early version of COMPO2 is now available at
> http://britseyeview.com/compo/.
>
> I'd appreciate some feedback from the Debian based users in the D
> community. It's not technical stuff, but it&#x
On Saturday, 8 February 2014 at 06:03:18 UTC, Steve Teale wrote:
A deb file of an early version of COMPO2 is now available at
http://britseyeview.com/compo/.
I'd appreciate some feedback from the Debian based users in the
D community. It's not technical stuff, but it's an examp
A deb file of an early version of COMPO2 is now available at
http://britseyeview.com/compo/.
I'd appreciate some feedback from the Debian based users in the D
community. It's not technical stuff, but it's an example of what
can be done with D+gtkd2.
Also, with a little tuto
On Wednesday, 29 January 2014 at 14:36:29 UTC, bearophile wrote:
Steve Teale:
I pushed changes to GitHub (https://github.com/britseye/compo)
today that allow a clean build with warnings and deprecations
on using DMD2.064.
In similar projects I suggest to pull out some generally useful
Steve Teale:
I pushed changes to GitHub (https://github.com/britseye/compo)
today that allow a clean build with warnings and deprecations
on using DMD2.064.
In similar projects I suggest to pull out some generally useful
modules (like some geometry ones), making them independent, and
I pushed changes to GitHub (https://github.com/britseye/compo)
today that allow a clean build with warnings and deprecations on
using DMD2.064.
Regularized shape and geometric objects so they are all
implemented
in a similar way for ease of maintenance.
Added a more complete implementation
I've been working for some time on a Linux graphical design program called
COMPO. It's about 20,000 lines of D code, built with 2.054 and a recent
version of gtkD.
I could do with some volunteers to give it a whirl. A .deb file and
documentation can be found at http://britseyeview.co
31 matches
Mail list logo
