• 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: WOProject/WOLips first impressions from an Xcode user
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOProject/WOLips first impressions from an Xcode user


  • Subject: Re: WOProject/WOLips first impressions from an Xcode user
  • From: Anjo Krank <email@hidden>
  • Date: Sat, 12 Aug 2006 16:52:07 +0200


Am 12.08.2006 um 14:56 schrieb email@hidden:

Well, a couple of hours ago I added my thoughts to Robert's blog.

Frankly, this is a *mailing list* - if people have to say something valuable, they should say it, let us discuss it here, and not make us read and comment on that stuff externally.


Is there a list of outstanding issues with regard to WO development on Eclipse?

There is jira, our tracking system:

 http://objectstyle.org/jira/browse/WOL

Before you go there and enter bug reports, please check thoroughly if they there isn't already a similar one.

(e.g. the reverse engineering
of the dependency between WOBuilder and XCode being open - I just grabbed
that one from a quick perusal of the archive).

This one is not really solvable, and, given the current situation, also a waste of time - most likely, its using PDO, not accessible from java. And on top of this, WOBuilder is pretty much a POS anyway, the current incarnation is totally buggy, slow and eventually eats up files when it feels like it. Also, this WYSWIG thing is totally overrated and mainly only useful for beginners, as you see exactly nothing once your components get a bit more complex. Use CSS and you'll be much happier...


The WOComponent editor that is in Eclipse is totally workable. It even has important new features like the validation, which has saved me tons of work so far.

If you really want or need WYSIWIG, I'd advise you to write some DreamWeaver plugin with a pre- and postprocessor that translates

Tr : WOGenericContainer {
  elementName = "tr";
}

to a <tr> tag, or something similar. This shouldn't be too hard, as these plugins are done in JavaScript. David Teran wrote a proof-of- concept in an afternoon.

Cheers, Anjo
_______________________________________________
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: WOProject/WOLips first impressions from an Xcode user
      • From: email@hidden
References: 
 >Re: WOProject/WOLips first impressions from an Xcode user (From: email@hidden)

  • Prev by Date: Re: General List Disclosure of WWDC WO info
  • Next by Date: Re: Tutorial project
  • Previous by thread: Re: WOProject/WOLips first impressions from an Xcode user
  • Next by thread: Re: WOProject/WOLips first impressions from an Xcode user
  • Index(es):
    • Date
    • Thread