On Sep 4, 2007, at 3:33 PM, Timmy wrote:

Me neither.

I must say, I've gotten very used to (very quickly) code completion in Eclipse. Me likey -- alot.

Now all I need to do is learn css a little more so that I can knock the tables out of my application. Web authoring is not my background so that is holding me up.

I'd guess that very few of us have that as a background or an expertise.


Anyone have reference material (or practical) advice for css. I'm mainly just using it for generic styles now.

Someone suggested Blueprint a while back. I have not used it yet, but it looks interesting:

Blueprint is a CSS framework, which aims to cut down on your CSS development time. It gives you a solid CSS foundation to build your project on top of, with an easy-to-use grid, sensible typography, and even a stylesheet for printing.
http://code.google.com/p/blueprintcss/


Chuck


On Sep 4, 2007, at 2:38 PM, Chuck Hill wrote:

For the record, I am NOT a vegetarian.  :-P


On Sep 4, 2007, at 2:28 PM, Steven Mark McCraw wrote:

For the record, I was trying to lend no comfort (cold or otherwise) by suggesting inline bindings. The tools are what they are. People were complaining about one aspect of the tool, and I offer inline bindings as a suggestion of what made that particular aspect of the tool workable for me, with the suggestion to try it and see if it had the same effect for you. I don't think anyone is calling anyone else slow or stupid or behind the times if they don't like the eclipse component editor. And certainly no one is trying to shove the eclipse component editor (which is apparently veal) down a vegetarian's (which is apparently the entire webobjects community) throat ;- p. But it is the accepted tool we have to work with, so it's nice to share tips about what helps and what has worked. No antagonism intended.


On Sep 4, 2007, at 5:14 PM, Galen Rhodes wrote:

That's the problem! It IS all about personal preference. No two people write code the same way. Just as people are individuals in their preference for color, clothes, music, whatever, people have preferences for how they write code! A good number of us became very use to working with WOBuilder and, yes, even got use to it's many quirks. What's faster for one person may very well be slower for others simply because we're use to working in a different way. For some of us who were use to WOBuilder, having to use Eclipse is like going from JEdit back to using VI. And telling us to try changing the paradigm even more by switching to inline bindings is cold comfort. You may as well be telling a lifelong vegetarian to just shut up and try the veal.


--
Galen Rhodes
[EMAIL PROTECTED]


On Sep 4, 2007, at 4:42 PM, Mike Schrag wrote:

- the ability to see, in a graphical way, what components are contained in other components, what they are, and (for simple things like conditionals), what their main binding is. Using WOBuilder with a complex component I can see what I need in less than a second, while it sometimes takes minutes in Eclipse to do the same thing. Although viewing tables is much easier this way, that's not the important thing. I don't need to see how the page will look-- I want to see the component hierarchy in a graphical way.
Just personal preference on this one ... I find the exact opposite. We don't do almost any table layout, and opening a complex css-laid-out component in WOBuilder appears to me to be unintelligible. Component editor in Eclipse shows both an outline view of your components as well as the collapsible HTML editor with rollovers that show the span of each tag. But this has been debated to death, so I'm leaving this at "personal preference."

- the ability to cut or copy a whole group of elements and paste them somewhere else, bindings and all.
This could definitely be added into component editor ... I can pretty easily, I think, track the associated wod bindings when you cut HTML and autocut/copy related wod entries.

ms

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/grhodes% 40thissmallworld.com

This email sent to [EMAIL PROTECTED]

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/mark% 40bluecollarsoftware.com

This email sent to [EMAIL PROTECTED]


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill% 40global-village.net

This email sent to [EMAIL PROTECTED]


--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects





_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/lists% 40thetimmy.com

This email sent to [EMAIL PROTECTED]



--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects





_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to