Hi Edgar,
That's a very good question about a common source of confusion. Let me
attempt to answer in such a way so as to explain not only TablePane, but
many other containers... This topic should probably be covered in the
"knowledge base", were we to have one :)
Container fundamentally provides
Hello, long time I haven't write to this list. I'm currently developing
a "text engine" for php, most of the component hierarchy model I'm using
is based on pivot (conceptually). For laying out components I've chose
to use Containers too, by looking at TablePane's source code I see it
extends C
Hi Greg,
>> I've seen that Greg has just entered a JIRA ticket for this.
>> Is needed some comment inside ?
>
> If you think the ticket requires additional detail, feel free to add some.
Ok, I'll think at something for tomorrow.
> You don't need to run an application in the browser to script it
for the 2.0 release, instead of overwriting the default (Terra), why
not add this as a new Skin ?
That is the plan.
And maybe we could move all Terra Code (and Resources) in a dedicated
subproject (in Subversion), and the same for this skin, to not fill
wtk with other (related, Ok) things ...
I've seen that Greg has just entered a JIRA ticket for this.
Is needed some comment inside ?
If you think the ticket requires additional detail, feel free to add
some.
Rather than creating a new macro language, why not simply take
advantage of the existing scripting facilities in the JVM?
Hi to all,
for the 2.0 release, instead of overwriting the default (Terra), why
not add this as a new Skin ?
And maybe we could move all Terra Code (and Resources) in a dedicated
subproject (in Subversion), and the same for this skin, to not fill
wtk with other (related, Ok) things ...
What do you
Hi to all,
thanks for your comments, and I'm happy you like the idea ...
I've used products that used mouse positioning and clicks, but many
problems occurred.
So, from my experience, i think too that the approach of the
(optional) automationID could be the right approach.
I've seen that Greg has
Hi Todd, I would love to give this a try, will do something based on the
screen posted at the issue page in the next few days.
ps: I have been on the pivot list for quite some time now :)
Thien
On Tue, Sep 22, 2009 at 7:15 PM, Todd Volkert wrote:
> Thien,
>
> I figured I'd ping you to gauge yo
[
https://issues.apache.org/jira/browse/PIVOT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-149.
--
Resolution: Won't Fix
Fix Version/s: (was: 1.4.1)
This feature will not be implemented.
> A
Add an "automationID" property to Component
---
Key: PIVOT-307
URL: https://issues.apache.org/jira/browse/PIVOT-307
Project: Pivot
Issue Type: New Feature
Components: wtk
Reporter
>
> With Pivot the testing tool should just be able to introspect the
>> component hierarchy to find whatever it likes anyway (I want to say
>> XPath, but you know what I mean).
>>
>
> The main problem with this approach is that, if the layout changes (such
> that a button no longer exists at a par
Depends what you're doing, I suppose, but I wouldn't want to litter my
code/WTKX with automation names, or at least it should be optional.
I agree - this property should be optional. I imagine it would be
added by QA teams during testing.
With Pivot the testing tool should just be able to i
2009/9/23 Greg Brown :
> WTKX IDs are not exposed outside the serializer (except via the serializer's
> Dictionary interface). We could try to repurpose them to suit this use case
> as well, but I don't think that's the right approach, since it would
> preclude performing automated testing on UIs t
I don't think performing automated testing based on mouse location is
a good idea either. I only suggested using the DisplayHost because
Sandro mentioned simulating mouse events in his original email. If we
all agree that it isn't a good approach, it is probably not worth
pursuing.
On Se
If the display host reported its position on the screen, then you could get
around the screen resolution issues, because the display host's screen
position would be your starting point, then you could combine that with
component locations to know where to place the mouse. Greg can comment on
how t
WTKX IDs are not exposed outside the serializer (except via the
serializer's Dictionary interface). We could try to repurpose them to
suit this use case as well, but I don't think that's the right
approach, since it would preclude performing automated testing on UIs
that were created in cod
Hi to all,
> I forgot about that class!
Me too :-) , I've never used directly but now I remember this could help.
> It literally takes over the mouse and lets you do things with anywhere
> on your desktop, not just Java apps. To make it really useful you'd
> have to work out where the Pivot comp
Hi all,
I just posted a release announcement for Pivot 1.3 on Javalobby:
http://java.dzone.com/announcements/announcing-apache-pivot-13
If you are a DZone member, be sure to go and vote it up! :-)
Greg
I forgot about that class!
Yes, it absolutely does let you do mouse events and key presses - I've
used it for some quite dangerous things over the years! ;)
It literally takes over the mouse and lets you do things with anywhere
on your desktop, not just Java apps. To make it really useful you'd
Why not just use java.awt.Robot? I'm not 100% sure, but I think it has the
ability to simulate mouse events and key events.
-T
On Wed, Sep 23, 2009 at 7:55 AM, Greg Brown wrote:
> All component behaviors in Pivot are invoked by public APIs. So, from your
> examples, you could do:
>
> button.req
All component behaviors in Pivot are invoked by public APIs. So, from
your examples, you could do:
button.requestFocus();
button.press();
listView.setSelectedIndex(0);
menuItem.press();
textInput.setText("foo");
We don't currently allow a caller to simulate mouse clicks via a Pivot
API, thou
Btw, sorry for the typos, was replying on my phone.
Cheers,
Chris
2009/9/23 Christopher Brind :
> It's a good idea, I think. Flex has this, so or wouldn't be unique to Pivot.
>
> Probably the Pivot component set should be atom atable (that a word?), and
> all ow custom components to be automtable
It's a good idea, I think. Flex has this, so or wouldn't be unique to Pivot.
Probably the Pivot component set should be atom atable (that a word?), and
all ow custom components to be automtable if they want through a help API
that Pivot provides.
We could even write an automated testing tool usi
Hi to all,
an idea to discuss with all the team ... what do you think on the
ability for Pivot Applications / Applets to be scripted from the
outside world ?
I'm thinking on something like Macros in Office and other programs ...
for example the ability to sent pivot the same events that usually ar
24 matches
Mail list logo
