Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #8449 > unrolled thread

XSharp - PRESS RELEASE

Started byRobert van der Hulst <rjvanderhulst@gmail.com>
First post2015-09-28 06:35 -0700
Last post2015-10-18 17:27 +1100
Articles 14 — 13 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  XSharp - PRESS RELEASE Robert van der Hulst <rjvanderhulst@gmail.com> - 2015-09-28 06:35 -0700
    Re: XSharp - PRESS RELEASE sherlocksoftware@gmail.com - 2015-09-28 07:05 -0700
    Re: XSharp - PRESS RELEASE Massimo Bighelli <info@arcasistemi.it> - 2015-09-28 18:51 +0200
    Re: XSharp - PRESS RELEASE "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> - 2015-10-02 16:02 +0200
    Re: XSharp - PRESS RELEASE "Marc Verkade [MITCon]" <marc@mitNOSPAMconDELETE.nl> - 2015-10-02 16:23 +0200
      Re: XSharp - PRESS RELEASE D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2015-10-04 23:07 +0200
    Re: XSharp - PRESS RELEASE "Danilo Giuliani" <softdevo@tiscali.it> - 2015-10-03 17:30 +0200
    Re: XSharp - PRESS RELEASE moshe attia <attiamx@gmail.com> - 2015-10-06 00:35 -0700
      Re: XSharp - PRESS RELEASE D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2015-10-06 14:15 +0200
    Re: XSharp - PRESS RELEASE "Philippe Bayard (Belgium)" <philbayard@gmail.com> - 2015-10-06 07:50 -0700
    Re: XSharp - PRESS RELEASE Jean-Pierre Maertens <jp.maertens@gmail.com> - 2015-10-16 12:41 -0700
      Re: XSharp - PRESS RELEASE Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2015-10-16 22:18 +0200
      Re: XSharp - PRESS RELEASE Robert van der Hulst <robert@heliks.nl> - 2015-10-16 22:24 +0200
        Re: XSharp - PRESS RELEASE "Craig Dawson" <craig_dawson@hotmail.com> - 2015-10-18 17:27 +1100

#8449 — XSharp - PRESS RELEASE

FromRobert van der Hulst <rjvanderhulst@gmail.com>
Date2015-09-28 06:35 -0700
SubjectXSharp - PRESS RELEASE
Message-ID<784286fe-ef26-443c-aa76-1b932e799001@googlegroups.com>
We've built it - we can make it better!
---------------------------------------
 
Epe: September 28 2015.
 
We have just returned from a VERY successful DevShare Conference in the UK. Many thanks go to Phil Hepburn, Mike Bertenshaw, Dai Darkin and their spouses Sue and Sue for organizing this great event. 

Our new XSharp initiative has received as very warm welcome at the conference, but also raised many questions. We would like to take the opportunity to repeat and answer the most common and most important question over here:

Why do you want to introduce a new compiler / competitor for a small market as Vulcan.NET?
 
The answer to this is the following:
 
We never had and still don't have the intention to start a Compiler war and introduce a competitor to Vulcan.NET.
 
Let us explain a little bit about what happened (without revealing secrets from private email and phone conversations)
 
All products have their product life cycle.  We feel that the product life cycle for Vulcan.NET in its current form has reached his end. The fact that that some of the developers of the product had left or planned to leave the development team also indicated that the product in its current form would have problems to survive. 
Everybody knows that the number of subscribers to the Vulcan Platinum Support is decreasing every year, and also that the number of attendees to Vulcan conferences is decreasing. 
Finally the progress in development has almost come to a stop. There are very few new features in Vulcan 4.
A roadmap for future development is missing, and it is no secret that the owner of Vulcan.NET has been looking for someone to buy the product for the last couple of years.

It is obvious that it is time for a successor, and to make that successor successful we think that it is necessary to broaden its user base. That is why we wanted to introduce a new product that not only targets the Visual Objects & Vulcan.NET market but the other xBase markets as well. But we also wanted to help maintain and support Vulcan.NET.

We have therefore approached GrafX (Brian Feldman) and opened the negotiations with him. We have offered to take over the maintenance, development and support (VPS) of Vulcan.NET and develop a successor at the same time (just like GrafX has done in 2002 when Visual Objects was a product from Computer Associates).
GrafX did not immediately agree with our proposal and came with additional demands.

