Tim,

The latest build  has just introduced a new component, TPage which is likely to offer a path to use what we need with no risk for EWB at all.

Cheers,
Leslie

Steve,

<< IMHO, I think this would be a bad idea.  I believe Tim should stick to his vision for EWB rather than start introducing compromises that could very likely cause issues later on. For some things, I have found that EWB is not yet at the stage where I can use it, so I'm using other tools in the meantime.  I'll be redeveloping them in EWB later when the time is right.>>

Once you invest in an other product and build lots of code on it, it can be difficult to change direction later. A few years back I really wanted to change our main dbengine to EDB. I have spent lots of time here in the forums getting to know the product. But there was a show stopper Tim had no solution for, so I had to move on, and it is very unlikely that I will turn back. I still rate Tim and his work, hence I am coming back to give it a try with EWB.  

Cheers,
Leslie

Hi Leslie,

<< Once you invest in an other product and build lots of code on it, it can be difficult to change direction later. A few years back I really wanted to change our main dbengine to EDB. I have spent lots of time here in the forums getting to know the product. But there was a show stopper Tim had no solution for, so I had to move on, and it is very unlikely that I will turn back. I still rate Tim and his work, hence I am coming back to give it a try with EWB.   >>

I guess it depends on what type of work you do and how versatile you are.  I do work for a number of large clients and develop applications for Oracle, MS SQL Server, MySQL, DBISAM and ElevateDB databases.  For web stuff, I hand-code in HTML, CSS, PHP, ISAPI, Javascript, using various frameworks and tools.

Steve,

I guess we all work with whatever we have to. But when I have full control over a project it is efficient to have well tested and known set of  components for every area.  I wanted  EDB to be the "default" engine for us.

Cheers,
Leslie

Leslie wrote:
> It can also be a sign of soemone not native English being tired.

I'll archive that as the truth.

Leslie,

<< The latest build  has just introduced a new component, TPage which is
likely to offer a path to use what we need with no risk for EWB at all.
>>

Yes and no.  You can easily display any HTML document, including those with
3rd party frameworks, etc. in them.  However, I wouldn't recommend this for
trying to get at things like Google Maps for one simple reason - there's no
way for your code to interface with the JS code contained within HTML
document.  You *can* interface with the document elements, etc. within the
HTML page (within the same domain), but that's it.  JS doesn't have the
concept of exports or libraries, in the traditional sense.  Therefore, you
have to have a declared external interface in your Object Pascal code for
the JS code.

--
Tim Young
Elevate Software
www.elevatesoft.com

Leslie,

<< Of course you cannot make me use a product I would not want to, but it is
exactely the opposite,
I  would really like to use it. In fact I am willing to go the extra
mile to be able to do it. I am just trying to make a point that it might be
possible to archive your long term goals with the product while giving the
developers a chance to archive their short term goals with it too. It seems
a suitable solution for this stage of EWB and  a win-win to me.  It is much
less work for us to replace the external stuff as the missing peaces from
the framework become available than redo the whole thing.

I am truely trying to understand your perspective about this. It might be a
good thing if you could wear our shoes just a little. >>

Well, you're saying that you would like to use it, but...   If the "but"
means that the product won't work for you, then that's just the situation as
it exists.  There's no magical solution that I can do that will bridge that
gap in a short amount of time, and you're talking in extremely vague and
general terms that amount to "just do it".  What exactly do you propose that
I *do*, exactly ?  You're talking about things like Google maps, for
example.  One can work with Google Maps in EWB, but someone has to define an
Object Pascal interface to the Google Maps JS code so that the compiler
knows how to handle such calls to the JS code (see the WebDOM unit for how
this is done).  In addition, a custom control is also needed that can
dynamically load the proper API scripts from Google (not hard, very simple,
in fact) and exposes the Google Maps functionality.  This type of
functionality will eventually make it into the product, but saying "just do
it" doesn't really amount to much, since the work still has to be done by
me.  I don't have a group of developers that I can just assign to the task,
and I'm still trying to get version 1 of the product out the door.  If I
keep stopping in order to satisfy the needs of every customer that wants a
particular control, etc., then I'll never get it done.  The framework will
develop as fast as I can develop it.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Dominique Willems" wrote:

Leslie wrote:
> It can also be a sign of soemone not native English being tired.

I'll archive that as the truth.

:D
Cheers,
Leslie

"Tim Young [Elevate Software]" wrote:

Leslie,

<< The latest build  has just introduced a new component, TPage which is
likely to offer a path to use what we need with no risk for EWB at all.
>>

Yes and no.  You can easily display any HTML document, including those with
3rd party frameworks, etc. in them.  However, I wouldn't recommend this for
trying to get at things like Google Maps for one simple reason - there's no
way for your code to interface with the JS code contained within HTML
document.  You *can* interface with the document elements, etc. within the
HTML page (within the same domain), but that's it.  JS doesn't have the
concept of exports or libraries, in the traditional sense.  Therefore, you
have to have a declared external interface in your Object Pascal code for
the JS code.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

There is a way this limitation can probably be worked around with acceptable performance. Both pages can communicate with  the server which can relay messages from one to the other. It may sound  strange at first to use RPC but in this case may be the only solution.
Cheers,
Leslie

Tim,

<<Well, you're saying that you would like to use it, but...   If the "but"
means that the product won't work for you, then that's just the situation as
it exists.  There's no magical solution that I can do that will bridge that
gap in a short amount of time, and you're talking in extremely vague and
general terms that amount to "just do it".  What exactly do you propose that
I *do*, exactly ?  You're talking about things like Google maps, for
example.  One can work with Google Maps in EWB, but someone has to define an
Object Pascal interface to the Google Maps JS code so that the compiler
knows how to handle such calls to the JS code (see the WebDOM unit for how
this is done).  In addition, a custom control is also needed that can
dynamically load the proper API scripts from Google (not hard, very simple,
in fact) and exposes the Google Maps functionality.  This type of
functionality will eventually make it into the product, but saying "just do
it" doesn't really amount to much, since the work still has to be done by
me.  I don't have a group of developers that I can just assign to the task,
and I'm still trying to get version 1 of the product out the door.  If I
keep stopping in order to satisfy the needs of every customer that wants a
particular control, etc., then I'll never get it done.  The framework will
develop as fast as I can develop it.>>

I think I have  fairly good idea that supporting your engines while creating something like EWB from scratch is lots of work. I can definitely appreciate the magnitude of the work creating EWB require in itself. We have different perspectives about the same thing.  I can tell you that for me it is very useful to learn yours. When I am trying  to bring something to your attention it is because even with all your talent  and experience you are still limited and letting you know what we need can shape your thoughts about how to go on.  I am always trying to find the common ground. If it does not work out I accept it and move on. Please always consider that my English is may not sophisticated enough to express myself the way I mean it. If I seem occasionally pushy it is probably because it is an important issue which can be a show stopper and I would really like to find a solution.
Cheers,
Leslie