I have been digging in the problem and I would suggest the following
enhancements:
In woproject add the ability to specify an external template for the
info.plist the template will be processed as usual with the variable
substitution if necessary. The template is optional and if not
present the templates in the resources are used.
In wolips incremental builder do the corresponding changes i.e. have
an external info.plist template and do the same substitutions
When this is done the question is do we need another plist editor or
do we rely on eclipse xml editor. The advantage of creating a
info.plist editor is that we can simplify some other ui and make if
more explicit where to set some of the values.
Any comments?
Pierre
On 13-Sep-06, at 5:38 AM, Ulrich Köster wrote:
> It's okay to change the incremental builder for that. I'll migrate
> it later to the wolips core plugin.
>
> Uli
> Am 12.09.2006 um 11:24 schrieb Pierre Frisch:
>
>> Thanks Mike. I have been digging in that area but Uli just
>> deprecated the entire com.objectstyle.wolips.datasets so I am a
>> bit confused on how it is meant to work.
>>
>> Pierre
>>
>> On 11-Sep-06, at 11:47 PM, Mike Schrag wrote:
>>
>>> For the adventurous, WOIncrementalBuilder.createInfoPlist() in
>>> org.objectstyle.wolips.builder.internal = Incremental plist
>>> generation, ProjectFormat.infoFilter(Iterator) and
>>> FrameworkFormat.infoFilter(Iterator) in woproject = ant
>>> Info.plist builder.
>>>
>>> On Sep 11, 2006, at 7:01 PM, Pierre Frisch wrote:
>>>
>>>> The behavior of woproject and wolips is inconsistent in regard
>>>> of the plist generation. The content of the generated plist is
>>>> different if generated form the incremental builder or with teh
>>>> ant command. I would suggest to make it identical and to add the
>>>> ability to specify the application version:
>>>>
>>>> <key>CFBundleVersion</key>
>>>> <string>$$applicationVersion$$</string>
>>>>
>>>> Pierre
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Fri Sep 15 2006 - 12:14:21 EDT