After consulting our financial partners we have accepted the proposal from GrafX under the normal condition that we would receive a Due Diligence report. In laymen's terms this means that GrafX needs to prove that it is indeed the owner of the Intellectual Property (they could have sold it to someone else before us) and GrafX had to show recent sales data to support the price it has asked for the product . This is a perfectly normal question in all (international) business transactions.
You would also never buy a house too without proof of ownership and an estimate of the value by a real estate agent. 
 
After more than one week (and a reminder from us) Brian Feldman answered us that he regretted his proposal and retracted the offer, without further explanation.

We have replied to him that we were willing to come to another proposal (for example transferring only part of the intellectual property) but we needed to see some proof
That was the end of the negotiations. Brian Feldman closed the door and told us that he is no longer interested in talking with us about selling Vulcan.NET

Brian Feldman is very proud of Vulcan.NET 4.0. And so he should be. The product has come a long way. Many customers has successfully converted a Visual Objects application to .NET with the aid of the product.
We have always and will always appreciate what Brian has done for the product and its predecessor Visual Objects. Without his intervention Visual Objects would have been buried on the graveyard of dead products inside Computer Associates. And he has also helped to start and develop Vulcan.NET.

But we are also very proud of what we have achieved with Vulcan.NET 4.0. We have built it, not alone of course, but together with Don Caton (who had to leave the development team a few years ago), Paul Piko and John Parker

We realize that this controversy has put you, the Vulcan.NET and VPS customers, in a difficult situation which we have tried to avoid. We know you have invested huge amounts of money and many man-years in your products and are now uncertain about the future of the products that you have used to develop your software. But we know you and we are convinced that you will make the right choice.

We suggest that you ask yourself who or what Visual Objects / Vulcan.NET is for you.

We think it is:
*	The team that converted a potentially strong, but sometimes very unstable  and unreliable Visual Objects 2.5 into the product that is today
*	The team that created a new product and achieved what a lot of people thought was impossible
*	The team that helps you solve your problems on the support forums, and often debug your code in their own time into the early hours of the day
*	The team that creates a quick fix to the issues you find in the product, so you can continue to work for your customers.
*	The team that travels all over the world to conferences to tell you about what works, but also very important, what not works in the product and how you could work around these limitation
*	The team that helped you to get started in the challenging new world of DotNet
*	The team you have drank a beer with and while sitting next to you and your laptop have helped you to fix issues in your code on the spot.

We apologize for the difficult choice we have forced you to make, but we know you, we are sure you will make the right decision.

To finish this:
We are still interested in ending this controversy by taking over Vulcan.NET, and welcome any constructive proposal from the side of GrafX.

You will understand that we are not going to wait for GrafX. We don't need GrafX. We have created Vulcan.NET before and will succeed again in creating its successor. We've built it - we can make it better! We wish GrafX & Brian Feldman all the best.

We will keep you informed about our progress through the usual channels: Newsgroups, Facebook, Twitter and of course our website xsharp.eu.

Robert van der Hulst
President XSharp B.V.
Co-Founder of the XSharp Project.

The XSharp Development team:
*	Fabrice Foray
*	Nikos Kokkalis
*	Chris Pyrgas
*	Robert van der Hulst
*	And others

[toc] | [next] | [standalone]


#8451

Fromsherlocksoftware@gmail.com
Date2015-09-28 07:05 -0700
Message-ID<372403f1-31a3-4477-be77-ef809edfeb12@googlegroups.com>
In reply to#8449
 The XSharp Development team:
 *	Fabrice Foray
 *	Nikos Kokkalis
 *	Chris Pyrgas
 *	Robert van der Hulst
 *	And others

Wish you well and the buyout.. which is the logical thing.
Very hard to hire a whole new, have them as competitors and there is so much open source you can add.. and contributions from the developers here.

Been in that space Brian is in.. and tough gig.. tough gig.

Phil McGuinness

[toc] | [prev] | [next] | [standalone]


#8453

FromMassimo Bighelli <info@arcasistemi.it>
Date2015-09-28 18:51 +0200
Message-ID<mubr70$ca8$1@speranza.aioe.org>
In reply to#8449
Il 28/09/2015 15:35, Robert van der Hulst ha scritto:
> We've built it - we can make it better!
> ---------------------------------------
>

very intersting story...

>
> The XSharp Development team:
> *	Fabrice Foray
> *	Nikos Kokkalis
> *	Chris Pyrgas
> *	Robert van der Hulst
> *	And others
>


