Best Regards,
Danijel Tkalcec, Team RTC
http://www.realthinclient.com
Does this include the remote portal stuff as well?
I would hate to see that go into the bit bucket.
That was the plan, yes.
> I would hate to see that go into the bit bucket.
Why?
Att.
Esteban Pacheco
"Danijel Tkalcec [RTC]" <r...@deltasoft.hr> wrote in message
news:487188d2$1...@newsgroups.borland.com...
Danijel,
You seem to have a licensing crisis every thee to six months, whether
you need it or not. If you are not making a living doing this under the
current licenses, I guess I can't blame you for looking for change.
But I assure you that this unceasing change of direction does not help
you. Find a way and stick to it, and devote your prodigious energy and
talent to developing software.
-Jim
--
I don't think anyone else can maintain and further develop RTC based
components better than you. I hate to see change of ownership of RTC, but if
it for financial reasons then it is ok. You have to do what is the best for
you and your family.
Best Regards
Zoran
"Danijel Tkalcec [RTC]" <r...@deltasoft.hr> wrote in message
news:4871722b$1...@newsgroups.borland.com...
It's not about licensing. RTC is getting too big for me to continue working
on everything by myself (it is now about 3 relatively complex component
sets: RTC SDK, RTC Portal VCL and RTC WAF) and I don't have enough funds to
pay other developers to do serious work, and was unable to find developers
interested in doing serious work for a share of the profits (which would
currently be relatively small, since only RTC Poral VCL is generating
revenue). So, instead of trying to do everything by myself and dragging
things along in slow motion, I've decided to find a larger company with
enough resources and available man-power to integrate the RealThinClient
components into their portfolio. Until I find a suitable owner, I will
continue working on RealThinClient components as before, so there is no
change for current customers, but I hope there will be a positive change
soon.
Regards,
Danijel
WHS. Since adopting it, we've had a lot of good support sessions with it, and it
works easily and well.
/Matthew Jones/
/Matthew Jones/
It is always a great pity when another component vendor has to throw in the
towel. The problem is that Delphi is just not as popular as it was nor as it
ought to be. On top of that, the Delphi middleware market is saturated. I
suspect that you may not get any offers that match what you think your
components are worth, especially bearing in mind the hours you have
invested, simply because they are not generating much profit.A better
solution might be to merge RTC with another middleware framework. The two
market leaders being kbmMW and RO.
In my opinion the best choice would be kbmMW since I believe you already
have a relationship. I am sure Kim would welcome someone with your talent
and energy to his team.
Best wishes
Trev
"Danijel Tkalcec [RTC]" <r...@deltasoft.hr> wrote in message
news:48721d27$1...@newsgroups.borland.com...
> I don't have
> enough funds to pay other developers to do serious work, and was
> unable to find developers interested in doing serious work for a
> share of the profits (which would currently be relatively small,
> since only RTC Poral VCL is generating revenue)
Raise your prices. You have excellent products that, IMO, are
undervalued. Don't go crazy though. :-)
> So, instead of
> trying to do everything by myself and dragging things along in slow
> motion,
I'd rather speed/quality/price, pick any two. I'll take quality and
price. I would rather the code quality and stability from you than
rolling the dice with someone else.
--
Kevin Powick
If TMS is only taking care of marketing and sales while the original authors
continue working on the products by themselves, then TMS would not be the
right choice for me, since I am looking for a company with a team which can
help on the development and support side too, and not only in marketing and
sales. As for kbmMW and RO, I think they would both only be interested in
ripping RTC apart and extracting and putting pieces of it into their own
products, but the RTC components as such would disapear. And that's most
certainly not what I have in mind when looking for a new home for RTC
components.
I have now increased RTC Portal VCL prices (Basic from 299 to 395 EUR,
Bronze from 499 to 695 EUR), and removed license restrictions for using the
components, which allows my current customers to use the RTC Portal VCL to
build and sell, copy or give away commercial support tools without having to
pay royalties or buy extra licenses. That's to make sure that licensed RTC
Portal VCL users won't have to worry about their rights to distribute
applications built with them, no matter what the new RTC Portal VCL owner
should decide (should there be an owner change for the RTC Portal VCL).
My main goal and the reason why I have decided to offer RealThinClient
components "on sale" is to find a company which would be ready to back up
development of RTC WAF, my idea of a Rapid Rich Internet Application
Development Framework. As said, the core functionality is already
implemented (Beta 3 now also has automatic client-side caching, which
further reduces traffic and improves remote performance) and I've made a
handfull of components work with the framework proving that the concept
works, but there is still a lot of work left to be done before the
components can be used for developing business applications and I'm affraid
I won't be able to handle the load by myself.
Best Regards,
Danijel Tkalcec
I like the RTC WAF idea very much, but if it's a choice between that and RTC,
I've rather you concentrate on RTC base code. I was going to use RTC
(commercial version) in an upcoming project, but I am not so sure now as it
seems it's future may be up in the air at this point. Am I reading the sign
incorrectly?
--
Warm Regards,
Lee
> I like the RTC WAF idea very much, but if it's a choice between that and
> RTC, I've rather you concentrate on RTC base code.
RTC WAF, as well as RTC Portal, are using the RTC SDK for communication.
In other words, the RTC SDK is the motor that drives all RTC components.
There is no question wether RTC SDK will be continued.
> I was going to use RTC (commercial version) in an upcoming project, but I
> am not so sure now as it seems it's future may be up in the air at this
> point. Am I reading the sign incorrectly?
I'd say you are reading things backwards. The idea is to find a company
which will have interest in continuing to work on the RTC SDK and RTC WAF.
Not to flush the products down the toilet.
Best Regards,
Danijel Tkalcec
Danijel seams to become more and more a instable factor. I would never use his
tools in a critical application now. I like his work, but I don't like this up's
and down's.
Gruß aus den Bergen
Günter
Then, I guess it's a good thing I'm stepping down from my "decision making
throne" and will be leaving my work to someone more stable.
Best Regards,
Danijel Tkalcec
Best Regards,
Danijel Tkalcec
Forgive my ignorance but, while I thought the WAF demo was very cool, I
don't really see the point of it. Why would someone use this instead of
writing a web application, be it in HTML with JS, ASP.NET, Flash,
Silverlight, or what have you. I don't quite see the angle for WAF. Maybe
I'm missing something but it seems like a web application but with a
specific client for rendering (instead of a browser, or Flash, etc).
Have a great vacation!
Cheers,
Van Swofford
Tybee Jet Corp.
> Why would someone use this
> instead of writing a web application, be it in HTML with JS, ASP.NET,
> Flash, Silverlight, or what have you.
This is why. :-)
http://www.theregister.co.uk/2008/07/07/web20_for_developers/
--
Kevin Powick
/Matthew Jones/
Almost all code need maintenance sooner or later. Only exception is really
simple code and I don't think RTC falls into that category.
"Nathanial Woolls" <nwo...@nospam.gmail.com> wrote in message
news:4875608a$1...@newsgroups.borland.com...
(I should point out that I was also quite sceptical of the idea of having to have a
server running all the time, but it just sits on our email server, and has been
really good as more than one person can view, and the customer can connect before
we do if they want.)
/Matthew Jones/
Here is the same. We are great fans of the RTC Portal and it was an
repacment for NTRSupport which was very expensive, not good supported.
I will have no problem when Danijel is gone with this tool (it can be
replaced easy with other tools) but when I want to use the RTC SDK in
my main application I would see this different.
And to say it again: I like Danijel and the work he is doing, but I
don't always like the way he acts.
Point taken. But what if someone doesn't step up to the plate? Are you still
committed to maintaining the RTC framework for some time to come or will it
languish? Don't get me wrong, I feel more secure in having the source
available, but little good it'll do me since I have neither the time nor
inclination to become familiar with it intimately enough for it to make a
difference.
--
Warm Regards,
Lee
Then, I will have to come up with "Plan B" (which I do not have yet).
Best Regards,
Danijel Tkalcec
http://pseudosavant.com/blog/2008/07/08/a-proprietary-web-blame-the-w3c/
He has is own RichClient though but will surely be interested in your
product. But..but..but you will have to be patient with him and explain
him everything....
HTH