Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » RWT/RAP VerifyEvent support and ClientScripting(Which way to go with keyboard events in RWT/RAP)
RWT/RAP VerifyEvent support and ClientScripting [message #990487] Wed, 12 December 2012 16:42 Go to next message
John Gymer is currently offline John GymerFriend
Messages: 191
Registered: November 2012
Location: UK
Senior Member
RAP 1.5 noted a difference between SWT and RWT as follows:

Quote:

Limitations in Verify and Modify Events: ModifyEvent, VerifyEvent
Modify and Verify events are not fired instantaneously, but with a small delay, possibly combining a number of changes into one event. Also, the values of the VerifyEvent fields text, start and end currently always report the entire text to have changed. The ClientScripting was created specifically to provide an alternative.


Firstly, VerifyEvent also does not populate event.character either, which is not such a big deal, but doesn't appear to be documented as a difference.

Incidentally, I'm using RAP 2.0 M3 rather than 1.5, but cannot see this as a documented difference.

So, the question, which has most likely been asked somewhere already, but I couldn't see a complete answer, is how to handle VerifyEvent logic in RWT/RAP and ultimately also Tabris, which I assume works the same way as RAP.

Performance of VerifyEvent is not great with RAP because of the round-trip nature of the event-browser-appserver-browser. I have read a little about ClientScripting, but does this technology have a future? It does mean that I can no longer single-source my application for SWT and RAP, but I can probably live with that if the solution is slick enough.

Is ClientScripting the way to go? What is its future? Is it supported in Tabris too? Or is there a sensible, more generic alternative?

I'd love to see an example of ClientScripting, perhaps implementing something simple like an upper-case translator for an entry field... anyone got a snippet they can share?

Here's the SWT equivalent that works well as a local SWT application:

VerifyListener validateUppercaseListener = new VerifyListener() {
  public void verifyText(VerifyEvent event) {
      event.doit = false; // assume don't allow char input
      char myChar = event.character;
      String myTxt = String.valueOf(myChar);
      if (Character.isUpperCase(myChar)) event.doit = true; // allow 0-9
      else if (Character.isLowerCase(myChar)) {
        event.text = event.text.toUpperCase();
        event.doit = true; // allow 0-9
    }
    if (myChar == '\b') event.doit = true; // allow backspace
    if (myTxt.codePointAt(0) == 127) event.doit = true; // allow delete
    if (myTxt.codePointAt(0) == 0) event.doit = true; // allow changes via code
  }
};

applied to a Text widget with:
myTxtWidget.addVerifyListener(validateUppercaseListener);


I'm very excited about all these technologies at the moment, but don't want to end up down the wrong path that will cause me grief later on.

Useful comments and help very much appreciated,
John


---
Just because you can doesn't mean you should
Re: RWT/RAP VerifyEvent support and ClientScripting [message #990771 is a reply to message #990487] Fri, 14 December 2012 08:44 Go to previous messageGo to next message
Ralf Sternberg is currently offline Ralf SternbergFriend
Messages: 1291
Registered: July 2009
Senior Member

Hi John,

We support the SWT Verify listener to improve the migration of existing
SWT code to RAP. But using server-side validation in RAP comes at the
price of higher network traffic (since we have to call the server for
every modification) and results appearing delayed by the network. There
aren't many places where the latency is a problem, but the Verify
listener is one of them. This is one of the reasons we started the
client scripting effort.

> Firstly, VerifyEvent also does not populate event.character either,
> which is not such a big deal, but doesn't appear to be documented as a
> difference.
>
> Incidentally, I'm using RAP 2.0 M3 rather than 1.5, but cannot see this
> as a documented difference.

Thanks for the hint. We'll add this detail to the documentation.

> So, the question, which has most likely been asked somewhere already,
> but I couldn't see a complete answer, is how to handle VerifyEvent logic
> in RWT/RAP and ultimately also Tabris, which I assume works the same way
> as RAP.

I would recommend to do the validation on the client using client
scripting, as this provides instant feedback and a snappier user
experience. Most of the time, the validation logic will be simple enough
to fit in a JavaScript snippet. Optionally, you can still trigger some
advanced validation on the server on focus-out.

> Performance of VerifyEvent is not great with RAP because of the
> round-trip nature of the event-browser-appserver-browser. I have read a
> little about ClientScripting, but does this technology have a future? It
> does mean that I can no longer single-source my application for SWT and
> RAP, but I can probably live with that if the solution is slick enough.

We consider client scripting a key feature and plan to extend the
support to more widgets and make more properties available to the client
listeners. We might even merge it into the core in a future release.

The way it is designed does not interfere with single sourcing. There
will always be some exceptions when single-sourcing an entire
application, some parts that need to be implemented a bit differently
for web and desktop. These parts can be separated from the shared code,
kept in separate bundles or fragments. For example, you can implement a
shared method that adds a validator to a given Text field. In SWT, this
method would add a VerifyListener, in RAP, it would attach a Client
listener.

> Is ClientScripting the way to go? What is its future? Is it supported in
> Tabris too? Or is there a sensible, more generic alternative?

Tabris 1.0 will not support client scripting, but I know it's on their
plan already and will be added soon after the release.

> I'd love to see an example of ClientScripting, perhaps implementing
> something simple like an upper-case translator for an entry field...
> anyone got a snippet they can share?

The clientscripting repository contains an additional page to our
examples demo, called "Input Validation" [1]. You find the code in the
bundle "org.eclipse.rap.demo.clientscripting" [2]. There is also an
auto-upper-case example.

> I'm very excited about all these technologies at the moment, but don't
> want to end up down the wrong path that will cause me grief later on.

So are we ;-)

Best regards,
Ralf


[1] http://rap.eclipsesource.com/rapdemo/examples#validation

[2]
http://git.eclipse.org/c/rap/incubator/org.eclipse.rap.incubator.clientscripting.git/tree/bundles/org.eclipse.rap.demo.clientscripting


--
Ralf Sternberg

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Re: RWT/RAP VerifyEvent support and ClientScripting [message #990784 is a reply to message #990771] Fri, 14 December 2012 09:24 Go to previous messageGo to next message
John Gymer is currently offline John GymerFriend
Messages: 191
Registered: November 2012
Location: UK
Senior Member
Excellent response Ralf - all the right answers!

Cool


---
Just because you can doesn't mean you should
Re: RWT/RAP VerifyEvent support and ClientScripting [message #990816 is a reply to message #990784] Fri, 14 December 2012 10:50 Go to previous messageGo to next message
John Gymer is currently offline John GymerFriend
Messages: 191
Registered: November 2012
Location: UK
Senior Member
Trying to use ClientScripting for the first time, have downloaded latest from git but getting project setup problems after importing into Eclipse 4.2.1 where my existing RAP projects are (RAP 2.0 M3, NO incremental fixes/commits applied).

Lots of setup issues, which I'm wondering whether I need to get a later version of RAP (nightly build)? I'd rather not keep updating in this way, as I am in experimental mode with my app so would like something at least semi-stable.

Here's one of the many errors:
In imported project 'org.eclipse.rap.clientscripting' within src member 'ClientScripingRenderer.java' I get an unresolved error on import of 'org.eclipse.rap.rwt.service.ApplicationContext'.
Indeed this is not within 'org.eclipse.rap.rwt.service' (part of the RAP 2.0 M3 'org.eclipse.rap.rwt_2.0.0.20121112-1148.jar).

Similar issues with:
'org.eclipse.rap.rwt.client.server.JavaScriptLoader' (clientscripting project)
'org.eclipse.rap.rwt.service.ResourceLoader' (clientscripting project)
'org.eclipse.rap.rwt.application.EntryPoint' (clientscripting.demo project)
'org.eclipse.rap.rwt.jstest.TestContribution' (clientscripting.jstest project)
'org.mockito.<various>' (clientscripting.test project)
'org.eclipse.rap.rwt.client.server.JavaScriptLoader' (clientscripting.test project)
'org.eclipse.rap.rwt.service.ResourceLoader' (clientscripting.test project)
'org.eclipse.rap.rwt.service.ResourceManager' (clientscripting.test project)

I realise that this is fairly basic project setup stuff, but am worried to go changing configuration too much in fear of breaking my own project in this workspace.

Have some of the base classes been renamed perhaps, since RAP 2.0 M3?

Is there information on what each of these clientscripting projects actually does, how it is used, and what its dependencies are? There doesn't seem to be a quick 'getting started' guide or simple downloadable project that exhibits it. Ok, I know it is still in incubator, but would like to get started with the minimum of fuss!

Please bear with me in getting this configured - I'm still new to RAP - but I'm sure I won't be the only one needing a more detailed step-by-step for ClientScripting.

Many thanks, John


---
Just because you can doesn't mean you should
Re: RWT/RAP VerifyEvent support and ClientScripting [message #990826 is a reply to message #990816] Fri, 14 December 2012 11:02 Go to previous messageGo to next message
Ivan Furnadjiev is currently offline Ivan FurnadjievFriend
Messages: 1856
Registered: July 2009
Senior Member
Hi John,
Yes... we are in a process of renaming/cleanup some of the old
classes/API. In order to run ClientScripting from git master you need
RAP Runtime from git master as well.
Best,
Ivan

On 12/14/2012 12:50 PM, John Gymer wrote:
> Trying to use ClientScripting for the first time, have downloaded
> latest from git but getting project setup problems after importing
> into Eclipse 4.2.1 where my existing RAP projects are (RAP 2.0 M3, NO
> incremental fixes/commits applied).
>
> Lots of setup issues, which I'm wondering whether I need to get a
> later version of RAP (nightly build)? I'd rather not keep updating in
> this way, as I am in experimental mode with my app so would like
> something at least semi-stable.
>
> Here's one of the many errors:
> In imported project 'org.eclipse.rap.clientscripting' within src
> member 'ClientScripingRenderer.java' I get an unresolved error on
> import of 'org.eclipse.rap.rwt.service.ApplicationContext'.
> Indeed this is not within 'org.eclipse.rap.rwt.service' (part of the
> RAP 2.0 M3 'org.eclipse.rap.rwt_2.0.0.20121112-1148.jar).
>
> Similar issues with:
> 'org.eclipse.rap.rwt.client.server.JavaScriptLoader' (clientscripting
> project)
> 'org.eclipse.rap.rwt.service.ResourceLoader' (clientscripting project)
> 'org.eclipse.rap.rwt.application.EntryPoint' (clientscripting.demo
> project)
> 'org.eclipse.rap.rwt.jstest.TestContribution' (clientscripting.jstest
> project)
> 'org.mockito.<various>' (clientscripting.test project)
> 'org.eclipse.rap.rwt.client.server.JavaScriptLoader'
> (clientscripting.test project)
> 'org.eclipse.rap.rwt.service.ResourceLoader' (clientscripting.test
> project)
> 'org.eclipse.rap.rwt.service.ResourceManager' (clientscripting.test
> project)
>
> I realise that this is fairly basic project setup stuff, but am
> worried to go changing configuration too much in fear of breaking my
> own project in this workspace.
>
> Have some of the base classes been renamed perhaps, since RAP 2.0 M3?
>
> Is there information on what each of these clientscripting projects
> actually does, how it is used, and what its dependencies are? There
> doesn't seem to be a quick 'getting started' guide or simple
> downloadable project that exhibits it. Ok, I know it is still in
> incubator, but would like to get started with the minimum of fuss!
>
> Please bear with me in getting this configured - I'm still new to RAP
> - but I'm sure I won't be the only one needing a more detailed
> step-by-step for ClientScripting.
>
> Many thanks, John
>

--
Ivan Furnadjiev

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Re: RWT/RAP VerifyEvent support and ClientScripting [message #990894 is a reply to message #990826] Fri, 14 December 2012 17:12 Go to previous messageGo to next message
John Gymer is currently offline John GymerFriend
Messages: 191
Registered: November 2012
Location: UK
Senior Member
Hello again, if you are in the process of renaming and cleaning things up, does it mean that the nightly build (13th Dec) is potentially bust?

I've installed RAP 2.0 M3 nightly from 13th Dec and my own application no longer starts up under RAP (SWT and RWT still work ok). The rapdemo project still works ok under RAP though, but I'm struggling to see what I've done wrong.

After applying the nightly build I had to change my IEntryPoint Class to reference EntryPoint instead, which I presume was one of the recent changes you made? Otherwise, no changes, and no other errors reported.

Sypmtoms are that when I launch the RAP app from within Eclipse (4.2.1), OSGi starts ok, and the OSGi console reports that my bundle is ACTIVE. However, the browser starts up and I just get a 404, as if the Application was never registered. Looks like a problem with the Application Extension, but I cannot see what.

Here's a simple bit of code for the Application implementation:
package rapide;

import org.eclipse.equinox.app.IApplication;
import org.eclipse.equinox.app.IApplicationContext;

public class RapideApplication implements IApplication {
  public Object start( IApplicationContext context ) throws Exception {
	  
	  System.out.println("Starting rapide Application runtime");

	  RapideEntryPoint rep = new RapideEntryPoint();
	  rep.fromRAP = true;
	  rep.setTheme = true;
	  rep.createUI();

	  System.out.println("Ending rapide Application runtime");
	  
	  return new Integer( 0 );
  }

  public void stop() {
  }
  
}


I never see 'Starting rapide Application runtime'.

Usual stuff inside EntryPoint Class, except changed from IEntryPoint to EntryPoint:

package rapide;

import org.eclipse.rap.rwt.application.EntryPoint;

public class RapideEntryPoint implements EntryPoint {

	@Override
	public int createUI() {
...


plugin.xml looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.4"?>
<plugin>
   <extension
         id="rapideApp"
         name="rapideApp"
         point="org.eclipse.core.runtime.applications">
      <application
            cardinality="singleton-global"
            thread="main"
            visible="true">
         <run
               class="rapide.RapideApplication">
            <parameter
                  name="path"
                  value="/rapide">
            </parameter>
            <parameter
                  name="brandingId"
                  value="aqua">
            </parameter>
         </run>
      </application>
   </extension>
   <extension
         id="aqua"
         name="aqua"
         point="org.eclipse.rap.ui.themes">
      <theme
            file="src/css/aqua.css"
            id="org.eclipse.rap.rwt.theme.Default"
            name="aqua">
      </theme>
   </extension>
   <extension
         point="org.eclipse.rap.ui.branding">
      <branding
            id="mybrand"
            themeId="aqua">
      </branding>
   </extension>


</plugin>


As I said, it works ok as RWT which runs from a web.xml looking like this:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
  version="2.4">

  <context-param>
    <param-name>org.eclipse.rap.applicationConfiguration</param-name>
    <param-value>rapide.RapideConfiguration</param-value>
  </context-param>

  <listener>
    <listener-class>org.eclipse.rap.rwt.engine.RWTServletContextListener</listener-class>
  </listener>

  <servlet>
    <servlet-name>rwtServlet</servlet-name>
    <servlet-class>org.eclipse.rap.rwt.engine.RWTServlet</servlet-class>
  </servlet>

  <servlet-mapping>
    <servlet-name>rwtServlet</servlet-name>
    <url-pattern>/rapide</url-pattern>
  </servlet-mapping>
  
</web-app>


I've probably missed something simple, but would appreciate any hints as to what I did wrong, or if there was a problem with the nightly build?

Thanks, John


---
Just because you can doesn't mean you should
Re: RWT/RAP VerifyEvent support and ClientScripting [message #990899 is a reply to message #990894] Fri, 14 December 2012 17:42 Go to previous messageGo to next message
Ivan Furnadjiev is currently offline Ivan FurnadjievFriend
Messages: 1856
Registered: July 2009
Senior Member
John,
we changed the way (again) the IApplications are registered and used in
RAP. See bug:
394805: "The parameter 'path' must not be null" when running RAP with
Workbench
https://bugs.eclipse.org/bugs/show_bug.cgi?id=394805
To use your IApplication you must add an entrypoint extension and point
the "applicationId" parameter to your IApplication id.
You could use RAP Workbench Demo as an example (org.eclipse.rap.demo).
HTH,
Ivan

On 12/14/2012 7:12 PM, John Gymer wrote:
> Hello again, if you are in the process of renaming and cleaning things
> up, does it mean that the nightly build (13th Dec) is potentially bust?
>
> I've installed RAP 2.0 M3 nightly from 13th Dec and my own application
> no longer starts up under RAP (SWT and RWT still work ok). The rapdemo
> project still works ok under RAP though, but I'm struggling to see
> what I've done wrong.
>
> After applying the nightly build I had to change my IEntryPoint Class
> to reference EntryPoint instead, which I presume was one of the recent
> changes you made? Otherwise, no changes, and no other errors reported.
>
> Sypmtoms are that when I launch the RAP app from within Eclipse
> (4.2.1), OSGi starts ok, and the OSGi console reports that my bundle
> is ACTIVE. However, the browser starts up and I just get a 404, as if
> the Application was never registered. Looks like a problem with the
> Application Extension, but I cannot see what.
>
> Here's a simple bit of code for the Application implementation:
>
> package rapide;
>
> import org.eclipse.equinox.app.IApplication;
> import org.eclipse.equinox.app.IApplicationContext;
>
> public class RapideApplication implements IApplication {
> public Object start( IApplicationContext context ) throws Exception {
> System.out.println("Starting rapide Application runtime");
>
> RapideEntryPoint rep = new RapideEntryPoint();
> rep.fromRAP = true;
> rep.setTheme = true;
> rep.createUI();
>
> System.out.println("Ending rapide Application runtime");
> return new Integer( 0 );
> }
>
> public void stop() {
> }
>
> }
>
>
> I never see 'Starting rapide Application runtime'.
>
> Usual stuff inside EntryPoint Class, except changed from IEntryPoint
> to EntryPoint:
>
>
> package rapide;
>
> import org.eclipse.rap.rwt.application.EntryPoint;
>
> public class RapideEntryPoint implements EntryPoint {
>
> @Override
> public int createUI() {
> ..
>
>
> plugin.xml looks like this:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <?eclipse version="3.4"?>
> <plugin>
> <extension
> id="rapideApp"
> name="rapideApp"
> point="org.eclipse.core.runtime.applications">
> <application
> cardinality="singleton-global"
> thread="main"
> visible="true">
> <run
> class="rapide.RapideApplication">
> <parameter
> name="path"
> value="/rapide">
> </parameter>
> <parameter
> name="brandingId"
> value="aqua">
> </parameter>
> </run>
> </application>
> </extension>
> <extension
> id="aqua"
> name="aqua"
> point="org.eclipse.rap.ui.themes">
> <theme
> file="src/css/aqua.css"
> id="org.eclipse.rap.rwt.theme.Default"
> name="aqua">
> </theme>
> </extension>
> <extension
> point="org.eclipse.rap.ui.branding">
> <branding
> id="mybrand"
> themeId="aqua">
> </branding>
> </extension>
>
>
> </plugin>
>
>
> As I said, it works ok as RWT which runs from a web.xml looking like
> this:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
> version="2.4">
>
> <context-param>
> <param-name>org.eclipse.rap.applicationConfiguration</param-name>
> <param-value>rapide.RapideConfiguration</param-value>
> </context-param>
>
> <listener>
> <listener-class>org.eclipse.rap.rwt.engine.RWTServletContextListener</listener-class>
> </listener>
>
> <servlet>
> <servlet-name>rwtServlet</servlet-name>
> <servlet-class>org.eclipse.rap.rwt.engine.RWTServlet</servlet-class>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>rwtServlet</servlet-name>
> <url-pattern>/rapide</url-pattern>
> </servlet-mapping>
>
> </web-app>
>
>
> I've probably missed something simple, but would appreciate any hints
> as to what I did wrong, or if there was a problem with the nightly build?
>
> Thanks, John
>

--
Ivan Furnadjiev

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Re: RWT/RAP VerifyEvent support and ClientScripting [message #991069 is a reply to message #990899] Mon, 17 December 2012 09:34 Go to previous messageGo to next message
John Gymer is currently offline John GymerFriend
Messages: 191
Registered: November 2012
Location: UK
Senior Member
Hi Ivan,

Thanks, this pointed me in the right direction, and I have added an Entry Point Extension specifically for RAP (as opposed to my RWT Extension), and this now works perfectly...

<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.4"?>
<plugin>
   <extension
         id="rapideApp"
         name="rapideApp"
         point="org.eclipse.core.runtime.applications">
      <application
            cardinality="singleton-global"
            thread="main"
            visible="true">
         <run
               class="rapide.RapideApplication">
            <parameter
                  name="path"
                  value="/rapide">
            </parameter>
            <parameter
                  name="brandingId"
                  value="aqua">
            </parameter>
         </run>
      </application>
   </extension>
   <extension
         id="aqua"
         name="aqua"
         point="org.eclipse.rap.ui.themes">
      <theme
            file="src/css/aqua.css"
            id="org.eclipse.rap.rwt.theme.Default"
            name="aqua">
      </theme>
   </extension>
   <extension
         point="org.eclipse.rap.ui.branding">
      <branding
            id="mybrand"
            themeId="org.eclipse.rap.rwt.theme.Default">
      </branding>
   </extension>
   <extension
         point="org.eclipse.rap.ui.entrypoint">
      <entrypoint
            applicationId="iet.co.uk.rapide.rapideApp"
            brandingId="mybrand"
            class="rapide.RapideEntryPointRAP"
            id="rapide"
            path="/rapide">
      </entrypoint>
   </extension>


</plugin>


Back to testing ClientScripting again now... Rolling Eyes

Thanks, John


---
Just because you can doesn't mean you should
Re: RWT/RAP VerifyEvent support and ClientScripting [message #991096 is a reply to message #991069] Mon, 17 December 2012 10:54 Go to previous messageGo to next message
Ivan Furnadjiev is currently offline Ivan FurnadjievFriend
Messages: 1856
Registered: July 2009
Senior Member
Hi John,
you don't need "path" and "brandingId" parameters in your
"org.eclipse.core.runtime.applications" extension point anymore.
Best,
Ivan

On 12/17/2012 11:34 AM, John Gymer wrote:
> Hi Ivan,
>
> Thanks, this pointed me in the right direction, and I have added an
> Entry Point Extension specifically for RAP (as opposed to my RWT
> Extension), and this now works perfectly...
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <?eclipse version="3.4"?>
> <plugin>
> <extension
> id="rapideApp"
> name="rapideApp"
> point="org.eclipse.core.runtime.applications">
> <application
> cardinality="singleton-global"
> thread="main"
> visible="true">
> <run
> class="rapide.RapideApplication">
> <parameter
> name="path"
> value="/rapide">
> </parameter>
> <parameter
> name="brandingId"
> value="aqua">
> </parameter>
> </run>
> </application>
> </extension>
> <extension
> id="aqua"
> name="aqua"
> point="org.eclipse.rap.ui.themes">
> <theme
> file="src/css/aqua.css"
> id="org.eclipse.rap.rwt.theme.Default"
> name="aqua">
> </theme>
> </extension>
> <extension
> point="org.eclipse.rap.ui.branding">
> <branding
> id="mybrand"
> themeId="org.eclipse.rap.rwt.theme.Default">
> </branding>
> </extension>
> <extension
> point="org.eclipse.rap.ui.entrypoint">
> <entrypoint
> applicationId="iet.co.uk.rapide.rapideApp"
> brandingId="mybrand"
> class="rapide.RapideEntryPointRAP"
> id="rapide"
> path="/rapide">
> </entrypoint>
> </extension>
>
>
> </plugin>
>
>
> Back to testing ClientScripting again now... :roll:
> Thanks, John
>

--
Ivan Furnadjiev

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Re: RWT/RAP VerifyEvent support and ClientScripting [message #991104 is a reply to message #991096] Mon, 17 December 2012 11:24 Go to previous messageGo to next message
John Gymer is currently offline John GymerFriend
Messages: 191
Registered: November 2012
Location: UK
Senior Member
Thanks Ivan, have removed those attributes to simplify it!

Ok, so ClientScripting setup next, which I'm struggling with, related to versions of bundles I think, although everything appears to be good. This is with ClientScripting from git on 14th Dec and RAP 2.0 M3 Nightly from 13th, so pretty much in sync.

I've imported 2 projects from the ClientScripting Zip (clientscripting and clientscripting.demo), which appear to be the only ones actually required for this test with RAP. No project errors, but if I try to run the RAP demo for ClientScripting, it complains with the following unresolved dependencies:

index.php/fa/12727/0/

The Dependencies look ok to my eye:

index.php/fa/12728/0/

Can you help point me at the piece that is versioned incorrectly?

Thanks, John


---
Just because you can doesn't mean you should
Re: RWT/RAP VerifyEvent support and ClientScripting [message #991109 is a reply to message #991104] Mon, 17 December 2012 11:50 Go to previous message
John Gymer is currently offline John GymerFriend
Messages: 191
Registered: November 2012
Location: UK
Senior Member
Actually, it would have been interesting to get the demo working... but the good news is that I have integrated the UpperCase example logic into my own project, and it works perfectly, first time, so no specific need to get the demo working now!

So simple too - literally add the line:

CustomBehaviors.addUpperCaseBehavior(widget.txt);


...and include the clientscripting Bundle in the RAP list of requirements.
Much nicer.
I've got the code branching for RAP to ClientScripting and SWT/RWT to a standard VerifyListener. Nice!

Thanks... time to play some more...
Cool


---
Just because you can doesn't mean you should
Previous Topic:How to cancel Display.timerExec for RWT? (tried timerExec(-1, runnable))
Next Topic:Application beforeDestroy() never gets called during browser close
Goto Forum:
  


Current Time: Tue Nov 25 22:29:15 GMT 2014

Powered by FUDForum. Page generated in 0.03283 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software