I can not translate "tough gig", though I'm not a Vulcaneer, and 
therefore I support everything that will come in .net to work with DBF.
One language or the other, what really distinguishes the xbase language 
from others, is the set of commands to the database: setrelation, 
setfilter, etc .. everything else makes no difference in vb.net or c #
So good luck with your project, I see it as a new life and continuity 
for xbase world

*Massimo Bighelli* ARCA Sistemi S.r.l.

[toc] | [prev] | [next] | [standalone]


#8456

From"Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it>
Date2015-10-02 16:02 +0200
Message-ID<mum2mg$e1g$1@dont-email.me>
In reply to#8449
Hi Robert,

thank you for all the information.

My company is surely interested in the progress of such a project as we have 
quite a lot of code written in VO and ready to be transferred to Vulcan.

I imagine that there must be some core programmers working in a paid form 
even if it will be an open source project. If not it may take too much time 
to realize such a new language. I imagine that it is possible to make some 
fund raising similar to the VOPS. Do you have planned something similar?

Arne Ortlinghaus

[toc] | [prev] | [next] | [standalone]


#8457

From"Marc Verkade [MITCon]" <marc@mitNOSPAMconDELETE.nl>
Date2015-10-02 16:23 +0200
Message-ID<2twPx.2497632$%B.58862@fx03.am1>
In reply to#8449
Wow... This is news!

I regret Brian's decision to shut the door but I know that every story has 
two sides and I wonder what Brians's side is.
I can imagine that he is feeling betrayed.... And that emotion is always 
difficult to handle!

Nevertheless, this reminds me of my talks with Rod Da Silva (CULE) and my 
attempts to peruade Brian to talk to him again and start a joined effort in 
stead of creating a concurring product Vulcan.Net.
I really hope that all players understand that joined forces ar way better 
than scattered resources, we are with little...
@All: Please use ratio and not emotions and try to get together and workout 
a plan to jumpstart this new development!

The main thing that lacks Grafx is proper communication to its customers 
through press-articles, website updates, roadmaps etc. IMHO.
As a software development tool a large audience is needed and decision 
makers must have information to trust a 'niche' product and Grafx failed 
miserably in marketing and communication.
There were other groups to target when Vulcan kicked off like FoxPro, 
Harbour and even Clipper but only shallow attempts to reach them were made.
That was and is, in my opinion, the main problem of VO and Vulcan : 
Marketing, communication and installed base...

I have great respect for the XSharp team since I know all of them and admire 
their skillsets and personalities.
I am sure that, if the team stays together and all ego's can be set aside, a 
great product can be developed.
Next to that I also admire the energy and determination of the team and wish 
them all the best.
I really hope that marketing and communication is part of the development 
plan of the team, that is essential to be succesful in this world, whatever 
you do.

I have started a new life and carreer at the 'warmest spot of Holland' and 
since I am not bothered with employees anymore, I can define my own 
time-schedule.
If I can help in any way, please let me know!

I wish you all good luck and you have my thumbs up!

Regards, Marc


"Robert van der Hulst"  schreef in bericht 
news:784286fe-ef26-443c-aa76-1b932e799001@googlegroups.com...

We've built it - we can make it better!
---------------------------------------

Epe: September 28 2015.

We have just returned from a VERY successful DevShare Conference in the UK. 
Many thanks go to Phil Hepburn, Mike Bertenshaw, Dai Darkin and their 
spouses Sue and Sue for organizing this great event.

Our new XSharp initiative has received as very warm welcome at the 
conference, but also raised many questions. We would like to take the 
opportunity to repeat and answer the most common and most important question 
over here:

Why do you want to introduce a new compiler / competitor for a small market 
as Vulcan.NET?

The answer to this is the following:

We never had and still don't have the intention to start a Compiler war and 
introduce a competitor to Vulcan.NET.

Let us explain a little bit about what happened (without revealing secrets 
from private email and phone conversations)

All products have their product life cycle.  We feel that the product life 
cycle for Vulcan.NET in its current form has reached his end. The fact that 
that some of the developers of the product had left or planned to leave the 
development team also indicated that the product in its current form would 
have problems to survive.
Everybody knows that the number of subscribers to the Vulcan Platinum 
Support is decreasing every year, and also that the number of attendees to 
Vulcan conferences is decreasing.
Finally the progress in development has almost come to a stop. There are 
very few new features in Vulcan 4.
A roadmap for future development is missing, and it is no secret that the 
owner of Vulcan.NET has been looking for someone to buy the product for the 
last couple of years.

