Hello, I am currently building an app using Cocoa which I plan to port
later to Windows etc. Because of Cocotron I have already decided
against CoreData and WebKit. However, I am still on ARC and would like
to know, if there will be support for ARC in the foreseeable future (1
year or so)? If not, I could skip on ARC too, just now when it doesn't
hurt so much as compared to maybe 1 year down the road.
As a general thought, you guys are doing a great job with Cocotron. I
like the approach so much, making a program beautiful where it matters
(on the Mac) and just let it run on Windows, however ugly it is ;) It
should not be the other way around like in most other cross-platform
tools. So thanks for Cocotron.
However, having said that, I would be a lot happier if the information
on the website would be updated more frequently. For example I
strongly miss announcements of what's planned in the future and what's
the status of the various frameworks. And a last blog entry from 2010
saying we re alive and kicking is not very encouraging for new
visitors. I wasn't new but when I revisited after a few months the
project looked just dead. Is the reason for the infrequent updates
that you wrote the web server in Objective-C and have no time to
maintain it? Maybe then it's just not the right tool for the job...
Oh and BTW, I would strongly suggest that you don't let the issue
tracker "spam" updates to this discussion group. It is very
frustrating to find the real discussions among those many automated
posts. This keeps people away from contributing useful input, because
no one answers their posts which in turn is because no one reads them
(read: no one find's them among the hundreds of automated messages).
Let the forum be the forum and the issue tracker be the issue tracker.
I say this because I am very frustrated at the moment because I
managed to compile cocotron with Xcode 3.2.6 on Snow Leopard
successfully but I could not get any of the examples to work on my
Windows7-64, they all keep crashing. And I am not able to find a
useful discussion on this board which could help me.
On Feb 10, 4:11 am, parels <andre.par...@gmail.com> wrote:
> Hello, I am currently building an app using Cocoa which I plan to port
> later to Windows etc. Because of Cocotron I have already decided
> against CoreData and WebKit. However, I am still on ARC and would like
> to know, if there will be support for ARC in the foreseeable future (1
> year or so)? If not, I could skip on ARC too, just now when it doesn't
> hurt so much as compared to maybe 1 year down the road.
> As a general thought, you guys are doing a great job with Cocotron. I
> like the approach so much, making a program beautiful where it matters
> (on the Mac) and just let it run on Windows, however ugly it is ;) It
> should not be the other way around like in most other cross-platform
> tools. So thanks for Cocotron.
> However, having said that, I would be a lot happier if the information
> on the website would be updated more frequently. For example I
> strongly miss announcements of what's planned in the future and what's
> the status of the various frameworks. And a last blog entry from 2010
> saying we re alive and kicking is not very encouraging for new
> visitors. I wasn't new but when I revisited after a few months the
> project looked just dead. Is the reason for the infrequent updates
> that you wrote the web server in Objective-C and have no time to
> maintain it? Maybe then it's just not the right tool for the job...
Thank you for taking the time to help me. I managed to get it working
by updating the trunk from hg and I also applied the "class!=0" check
to the runtime. Pauli, but how does your actual patch (which was
already merged by Chris into the trunk when I was having these
problem) solve the actual problem? I mean, the patch is for something
with dllmain not NSObject? I was confused by that.
Nonetheless, I am happy that it works now! I'm also glad that the
color picker dialog looks much better now than in the binary cocotron
examples. I look forward to exploring more of current Cocotron now.
Thanks again
On Feb 12, 5:02 am, rosstulloch <r.tull...@gmail.com> wrote:
Yeah, sorry -- my commit history was confusing because I had
accidentally committed some debug printout code together with the fix,
and then I had to undo those. So the revision to which I posted the
link appeared to be about dllmain.m only, but actually it was just the
"cleanup" for my commit mistake.
Anyway, I merged my clone with the main branch. There seems to be
things happening with the runtime, so it's possible that my "check for
NULL superclass" fix isn't even necessary anymore... It doesn't hurt
to have it, though. I'll ask Chris to pull it to the main branch.
> Thank you for taking the time to help me. I managed to get it working
> by updating the trunk from hg and I also applied the "class!=0" check
> to the runtime. Pauli, but how does your actual patch (which was
> already merged by Chris into the trunk when I was having these
> problem) solve the actual problem? I mean, the patch is for something
> with dllmain not NSObject? I was confused by that.
> Nonetheless, I am happy that it works now! I'm also glad that the
> color picker dialog looks much better now than in the binary cocotron
> examples. I look forward to exploring more of current Cocotron now.
> Thanks again
> On Feb 12, 5:02 am, rosstulloch <r.tull...@gmail.com> wrote:
> > > I could not get any of the examples to work on my
> > > Windows7-64, they all keep crashing.
