• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Bringing back the dev tools
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bringing back the dev tools


  • Subject: Re: Bringing back the dev tools
  • From: "Mr. Pierre Frisch" <email@hidden>
  • Date: Mon, 25 Feb 2008 19:29:42 -0800

I may be repeating myself but DO NOT USE EOModeler with WebObjects 5.4.x. There are some new data in the eomodels that EOModeler knows nothing about and will not only ignore but remove. There is no version protection in EOModeler so you will be disappointed. The only way to edit model for WebObjects 5.4 is Entity Modeler which exist as a stand alone application if you really do not want to use eclipse.

Pierre
--
Pierre Frisch
email@hidden


On Feb 25, 2008, at 2:03, Gino Pacitti wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David
Thanks for all the help - this looks great and all seems to be
working well.. Except the bug with WOBuilder but I think I can live
with that.... :-)

Gino
On 25 Feb 2008, at 09:25, David Elliott wrote:

Hi Gino,

Would you have a look at your console log by opening up the Console
app in /Applications/Utilities?

My guess is that they got redirected somewhere, probably back into
the .dst root!  It seems for some queer reason that the created
package references the apps by bundle ID and attempts to replace an
existing app with that bundle ID rather than install into the
proper location.  I wish I knew some way to turn this off because
not too many people really care to move them as far as I know,
particularly when all the frameworks they depend on need to be in
the fixed locations to work anyway.

Try nuking /tmp/WebObjectsLegacyDevelopment.dst and then installing
the package again.. it'll probably work because launch services
won't have remembered that EOModeler and friends were "installed"
in the tmp dir.

As for Xcode, follow the instructions at the end of the new (r18)
README.txt so that Xcode can find the file templates.

-Dave

On Feb 25, 2008, at 4:13 AM, Gino Pacitti wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David

I am really pleased with this... it was just what I was looking for
to move forward with using WO in conjunction with Leopard... Thanks
for your great work.

I do have a couple of final questions though as I am unable to add a
new WOApplication or WOComponent from the file menu in XCode.. Any
reason why this was...

BTW after I ran the final script I looked for the .dmg file in tmp
and installed that - yet for some reason the tools did not install
in /Developer/Applications/
I had to manually copy it across...

The rest seemed to be installed but I copied from the .dst file all
the directory contents into their respective paths...

Anyway Xcode opens projects and compiles and I can open WOComponents
which still have their link to the project...

If you do have a sec and can help with the question above I would
surely appreciate it..

GIno
On 24 Feb 2008, at 19:06, David Elliott wrote:

Hi Gino,

I think you mean lWOCompatibilityStreams not
IWOCompatibilityStream.  That is, a lowercase ell like the "-l"
option to the linker.

I've got Xcode set at the defaults and I did just check and find
that if you set a custom build products location you need to be
sure to set it to place intermediate build products "with build
products".

There are equivalent options in the project inspector.  If you've
customized it in your general Xcode preferences then make sure you
select Place Intermediate Build Files in: "Build Products Location"
from the project inspector.

Also note that putting the build products anywhere but the normal
build directory is going to require that you modify the woroot-
fixup.sh script slightly.  So if in doubt, set the build products
(Place Build Products in:) to /path/to/WOCompatibility-r16/build

I am guessing you got this error on the SystemWOCompatibility
target which was unable to find its dependencies.

-Dave


On Feb 24, 2008, at 7:54 AM, Gino Pacitti wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David

I tried to build the WOCompatibility.xcodeproj with XCode 3 on
Leopard and I get an error: library not found
IWOCompatibilityStream?

I had run the first script with XCode 2.5 mounted and that went
well
but the requirement to build the project first gave me the error.

I did download the Libstreams first and they are in the folder...

Any help appreciated

Gino
On 24 Feb 2008, at 09:54, David Elliott wrote:

[NOTE: CC'd anyone who posted publicly expressing interest and
BCC'd anyone who sent me a private mail]

On Feb 24, 2008, at 4:30 AM, Simon McLean wrote:


In fact, I believe that most WebObjects developers have only
moved to Eclipse because they were forced to.

I think you're absolutely right. But very shortly after arriving
on planet Eclipse we realised just how stupid we were clinging on
to XCode.

Tried it. Didn't like it. It does a lot of stuff, none of
which I
really care about most of the time. The old stuff was better for
my workflow. Or rather maybe I should say the old stuff IS better
for my workflow.


http://tgwbd.org/WOCompatibility/index.html

Enjoy,
-Dave

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com

This email sent to email@hidden


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.7.0 (Build 1012)
Charset: US-ASCII

wj8DBQFHwWkwTKoUwFtLxjwRAnbYAJ9+XP/A8zPzMZtqzcT08jpvQN4ZqwCfS+in
wZD4nM0vXW7rXRERssa9yeQ=
=6+Yq
-----END PGP SIGNATURE-----



-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.7.0 (Build 1012)
Charset: US-ASCII

wj8DBQFHwoasTKoUwFtLxjwRAj83AJ4ju+N92zO4Oy2WbIsj2rnQcOtwXQCeIqgz
l+VB1MAwl5X8JuXf+G2FY1I=
=tMdT
-----END PGP SIGNATURE-----



-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.7.0 (Build 1012)
Charset: US-ASCII

wj8DBQFHwpKUTKoUwFtLxjwRAjfHAJwIpahxiinyH+lvKekSx/M3Ec1c8wCfTE1n
YLnglrgP8ZmrUyIXFeuo0G0=
=fMex
-----END PGP SIGNATURE-----
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Bringing back the dev tools
      • From: David Elliott <email@hidden>
References: 
 >Bringing back the dev tools (From: David Elliott <email@hidden>)
 >Re: Bringing back the dev tools (From: Thomas <email@hidden>)
 >Re: Bringing back the dev tools (From: Clark Mueller <email@hidden>)
 >Re: Bringing back the dev tools (From: Thomas <email@hidden>)
 >Re: Bringing back the dev tools (From: Pascal Robert <email@hidden>)
 >Re: Bringing back the dev tools (From: Michelle Parker <email@hidden>)
 >Re: Bringing back the dev tools (From: Simon McLean <email@hidden>)
 >Re: Bringing back the dev tools (From: David Elliott <email@hidden>)
 >Re: Bringing back the dev tools (From: Gino Pacitti <email@hidden>)

  • Prev by Date: Re: JavaEOGenerator, Eclipse, WOLips, WO 5.4, Mac OS X 10.5.2
  • Next by Date: Re: Bringing back the dev tools
  • Previous by thread: Re: Bringing back the dev tools
  • Next by thread: Re: Bringing back the dev tools
  • Index(es):
    • Date
    • Thread