• 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: .WO woes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: .WO woes


  • Subject: Re: .WO woes
  • From: David Avendasora <email@hidden>
  • Date: Mon, 1 Jun 2009 08:52:59 -0400


On May 31, 2009, at 7:58 PM, Lachlan Deck wrote:

On 01/06/2009, at 9:50 AM, Mike Schrag wrote:

i had to make a bunch of changes to the plugins just to make it COMPILE under 3.5 ... i'm really not even sure how it's working. oh well .. cool.

Well, bear in mind that I'm not just using plain-ol' wolips incremental building :-)

You know, I really appreciate Lachlan more and more. He makes me look so normal.


Thanks Lachlan, I owe you some beer at WOWODC!

Dave



On May 31, 2009, at 7:48 PM, Lachlan Deck wrote:

On 31/05/2009, at 10:28 PM, Mike Schrag wrote:

I have run into three separate issues with WO editing recently in WOLips and I'm wondering if there's some setting I've missed or accidently turned off in Eclipse. I'm using WOLips 5800 nightly.

Issue 1:
No content assist between the : and { in the wod file.

I noticed that too. Should have piped up as I assumed it might be 'cause I'm using eclipse 3.5M..

Yeah I just noticed #1 recently also .. it's not just a 3.5 problem.


So you're on 3.5 ... Are you using the 3.5 WOLips branch, or just getting lucky using the 3.4 version? Honestly I haven't even tried to RUN the 3.5 branch yet.

I've been running 3.5 for a couple of months now on the usual nightly - haven't tried the branch. It's pretty nice (in eclipse terms). There was a couple of quirks earlier on (in general with eclipse e.g., memory leak) but it's been pretty good lately. e.g., I've never had to clean... projects like I had to constantly do with 3.4.


Issue 2:
<webobject name = "Something" / > (Notice the extra space between the / and the > at the end of the tag)
That parses fine with no red Xs in WOLips, but causes parsing failure when the app is running.

File a Jira.
yep

Issue 3:
Abe: WOString {
	value = "Lincoln";

George: WOString {
	value = "Washington";
}

File a Jira. This is bad.
yeah, I've known about this one ... I don't recall why I didn't fix it eons ago. but log a jira.

ms


with regards, --

Lachlan Deck



_______________________________________________
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

with regards, --

Lachlan Deck



_______________________________________________
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: .WO woes
      • From: Chuck Hill <email@hidden>
  • Prev by Date: Re: where's Search field Icon?
  • Next by Date: Re: WebObjects 4.5.1 deployment license for Solaris...
  • Previous by thread: Re: where's Search field Icon?
  • Next by thread: Re: .WO woes
  • Index(es):
    • Date
    • Thread