It is obvious that it is time for a successor, and to make that successor 
successful we think that it is necessary to broaden its user base. That is 
why we wanted to introduce a new product that not only targets the Visual 
Objects & Vulcan.NET market but the other xBase markets as well. But we also 
wanted to help maintain and support Vulcan.NET.

We have therefore approached GrafX (Brian Feldman) and opened the 
negotiations with him. We have offered to take over the maintenance, 
development and support (VPS) of Vulcan.NET and develop a successor at the 
same time (just like GrafX has done in 2002 when Visual Objects was a 
product from Computer Associates).
GrafX did not immediately agree with our proposal and came with additional 
demands.

After consulting our financial partners we have accepted the proposal from 
GrafX under the normal condition that we would receive a Due Diligence 
report. In laymen's terms this means that GrafX needs to prove that it is 
indeed the owner of the Intellectual Property (they could have sold it to 
someone else before us) and GrafX had to show recent sales data to support 
the price it has asked for the product . This is a perfectly normal question 
in all (international) business transactions.
You would also never buy a house too without proof of ownership and an 
estimate of the value by a real estate agent.

After more than one week (and a reminder from us) Brian Feldman answered us 
that he regretted his proposal and retracted the offer, without further 
explanation.

We have replied to him that we were willing to come to another proposal (for 
example transferring only part of the intellectual property) but we needed 
to see some proof
That was the end of the negotiations. Brian Feldman closed the door and told 
us that he is no longer interested in talking with us about selling 
Vulcan.NET

Brian Feldman is very proud of Vulcan.NET 4.0. And so he should be. The 
product has come a long way. Many customers has successfully converted a 
Visual Objects application to .NET with the aid of the product.
We have always and will always appreciate what Brian has done for the 
product and its predecessor Visual Objects. Without his intervention Visual 
Objects would have been buried on the graveyard of dead products inside 
Computer Associates. And he has also helped to start and develop Vulcan.NET.

But we are also very proud of what we have achieved with Vulcan.NET 4.0. We 
have built it, not alone of course, but together with Don Caton (who had to 
leave the development team a few years ago), Paul Piko and John Parker

We realize that this controversy has put you, the Vulcan.NET and VPS 
customers, in a difficult situation which we have tried to avoid. We know 
you have invested huge amounts of money and many man-years in your products 
and are now uncertain about the future of the products that you have used to 
develop your software. But we know you and we are convinced that you will 
make the right choice.

We suggest that you ask yourself who or what Visual Objects / Vulcan.NET is 
for you.

We think it is:
* The team that converted a potentially strong, but sometimes very unstable 
and unreliable Visual Objects 2.5 into the product that is today
* The team that created a new product and achieved what a lot of people 
thought was impossible
* The team that helps you solve your problems on the support forums, and 
often debug your code in their own time into the early hours of the day
* The team that creates a quick fix to the issues you find in the product, 
so you can continue to work for your customers.
* The team that travels all over the world to conferences to tell you about 
what works, but also very important, what not works in the product and how 
you could work around these limitation
* The team that helped you to get started in the challenging new world of 
DotNet
* The team you have drank a beer with and while sitting next to you and your 
laptop have helped you to fix issues in your code on the spot.

We apologize for the difficult choice we have forced you to make, but we 
know you, we are sure you will make the right decision.

To finish this:
We are still interested in ending this controversy by taking over 
Vulcan.NET, and welcome any constructive proposal from the side of GrafX.

You will understand that we are not going to wait for GrafX. We don't need 
GrafX. We have created Vulcan.NET before and will succeed again in creating 
its successor. We've built it - we can make it better! We wish GrafX & Brian 
Feldman all the best.

We will keep you informed about our progress through the usual channels: 
Newsgroups, Facebook, Twitter and of course our website xsharp.eu.

Robert van der Hulst
President XSharp B.V.
Co-Founder of the XSharp Project.

The XSharp Development team:
* Fabrice Foray
* Nikos Kokkalis
* Chris Pyrgas
* Robert van der Hulst
* And others 

[toc] | [prev] | [next] | [standalone]


