On Aug 15, 2006, at 11:00 AM, Mike Schrag wrote:
> I don't think Chuck was blaming you for not understanding something
> (Eclipse is daunting),
No, not blaming you at all. Eclipse is large and the deep you go
(e.g. the API for developing) the larger it gets.
> rather I think he was pointing out that it's important for everyone
> to work together to try to answer questions and/or develop content
> that answers questions. The questions we're getting and will be
> getting soon should at least provide the basis for a good FAQ that
> could go up on the WOLips wiki.
Yes, that was my intent. I an concerned that if the community
continues to rely on only a few people to produce everything that
those people will lose interest and stop contributing. We are all
developers, we can all contribute something. Even if it is incorrect
documentation, at least that is a starting point for someone who
knows the full information to correct the inaccuracies while they may
not have the time or energy to document the whole thing.
> I'm curious if people prefer the WOLips wiki being "private" vs
> open like the wikibook? I don't know what limitations Confluence
> has or even if Andrus would even want it to be publicly editable,
> but it might help accelerate the development of some of this content.
I'd prefer open, it makes for less of a barrier to contributions.
Chuck
>
> ms
>
> On Aug 15, 2006, at 1:56 PM, David Holt wrote:
>
>> Thanks Chuck, Mike and Marc,
>>
>> I was just looking for general information, not a step by step. I
>> see that it is done exactly as I suspected it would be. I'll play
>> around with it. Sorry for the basic question, it is just that
>> everything looks quite "foreign" in Eclipse at the moment, but
>> there are enough familiar elements that I wasn't sure if I should
>> just be double clicking on something and it would all be taken
>> care of ;-)
>>
>> No more questions until everyone is caught up, I promise.
>> (unless, of course, that means no more questions, ever!)
>>
>> David
>>
>> On 15 Aug 2006, at 10:40 AM, Chuck Hill wrote:
>>
>>>
>>> On Aug 15, 2006, at 10:23 AM, David Holt wrote:
>>>
>>>> Hi Mike,
>>>>
>>>> Are there any special considerations for importing an XCode
>>>> WebObjects project to Eclipse? If so, would you consider adding
>>>> this to the tutorial as well at some point? I have gone through
>>>> the introductory stuff, but I will need to migrate my existing
>>>> XCode projects and I am guessing that there will be a number of
>>>> us in a similar position. Thanks!
>>>
>>> David, this is not aimed at you personally, this just seemed like
>>> a good message to add this onto.
>>>
>>> I think one thing that we all need to stop doing is saying, "Mike
>>> can you do ...?" Mike worked his ass off getting Entity Modeler
>>> ready and added a lot of features that he had no need for. Mike
>>> has real work to do, a deadline, a family, and no where near
>>> enough sleep. The rest of us need to pick up the ball and
>>> provide documentation, test plans, tutorials, etc. Mike has done
>>> more than his fair share, we owe Mike and mDimension a huge debt
>>> of gratitude. It is time for the rest of to pick up the ball and
>>> run with it and let Mike go back to his life.
>>>
>>> So, who has done this, can document it, and help David out? I
>>> would, but I am already four days behind this week and it is only
>>> Tuesday. Anybody?
>>>
>>> In a general answer to your question, there is no "Import xCode
>>> project that I am aware of. What _I_ have done in the past is to
>>> create an Exclipse project of the same name in a different
>>> location. Then copy all of the files that Eclipse created
>>> (except the Xcode project files!) into the Xcode project. Then
>>> discard / delete the empty Eclipse project and open the now Xcode/
>>> Eclipse one in Eclipse and start moving things around. Put all
>>> the .java under /src adn (I think) Eclipse will help move them in
>>> to the proper packages. One thing to remember is that Eclipse is
>>> file name and location based not Group based, so project
>>> maintenance can be a lot simpler.
>>>
>>>
>>> Chuck
>>>
>>>
>>>
>>> --
>>>
>>> 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
>>>
>>>
>>>
>>>
>>>
>>
>
--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
This archive was generated by hypermail 2.0.0 : Tue Aug 15 2006 - 18:09:15 EDT