[Wonder-disc] Roots history

[Max M. <max...@ma...>]

Hi,
	The simple history behind the Roots directory is that PBWO does not 
support rapid turnaround at the framework level for non-install builds, 
meaning unless you are performing a make install after changing any 
piece of code then you can't work with frameworks in a rapid-turnaorund 
context. Enter crazy little awk script that if specified as part of the 
build target will automatically copy the built .framework of a regular 
build into this special directory, the reason for not making this 
directory the /Library/Frameworks was permission issues and the reason 
for not using ~/Library/Frameworks was cross-platform project search 
paths (if I recall correctly).
	Now bumping up the clock to the world of WO 5 and PBX. In the Infinite 
wisdom of the PBX team referencing frameworks from a project can not be 
done with a search path but instead has to be done as either an 
absolute reference, a build product relative reference or a project 
relative reference. This bites in my opinion, I know Chuck posted a 
hack/solution to allow search paths with PBX but I haven't had a chance 
to look at the implementation. Having all of the frameworks set to link 
their frameworks as build product relative in the same directory seems 
to be the best possible solution (you can set everything to build in 
any directory you want say ~/Library/Frameworks instead of Roots) for 
frameworks (for applications this isn't the best solution).
	As for getting rid of PBX build support, I don't think that is a great 
idea at this time. Given that PBX doesn't natively support Ant building 
which would require anyone who downloads the Wonder source to have Ant 
1.5 installed and configured, not something that I think we should 
require at this point.

Regards,
	Max

On Friday, September 27, 2002, at 10:41 AM, Tatsuya Kawano wrote:

>
> Anjo: You're back!
>
> Well, we've got Ant builds basically working on multiple platforms, 
> and I'd
> like to update it to perform different build styles: development, 
> deployment
> (install), and web (split install).  I saw Anjo put some code at the 
> very
> beginning to accomplish install and web builds for frameworks, and I'd 
> like
> to update it to support applications as well.
>
> What I'm wondering is that the role of the ~/Roots directory. Is that 
> only
> for development time or supposed to be used even for deployment?
>
> Also, is that a good thing that we keep the ~/Roots directory for
> development build?
>
> On 8/28/02, Anjo Krank wrote:
>> Which reminds me: can we go away from the ~/Roots thing now that the
>> ant builds work? In fact, shouldn't we remove the pbx-based build
>> completely?
>
> Actually, I still don't know what the problem with the pbx-based build 
> was
> (shame).  I couldn't really figured this out by reading the Wrox book 
> which
> is the story about Project Builder WO (same one to WO 4.5, not 5.x)
>
> So if someone gives me directions or a history about ~/Roots (The 
> Roots of
> Roots?), that would be great.
>
> Thanks,
> Tatsuya
>
> p.s.
> Somebody on the Japanese discussion list has got a basic PBX project
> template for Wonder. I'd like to add it to the repository very soon.
>
> Also, I have nothing significant to report from the discussion list; 
> no new
> glitch for today, which is good.
>
>
> ------ Forwarded Message
> From: anj...@t-... (Anjo Krank)
> Date: Wed, 28 Aug 2002 19:22:03 +0200
> To: Tatsuya Kawano <tat...@ma...>
> Cc: wonder disc <won...@li...>
> Subject: Re: [Wonder-disc] Bug with packaging
>
> Hi Tatsuya,
>
> Am Mittwoch, 28.08.02, um 18:33 Uhr (Europe/Berlin) schrieb Tatsuya
> Kawano:
>
>> I'll check my mailbox later when I have more time. As far as I can
>> remember
>> now, other common installation questions are:
>>
>> - Having a newer version of Log4J in my Java extensions folder and 
>> it's
>> conflicting with the frameworks. (The one in the Java extensions
>> folder is
>> always loaded before one on the classpath, and certain security
>> restrictions
>> may apply. The real problem is that don't remember which deployed
>> applications use the Log4J in the extension folder, so can't easily
>> remove.)
>
> Also, I believe that classes from there can't load other classes not in
> the extensions - which poses problems with ERXLogger...
>
>> - What's the quickest (and proper) way to set up MySQL just for enjoy
>> using
>> BugTracker? (including Anjo's MySQL plugin class)  Also, people often
>> don't
>> populate the database before they try to use.
>
> The *very* best thing is to optionally create the database at first
> start and populate it with a javaeoutil file once it gets usable
> again.. the next best thing is to at least warn the user that he needs
> to
>
>   mysqladmin create bugtracker; mysql bugtracker <
> ~/Wonder/Common/Applications/BugTracker/Frameworks/BTBusinessLogic/
> Support/populate.sql
>
> and
>
>   mysqladmin create ercore; mysql ercore
> <~/Wonder/Common/Frameworks/ERCoreBusinessLogic/Support/populate.sql
>
> As to my plugin: I have no problem to include it, but AFAIK, it's not
> strictly needed anymore. The problem is that in order to use it, it has
> to patch around to get loaded in the first place - at least it needed
> to last time I looked. So it needs to stay either in its own framework
> or we integrate put the starter code into ERXExtensions - neither of
> which I like...
>
> Which reminds me: can we go away from the ~/Roots thing now that the
> ant builds work? In fact, shouldn't we remove the pbx-based build
> completely?
>
> Also, shouldn't we have a "WONDER_HOME" env var? This should allow the
> user to specify where he wants to put the code while making it easier
> on the Ant script...
>
> And finally, what we need the most are reasonable project templates and
> file templates! I have some set up, but they are specific to my jobs,
> I'll probably write a small script that can turn any project into a
> template.
>
> The file templates in particular are very handy for creating new
> components and putting them into the required directory structure.
>
>> - I found people often forget to create Log4J property list and 
>> causes  app to
>> crash. (I already addressed this issue. App should no longer crash.) 
>> Also,
>> "SampleConfiguration.config" didn't work. (It now works.)
>>
>>
>> I answered above questions already and I had many other small  
>> questions as
>> well. I think half of CVS commits I made recently were for addressing 
>>  tiny
>> bugs reported from Japanese people.
>>
>> Also, I'll eventually write a quick start guide in one place,  
>> including how
>> localization and validation exception stuff work, log4j 
>> configuration,  Ant
>> build, ERNeutralLook advantage, et cetera, et cetera...
>>
>> By the way, there are certainly great interest rising on the Wonder  
>> project
>> and frameworks. I heard even a person on WO 4.5.1 started to try  
>> NetStruxr
>> framefork out too.
>>
>> I've been also trying to educate people how an open source project  
>> works.
>> Trying to ask them to participate the project, as a user, as a  
>> developer.
>>
>> Thanks,
>> Tatsuya
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Wonder-disc mailing list
> Won...@li...
> https://lists.sourceforge.net/lists/listinfo/wonder-disc