On 10/31/06, George Birbilis <[EMAIL PROTECTED]> wrote:
* For example apps deployable via both offline media and network URLs or
webpages, that can check for updates automatically or manually and
autoupdate from the web,

You don´t need .NET for that. Just write a component that
automatically updates an app. Send the component to Lazarus Code and
Component repository on a nice license such as Modifyed LGPL and
everyone will be able to use it.

running both offline as desktop apps and online
from inside webpages, all the stuff that OneClick deployment for example
does (without the fuss that one would have to go into to do it with other
platforms).

We don´t need .NET for that. We are planning to write a IntraWeb-like
widgetset for Lazarus.

And will be even better then IntraWeb as you won´t need to add
different component, just recompile the existing app for web-mode. It
should run on all platforms supported by Apache or LNet, depending on
the implementation.

* Managed plugins for applications (say for the recent versions of Office
for example)

Does office allow non-managed plugins? If not, then you reached
something you cannot do with Free Pascal today.

* Any commercial app for .NET in Object Pascal without buying an IDE (Chorme
and Borland tools aren't free for commercial use) or moving to other
language

Here you reach almost a contradiction, because to add .NET support for
Free Pascal you will need to invest on it anyway. Maybe not money, but
at least lot´s of time, so it may be much cheaper to buy Chrome and
Delphi.NET (unless you need 100s of copies).

> I think you can use Delphi IDE to write a
> DLL that exports a procedural interface to whatever you want to do.

What do you mean with this? Do you have an example?

No, I only read on borland newsgroups that this is possible.

--
Felipe Monteiro de Carvalho

_________________________________________________________________
    To unsubscribe: mail [EMAIL PROTECTED] with
               "unsubscribe" as the Subject
  archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to