#8464

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2015-10-04 23:07 +0200
Message-ID<s4431b11p8i5jvakhib032jndtje74e1uc@4ax.com>
In reply to#8457
On Fri, 2 Oct 2015 16:23:43 +0200, "Marc Verkade [MITCon]"
<marc@mitNOSPAMconDELETE.nl> wrote:

Hello Marc and others,

>The main thing that lacks Grafx is proper communication to its customers 
>through press-articles, website updates, roadmaps etc. IMHO.

Plus the lack of progress. Robert stated litteraly:

"Finally the progress in development has almost come to a stop. There
are very few new features in Vulcan 4."

VPS would have had true value if members could see their problems
fixed within days and they could download it - even at their own risk.
Instead the number of new releases was 1-2 a year (instead of the
minimum of 4 as was promised), apparently because creating a new
release was taking days. As I am not a compiler builder, I can't judge
why this takes so long while I could release a new version solving a
bug of our software within 15 minutes. But I am sure that an " XPS" ,
funding xSharp, would be more valuable than VPS when Robert and his
team could do just that.

>I really hope that all players understand that joined forces ar way better 
>than scattered resources

Right. I can't say wether or not XSharp can attract enough users to be
succesful, although a base version as Open Source software is a good
reason. What if, say, half of the Vulcan users decide to go to XSharp?
Something which is not  unrealistic. Vulcan would have no future.

