Re: GtkD 3.1.0 released, GTK+ with D.
Broadly speaking, how much work is involved in converting an app using GtkD 2.4? Thanks Steve Judging form the demos, the needed changes are minimal. OK, I'm now in a position to confirm that view. I've reworked my COMPO app to work with GTK+3, and it was pretty straightforward ;=)
Re: GtkD 3.1.0 released, GTK+ with D.
On Thursday, 26 March 2015 at 22:41:01 UTC, Mike Wey wrote: GtkD is a D binding and OO wrapper of Gtk+ and is released on the LGPL license. Shortly after the last release, GtkD has been updated for GTK+ 3.16. GtkD 3.1.0 is now available on gtkd.org: http://gtkd.org/download.html Mike, Broadly speaking, how much work is involved in converting an app using GtkD 2.4? Thanks Steve
Re: Experimental win32 OMF linker written in D now on github
On Tuesday, 25 March 2014 at 03:27:07 UTC, Jack Applegame wrote: Nifty! I love this Pro: - Usually produces working executables :) Me too. But not more than Written in D :) But the best is Not written before I was born :) When I was a lad we had to Steve
Re: COMPO
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?
Re: COMPO
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
Re: COMPO
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
Re: COMPO
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
Re: 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 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
Re: COMPO
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.
Re: COMPO
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
Re: COMPO
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.
Re: COMPO
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
Re: COMPO
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?
Re: COMPO
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.
Re: COMPO
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 be present in the repository. I'll fix it. Fixed now I hope. I had to change the name of main.d so I could write the stub compo.d file required by DUB. If I imported main into that, it clashed with main(). A bunch of changes were added at the same time, so what's there now should be the same as what created the current deb file.
Re: COMPO
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 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. a) How do I tell if my GCC version is multilib, b) Can I build a static 64 bit library - gtkd2 - on my 32 bit system. Thanks Steve
COMPO
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.
Re: COMPO - 2.064
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 modules (like some geometry ones), making them independent, and making them available (with DUB or on GitHub). This allows other projects to re-use those modules and reduce their size. Bye, bearophile I'm 72 in April. I'd like to get what I started finished - including documentation - before I die. The source code is there, so if there are bits that are generally useful, people can cherry pick! Also, if I come across bits that I think are generally useful, like approximating a circle with Bezier curves, or using meshes, I try to write an article on my web page that separates it out. BTW, thank you for your consistent and continuing contributions to the development of D ;=)
COMPO - 2.064
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 of Flatten and Drawing, and a new pattern type - BrushDabs. This introduces the idea of 'shim' layers - objects that do not normally display themselves, but effect the following layer. So BrushDabs will be used as fill for any closed shape or geometric object that is placed over it. The Codeblocks project file is also changed somewhat - hopefully for the better. Codeblocks linking is very fragile.
Re: So, You Want To Write Your Own Programming Language?
On Wednesday, 22 January 2014 at 04:29:05 UTC, Walter Bright wrote: http://www.reddit.com/r/programming/comments/1vtm2l/so_you_want_to_write_your_own_language_dr_dobbs/ Nice Walter. You're almost as down-to-earth as me. I love what you have achieved.
Re: Dmitry Olshansky is now a github committer
On Thursday, 23 January 2014 at 17:38:04 UTC, Andrei Alexandrescu wrote: Congratulations to Dmitry! (His github ID is blackwhale.) Andrei Can't you go to prison for that?
Re: Gtkd2 in serious use
On Thursday, 9 January 2014 at 16:22:59 UTC, Steve Teale wrote: A couple of months ago I was handing out congratulations to Mike Wey on his splendid work in creating gtkd2. I have had a good go at it since, and with a couple of small glitches along the way, it has been as close to flawless as I can imagine. Anyway, I have got a long way down the road I've been following, but I'm getting close to the point where I need some help. There's a very quick description of what I'm doing at http://britseyeview.com/compo/ - even that is not finished yet. But anyway, if anyone in the D community is interested, I could use some help with: 1) QA - on Debian based systems - I need people to break it. 2) Building on a recent version of Windows. 3) Advice on which repository to use for the source code. Thanks Steve It's on github now - britseye/compo. I added a makefile, so you don't have to use CodeBlocks to build it.
Re: Gtkd2 in serious use
On Friday, 10 January 2014 at 17:33:31 UTC, Steve Teale wrote: I have done more work on the web page to cut out fluff, and to cover all the composition elements. There is also a beginning for the description of the user interfaces. I lied unwittingly on the web page. I do have the source for the Windows program, but it was in a password protected zip file, and I'd forgotten the password. While checking on it yesterday it suddenly occurred to me what I would have used, and so now I do have it. But there's no way I'm going back to C++.
Re: Gtkd2 in serious use
I have done more work on the web page to cut out fluff, and to cover all the composition elements. There is also a beginning for the description of the user interfaces.
Gtkd2 in serious use
A couple of months ago I was handing out congratulations to Mike Wey on his splendid work in creating gtkd2. I have had a good go at it since, and with a couple of small glitches along the way, it has been as close to flawless as I can imagine. Anyway, I have got a long way down the road I've been following, but I'm getting close to the point where I need some help. There's a very quick description of what I'm doing at http://britseyeview.com/compo/ - even that is not finished yet. But anyway, if anyone in the D community is interested, I could use some help with: 1) QA - on Debian based systems - I need people to break it. 2) Building on a recent version of Windows. 3) Advice on which repository to use for the source code. Thanks Steve
Re: dmd 1.071 and 2.056 release
I'm only saddened that my std.socket cleanup pull request[1] wasn't merged, despite being ready for merging for over a month of inactivity. Vladimir, What's new and different in your std.sockets. Should I be using it for the native MySQL client? Steve
Re: std.dateparse reincarnation
On Thu, 13 Oct 2011 22:09:39 +0300, Vladimir Panteleev wrote: On Thu, 13 Oct 2011 07:22:06 +0300, Jesse Phillips jessekphillip...@gmail.com wrote: Thought I would let everyone know that while std.dateparse is deprecated and will be removed from Phobos in February, I've updated it to output a std.datetime.SysTime. https://gist.github.com/1283011 I don't have any interest in maintaining it, but since I did use it I updated it for me. Time formatting and parsing seems like a gap of missing functionality in Phobos 2. I've written something to format and parse SysTimes using format strings based on the format PHP uses for its date() function: https://github.com/CyberShadow/ae/blob/master/utils/time.d Feel free to use this file as public domain. Yes, me too. I used to get tremendously frustrated with the old std.date, because all I wanted to do was get the current time and write it into a log file! Steve
Re: [Phoronix] Merging In The GNU D Language Compiler To GCC
Are you saying that GDC is way faster? But I take your point. Steve
Re: [Phoronix] Merging In The GNU D Language Compiler To GCC
Iain, You've made a cross for yourself there! If you need help with grunt tasks - like a broken piece of D code with a decent description of the problem, or even grunter, I might be able to help. As you know, I've been in those muddy waters before with nobody to even consult. With a guru like you I could probably get moving fairly quickly. Just as a matter of interest, how do you rate GDC 2.055 for speed alongside the Linux DMD. Steve
Re: Some basic rules, OK??
Georg, Did I provoke that little outburst? I thought my invitation was quite low key, and there was a reference to lots of information. If so, I apologize, but I may do it again! Steve
COMPO
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.com/software/compo/ Steve
GDC-newbies
I have made a provisional web page to provide help and information for potential users of the GDC compiler at http://www.britseyeview.com/GDC-newbie.html. Please let me have your comments and suggestions for improvement/removal. Thanks, Steve
GDC-newbies
I have made a provisional web page to provide help and information for potential users of the GDC compiler at http://www.britseyeview.com/GDC-newbie.html. Please let me have your comments and suggestions for improvement/removal. Thanks, Steve
Re: GDC-newbies
Steve Teale Wrote: I have made a provisional web page to provide help and information for potential users of the GDC compiler at http://www.britseyeview.com/GDC-newbie.html. Please let me have your comments and suggestions for improvement/removal. Thanks, Steve Really screwed that up - URL is http://www.britseyeview.com/GDC-newbie.html - previously, the period at the end of my sentence was included, and somehow I posted it twice.
Re: D compiler as part of GCC
Walter Bright Wrote: Leandro Lucarella wrote: I agree that embarking a new front-end will be a huge effort that probably will end up abandoned before it's completed, unless there is some economic sponsorship or something, but having a front-end which copyright can be given to the FSF is a necessary condition to merge GDC (or whatever it's named) to GCC. Will they take a fork of the dmd source, such that they own the copyright to the fork and Digital Mars still has copyright to the original? Go for it Walter - the paths to fame are incomprehensible. Also, you'll still be faster than they are!
Re: D compiler as part of GCC
Nick Sabalausky Wrote: Eldar Insafutdinov e.insafutdi...@gmail.com wrote in message news:hj2njd$o1...@digitalmars.com... Having a solid GDC implementation you can be sure that it will be included in distributions (Debian had GDC for quite a long time). had? Is that a typo or did they drop it? I just apt-get install gdc on Ubuntu and got 4.2.4
MySQLD
I have posted this version 0.00 module on my DCat web page - http://www.britseyeview.com/dcat/ from where you can download it. The generated documentation is also there. The header files I translated to D are GPL. License experts out there, where does that leave the D version? At the moment I have retained the GPL header. I'd welcome comments. Steve
Re: Descent with compile-time debug for testing
Trass3r Wrote: Ary Borenszweig schrieb: That's ddbg working wrong, not Descent. :-P Ah, damn so no way this gets fixed. Debugging D is a pain :( So is ddbg dead?
ODBCD
I have an alpha version of an ODBCD working. I have tested it so far with MySQL and SQL Express 2005 on Windows XP. Both have their shortcomings, but I don't think they have that much to do with the ODBCD code. If you have a different database and/or ODBC driver, and are interested in testing/helping, please email me and I'll send you a zip. It's quite small and relatively easy to work with, since ODBC drivers tend to produce pretty reasonable error information, but it still needs a lot of work. This will eventually be part of DCat - http://www.britseyeview.com/dcat/ - however because ODBC now seems to be on everyone else's back burner I'm thinking of trying some closer-to-native implementations as well. Steve
DCat version 0.005
Did a makeover of the ASD reader/parser. Should now be more robust. Made some spaec modifications as a result. Fixed some bugs. Added a general-purpose message file to make event-logging work sensibly. Download at http:\\www.britseyeview.com\dcat\.
DCat screw-up - sorry!
There was a bug in my use of VirtualProtect and in my testing. I apologize to anyone who took the trouble to download it. There's a new zip file now that fixes it.
DCat version 0.004
I've just posted DCat V0.004 at http://www.britseyeview.com/dcat/. Dynamically loaded modules now use single memory block allocated with VirtualAlloc, and protected via VirtualProtect. Improved and automated error handling. Further examples.
DCat web application server
The web application server DCat now builds with DMD1.043 or DMD2.029. Download available at http://www.britseyeview.com/dcat/. Mixin rules OK!
DCat - a compact web application server in D.
This is incomplete at this point, but there's a working example. I have to break off now and do some building work. You can find documentation and a zip file (currently it is Windows only, DMD2.026, and Phobos) at http://www.britseyeview.com/dcat/. It works with Apache2, and uses the AJP13 protocol like Tomcat.
