I've finished the initial part of translating Camelia
to Qt4. It now uses no Qt3 classes/methods, and compiles cleanly
with Qt3 support disabled. Some minor Qt3-isms were refactored,
but it's just a tip of the iceberg. I now have to get it into a running shape.
I commit to SVN every day or two, on
That works for me.
In future I can implement functionality similar to Visual Studio's .vcproj
files, where you can basically hand-tune the build process, all without
leaving the IDE. I have had a go at writing a proof-of-concept stand-alone
"executor" or "builder" for .vcproj files, and it's not o
On Monday 20 October 2008, Romain Bardou wrote:
> Kuba Ober a écrit :
> >> I'm not sure that parsing ocamlbuild file is the right thing to do. For
> >> a simple OCaml project (which would probably mean most Camelia
> >> projects), there are no OCamlBuild files at all.
> >>
> >> Mmmhhh there's .
> I thought of reading through the code and maybe contributing, but the fact
> that it's all in C++ is holding me back a bit. Still, I'm going to take a
> look once I have time.
> Actually, porting the code to pure OCaml might prove the most interesting
> task to me. I wonder what is the state of Q
Kuba Ober a écrit :
I'm not sure that parsing ocamlbuild file is the right thing to do. For
a simple OCaml project (which would probably mean most Camelia
projects), there are no OCamlBuild files at all.
Mmmhhh there's .itarget (i.e. a list of files you wish generated
after compilation), but
> I'm not sure that parsing ocamlbuild file is the right thing to do. For
> a simple OCaml project (which would probably mean most Camelia
> projects), there are no OCamlBuild files at all.
>
> Mmmhhh there's .itarget (i.e. a list of files you wish generated
> after compilation), but that's abo
I'm not sure that parsing ocamlbuild file is the right thing to do. For
a simple OCaml project (which would probably mean most Camelia
projects), there are no OCamlBuild files at all.
Mmmhhh there's .itarget (i.e. a list of files you wish generated
after compilation), but that's about it. And,
Replying to myself -- must be old age ;)
I know that the indenter support will be gone at least for the alpha version,
as the indenter needs a revamp -- the QSyntaxHighlighter machinery
can be (ab)used to modify the text in-place, and will most likely host
all of the indenter. Right now, indenter
On Friday 17 October 2008, David Teller wrote:
> A notion of projects would be nice, which would give the ability to
> save/load multiple files.
At first, I will add "Save all" to the menu (if not already there), so
that all modified documents will be saved with a single action.
As for real proje
On Saturday 18 October 2008, you wrote:
> Hi,
>
> In the meantime, is there a public source control with the current version
> or a tarball? (I'd just like to take a look at the code, not necessarily
> run it).
SVN is in the usual sourceforge.net location. The original 1.1 release from
a couple ye
Since I am slightly responsible for getting you into this exercise, I
volunteer to test the code on Ubuntu 7.04, Intel and AMD64
architectures. Let me know when you want something done.
Best regards,
Andrej
___
Caml-list mailing list. Subscription mana
A notion of projects would be nice, which would give the ability to
save/load multiple files.
And "slight" thanks for your work,
David :)
On Fri, 2008-10-17 at 09:55 -0400, Kuba Ober wrote:
> The upcoming version will be 2.0, and I hope to add some features
> to it before it's final. I'm sure of
Here's the update from the trenches: I'm about 75% done
porting Camelia code to Qt4, the editor-related parts took
longer than anticipated since a lot of code had to change due
to the arguably better way that Qt4 handles text editing. The
code shrinks quite a bit in the process (20% or so, per the
13 matches
Mail list logo
