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 seeing errors such as:
>
> acomp.d(782): Error: cannot implicitly convert expression (parent.children.length + 1LU) of type ulong to int
> acomp.d(801): Error: cannot implicitly convert expression (p.children.length + 1LU) of type ulong to int
> acomp.d(857): Error: cannot implicitly convert expression (p.children.length) of type ulong to int
>
> so it looks like your code is 32-bit specific. I guess this is the
> ago-old problem of C, C++, D, etc. that int is the most natural size for
> the platform, code is inherently not as portable as you think.

Thanks Russel. I suspected that would be the case - like you say, old habits die hard. I guess I'll have to install 64 bit Ubuntu on my laptop so I have somewhere to launder the code, and build 64 bit.

Steve

On 8 February 2014 06:03, Steve Teale <steve.teale@britseyeview.com> 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 example of what can be done with D+gtkd2.
>
> Also, with a little tutoring, your kids might like it.
>
> I have to take a break from developing it, and write some documentation now.

Looks like some 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').

Regards
Iain

On Sunday, 9 February 2014 at 22:48:23 UTC, Iain Buclaw wrote:
>
> Looks like some 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').
>
> Regards
> Iain

You mean one humungous file?

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 <steve.teale@britseyeview.com>wrote:

> On Sunday, 9 February 2014 at 22:48:23 UTC, Iain Buclaw wrote:
>
>>
>> Looks like some 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').
>>
>> Regards
>> Iain
>>
>
> You mean one humungous file?
>

On 10 Feb 2014 05:06, "Steve Teale" <steve.teale@britseyeview.com> wrote:
>
> On Sunday, 9 February 2014 at 22:48:23 UTC, Iain Buclaw wrote:
>>
>>
>> Looks like some 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').
>>
>> 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'

:) ah right, you did say module.



On Mon, Feb 10, 2014 at 9:11 AM, Iain Buclaw <ibuclaw@gdcproject.org> wrote:

> On 10 Feb 2014 05:06, "Steve Teale" <steve.teale@britseyeview.com> wrote:
> >
> > On Sunday, 9 February 2014 at 22:48:23 UTC, Iain Buclaw wrote:
> >>
> >>
> >> Looks like some 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').
> >>
> >> 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'
>

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 of fracturing CodeBlocks fragile project structure. But it's a good suggestion. I am frantically trying to get COMPO to a state of some usability, and built for Windows, with documentation, before I die.

When I am calmer I will take up your point. It would probably help me in getting collaborators, and would suit DUB.

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/compo/.

The binary that is available there is still just i386. My next job is to install Ubuntu 12.04 64 bit as dual boot on my machine, and attempt to build an amd64 version.

The binary matches what is currently on GitHub.

I would love to get some feedback on both the application and the documentation

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 tomorrow.

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