Am Donnerstag, 21.11.02 um 20:11 Uhr schrieb Ian McDougall:
>>
>> Hi Ian,
>>
>> I think we should put this thread public.
>
> If you think it'll do good, then I agree.
>
>
>>>> Any feature requests for 0.9.3?
>>>
>>>> From my point of view, I have two feature requests:
>>>
>>> - allowing of a more dynamic project structure. i.e. allow source
>>> directories anywhere in project and have PB.project update properly.
>>> The
>>> PBIndex ant task would be sufficient for this. I'm spending more and
>>> more
>>> time wrestling with trying to synchronize the PB.project files lately
>>> in 4
>>> projects and 7 subprojects. Unfortunately, I came on board around
>>> the
>>> 0.8.7
>>> release and have already CVS'd the project which uses a 'src'
>>> directory in
>>> each project and subproject.
>> This is the point "dynamically resolve the src folder". I hope this
>> get
>> fixed soon. It is important that you report problems early. If we see
>> something is important , there is a very good chance that it get in
>> next release.
>
> This would be very nice. The primary issue I can see is this: where
> do the
> java files for a new component go? How will WOLips know where the
> source
> forder is for the current project? (or more importantly, subproject?)
> Will
> there be a WOLips config entry in .properties that states the projects,
> subprojects, and their associated source folders? That would then make
> putting a component's .java files in the .wo directory nearly
> impossible (or
> at least quite complicated).
That`s the reason for the src folder name.
>
>> From what I've seen, the best bet would be to put all .java files
>> into one
> source directory, and have a WOLips view which groups components and
> java
> together (as I mentioned before ;) )
>
>
>>>
>>> - Documentation. What does target builder do? I dunno. I'd dive
>>> into the
>>> code, but I really don't have time. I think this has the potential
>>> to
>>> be
>>> _very_ big in the WO community, and I'd hate to see you adopt Apple's
>>> previous stance on documentation ;). I'm trying to get all WO
>>> developers at
>>> our shop over onto Eclipse, but I don't want to spend a day trying to
>>> explain to them how Eclipse works.
>> The targetbuilder can build different targets within Eclipse. This is
>> usefull for developing JavaClientApplications. I wish we have more
>> time
>> for WOLips. So things will improve with every release.
>
> I'm guessing that target building is more of an PBX concept than a
> PBWO.
> Moving forward is always a good thing when it comes to docs. ;)
May be Uwe can tell more about the target builder.
>
>>> Another request would be to dynamically resolve all components,
>>> api's,
>>> and
>>> source into one consolidated view, regardless of their location in
>>> the
>>> project (logical vs. physical view). As I mentioned, our project is
>>> quite
>>> wide spread, and much time is spent jumping between .java and .wod
>>> files.
>>> Maybe even a popup command that jumps to the associated .java or .wod
>>> file
>>> for the currently highlighted file would be a great start.
>> Currently I`m setting up a draft for it. It drives me crazy too.
>
> We have a WOLips perspective, but a WOLips view would be most useful.
>
>>>
>>> I'm slowly trying to look at the code to see if I can be of some
>>> help.
>>> I
>>> feel bad asking others to do all the work. Perhaps I can be of some
>>> development help in the future. This is the first open source
>>> project
>>> I've
>>> come across that I really have interest in, and a need for!
>> You are welcome :-). For me this is a thing I would pay for. Share
>> your
>> ideas, questions, bugs.... . and time.
>
> I would be willing to pay for it as well.
>
>>> PS. the build scripts are seriously broken for windows development.
Could you send me the log?
>
>
This archive was generated by hypermail 2.0.0 : Thu Nov 21 2002 - 16:18:52 EST