Hi Tim,
some random notes:
You can specify a native library location for jars in eclipse in the build path
settings.
For deployment either put them in /Library/Java/Extensions or explicitly
specify the location (I don't have example code for that at hand).
You can generate the headers with an
On 30/Sep/2010, at 1:26 PM, David Holt wrote:
> On 2010-09-30, at 1:23 PM, Daniel Beatty wrote:
>> Greetings Mark,
>> Looks like it might. What procedure do I need to apply to this XCode
>> project to make it behave. It appears to an Old WO code.
> http://wiki.objectstyle.org/confluence/display
I'm looking to do some work on a WO project with JNI calls that was built in
XCode and move it to Eclipse. I guess workflow advice is the most important
thing - for mixing WO with JNI to call native c libraries. Since this whole
subject is new to me in general I'm interested in advice on:
- Ecl
NSKeyValueCodingAdditions.Utility.valueForKeyPath(lpi,
"displayGroup.dataSource");
Or you could use ERD2WUtilities.enclosingPageOfClass(sender,
ERDListPageInterface.class) so you can just call displayGroup()
directly.
Ramsey
On Oct 8, 2010, at 2:59 PM, David Avendasora wrote:
Hi Ramsey
Nevermind. I was casting it to WOComponent. Casting it to ERD2WListPage is what
I wanted. So I end up with:
lpi.setDataSource(((ERD2WListPage)
ERD2WUtilities.parentListPage(sender)).dataSource());
Which works perfectly!
Dave
On Oct 8, 2010, at 2:59 PM, David Avendasora wrote:
> Hi Ramsey!
>
Hi Ramsey!
Okay, so how do I get the EODataSource from the resulting ListPageInterface?
Dave
On Oct 8, 2010, at 2:12 PM, Ramsey Gurley wrote:
> ERD2WUtilities.parentListPage(sender) should give you the next list page up
> for the sender even if the sender is nested.
>
> Ramsey
>
> On Oct 8,
It would be worth looking at the WOOGNL parser to see if this could be added
somehow. It is debugging information that I have often wished for.
Chuck
On Oct 8, 2010, at 11:09 AM, Kieran Kelleher wrote:
> Thanks Chuck - I had even checked your "Secret Life of Components" chapter in
> PWO for
ERD2WUtilities.parentListPage(sender) should give you the next list
page up for the sender even if the sender is nested.
Ramsey
On Oct 8, 2010, at 1:56 PM, David Avendasora wrote:
Hi all,
I'm using the instructions here: http://wiki.objectstyle.org/confluence/display/WO/D2W+Flow+Control
t
Thanks Chuck - I had even checked your "Secret Life of Components" chapter in
PWO for clues earlier.
Regards, Kieran
On Oct 8, 2010, at 2:01 PM, Chuck Hill wrote:
> I think that is only known at parsing time, not at runtime.
>
>
> On Oct 8, 2010, at 10:55 AM, Kieran Kelleher wrote:
>
>> Addi
I think that is only known at parsing time, not at runtime.
On Oct 8, 2010, at 10:55 AM, Kieran Kelleher wrote:
> Adding a debugging feature and I want to grab/log the name of the current wod
> label in the current stateless subcomponent context ... as highlighted in
> this pic:
>
> _Use
Hi all,
I'm using the instructions here:
http://wiki.objectstyle.org/confluence/display/WO/D2W+Flow+Control to add a
function to my D2W listing page that will create and Excel file of the objects
listed. It works great, but I'm not comfortable with how I'm getting the
EODataSource from the exi
Adding a debugging feature and I want to grab/log the name of the current wod
label in the current stateless subcomponent context ... as highlighted in
this pic:
<>
Cannot see any clues in here either when overriding _setParent .. anyone
know where this tidbit of info is stashed?:
Le 2010-10-08 à 11:52, Simon a écrit :
> i've just started using these for auto-configuring production servers.
> it's cracking stuff - thanks!
Good to know that people are using it!
> is there any javadoc, or a list somewhere of all the functions
> available ?
I added a couple of examples in
i've just started using these for auto-configuring production servers.
it's cracking stuff - thanks!
is there any javadoc, or a list somewhere of all the functions
available ? if not, where do they live in the code (i.e what class
handles them ?). stupid question, i know, but i'm new to rest and i
14 matches
Mail list logo