Re: Migrating Mono 2.0. Crossplatform GUI components.

Hi,

Well, it's not actually a product but an internal library we use. We don't sell it. Did you like how it looks like? If so I'll check here whether everyone agrees to make it open.

pablo

Debacker escribió:

Hi,

Is the GUI part of Plastic SCM free/open-source? I only see marketing for your commercial package, which is a bit overskill if someone wants your widgets only.

Regards,
Laurent Debacker.

On Sun, May 18, 2008 at 11:38 AM, pablosantosluac@... <mailto:pablosantosluac@...> <pablosantosluac@... <mailto:pablosantosluac@...>> wrote:

   Hi,

   We've developed a small set of controls for Plastic SCM to make
   our GUI
   fully portable using winforms.

   You can take a look at some screenshots here:
   http://www.flickr.com/photos/15875826@N04/sets/72157603891722391/


   pablo





   Jonathan Pobst escribió:
   > I guess it depends on your requirements.  .Net (and Mono) comes
   with a
   > toolbar, grid, and tree.  So part of it will be figuring out what
   > additional functionality you need that you are getting from
   third party
   > controls.
   >
   > Right now, I do not know of any third party controls that work
   out of
   > the box with Mono.  Hopefully, with the release of Mono 2.0,
   this will
   > change as we work with some third party vendors to get their
   controls
   > working on Mono.
   >
   > Jonathan
   >
   >
   > Yakov Danilov wrote:
   >
   >> Hi everyone.
   >>
   >>     Because of Mono 2.0. release our firm has some plans about
   creation of crossplatorm client that could be used with .Net 2.0
   on Windows and Mono 2.0 on Linux systems.
   >>
   >>     Business logic can be used without any problem, but GUI has
   been created using Infragistics components that have too many Win
   Api calls and can be used only on Windows.
   >>
   >>     Thats why we need components written in managed C# and
   WinForms that can be used on both platforms. Basically we need
   Toobar, Grid, Tree. At this time I find only SourceGrid. Can
   anybody advice us such components? Writing own components too
    laborious.
   >>
   >> p.s. Sorry if my English is not so well.
   >> _______________________________________________
   >> Mono-devel-list mailing list
   >> Mono-devel-list@...

   <mailto:Mono-devel-list@...>

   >> http://lists.ximian.com/mailman/listinfo/mono-devel-list
   >>
   >>
   >>
   >
   > _______________________________________________
   > Mono-devel-list mailing list
   > Mono-devel-list@...

   <mailto:Mono-devel-list@...>

   > http://lists.ximian.com/mailman/listinfo/mono-devel-list
   >
   >

   _______________________________________________
   Mono-devel-list mailing list
   Mono-devel-list@...

   <mailto:Mono-devel-list@...>

   http://lists.ximian.com/mailman/listinfo/mono-devel-list