Am 27.10.2007 um 19:46 schrieb Simon McLean:
Hi Ken -
I wouldn't class myself as an expert, but I know enough to know
that your at a dead end trying to avoid eclipse/WOLips.
Besides, why would you want to avoid it ? Believe me, it's sooo
much better.
For me because of the missing W
Just to follow up on this further. I have managed to work out that it
appears to be a localisation related issue.
The HelloWorld example is localised and therefore has no Resources/
Main.wo instead it has a bunch of Resource/.lprog/Main.wo
components.
It seems that when launched with WOCachi
Hi all,
I've not managed to get my hands on Leopard yet. Could one of you be
so kind to elaborate on these release notes:
Deprecations:
Java Client Nib based applications
Direct to JavaClient based applications
EOCocoaClient based applications
These are all of the Apple standard Java Clien
Please keep threads on the mailing list ... I'm not sure what you've
setup in your classpath, but you should review the WOLips tutorials
on the Wiki. It looks like you setup a classpath variable instead of
adding the JNDI framework to the WO Frameworks list under the
classpath Library tab.
... related to this discussion, an upcoming Entity Modeler will write
out some sort of change tracking file (format as of yet undetermined
-- possibly it will actually spit out Project Wonder migration code)
that will provide a basis for writing migrations. This is still in
development and
You can just copy your WO 5.3 frameworks onto Leopard. The
frameworks are all just Java, so will work fine. You will want:
JavaDTWGeneration.framework
JavaDirectToWeb.framework
JavaEOAccess.framework
JavaEOApplication.framework
JavaEOCocoa.framework
JavaEOControl.framework
JavaEODistribution.
I believe the launchd scripts were inadvertently left out of 5.4
client. I believe they will make it in in a point release, but in
the meantime, I suspect you can steal the LaunchDaemon scripts from
Tiger server:
/System/Library/LaunchDaemons/com.apple.wotaskd.plist:
www.apple.com/DTDs/Pr
It does not do database syncing at this point ... It's something I've
considered, but in the general case, that technique does not work. I
would recommend that you look into Project Wonder migrations for the
future directions things are headed.
ms
On Oct 27, 2007, at 2:09 PM, Simon McLean
I have tried deployment of WO 5.4 applications on a 10.5 (client)
with WO 5.4 installed. But I cannot figure out how to launch wotaskd
on 10.5 client. Is it possible?
Thanks
JPM
___
Do not post admin requests to the list. They will be ignored.
Webo
Hi,
I have a PowerMac I use for development (occasionnally) and for
deployment testing. I have upgraded it to Leopard (client).
I have NOT installed WO 5.4. I would like to be able to continue
deploying WO 5.3 apps on this box. Is it possible? If it is possible,
how can i do it?
Thanks
J
Yes, WOLips provides "Entity Modeler" which is a brilliant
replacement for the now defunct EOModeler.
Yes, it does DB sql generation, but i'm not sure about synching. We
use Navicat for synching DB structures.
Simon
On 27 Oct 2007, at 19:05, Christian Evans wrote:
I have been away from W
I have been away from WO for a while. Does eclipse/WOLips support an
EOModeler kind of design tool or is the design of the DB now all done
by hand? And if it does support a GUI approach does it also have the
"sync" type feature that EOModeler had? I loved that when applying
changes to th
Hi Ken -
I wouldn't class myself as an expert, but I know enough to know that
your at a dead end trying to avoid eclipse/WOLips.
Besides, why would you want to avoid it ? Believe me, it's sooo
much better.
Simon
On 27 Oct 2007, at 17:43, Ken Foust wrote:
So you can't create a new W
On Oct 27, 2007, at 9:43 AM, Ken Foust wrote:
So you can't create a new WO project with Xcode 3.0
No.
can you load 2.4 as well a use that for WO development?
Yes, but...
if yes then what about the compiler - Use java 1.5 or 1.4
WO 5.4 is Java 1.5
i cannot open EOModeler App or WO
Le 07-10-27 à 12:43, Ken Foust a écrit :
So you can't create a new WO project with Xcode 3.0
can you load 2.4 as well a use that for WO development?
if yes then what about the compiler - Use java 1.5 or 1.4
i cannot open EOModeler App or WO Builder
They don't run at all, because the old Obj
So you can't create a new WO project with Xcode 3.0
can you load 2.4 as well a use that for WO development?
if yes then what about the compiler - Use java 1.5 or 1.4
i cannot open EOModeler App or WO Builder
I am trying to avoid going to eclipse/WOLips
What say you experts
Thanks ken
__
Heh, feel no remorse; I invited that. Besides, what the heck are
you doing answering email at 7:00 AM on Saturday??? Just can't keep
those fingers off the keyboard?
It's called "sleeping 30 mins the previous night" ... I crashed early
last night and the next thing I know I'm awake at 5am toda
On Oct 27, 2007, at 7:01 AM, Mike Schrag wrote:
You and your lucky GMT+10 :) Now that Leopard is officially
released, I can actually comment on some of these things. I can't
I wonder what I was going to say in the end of this sentence :)
"I can't " "... wait to get Leopard"? "... find m
On Oct 26, 2007, at 10:18 PM, Art Isbell wrote:
I am breaking various rules about not making more than one change
simultaneously by moving from Apple WO tools to Eclipse (3.2.2 -
too timid to move to 3.3.1 yet :-)
Probably you will be more successful using 3.3.1/wolips nightly ...
3.2.2 w
You and your lucky GMT+10 :) Now that Leopard is officially
released, I can actually comment on some of these things. I can't
I wonder what I was going to say in the end of this sentence :) "I
can't " "... wait to get Leopard"? "... find my keys"? Who
knows :)
The Shadow knows... (
However, its treatment of Mike's "lazy tags" wasn't ideal from my
perspective.
WOLips in the 3.3.x builds makes this much better. In the 3.2.x
branch, I treated them all like a paragraph tag that you left off the
closing tag for. In 3.3.x it knows that some lazy tags really are
single tag
The error: "The method arrayByAddingObjectsFromArray
(NSArray) in the type NSArray is not
applicable for the arguments (NSArray)". Say what?!
An EOAttribute is an EOProperty!
This is a bug in 5.4 -- Wonder had this same bug in our generic form
of NS* originally, but it is fixed in Wonder.
Am 27.10.2007 um 04:18 schrieb Art Isbell:
[...]
http://www.foo.com/bar.css";
type="text/css" charset="utf-8" />
but I could not rewrite a script tag with no contents as:
http://www.foo.com/bar.js"; type="text/
javascript" charset="utf-8" />