ANN: RealThinClient components (full source code for Delphi and BCB) > available now
Danijel Tkalcec
internet-enabled applications using any Delphi version (even the personal
edition) and BCB. No other components are needed. It even comes with a
ready-to-use WebServer implementation comparable to Appache, supporting
PHP5.
RealThinClient Core 1.x components - commercial license with full source
code for Delphi and BCB = 95,- EUR
Check www.realthinclient.com for more info.
With this purchase, you get 1 year first-hand techical support with all
minor updates and bug fixes.
As a licensed RTC user, you can define the way RTC will be evolving in the
future.
RealThinClient Core now contains
* RTC Core Server components:
- TRtcUDPServer
- TRtcTCPServer
- TRtcDataServer
- TRtcDataServerLink
- TRtcDataProvider
- TRtcServerModule
* RTC Core Client components:
- TRtcUDPClient
- TRtcTCPClient
- TRtcDataClient
- TRtcDataClientLink
- TRtcDataRequest
- TRtcClientModule
* RTC Core Remote Function components:
- TRtcFunction
- TRtcFunctionGroup
- TRtcResult
* RTC Core Value objects:
- TRtcValue
- TRtcArray
- TRtcRecord
- TRtcDataSet
- TRtcFunctionInfo
Some information about RTC Core components:
----------------------------------------
* Complete package: You don't need to buy the Enterprise version of Delphi
or BCB, nor upgrade to the latest Delphi/BCB version to use RealThinClient
components. All RTC components compile with standard editions of Delphi and
BCB, starting from Delphi 4.
* True RAD: Everything you do with RTC is component-based, while all the
code you will ever need to write is defined as events, so you can truly
design your server and your client applications, without the need to use
wizzards or code your interfaces.
* Multi-Threading: A very sophisticated Threading mechanism is built into
all RTC Connection components, which allows thousands of active connections
to be running in separate threads, all at the same time. And the only thing
you need to do is change a simple MultiThreaded property to True. Then, any
newly received connection will be handled by a thread pooling mechanism
which saves valuable System resources, while enabling nearly unlimited
number of symultaneous connections at the same time.
* Uses Proxys: Data Clients will never have to be specialy configured to get
through corporate firewalls to reach the server. Simply by setting the
UseProxy property to True, DataClient connection will use a connection
provider which uses the same settings as Internet Explorer for browsing the
Web. This means that Clients can work in any corporate LAN and have full
access to the internet.
* Non-Blocking: Other than most other internet components, RTC connection
components are non-blocking and event-driven. This means that, even when not
using a multithreaded mode, your users will not be blocked ("Application Not
Responding") during communication between your client and the server. For
each state change in the connection, there is an event that will be
triggered.
* Remote Functions: Implementing and using remote functions is as easy as
writing local functions. You just place a RtcFunction component on your Form
or a DataModule, set function name and write your OnExecute event. OnExecute
event receives the Connection object, Function Parameters and a Result
object. You just have to use the parameters passed to the function to
prepare the result. The rest is done "under the hood" by RealThinClient
components.
* Strong Encryption: RTC components offer easy-to-use strong encryption with
Encryption Keys of variable length. And you don't even have to think about
the keys to use, they will be generated and maintained for you. Also, for
remote functions, it makes no difference wether function parameters and
result are transmitted using a secure encrypted connection or just plain
text, it is marely a parameter you define for your Server- and Client-Module
components.
* Use/Write Plug-Ins: All Client and Server code you write using RTC Core is
ready to be used as building blocks or plug-ins in any application that uses
RTC Core. For example, you can combine a WebServer, Messenger server,
Application server, Database server and your own functions in one Data
Server, even when those components weren't specialy designed to share the
same Server space. Because of the easy-to-use plug-in framework on top of
which all RTC Components are built, you can link unlimited number of
functionality and data providing components like DataProvider, ServerModule
and/or DataLink to one DataServer, enhancing that server's functionality
with each new component. And by keeping code in separate units
(DataModules), you can even provide your own plug-ins (and sell those
plug-ins) to anyone who uses the RTC Core Library.
* Small footprint: A complete WebServer implementation, using RTC Core
components, is less than 600 KBytes when compiled with D7. Even though it is
so small, it offers enough functionality with great stability and
scalability.
For more information on RealThinClient components, check:
www.RealThinClient.com
(powered by the RTC DataService)
Best Regards,
Danijel Tkalcec
Ted Nicolson
for your previous project (Remote Tools). Three months later you sold code
rights to another company leaving your own registered clients without
updates or bug fixes.
Instead that, you asked them to promote and advertise this new company just
to have access to new source.
And now you believe that we gonna spent more money for your new "efforts" ?
What a joke !
Ted
Nick Rollas
You left the Remote Tools project with lot of missing features and LOT of
bugs.
I agree Ted, what a joke !
Nick
"Ted Nicolson" <n...@email.pls> wrote in message
news:4289...@newsgroups.borland.com...
Keith Blows
I'll third that!
Most disappointing turn of events.
Regards,
Keith Blows
Danijel Tkalcec
1.) I still support all licensed Remote Office users (check
www.realthinclient.com forum, it still has a RemoteOffice section) and if
anyone had any questions regarding Remote Office, they contacted me directly
and we solved the problems.
2.) There are quite a few Remote Office users who are more than happy with
Remote Office and use it on a daily basis to support their customers. The
only "problem" is that only the trouble-makers stand up and scream out loud,
while happy customers mind their own bussiness. Some of those happy
customers added features to their Remote Office version and created
comemrcial products based on Remote Office, which you can also find in this
newsgroup.
3.) RealThinClient code has nothing to do with RemoteOffice. RealThinClient
has a completely new code base, which I have been working on the past 6
months. RTC is fully component-based, has detailed help (also available as
Web Help), demo applications that show you how to use each component (which
includes a fully functional WebServer) and a Quick-Start guide, which I will
be enhancing with visual presentation guides.
Anyway ... if you have questions about RemoteOffice, you can still contact
me directly (or post questions to the RTC Forum at www.realthinclient.com).
I will be more than happy to help you.
Best Regards,
Danijel Tkalcec
prom
i use Remote Office, and are very happy with it.
With Remote Office i could realize a nice and good working
support software for my customers, and it works perfect!
And if i need help, i can write to the developer and get
quickly answers.
As i bought Remote Office i got the sourcecode and a well working
example. Thats all what i expect from good vcl-components.
AND i couldn't find bugs.
It' not a new thing, that VCL-components change owners and companies.
This happens often.
best regards
Gerhard Knapp
prom
best regards
Gerhard Knapp
> Nick Rollas wrote:
Jonathan Neve
I was also (and still am) a user of RemoteOffice, and I don't agree with
your statements.
I do realise of course, that Danijel made a bit of a commercial mistake
with RemoteOffice, and I can understand that you would be disappointed
with the way things turned out. However, I don't see why that should
make you so bitter against him, nor why you should try to defame his new
product because of it.
I really think you're exagerating, because:
a) You paid a very moderate price, and what you got was well worth the
price, considering that you have the full source code. You are therefore
completely free to do what you like with it. Obviously, this isn't as
good as having Danijel continue working on improving it, but surely it's
better than being left stranded without even the source code.
b) The product you now have works fine. If it's missing some features,
you can always add them, but even as it is, it's quite adequate for a
lot of people. For example, all I changed in my version is the user
interface.
c) As Danijel stated, there is still support for RemoteOffice. The only
"problem" is that Danijel is no longer adding features.
d) If you really needed new features, why didn't you accept the
Acclimate partner agreement. I know, it was a bit complex, and over all,
a surprising way of doing things. But at the end of the day, it wasn't
that bad. If you can get the full source code and updates for merely
partnering with Acclimate to some extent, that's even cheaper than
RemoteOffice ever was. Of course, if you wanted to produce a commercial
application based on the source code, that wouldn't have been possible.
But in that case, staying with RemoteOffice was still possible.
e) I find it perfectly understandable that someone may sell his product
to a third-party, and that that third-party may not choose to
commercialise it in the same way as before. Danijel didn't break the
licence agreement you had agreed to in any way, because if you didn't
like the new terms, you were allowed to stay with the old agreement.
f) RealThinClient has nothing to do with RemoteTools.
g) Danijel's a nice guy, he just made a commercial mistake. Please stop
trying to give him a bad name for all his future developments.
Regards,
Jonathan Neve.
Ted Nicolson
Sorry Danijel, but it's true.
I'm sure you know, how many users disappointed by your behavior last year.
They paid for Remote Tools, and you stopped upgrading - fixing it. In
contrast, after joining Acclimate, you asked your clients to promote that
company, just to have access to code updates.
And now, after your unsuccessful partnership with Acclimate, you're here
again asking for new "victims". This is ridiculous.
Please don't insist that the above are not true, I have archived all posts
sent by you and your ex-partner Christian Prince (Acclimate)
So please, make us a favorite, get a real job ! And next time, respect the
rest developers who trusted you and gave you their hard earned money.
Ted
-------------------------
"Danijel Tkalcec" <dtka...@hotmail.com> wrote in message
news:4289b790$1...@newsgroups.borland.com...
Tim Shields
However, as we use the software everyday and I can honestly say that
our company could not function with out his software I got over it
pretty quickly!
Oliver Feins
>With this purchase, you get 1 year first-hand techical support with all
>minor updates and bug fixes.
>As a licensed RTC user, you can define the way RTC will be evolving in
>the future.
How do you see it evolving yourself now?
With TRtcDataClient, remote functions..., how would you compare your
offering to KbmMW or RemObjects ?
>* Complete package: You don't need to buy the Enterprise version of
>Delphi or BCB, nor upgrade to the latest Delphi/BCB version to use
>RealThinClient components. All RTC components compile with standard
>editions of Delphi and BCB, starting from Delphi 4.
Any plan to have it all compile and run on FreePacal and Lazarus to allow
Linux support?
>* Remote Functions: Implementing and using remote functions is as easy
>as writing local functions. You just place a RtcFunction component on
>your Form or a DataModule, set function name and write your OnExecute
>event. OnExecute event receives the Connection object, Function
>Parameters and a Result object. You just have to use the parameters
>passed to the function to prepare the result. The rest is done "under
>the hood" by RealThinClient components.
Could we think of something like RemoteForms? that would output XForms and
link to Remote Functions written with RtcFunction ?
You spoke of integration with PHP. Any support to call Java methods
planned?
Regards,
Oliver
Danijel Tkalcec
several possibilities for every licensed Remote Office user after the
copyright transfer. If you were one of them, you would have known that.
1.) You could have partnered with Acclimate and get access to their
Support-Bridge (new Remote Office) with all future upgrades at no cost
(totaly free). This agreement might have been confusing, but the only thing
they asked for is that you don't go and create a competing product (meaning:
sell Support-Bridge as your product), which is understandable, since they
are doing all the upgrades and the coding.
2.) You could continue using the source code as it was, or make some minor
interface changes (different language, reorder buttons, add your remote
functions), which is pretty easy, considering the fact that you had the full
source code, all components were on a standard Delphi form and everything
was working just fine as it was. And if you should get stuck, there was
always the possibility to contact me for support.
3.) There were no known bugs (as you would like to present here) in
RemoteOffice source code, it worked fine (still does). After RemoteOffice
became Support-Bridge, there was not a bug-fixing needed in the RemoteOffice
core library. The only thing that was done is a new interface (polish the
thing a bit), encrypted communication and a gateway option.
In any case, I was offering full support to all RemoteOffice licensed users,
wether they chose to continue using the original code or partner with
Acclimate. I still am doing this, as good as I can, but you have to say if
you have a problem, I can't baby-sit you. I didn't hide, nor dissapear.
Whenever someone contacted me or posted a query on the forum, I helped them
out (but there were not a lot of such queries, since everything worked fine
as it was). And my E-Mail address is still the same as before (check the
copyright notice at www.realthinclient.com). So, I can't understand why
you're crying out loud that I left you on the street. If you have a problem
with RemoteOffice, what is stopping you from contacting me directly or using
the Support Forum? RemoteOffice forum was open and I was there all the time.
And last but not least, would you please state your real name? "Ted
Nicolson" did not license a copy of Remote Office (never did), nor had
anyone named "Ted" or "Nicolson" ever try to contact me anytime in the past
2 years (guess what, I also keep track of all my E-Mails). For all I know
(especially since you are using a fake E-Mail address), you are just someone
who doesn't want RealThinClient to take off. And your statements like "get a
real job!" may only prove that I'm right. Well, I wish you all the luck in
your actions, I'm not taking part in this sharede anymore.
Best Regards,
Danijel Tkalcec
"Ted Nicolson" <n...@email.pls> wrote in message
news:4289...@newsgroups.borland.com...
Danijel Tkalcec
> How do you see it evolving yourself now?
> With TRtcDataClient, remote functions..., how would you compare your
> offering to KbmMW or RemObjects ?
The RTC Core is now a basic component set for remoting and web development.
It mostly compares to something a Java developer is used to having at start,
since you write server-side code for processing requests and execute remote
functions. So, it is the base for developing any internet-enabled
application by coding the server to produce HTML content for the browser,
and/or using remote functions to writing server-side functionality useabe by
any RTC Client.
The two things that RTC mostly resembles now in the Delphi world are:
1.) IntraWeb: only without a Forms designer, since you send your web content
as pure HTML code.
2.) RemObjects, since RTC is offering very simmilar functionality without
the use for shared interfaces
> Any plan to have it all compile and run on FreePacal and Lazarus to allow
> Linux support?
I'd love to do that. I plan to port the components to .NET next year, but
I've also thought about Kylix and other Pascal versions. The only things
that should change are the connection provider components, which I have kept
"under the hood", so they can be replaced without compromising the public
interfaces.The rest of the code should be compatible across sysems, by using
compiler directives.
> Could we think of something like RemoteForms? that would output XForms and
> link to Remote Functions written with RtcFunction ?
Yes. That is what I want to do next, but that will be quite a lot of work,
since you need a separate component for everything visual. This will be made
available to everyone who has licensed RTC Code as add-on, since not
everyone will want to use those components to build their server/client
applications.
> You spoke of integration with PHP. Any support to call Java methods
> planned?
I plan on making the Remote Functions work with SOAP,
the same way they work now by using the RTC format.
Java methods could then be called using SOAP, if they are published as a
service.
But, I could also write a component set for creating RTC Objects in Java,
so you could write the same remote functions in java and call them using a
RTC native format.
Best Regards,
Danijel Tkalcec
Danijel Tkalcec
Judging by the reactions of some people here, someone might think that I am
selling waporvare (software that isn't finished or needs a lot of testing
and polishing to work). This isn't so. I have been working on RTC Core since
October 2004 (that's 7 months) and it has been my full-time job since. But,
I didn't feel like publishing it or offering it here befoere I had a
complete Core component set for the client and for the server, which can be
used to write fully-functional applications client/server applications.
I do not want RealThinClient to have the same faith as RemoteOffice, where
some people are still attacking me just because I've sold the copyrights to
a company which didn't want to offer the same licensing terms for their
product I did while it was mine. I also do not want to make any promisses
regarding future upgrades and RTC updates. When I say that I plan to do
something, it is only ideas which I would like to realize.
RTC Core 1.1 is best suited for writing Web Servers, SOAP/XML Services, or
Client/Server applications. For WebServers and Services, you will be writing
server-side code only, using RtcDataProvider components to implement the
functionality. And for Client/Server applications, you will most likely be
using server-side remote functions, called by your clients. Since the
framework of RTC Core is built with a goal to work as a general server,
being capable of supporting data from different sources, all RTC components
can be used together in one application.
I will be enhancing RTC Core continualy, but ... please, do not go and buy a
copy if you are doing this only because I might add some feature in the
future. If you like RTC Core but miss some functionality, please contact me
directly (www.realthinclient.com) and I will tell you if that functionality
is implemented or will be inplemented in short, so you know if it is worth
waiting or you should take some other component set, already available. Each
time I add something interesting to the RTC Components library, I will post
it here as an announcement [ANN]. If you like what you see and feel like you
can use it, then RTC may be worth taking a look.
Again: Don't buy something you can't start using today. But, if you have
ideas for RTC and want to help me realize those, I would be more than happy
to grant you a free RTC license in return for your help.
Best Regards,
Danijel Tkalcec
Ted Nicolson
> You can't say that I have left Remote Office users on the street. There
> were several possibilities for every licensed Remote Office user after the
> copyright transfer. If you were one of them, you would have known that.
Like what ? To put Acclimate advertise in our company's website, just to get
updated code ? Are you serious ?
BTW if Acclimate was such a honest and trusty company, then why do you left
?
Come on now Danijel, most of your registered clients know exactly what I
mean.
And something about my name. Remote Office was registered by Sakis
Papademetriou, our company's development manager. I think we were the first
who registered Remote Office since first announced.
I'm in development business since early eighties and current registered user
of more than fifty programming tools / libs. I really hate been offending
but your practice to gain business was one of the worst ever heard about.
Ted
Danijel Tkalcec
> get updated code ? Are you serious ?
> BTW if Acclimate was such a honest and trusty company, then why do you
> left ?
Question: are you attacking me now, or Acclimate? I am still in contact with
Acclimate and I am still good friends with Christian and Mike. The reason
for me leaving Acclimat was not because they are not trustworthy, but
because I wanted to do things alone, like I was used to. I'm not a team
player, that has nothing to do with Acclimate. I was always doing things on
my own and I'm used to having complete control over things (same goes for
the code I use or write). You could say, I wanted to be my own boss. That is
the only reason I don't work for Acclimate anymore. But, as I said, I still
value Christian and Mike as good friends and we are still in contact. Btw
... Christian got a wonderful baby daughter a few weeks ago :o)
> Come on now Danijel, most of your registered clients know exactly what I
> mean.
Not really.
> And something about my name. Remote Office was registered by Sakis
> Papademetriou, our company's development manager. I think we were the
> first who registered Remote Office since first announced.
In that case, I understand your anger even less, since Sakis Papandemetriou
never complained about anything regarding Remote Office. The last contact I
has with him was when he even for the unpack key to download the last
available Remote Office package in February this year, and I've then sent
him the unpack key. I never had exchanged any angry words with him.
> I'm in development business since early eighties and current registered
> user of more than fifty programming tools / libs. I really hate been
> offending but your practice to gain business was one of the worst ever
> heard about.
As someone having so much experience, you whould have to addmit that you
can't expect someone to be in your costidy forever, just because you
purchased source code for 99,- EUR. You bought Remote Office while it was
still in its early stages and if you follow its development history now, you
will see that I did a number of enhancements to Remote Office before I've
sold the copyrights. And most of them were pretty complicated and
time-consuming. Example: GDI Hooks, pure assembly routines for fastest
compression, RemoteOffice in form of VLC components (it was just a form
before), etc. RemoteOffice expecienced an explosion in enhances over just a
few months, just because I was working hard to keep all licensed users
happy.
By the time Acclimate took over, the only thing that was missing was
encryption and the gateway option (which is not that important). There were
no bugs. And the only time that Sakis Papandemetriou has contacted me about
a possible bug inside remote office was a few weeks after his purchase, but
even that came out to be a Windows limitation and not my fault. And I sent
him the answer to his problems on the same say.
I think that by now, after over a year has passed, you should really get
over it.
Best Regards,
Danijel Tkalcec
Ted Nicolson
> Question: are you attacking me now, or Acclimate? I am still in contact
> with Acclimate and I am still good friends with Christian and Mike
Good for you...
> In that case, I understand your anger even less, since Sakis
> Papandemetriou never complained about anything regarding Remote Office.
> The last contact I has with him was when he even for the unpack key to
> download the last available Remote Office package in February this year,
> and I've then sent him the unpack key. I never had exchanged any angry
> words with him.
Nobody, including our manager, was happy with your practice. But that's
another story...
> As someone having so much experience, you whould have to addmit that you
> can't expect someone to be in your costidy forever, just because you
> purchased source code for 99,- EUR.
Sorry, but what exactly the word "forever" means ? Less than five months
after you first announced Remote Office and before its bugs been fixed, you
passed rights to Acclimate asking from us to accept new license terms or
stay with the old unfixed code. Do you really call that honest author to
clients relation and trusty business proctice ?
Maybe 99 EUR mean nothing to you, but not everybody agrees with that.
> I think that by now, after over a year has passed, you should really get
> over it.
I'm sure that is what you thought...
Ted
Matthew Jones
Not that I want to step in, but could you say what bugs there were?
Danijel says there weren't any, and you apparently didn't tell him of any
problems, and others don't have any problems, so I really don't understand
your problem here? Did you email him with bug reports?
/Matthew Jones/
Ted Nicolson
> I really don't understand your problem here?
Obviously, you're not one of Danijel's registered clients.
Ted
Matthew Jones
such things. I can't see what the real problem is here. I ask again, what
bugs did you have? The scale of the problem would put it into perspective
for me.
/Matthew Jones/
Jim Gallagher
> Obviously, you're not one of Danijel's registered clients.
I am, and I use Remote Office every day. I have the source code so I'm
able to make any changes I want to the user interface, and even sell
the resulting product. There are no bugs that affect what I do with
the software.
I would have preferred that Danijel kept control of the software and
continued updates, particularly encryption, but that is a risk you take
with any software - and why it is important to get a good license and
the source code, both of which he provided.
I personally think that Remote Office is an excellent product and I'm
looking forward to seeing what he does with the Real Thin Client
software.
-Jim Gallagher
Darryl Strickland
where disappointed when the development stopped, however that's business.
The RO code is well written and performs as described. I have had several
emails and requests with Danijel over the last couple of years and his
support and friendliness has been great. I completely support his efforts
and look forward to Danijel's new products.
Darryl Strickland
"Jim Gallagher" <zenia!NOSPAAM!@earthlink.net> wrote in message
news:428a1cba$1...@newsgroups.borland.com...
listmember
RTC looks fine to me.
The only thing I'd like it to do is that it should
work with FPC (Free Pascal Compiler).
The reason I would like it is this:
I have my own application which I would like to serve
to Internet. I'd like to do it under Linux for various
reasons.
I can get a X86_64 box dead cheap, which means I'd like
my own app to be 64bit native.
Kylix can not do that --I am not sure if Borland will
ever release another Kylix let alone 64bit version.
Cheers,
Ray
Danijel Tkalcec
If you are interested in helping me to port RTC to Free Pascal, I would be
more than happy to do this. I would give you one RTC Core license in
exchange for your support. I wouldn't ask you to do any coding, though. Just
point me in the right directions, in case you are familiar with Free Pascal.
If you are interested, pleasae contact me directly (you will find my E-mail
address at the bottom of my www.realthinclient.com site).
Best Regards,
Danijel Tkalcec
Scott Martin
The software was sold as a 1 time fee of 99.00 (as I remember) for the
source and a _lifetime_ of free upgrades.
After a few months, Danijel sold his software to another company. This is
his right.
That said ...
The problem that I had is that since we bought the software under the
previous
agreement, all existing users should have been "honored" as registered users
with the new company.
This was not the case. We were forced by the new
owners to make additional purchases or advertise their software.. or some
crap.. I don't remember, or care to.
One could argue the the new company has this right, but what got my
attention
was that right before the sale, a big announcement was made about this
software
and it did mention lifetime. It was seen by us a last ditch effort to obtain
purchases
before he sold the software.
It was presented one way, end up another. Simple.
I agree that it was against any "Gentleman's Agreement" you have with most
companies. The manner in which the transfer was handled was not appreciated
by many users.
True I have the code, but I have too much of my own work to fix someone
else's code. No excuse, but true.
Personally, I have just written it off as a bad investment.
I wish Danijel all the success in the world, but it won't come from any
purchases
from us and/or companies we support.
Regards,
Scott.
"Matthew Jones" <mat...@matthewdelme-jones.delme.com> wrote in message
news:memo.2005051...@nothanks.nothanks.co.uk...
Matthew Jones
"lifetime" free upgrades is something that can't be provided economically
for 99 Euros. I don't disagree it sucks, but I suppose it seems there is a
lot of anger here and it is hard to understand from an external
perspective.
/Matthew Jones/
Danijel Tkalcec
1.) Ted is complaining about unfixed bugs and me leaving unfinished code,
but he never sent me any bug reports (not by mail, nor on the RemoteOffice
forums), so I don't know of any bugs and he isn't ready to specify them
either, while a lot of other people are using Remote Office today as they
did a year ago, even though there are no more updates (licensed users and
those who downloaded RemoteOffice executables for free from
www.realthinclient.com ).
2.) Since there were no known bugs in Remote Office source code and it
worked as expected, I don't understand people who say they have thrown the
code away, because there will be no more updates (like Scott). It is only
natural that every owner change brings changes. And Acclimate didn't force
anybody into doing anything, they just offered a way for all RemoteOffice
licensed users to get free access to all updates Acclimate will be doing to
their product (Support-Bridge). But, since every licensed Remote Office user
has the full source code which is working fine, there was no real need for
that. There were absolutely no known bugs in Remote Office which would have
made the product unuseable (as some people would like to make you believe
now). But, everyone can download Remote Office for free (all RemoteOffice
tools in executable form) from www.realthinclient.com and judge for
themselves. It might not have the same nice inetrface you are used to by
commercial products like PcAnywhere, but it does the job and all licensed
Remote Office users got the complete source code, they didn't pay any
royalties for distributing it in executable form, and anyone can polishing a
form's interface with Delphi and BCB (keep in mind that no source code
changes were needed to change the interface, since Delphi/BCB are Visual
tools).
3.) Here is the license agreement for Remote Admin Tools / Remote Office
License Agreement (this part never changed):
*** License Agreement *******
You have the right to use and modify the source code, compile it and sell it
in executable form, without paying any royalties. But, you don't have the
right to give away or sell the source code (or parts from it), nor to create
one or more DLL files (Dynamic Link Libraries) that would enable others to
use the Remote functionality from their code.
*************************
4.) Here is the text I used to promote Remote Admin Tools when I started
selling it:
-----------------------------
Remote Admin Tools with complete source code for Delphi and C++ Builder!
cca 16.000 lines of code, commented in English language, written for Delphi
(tested on D4, D5, D6 & D7) and Borland C++ Builder (tested on BCB5 & BCB6),
can be tested and purchased from the Remote Office forum
(http://www.deltasoft.hr/remote/forum). Using Remote Tools Source Code, you
can easily add Remote Administration functionality to your existing Delphi
or C++ Applications.
If you License the Source code, you get the complete source code package,
including all files needed to compile all Remote Admin Tools (with the
Remote Desktop option). You can use and modify the code, compile it and sell
it (as remote tools or as part of your Application) in executable form,
without paying any royalties. You also get a lifetime source code License,
with access to the Source Code Discussion forum and all upcoming source code
updates.
To add remote functionality to your Applications, you won't even have to
change a single line of your existing code. If you want, you can also create
your own Remote Administration Tools for general purpose usage.
---------------------------------
5.) This the Text I used to promote RemoteOffice as the last offer before
copyright transfer:
----------------------------
This offer is available only until March 1st 2004!
When you License the Commercial Remote Office version with full Source Code
for Delphi and C++ Builder, you gain the right to use Remote Office for
commercial purposes, modify Remote Office source code and sell it (or give
away) in executable form, without paying any royalties. The only thing you
don't get is the right to sell or give away the Remote
Office source code, or any part of the source code.
Remote Office is written in pure Delphi, uses no third-party libraries, has
cca 20.000 lines of code, is commented in English language and ready to be
compiled with Delphi 4, 5, 6, 7 and Borland C++ Builder 5, 6 (out of the
box). Using Remote Tools Source Code, you can easily add Remote
functionality to your Delphi and C++ Applications, or create your own
versions or Remote Tools. To add remote functionality to your Applications,
you won't have to change a single line of code (just "use" the unit).
After March 1st 2004, Remote Office will be available only in executable
form, without source code. All users who license Remote Office before March
1st 2004, will keep the current source code license Agreement, which gives
them the right to integrate Remote Office source code into their
applications, without paying any royalties.
----------------------------
I never charged for any updates I did to Remote Office, I did fix any bugs
users would have found and I added a number of features to Remote Office in
a very short time, making this a very good solution for remote customer
support. And if there would have been bugs left in RemoteOffice source code
after copyright transfer, I offered to fix them and give them out to all
licensed RemoteOffice users as a free update. I did make a few updates to
RemoteOffice, even after the copyright transer, but there were no bug
reports in the past year. You can download RemoteOffice executables and
documentation for free, here:
www.realthinclient.com
Best Regards,
Danijel Tkalcec
Danijel Tkalcec
I will NEVER use the word LIFETIME to promote any of my future products.
best Regards,
Danijel Tkalcec
Mike
Some vendors just disappear from all existence and you offered an
alternative. I do not see what the big deal is. I still think I got a
deal.
Later.
"Danijel Tkalcec" <dtka...@hotmail.com> wrote in message
news:428a...@newsgroups.borland.com...
Doug Olson
I too use it, and for 99 bucks - I can do what I want with it. Beats having
to put PCAnywhere on 450 computers (cost and usefulness). Do I wish that
product continued? Well, actually by not having it available, and the fact
it works as described, I now have a competitive advantage that no one else
can buy :)
I use it for two things: Remote Present!, and Remote Help! Cheaper that
PCAnywhere (I know, I said that) and WebEx, that's for sure!
Doug
"Mike" <mi...@aol.invalid> wrote in message
news:428a3cf3$1...@newsgroups.borland.com...
Scott Martin
It was his software to do what he pleases.
I could be completely wrong and Danijel could
be completely right. It just rubbed me wrong.
As mentioned, not a real issue for me. I have
what I paid for.. somewhere on a burnt CD in the bottom
of some box in my closet.
I think this thread has hit the wall, at least for me.
Regards,
Scott.
"Matthew Jones" <mat...@matthewdelme-jones.delme.com> wrote in message
news:memo.2005051...@nothanks.nothanks.co.uk...
listmember
Hi Danijel,
I'd like to, but I am probably not the best person that can
do that, not yet at least. Why dont you ask the same question
in FPC forums/NGs.
Cheers,
Ray
Matthew Jones
> I will NEVER use the word LIFETIME to promote any of my future products.
"You also get a lifetime source code License,"
To me, this is the key. I think it is perhaps possible to mis-interpret
due to the word "lifetime", but I've certainly issued licenses to people
using the term "[I] grant a perpetual license to [source]". Basically, to
me this says that there are no royalties, and the licence cannot be
terminated (subject to compliance with conditions).
Having thought about it though, I guess someone who bet their business on
this would be annoyed, but given it worked, and continued to do so, it
seems petty to rake it up.
/Matthew Jones/
Danijel Tkalcec
>
> To me, this is the key. I think it is perhaps possible to mis-interpret
> due to the word "lifetime", but I've certainly issued licenses to people
> using the term "[I] grant a perpetual license to [source]". Basically, to
> me this says that there are no royalties, and the licence cannot be
> terminated (subject to compliance with conditions).
And that is exactly what I wanted to say, but in the lack of better english,
I've used this unforgiving formulation, which seems to be following me
anywhere I go. It's almost like I sold my soul to the devil. Every time I
post something to this forum, I have to prepare for being attacked because I
sold Remote Office copyrights. I had numerous duiscussions about that on
this forum, but some people don't seem to get enough.
Best Regards,
Danijel Tkalcec
listmember
> The problem that I had is that since we bought the software under the
> previous agreement, all existing users should have been "honored"
> as registered users with the new company.
[...]
> I agree that it was against any "Gentleman's Agreement" you have with
> most companies. The manner in which the transfer was handled was not
> appreciated by many users.
I think you are overreacting a little.
Yes, it would be nice if your license were honored by the new owners,
but it never is implicit. I have seen whole product lines slashed on
him by major (MAJOR) companies with short notice.
And, what exactly does 'fifetime' mean? Lifetime of who or what;
the product, the company or the customer?
I dont see anyone voice any similar tone against, say, TurboPower
(or against the owners, or the dev team) which decided to close
shop all of a sudden. And, believe me, it was no real mercy that
they released their sources in SourceForge.
Just take a look at what sort of activity they have seen since. There
are still bugs in them, unlike the product you're referring to which
claims no bugs.
And, BTW, I did not own, or use RemoteOffice; nor do I have any
affiliation with it in anyway.
Cheers,
Ray
listmember
> Yes, it would be nice if your license were honored by the new owners,
> but it never is implicit. I have seen whole product lines slashed on
> him by major (MAJOR) companies with short notice.
Correction:
Yes, it would be nice if your license were honored by the new owners,
but it never is implicit. I have seen whole product lines slashed on
*whim* by major (MAJOR) companies with short notice.
Martyn Ayers
If you don't mind me saying, I can't help wondering whether part of
the reason for a certain lack of sympathy with your position doesn't
derive from the fact that at the time you were actively developing RO,
you went a little OTT with announcements in here almost daily IIRC.
That, and the sudden announcement of the then-forthcoming change, gave
a rather different impression than other 3rd parties manage to
achieve.
Cheers, Martyn (I have a registed copy of RO, btw)
Robert
"Scott Martin" <sa...@senderosoftware.com> wrote in message
news:428a252c$1...@newsgroups.borland.com...
> Being a registered customer myself, here is the stance I take ...
>
> The software was sold as a 1 time fee of 99.00 (as I remember) for the
> source and a _lifetime_ of free upgrades.
>
I still have lifetime support for the new and improved version of CPM. Gimme
a break. You can't take those things literally.
> After a few months, Danijel sold his software to another company. This is
> his right.
>
Of course it is.
> That said ...
>
> The problem that I had is that since we bought the software under the
> previous
> agreement, all existing users should have been "honored" as registered
users
> with the new company.
>
Obviously, that was a decision for the new company to make. They thought
otherwise.
>
> I agree that it was against any "Gentleman's Agreement" you have with most
> companies. The manner in which the transfer was handled was not
appreciated
> by many users.
>
Considering the very low cost of many of these components, and the fact that
the developers are scattered all over the world, it is amazing to me that
things work as well as they do, and that by and large developers from
Argentina to Zimbabwe value their reputation and try to do good work and
support their customers. It is a pretty good business story, IMO. I still
think it is incredible that I send an email to somebody in Russia about some
bug in a component I bought, and in a few hours I get a courteous reply with
a solution. Wish my phone company was that good.
> True I have the code, but I have too much of my own work to fix someone
> else's code. No excuse, but true.
>
Fix what? You still acting as if the product was unusable, or close to. But
even though you were one of the first users, you apparently never sent any
bug reports. So what is there to fix? What's wrong with stable software that
works? I have tons of stuff that just works, never touch it, never replace
it with new and improved nothing.
Robert
listmember
> I have just checked the www.freepascal.org site and I really like
> what I see there. Being able to write one code for multiple platforms
> is exactly what I was hoping for. Never knew this was possible with
> Pascal, I thought this is only possible with C.
Yep! Those guys are on Mac OS X, as well as 64-bit platforms already.
> I will take a closer look at FreePascal and see how much work it
> would be to port RTC components to FreePascal. If it's not too
> much incompatible with Delphi4, I will most likely port RTC
> components to FreePascal before I port them to Delphi 2005 and .NET.
> I won't be making any promisses here, since that port will most
> likely take a couple of months and there are some other things
> I planned to do before that.
Good to hear rthat :-)
Cheers,
Scott Martin
"Robert" <ngsema...@yahoo.com> wrote in message
news:428a...@newsgroups.borland.com...
>
Danijel Tkalcec
there. Being able to write one code for multiple platforms is exactly what I
was hoping for. Never knew this was possible with Pascal, I thought this is
much incompatible with Delphi4, I will most likely port RTC components to
FreePascal before I port them to Delphi 2005 and .NET. I won't be making any
promisses here, since that port will most likely take a couple of months and
there are some other things I planned to do before that.
Best Regards,
Danijel Tkalcec
"listmember" <listm...@letterboxes.org> wrote in message
news:428a4536$1...@newsgroups.borland.com...
listmember
> I still think it is incredible that I send an email to somebody
> in Russia about some bug in a component I bought, and in a few hours
> I get a courteous reply with a solution. Wish my phone company was
> that good.
:-)
Spot on.
Hell, years ago, I had an account with 'ibm.net' which they
sold off to attglobal.something.
ATTGlobal supported the old domain name for a few months and
then, voila, they dropped it.
I had numerous fun and joy with interesting people like
Network Solutions, trying to tell them that my email address
was changed without me having a say in all this... ATTGlobal
would not acknowledge --well they never replied.
How was I to remember all those places where I posted my email
address. I lost a couple of domain names...
Tell me about a serious company. I could kill anyone from
IBM --I still can.
Cheers,
Ray
Danijel Tkalcec
Delphi and Lazarus. I've ported all my high-level components to Lazarus, so
that RTC now compiles with Delphi/BCB and with Lazarus. The only thing I
will have to do now is find a good cross-platform library for basic TCP/IP,
so I can use this to implement a connection provider for RTC. If I get
lucky, then Kylix version of ICS will do the trick and RTC will be ready for
Linux :o)
Regards,
Danijel Tkalce
"listmember" <listm...@letterboxes.org> wrote in message
news:428a5ed6$1...@newsgroups.borland.com...
listmember
> Well, I have to say, I am surprised by the compatibility level
> between Delphi and Lazarus. I've ported all my high-level components
> to Lazarus, so that RTC now compiles with Delphi/BCB and with
> Lazarus. The only thing I will have to do now is find a good
> cross-platform library for basic TCP/IP, so I can use this to
> implement a connection provider for RTC. If I get lucky, then Kylix
> version of ICS will do the trick and RTC will be ready for Linux :o)
ICS is good.
I suggest you take a look at Synapse too.
http://www.ararat.cz/synapse/
Danijel Tkalcec
Windows clients and servers with them.
Next step will be to port the low-level communication stuff to Linux.
Regards,
Danijel Tkalcec
"listmember" <listm...@letterboxes.org> wrote in message
news:428b5c6c$1...@newsgroups.borland.com...
Bob Devine
Well Ted if you're _that_ unhappy I'd be delighted to purchase the licence
from you for 99 Euro plus another 50 to compensate you for emotional
distress <g> I was a bit disappointed to miss that offer from Danijel...
Cheers, Bob
Ted Nicolson
If you really want to get a license call Danijel, I'm sure he'll help you.
Emotional distress comes next :o)
Regards
Ted
"Bob Devine" <rdevine@nae_spam_blueyonder.co.uk> wrote in message
news:428b...@newsgroups.borland.com...
Danijel Tkalcec
have now is not for sale anymore. If you are really _that_ dissapointed with
RemoteOffice, I would be happy to take the license back and give you a full
refund if you are ready to remove the source code you used from RemoteOffice
in all your projects and delete any copies you may have. This is a one-time
offer, just for you, as my valued customer. Take it, or leave it.
And please, for God's sake, stop flooding this newsgroup with nonsense.
Best Regards,
Danijel Tkalcec
"Ted Nicolson" <n...@email.pls> wrote in message
news:428c...@newsgroups.borland.com...
Danijel Tkalcec
from the face of the Earth and that it isn't sold "because of bugs" ... what
Remoteoffice became after owner change is "Support-Bridge", which is
available from Acclimate Technologies at www.support-bridge.com. They still
offer source code to developers, but with different licensing terms and for
a different price.
Best Regards,
Danijel Tkalcec
Ted Nicolson
news:428c...@newsgroups.borland.com...
> I would be happy to take the license back and give you a full refund if
> you are ready to remove the source code you used from RemoteOffice in all
> your projects and delete any copies you may have. This is a one-time
> offer, just for you, as my valued customer. Take it, or leave it.
Danijel, do you really think I'm pretending the disappointed client, to get
a refund?
If that was the problem, I'd asked that when you passed RemoteOffice rights,
not now.
BTW, we never used your code in any of our projects, not because it was that
bad, just had to use another, supported solution.
End of story.
Ted
Dean Hill
> Danijel, do you really think I'm pretending the disappointed client,
> to get a refund?
> If that was the problem, I'd asked that when you passed RemoteOffice
> rights, not now.
> BTW, we never used your code in any of our projects, not because it
> was that bad, just had to use another, supported solution.
>
> End of story.
That seems a bit stranage since Sakis Papademetriou asked for an unlock
key in Feb this year. Not something someone would do if they had
"another, supported solution".
Cheers
Dean
JED
> 2.) There are quite a few Remote Office users who are more than happy
> with Remote Office and use it on a daily basis to support their
> customers. The only "problem" is that only the trouble-makers stand
> up and scream out loud, while happy customers mind their own
> bussiness. Some of those happy customers added features to their
> Remote Office version and created comemrcial products based on Remote
> Office, which you can also find in this newsgroup.
I bought it and use it quite regularly. Although I have never contacted
support (nor looked at the source code) I find it was a nice to have
item.
I would like to know if the server and client source was included with
the source distribution as I'd like to add multi monitor support one
day.
I also received an email about the change of address for support.
cheers,
Jeremy (a happy customer) <g>
Ted Nicolson
news:xn0e2g4k...@forums.borland.com...
> That seems a bit stranage since Sakis Papademetriou asked for an unlock
> key in Feb this year.
Please read the following quote from an e-mail we've got from Danijel, this
February.
>> If you are still using an old Remote Office version and want to update
>> it,
>> you can also download the last Remote Office Source Code package from
>> the RealThinClient website. It is password-protected. To unpack the file,
>> just send me a short E-Mail and I will send you the key.
The "magic" word is update. We had to get a password for the "new" package.
Of course almost nothing had changed, it was the same old code.
BTW none of our current and future projects has remoting abilities. Nowdays,
we use VNC to access our clients machines for supporting purposes.
Ted
Danijel Tkalcec
the RealThinClient package, it includes full source code for all components
and demos.
Best Regards,
Danijel Tkalcec
JED
> Full Source code for all tools was included in RemoteOffice. Same
> goes for the RealThinClient package, it includes full source code for
> all components and demos.
Thanks for that Danijel
Andrea Raimondi
> The "magic" word is update. We had to get a password for the "new" package.
> Of course almost nothing had changed, it was the same old code.
What is your problem with "old version"? If it had already changed
owner, I wonder what you were expecting?
> BTW none of our current and future projects has remoting abilities. Nowdays,
> we use VNC to access our clients machines for supporting purposes.
Then, please, do us a favour: shut-up. This thing is getting really
beyond any decence limit. Please *DO*-*STOP*-*IT*.
Thank you,
> Ted
Andrew
Danijel Tkalcec
still used versions that were extremely old (some even from 2003) and I
wanted to make sure everyone has the last RemoteOffice version (from April
2004) before I remove all RemoteOffice source code download links from my
site (so that nobody gets the idea to hack the password). And, as I
suspected, most users were happy to get the last available version.
So, it depends on each developer wether they had already downloaded the last
version available, or not. And since RemoteOffice was working, no matter
which version you used, it wasn't necessary to downloading each update,
since not everyone needed the features I added.
And as you said, you have had the last version already.
Best Regards,
Danijel Tkalcec
Ted Nicolson
news:428d8447$1...@newsgroups.borland.com...
> Then, please, do us a favour: shut-up. This thing is getting really
> beyond any decence limit. Please *DO*-*STOP*-*IT*.
If you read a few posts above, you'll see my previous post where i said "end
of story"
It was you who asked me something. And I always answer when someone asks me.
I say nothing offending about you so please "mind your own business"
Ted
Robert Baker
one of the best software values I've ever enjoyed. Danijel, you are a very
honest "stand up guy"! I admire the way that you went out of your way to
solicit opinions on the best way to transfer ownership of you product and
take care of licensing issues in advance - a rarity in this industry. I
applaud your integrity - it is right up there with the best! I sincerely
hope you keep on creating new offerings.
My best,
Robert Baker
Oliver Feins
Congratulations for the good work you are doing ! and the communication of your
progress on the newsgroup.
>> Any plan to have it all compile and run on FreePacal and Lazarus to
>> allow Linux support?
>
>I'd love to do that. I plan to port the components to .NET next year,
>but I've also thought about Kylix and other Pascal versions. The only
>things that should change are the connection provider components, which
>I have kept "under the hood", so they can be replaced without
>compromising the public interfaces.The rest of the code should be
>compatible across sysems, by using compiler directives.
Great. As far as the cross-platform library for basic TCP/IP is concerned, I
think you should investigate Synapse. Would love to read that you would achieve
full compatibility between Delphi and FreePascal/Larazus using your tool. I
followed your progress on that in the newsgroup and find that great.
I believe you should work on that before the port to .NET. That would allow
Delphi developers to target Linux easily while still developing for Windows.
Many corporations are looking for an alternative to Microsoft on the server
side now, and next the client side. Developers, I believe, want, for now, to
target Windows first, and do want to easily build a Linux version effortlessly
and let their client choose between the two offering. I believe you are close
to that with your tool.
>> Could we think of something like RemoteForms? that would output XForms
>> and link to Remote Functions written with RtcFunction ?
>
>Yes. That is what I want to do next, but that will be quite a lot of
>work, since you need a separate component for everything visual. This
>will be made available to everyone who has licensed RTC Code as add-on,
>since not everyone will want to use those components to build their
>server/client applications.
This is really great to read that. I hope you will be successful. I would like
to see that on your road map.
>> You spoke of integration with PHP. Any support to call Java methods
>> planned?
>
>I plan on making the Remote Functions work with SOAP,
>the same way they work now by using the RTC format.
>Java methods could then be called using SOAP, if they are published as a
>service.
>But, I could also write a component set for creating RTC Objects in
>Java, so you could write the same remote functions in java and call them
>using a RTC native format.
Really great. I hope you can invest some time in that. It really sounds great.
Having both Freepacal/Lazarus support and great Java integration is really the
way forward to convince companies to move to something more productive and
efficient than what is offered today on the market. Both of what you are
proposing is needed and very interesting.
Please, continue you great work and keep us informed !
Oliver
BTW, I saw the great work you are doing on your new web site.