Screenshots

[Leauki]

I have a simple test application that I use against new versions of
Mono (just for sanity checks). It's called QuickInfo and it simply
displays some environment info.

I experimented a bit and made a Cocoa# version:

http://web.mac.com/ajbrehm/Resources/CocoaSharp.html

What's funny is that Environment.Version gives different results for
Windows (Microsoft .NET), Mac OS X but compiled on Windows, and Mac OS
X and compiled on OSX/Mono.

Four windows, all the same program.

First one is QuickInfo.exe running under Windows, second one is
QuickInfo.exe run under OS X using X11, third one is QuickInfo.app
using native Quartz Winforms under Mac OS X, fourth is QuickInfo.app
using a NIB GUI and Cocoa#.

Note that "porting" QuickInfo to Cocoa# was nearly a rewrite as
QuickInfo doesn't have any "business logic". I do have a model class
anyway.

I'll publish the source code once I have commented it. It's really
simple but it gives me hope that Cocoa# can be used to make .NET
applications into native Mac applications and hence allow
crossplatform development in C# and perhaps Visual Basic instead of
REALbasic or C++ _and_ using completely native GUIs rather than a
common subset.

There is a tutorial coming from another poster.

Again, this is completely primitive code and is only supposed to show
what Cocoa# looks like as a quick reference for those who are
considering Cocoa# and know nothing about it (i.e. people like
myself).

[Manuel de la Pena]

I finally sorted my internet connection here in England... I'll post
tom my 2 tutorials a very simple hello world using ObjectiveCSharp and
an other one that combines ADO.NET and CocoaSharp. I'm really sorry it
has taken so much time but I was moving to England.

Changing the topi,c has anyone heard about the people that run the
project???? I'm saying this because I have a server, and I'm able
offer it to post the cocoa sharp webpage using some kind of content
management like drupal (which I hope to change to a mono asp one
running on mono ASAP) What do you guys think??? I really think we
should try to get the project going with some resources.

Any suggestion. are welcome

[Dave]

For the project management goes, I can comment a bit on that since I
am the manager of this group and of the Google code page. Basically,
the original plan was to shutdown the cocoasharp.org page and move all
the content to here. I moved all the relevant pages but cocoasharp.org
is still operating and has been updated a bit. I'd be more than happy
to have the content of this forum moved to another location if that is
what everyone wants. Also note that the cocoa# code is located on the
Mono site, so getting SVN access for developers can be problematic.
You may want to consider what I did for the CSharpPlugin for Xcode and
move the code to google Code.

> > myself).- Hide quoted text -
>
> - Show quoted text -

[Leauki]

I am in favour of anything that helps Cocoa#.

(Will there be an Xcode 3 version of the plugin soon?)

Trying out Cocoa# a bit I found that it is a lot of fun, since I like
both Visual Studio and Xcode and I was looking for a good
crossplatform solution anyway. (I use REALbasic for my own home
projects, but C# is cooler.)

Maybe there should be less of a .NET focus and more of a focus on
crossplatform development? I.e. don't compare Cocoa# to Windows Forms
but to QT or REALbasic.

Plus, I think we want some of the key people on .NET Rocks or
Hanselminutes.

http://www.dotnetrocks.com/

http://www.hanselminutes.com/

They had Miguel de Icaza twice on .NET Rocks and Hanselminutes just
discussed Cocoa (and ObjectiveC) and didn't like the fact that it
doesn't do memory management automatically.

I also think that we want as much Novell icons on the project page as
possible, gives the thing more credibility, maybe even enough to
convince Novell to focus on the Mac a bit more.

What I plan to do next:

1. Comment the source for my screenshot example and publish it as an
easy example.

2. Look through Manuel's tutorials, understand them, and tell people
about them.

3. Write a step-by-step guide for creating a Winforms application in
Visual Studio and then porting it to Cocoa#.

I think .NET Rocks exposure would be excellent.

Regards,
Andrew (really excited but not really doing anything useful)

[Manuel de la Pena]

Hi,

Well about using google code, I'm one of those freaks that doesn't
trust them, but have a gmail account (what an irony,,,,)

I'm up to offer the server to host a webpage where we can integrate
all the stuff we have, nothing to complicated... focus on the
documentation for now, start documenting as much as possible (if my
ISP decides not to let me with no connection again). Maybe some basic
objective-c tutorials for the C# people to teach them how to work with
what we have, and try to get as much attention as possible. The
project is a great idea but we need some "media" to be attracted to it.

Cross platform focus seems to be the way to go, make things easy for
c# people to get their apps on MacOSX fast an easy (I even have some
ideas of writing some fake dlls for address books that will imitate
the Macs address book on windows and linux). We should think about the
kind of audience we want, either c# programmers that look for
portability or people that want to learn programming c# on a mac (f I
have the choice I would go for the first one)

Manuel (wants to work a lot on this, but BT doesn't let him)

PS: About objec-c miguel might be a bit outdated, it finally got
garbage collection and you can stop using the [] that we all love so
much sigh*

[Leauki]

I'll write the beginner's how-tos! :-)

(Like what software to install and how to compile etc.)

On Jan 18, 12:31 am, Manuel de la Pena <eti...@gmail.com> wrote:
>
> PS: About objec-c miguel might be a bit outdated, it finally got
> garbage collection and you can stop using the [] that we all love so
> much sigh*
>

But that only works on Leopard, right? They didn't backport the new
runtime, did they?