But what if Robert & team will have full access to Vulcan (and all
rights to use DLL's etc) and their approach increases use of
Vulcan/XSharp together and, as a result, at the same time protects the
investment of users into Vulcan. And would benefit from the knowledge
of those still committed (or about to commit) to Vulcan, valuable
people like Dieter of Willie and those from which their cooperation to
VUlcan or XSharp is still not public knowledge.

I think Brian's decision to resume negotation with Robert would
benefit Grafx, the team and all xBase + Viulcan users.

During Devshare in the UK, last week,  Robert gave us full insight of
his plans. These are interesting times....

Dick

[toc] | [prev] | [next] | [standalone]


#8458

From"Danilo Giuliani" <softdevo@tiscali.it>
Date2015-10-03 17:30 +0200
Message-ID<muosb4$nc6$1@speranza.aioe.org>
In reply to#8449
Wow ... This is news! I work with Vulcan and I am fine.
My fear is that the project could die any day. It is clear that each year
the number of users decreases.
The continuous change of the development team is not a good sign.
The complete lack of a marketing strategy that would give new energy to the
project is completely absent.
It almost seems that Brian does not care anything Vulcan.
I hope a product that guarantees a long life to the language.
Whether this is called Vulcam, X #, or YYYY not matter.
The important thing is to ensure a future for my applications.

Danilo


"Robert van der Hulst"  ha scritto nel messaggio 
news:784286fe-ef26-443c-aa76-1b932e799001@googlegroups.com...

We've built it - we can make it better!
---------------------------------------

Epe: September 28 2015.

We have just returned from a VERY successful DevShare Conference in the UK. 
Many thanks go to Phil Hepburn, Mike Bertenshaw, Dai Darkin and their 
spouses Sue and Sue for organizing this great event.

Our new XSharp initiative has received as very warm welcome at the 
conference, but also raised many questions. We would like to take the 
opportunity to repeat and answer the most common and most important question 
over here:

Why do you want to introduce a new compiler / competitor for a small market 
as Vulcan.NET?

The answer to this is the following:

We never had and still don't have the intention to start a Compiler war and 
introduce a competitor to Vulcan.NET.

Let us explain a little bit about what happened (without revealing secrets 
from private email and phone conversations)

All products have their product life cycle.  We feel that the product life 
cycle for Vulcan.NET in its current form has reached his end. The fact that 
that some of the developers of the product had left or planned to leave the 
development team also indicated that the product in its current form would 
have problems to survive.
Everybody knows that the number of subscribers to the Vulcan Platinum 
Support is decreasing every year, and also that the number of attendees to 
Vulcan conferences is decreasing.
Finally the progress in development has almost come to a stop. There are 
very few new features in Vulcan 4.
A roadmap for future development is missing, and it is no secret that the 
owner of Vulcan.NET has been looking for someone to buy the product for the 
last couple of years.

It is obvious that it is time for a successor, and to make that successor 
successful we think that it is necessary to broaden its user base. That is 
why we wanted to introduce a new product that not only targets the Visual 
Objects & Vulcan.NET market but the other xBase markets as well. But we also 
wanted to help maintain and support Vulcan.NET.

We have therefore approached GrafX (Brian Feldman) and opened the 
negotiations with him. We have offered to take over the maintenance, 
development and support (VPS) of Vulcan.NET and develop a successor at the 
same time (just like GrafX has done in 2002 when Visual Objects was a 
product from Computer Associates).
GrafX did not immediately agree with our proposal and came with additional 
demands.

After consulting our financial partners we have accepted the proposal from 
GrafX under the normal condition that we would receive a Due Diligence 
report. In laymen's terms this means that GrafX needs to prove that it is 
indeed the owner of the Intellectual Property (they could have sold it to 
someone else before us) and GrafX had to show recent sales data to support 
the price it has asked for the product . This is a perfectly normal question 
in all (international) business transactions.
You would also never buy a house too without proof of ownership and an 
estimate of the value by a real estate agent.

After more than one week (and a reminder from us) Brian Feldman answered us 
that he regretted his proposal and retracted the offer, without further 
explanation.

We have replied to him that we were willing to come to another proposal (for 
example transferring only part of the intellectual property) but we needed 
to see some proof
That was the end of the negotiations. Brian Feldman closed the door and told 
us that he is no longer interested in talking with us about selling 
Vulcan.NET

Brian Feldman is very proud of Vulcan.NET 4.0. And so he should be. The 
product has come a long way. Many customers has successfully converted a 
Visual Objects application to .NET with the aid of the product.
We have always and will always appreciate what Brian has done for the 
product and its predecessor Visual Objects. Without his intervention Visual 
Objects would have been buried on the graveyard of dead products inside 
Computer Associates. And he has also helped to start and develop Vulcan.NET.

But we are also very proud of what we have achieved with Vulcan.NET 4.0. We 
have built it, not alone of course, but together with Don Caton (who had to 
leave the development team a few years ago), Paul Piko and John Parker

We realize that this controversy has put you, the Vulcan.NET and VPS 
customers, in a difficult situation which we have tried to avoid. We know 
you have invested huge amounts of money and many man-years in your products 
and are now uncertain about the future of the products that you have used to 
develop your software. But we know you and we are convinced that you will 
make the right choice.

We suggest that you ask yourself who or what Visual Objects / Vulcan.NET is 
for you.

We think it is:
* The team that converted a potentially strong, but sometimes very unstable 
and unreliable Visual Objects 2.5 into the product that is today
* The team that created a new product and achieved what a lot of people 
thought was impossible
* The team that helps you solve your problems on the support forums, and 
often debug your code in their own time into the early hours of the day
* The team that creates a quick fix to the issues you find in the product, 
so you can continue to work for your customers.
* The team that travels all over the world to conferences to tell you about 
what works, but also very important, what not works in the product and how 
you could work around these limitation
* The team that helped you to get started in the challenging new world of 
DotNet
* The team you have drank a beer with and while sitting next to you and your 
laptop have helped you to fix issues in your code on the spot.

We apologize for the difficult choice we have forced you to make, but we 
know you, we are sure you will make the right decision.

To finish this:
We are still interested in ending this controversy by taking over 
Vulcan.NET, and welcome any constructive proposal from the side of GrafX.

You will understand that we are not going to wait for GrafX. We don't need 
GrafX. We have created Vulcan.NET before and will succeed again in creating 
its successor. We've built it - we can make it better! We wish GrafX & Brian 
Feldman all the best.

We will keep you informed about our progress through the usual channels: 
Newsgroups, Facebook, Twitter and of course our website xsharp.eu.

Robert van der Hulst
President XSharp B.V.
Co-Founder of the XSharp Project.

The XSharp Development team:
* Fabrice Foray
* Nikos Kokkalis
* Chris Pyrgas
* Robert van der Hulst
* And others 

[toc] | [prev] | [next] | [standalone]


#8473

Frommoshe attia <attiamx@gmail.com>
Date2015-10-06 00:35 -0700
Message-ID<338058df-e938-48e6-9ae3-5035064fc5ba@googlegroups.com>
In reply to#8449
On Monday, September 28, 2015 at 1:35:16 PM UTC, Robert van der Hulst wrote:
> We've built it - we can make it better!
> ---------------------------------------
>  
> Epe: September 28 2015.
>  
> We have just returned from a VERY successful DevShare Conference in the UK. Many thanks go to Phil Hepburn, Mike Bertenshaw, Dai Darkin and their spouses Sue and Sue for organizing this great event. 
> 
> Our new XSharp initiative has received as very warm welcome at the conference, but also raised many questions. We would like to take the opportunity to repeat and answer the most common and most important question over here:
> 
> Why do you want to introduce a new compiler / competitor for a small market as Vulcan.NET?
>  
> The answer to this is the following:
>  
> We never had and still don't have the intention to start a Compiler war and introduce a competitor to Vulcan.NET.
>  
> Let us explain a little bit about what happened (without revealing secrets from private email and phone conversations)
>  
> All products have their product life cycle.  We feel that the product life cycle for Vulcan.NET in its current form has reached his end. The fact that that some of the developers of the product had left or planned to leave the development team also indicated that the product in its current form would have problems to survive. 
> Everybody knows that the number of subscribers to the Vulcan Platinum Support is decreasing every year, and also that the number of attendees to Vulcan conferences is decreasing. 
> Finally the progress in development has almost come to a stop. There are very few new features in Vulcan 4.
> A roadmap for future development is missing, and it is no secret that the owner of Vulcan.NET has been looking for someone to buy the product for the last couple of years.
> 
> It is obvious that it is time for a successor, and to make that successor successful we think that it is necessary to broaden its user base. That is why we wanted to introduce a new product that not only targets the Visual Objects & Vulcan.NET market but the other xBase markets as well. But we also wanted to help maintain and support Vulcan.NET.
> 
> We have therefore approached GrafX (Brian Feldman) and opened the negotiations with him. We have offered to take over the maintenance, development and support (VPS) of Vulcan.NET and develop a successor at the same time (just like GrafX has done in 2002 when Visual Objects was a product from Computer Associates).
> GrafX did not immediately agree with our proposal and came with additional demands.
> 
> After consulting our financial partners we have accepted the proposal from GrafX under the normal condition that we would receive a Due Diligence report. In laymen's terms this means that GrafX needs to prove that it is indeed the owner of the Intellectual Property (they could have sold it to someone else before us) and GrafX had to show recent sales data to support the price it has asked for the product . This is a perfectly normal question in all (international) business transactions.
> You would also never buy a house too without proof of ownership and an estimate of the value by a real estate agent. 
>  
> After more than one week (and a reminder from us) Brian Feldman answered us that he regretted his proposal and retracted the offer, without further explanation.
> 
> We have replied to him that we were willing to come to another proposal (for example transferring only part of the intellectual property) but we needed to see some proof
> That was the end of the negotiations. Brian Feldman closed the door and told us that he is no longer interested in talking with us about selling Vulcan.NET
> 
> Brian Feldman is very proud of Vulcan.NET 4.0. And so he should be. The product has come a long way. Many customers has successfully converted a Visual Objects application to .NET with the aid of the product.
> We have always and will always appreciate what Brian has done for the product and its predecessor Visual Objects. Without his intervention Visual Objects would have been buried on the graveyard of dead products inside Computer Associates. And he has also helped to start and develop Vulcan.NET.
> 
> But we are also very proud of what we have achieved with Vulcan.NET 4.0. We have built it, not alone of course, but together with Don Caton (who had to leave the development team a few years ago), Paul Piko and John Parker
> 
> We realize that this controversy has put you, the Vulcan.NET and VPS customers, in a difficult situation which we have tried to avoid. We know you have invested huge amounts of money and many man-years in your products and are now uncertain about the future of the products that you have used to develop your software. But we know you and we are convinced that you will make the right choice.
> 
> We suggest that you ask yourself who or what Visual Objects / Vulcan.NET is for you.
> 
> We think it is:
> *	The team that converted a potentially strong, but sometimes very unstable  and unreliable Visual Objects 2.5 into the product that is today
> *	The team that created a new product and achieved what a lot of people thought was impossible
> *	The team that helps you solve your problems on the support forums, and often debug your code in their own time into the early hours of the day
> *	The team that creates a quick fix to the issues you find in the product, so you can continue to work for your customers.
> *	The team that travels all over the world to conferences to tell you about what works, but also very important, what not works in the product and how you could work around these limitation
> *	The team that helped you to get started in the challenging new world of DotNet
> *	The team you have drank a beer with and while sitting next to you and your laptop have helped you to fix issues in your code on the spot.
> 
> We apologize for the difficult choice we have forced you to make, but we know you, we are sure you will make the right decision.
> 
> To finish this:
> We are still interested in ending this controversy by taking over Vulcan.NET, and welcome any constructive proposal from the side of GrafX.
> 
> You will understand that we are not going to wait for GrafX. We don't need GrafX. We have created Vulcan.NET before and will succeed again in creating its successor. We've built it - we can make it better! We wish GrafX & Brian Feldman all the best.
> 
> We will keep you informed about our progress through the usual channels: Newsgroups, Facebook, Twitter and of course our website xsharp.eu.
> 
> Robert van der Hulst
> President XSharp B.V.
> Co-Founder of the XSharp Project.
> 
> The XSharp Development team:
> *	Fabrice Foray
> *	Nikos Kokkalis
> *	Chris Pyrgas
> *	Robert van der Hulst
> *	And others

hi to all
where i can begin with  XSharp 
download and install

thank you

[toc] | [prev] | [next] | [standalone]


#8475

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2015-10-06 14:15 +0200
Message-ID<8ke71b506gd5sjt1edt3e401jra115o5en@4ax.com>
In reply to#8473
On Tue, 6 Oct 2015 00:35:48 -0700 (PDT), moshe attia
<attiamx@gmail.com> wrote:

Hello Moshe,

>where i can begin with  XSharp 
>download and install
>

That's a bit premature. Although Robert has shown a working compiler
on Devshare using a basic sample program, it all has just started.
However Robert expects a working version early 2016.

See http://xsharp.nl/ and especially
http://xsharp.nl/xsharp.nl/files/XSharpLaunch.pdf

Dick

[toc] | [prev] | [next] | [standalone]


#8485

From"Philippe Bayard (Belgium)" <philbayard@gmail.com>
Date2015-10-06 07:50 -0700
Message-ID<ec64016a-d67c-42fa-9dcd-2d2046a88e43@googlegroups.com>
In reply to#8449
Interesting subject.

I have some question. 

1) Is there gonna be some tools to move VO projects to X# ? ( like the one in Vulcan ). 

