Hi,
I will set up two documents. One for the views and another for the
project structure.
Have fun
Ulrich
Am Freitag, 01.11.02 um 22:10 Uhr schrieb Christian Edward Gruber:
> I'm still using 8.8, but what I've done is use the following structure.
>
> / - project root
> /src/Components (.wo and .api)
> /src/Java (.java files for .wo's and others)
> /src/Test (.java files for junit testing)
> /src/Resources (.eomodels, etc)
> /src/WebServer (you get the idea.)
> /obj (classes)
> /doc
> /doc/api
> /release (project's .woa result)
>
> If I used sub-projects, I'd probably want to use /projects and have the
> same structure as the above underneath it. I'll adapt to the decided
> upon form, but I find the above extremely convenient, and I only needed
> to re-organize the build.xml file as included.
>
> Regards,
> Christian.
>
>> -----Original Message-----
>> From: Anders Peterson [mailto:anders_peterso..ptimatika.se]
>> Sent: Friday, November 01, 2002 12:33 PM
>> Cc: woproject-de..bjectstyle.org
>> Subject: Re: Time to release 0.9.0
>>
>>
>> Currently I only have three wishes.
>>
>> 1) The WOLips Navigator doesn't have to do everything. We
>> still have the
>> ordinary Navigator, Package Explorer and ... Focus on what is
>> specific
>> to WO, and make the view as clean as possible.
>>
>> 2) Don't store/show anything directly under the project root.
>> Anything
>> that there is going to be more than one of should have a
>> collection node
>> (folder), and everything else could either be hidden or bundled under
>> one node.
>>
>> 3) I'd like some sort of collective view of components -
>> they're central
>> to WO.
>>
>> /Anders
>>
>> Ulrich Köster wrote:
>>
>>>
>>> Am Freitag, 01.11.02 um 16:35 Uhr schrieb Markus Nolte:
>>>
>>>>
>>>>> 1) In the new project wizard when you point out the
>> project content
>>>>> path; that's normally where you want the new project to
>> end up. You
>>>>> could point to an already existing project, but the new project
>>>>> will end up at that path. New WOLips projects always end
>> up at the
>>>>> default location. There needs to be two paths. One that
>> points to
>>>>> the existing project (if there is one) and one that
>> points to where
>>>>> you want the new project.
>>>>
>>>>
>>>> okay, I commit that I was too lazy to create another
>> composite, it's
>>>> now part of my TODO list
>>>>
>>>>> 2) Is 'MyProjectName.proj.src' better than 'src'? Why was this
>>>>> changed? I tried to rename it, but then things stopped working.
>>>>> Maybe it should be called 'java_src' since there are
>> other kinds of
>>>>> source files.
>>>>
>>>>
>>>> you can rename the project source folder anyway you like, but the
>>>> extension must be '.src',
>>>> subproject source folders cannot be renamed.
>>>>
>>>>> 3) Is it possible to have one file show up in many places in the
>>>>> WOLips Navigator? So that you could have all java files in one
>>>>> place, all html files in one, all api ... but also all
>> components,
>>>>> with all five files together, in one place.
>>>>
>>>>
>>>> good idea, working on great projects is quite difficult,
>> if you have
>>>> 15+ subprojects & components, but all java files in one
>> place will
>>>> be too much. I'm thinking of a ProjectBuilder like
>> navigation, but I
>>>> haven't the motivation to implement this, maybe Uli's task ;-)
>>>
>>>
>>> I will do my very best :-) Any ideas how to structure the navigator
>>> (localisation, parts of a component: wod,api,html,woo and java)?
>>>
>>> Or should it look like pbx?
>>>
>>>
>>>
>>>
>>> Another way is to use the tabs: JavaBrowser,ComponentNavigator,
>>> ResourcesNavigator(Resources, docs and WerServerResources)
>> and one for
>>> rest(frameworks products and so on). I`ll find the up and down
>>> scrolling very frustating.
>>>
>>>
>>> Ulrich
>>
>>
>>
>>
> <build.xml>
This archive was generated by hypermail 2.0.0 : Mon Nov 04 2002 - 04:37:31 EST