I think this would be a very worth while feature on the plugin, and
would solve many issues that WOLips now faces.
I've sent a message over to a contact in the XCode team to see if
they can provide us with some info on how the protocol works and the
data structures used.
I'll let you know what they say!
- Ian
On Aug 12, 2005, at 6:18 AM, Mike Schrag wrote:
> Hmmm .. So maybe wobuilder DOES use that protocol. I'll look more
> into how exactly it communicates w/ Xcode.
>
> ms
>
> On Aug 12, 2005, at 4:01 AM, Timo Hoepfner wrote:
>
>
>> Hi there,
>>
>>
>>
>>> Any reason you can think of why we can't/don't-want-to just roll
>>> this functionality into the incremental builder also so you don't
>>> have to think about it?
>>>
>>>
>>
>> one more thing regarding that: It's not enough to have an up-to-
>> date xcode project, but you must have the project opened in xcode
>> to get wobuilder to work properly. Otherwise wobuilder shows
>> "could not find project" and has no info on keys, actions, etc.
>> This is different from the older PB.project, which AFAIK was
>> parsed by WOBuilder itself.
>>
>> If you update the project outside of xcode (e.g. by woproject
>> xcodeindex task), xcode will prompt if you want to reload the
>> project and only after that confirmation wobuilder will see the
>> changes.
>>
>> So if the xcodeindex functionality is rolled into the incremental
>> builder, you will still have to open the project in xcode and go
>> to xcode and confirm reloading the project after making changes.
>>
>> Is the way wobuilder communicates with xcode documeted somewhere?
>>
>> Timo
>>
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Fri Aug 12 2005 - 11:39:10 EDT