2) What will be the major advantage of X# "except" introducing our old app into .NET world? I mean, when i was working in Vulcan, i did have to rewrite some stuff in Vulcan which was already existing in c# , so i finally did it in c# rather than in Vulcan. 

So refractoring Vulcan code to c# was somehow a way to finally be in c# and going on with c#. So back to my question, what will be the advantage of working in x# ? ( the support of DBF is quite a nice one, which give the possibility to go to .net first, then to go to SQL then).

Best regards, and good luck with X#, it's always nice to see open source projects.

Jean-Philippe

[toc] | [prev] | [next] | [standalone]


#8527

FromJean-Pierre Maertens <jp.maertens@gmail.com>
Date2015-10-16 12:41 -0700
Message-ID<8549f6db-3855-4b33-8186-993b9089c6ae@googlegroups.com>
In reply to#8449
Is the x-sharp forum down ?

[toc] | [prev] | [next] | [standalone]


#8528

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2015-10-16 22:18 +0200
Message-ID<6rm22bdaomgoub4t297sj75fdthft8vhee@4ax.com>
In reply to#8527
Jean-Pierre,
>Is the x-sharp forum down ?

No, try
http://xsharp.info/

i think the address had some changes...

Karl 

[toc] | [prev] | [next] | [standalone]


#8530

FromRobert van der Hulst <robert@heliks.nl>
Date2015-10-16 22:24 +0200
Message-ID<56215D12.6090204@heliks.nl>
In reply to#8527
JP,

No but we moved the main website to a different provider.
If you have link to xsharp.nl then change that to xsharp.info


Robert
> Is the x-sharp forum down ?
> .
>


-- 
Robert van der Hulst
robert@heliks.nl

[toc] | [prev] | [next] | [standalone]


#8532

From"Craig Dawson" <craig_dawson@hotmail.com>
Date2015-10-18 17:27 +1100
Message-ID<mvve08$r05$1@dont-email.me>
In reply to#8530
XSharp - I am liking what I am seeing...
----------------
Craig Dawson


"Robert van der Hulst" <robert@heliks.nl> wrote in message 
news:56215D12.6090204@heliks.nl...
> JP,
>
> No but we moved the main website to a different provider.
> If you have link to xsharp.nl then change that to xsharp.info
>
>
> Robert
>> Is the x-sharp forum down ?
>> .
>>
>
>
> -- 
> Robert van der Hulst
> robert@heliks.nl 

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web