Home › Developer Forums › Echo 3.x Platform (Echo3) › Help & Support (3.x)

Porting from Echo2-Echo3

aze's picture
Wed, 01/09/2008 - 23:39 — aze

Hello all,

I am trying to port our echo2 application to echo3. the package name replace was easy. The main problem I am having is because of Echopointng components.

In our echo2-based application we used the echopointng components everywhere like Tree, DefaultMutableTreeNode,JavaScripteval etc.

Now as far as I know there is no ported version of echopointng in svc or in echo3go available. is the Porting of Echopointng in progress? can i get already ported components from cvs?

Or should I start converting components back to basic Echo3 ....

Please advice. thanks a lot in advance.

aze

‹ Client-Side JavaScript Components and Rendering Peers Missing something about color ? ›
Wed, 01/09/2008 - 23:50 — tliebeck
tliebeck's picture

There is a Tree in Echo3 Extras now.

For JavaScript Eval, I'd recommend writing a command. No docs for writing these yet in Echo3, but you'd be in decent shape if you studied / cut-and-pasted from the Echo3 source of the BrowserOpenWindowCommand stuff. (There's a Command object, CommandPeer, client-side JS object, and entry in the SynchronizePeerBindings.properties file.)

As I understand it there will be an EchoPoint 3, but I do not know the status.

Thu, 01/10/2008 - 02:10 — rainsill

epng3 port is just beginning. I'll send out a full announcement soon.

Tod Liebeck wrote:

There is a Tree in Echo3 Extras now.

For JavaScript Eval, I'd recommend writing a command. No docs for writing these yet in Echo3, but you'd be in decent shape if you studied / cut-and-pasted from the Echo3 source of the BrowserOpenWindowCommand stuff. (There's a Command object, CommandPeer, client-side JS object, and entry in the SynchronizePeerBindings.properties file.)

As I understand it there will be an EchoPoint 3, but I do not know the status.

Thu, 01/10/2008 - 02:16 — aze
aze's picture

rainsill wrote:

epng3 port is just beginning. I'll send out a full announcement soon.

Hi,
great,
are you planning to port all components of epng to epng3 ? what do you think how long could it take?

Mon, 01/14/2008 - 02:27 — edge

Aze,
Great to hear that EchopontNG is being ported. We have a very large
Echo2 application that makes extensive use of EPNG and which we want to port to 3.0. We'd be happy to give some help especially in testing etc.

Edge

Mon, 01/14/2008 - 04:31 — spider

rainsill wrote:

epng3 port is just beginning. I'll send out a full announcement soon.

Great, can't wait for it... ;)

Anyway, I wonder if the policy of duplicated widgets (Label/LabelEx, Button/ButtonEx) will be continued in version 3. In my opinion now would be a good moment to actually merge them, because for the end user there is no case having the components duplicated.

I'm aware that the reasons therefor were on the developer side (reducing the to risk for breaking the base implementation, less ppl need granted SVN commit access to the core), but with a good coordination effort, shouldn't it be possbile to overcome these issues?

cheers, Chris

Tue, 01/15/2008 - 03:49 — Grolubao

rainsill wrote:

epng3 port is just beginning. I'll send out a full announcement soon.

Great hearing that! Thanks for all the work.

For us, we don't have any problem having the duplicate classes (e.g Label, LabelEx) but if it could be merged, the better. I'm just afraid that by porting with the merge and by refactoring each usage of the old EchopoingNG classes, it could origin a lot of problems...

Tue, 01/15/2008 - 08:46 — rainsill

See Announcement: [url=http://forum.nextapp.com/forum]http://forum.nextapp.com/forum]