Menu
▾
▴
binarycloud-dev
|
From: Alex B. <en...@tu...> - 2001-07-12 18:32:32
|
hi all, I'm going to establish a subdir in the pear core cvs: binarycloud/ I'm _not_ going to move primary development to php cvs, but from now on I intend to maintain a fairly up-to-date synch to the pear repository. :) _alex -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |
|
From: John D. <jo...@we...> - 2001-07-12 19:03:57
|
I think you stand to meet some significant resistance here. One of PEAR's goals is synergy and non-replication. You'll effectively be giving PEAR its second database abstraction layer, as well as some other things.. The exposure is good though. John On Thu, 12 Jul 2001, Alex Black wrote: > hi all, > > I'm going to establish a subdir in the pear core cvs: binarycloud/ > > I'm _not_ going to move primary development to php cvs, but from now on I > intend to maintain a fairly up-to-date synch to the pear repository. > > :) > > _alex > > > > -- > alex black, ceo > en...@tu... > > the turing studio, inc. > http://www.turingstudio.com > > vox+510.666.0074 > fax+510.666.0093 > > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > http://lists.sourceforge.net/lists/listinfo/binarycloud-dev > > -- John Donagher Application Engineer Intacct Corp. - Powerful Accounting on the Web 408-395-0989 720 University Ave. Los Gatos CA 95032 www.intacct.com Public key available off http://www.keyserver.net Key fingerprint = 4024 DF50 56EE 19A3 258A D628 22DE AD56 EEBE 8DDD |
|
From: Alex B. <en...@tu...> - 2001-07-12 19:18:46
|
Stig seemed to think it was fine. And he _must_ remember what bc is, so we'll see. I'm doing this intentionally to see if they get pissy :) > The exposure is good though. That's what I'm thinking. Even if it makes trouble, people see it, and some think it's really cool. _a > I think you stand to meet some significant resistance here. One of PEAR's > goals > is synergy and non-replication. You'll effectively be giving PEAR its second > database abstraction layer, as well as some other things.. > > The exposure is good though. > > John > > On Thu, 12 Jul 2001, Alex Black wrote: > >> hi all, >> >> I'm going to establish a subdir in the pear core cvs: binarycloud/ >> >> I'm _not_ going to move primary development to php cvs, but from now on I >> intend to maintain a fairly up-to-date synch to the pear repository. >> >> :) >> >> _alex >> >> >> >> -- >> alex black, ceo >> en...@tu... >> >> the turing studio, inc. >> http://www.turingstudio.com >> >> vox+510.666.0074 >> fax+510.666.0093 >> >> >> >> _______________________________________________ >> binarycloud-dev mailing list >> bin...@li... >> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev >> >> -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |
|
From: Alex B. <en...@tu...> - 2001-07-12 19:22:48
|
For those of you interested why I decided to do this, for a couple reasons:
-I am very much interested to see their reaction
-We adhere to the coding standards, so "why not?"
-We may end up merging some of the classes, but if we'' only do that if
we get the features we need - so I'm happy to do that. (I.e. we had
discussed adding some things to PEAR_Error, instead of writing a binarycloud
error class from scratch.)
-Those doing pear are competent, experienced coders, and it can never
hurt to have 'em looking at the code.
It's sort of a whim, very much a political experiment. We'll see what we
see, eh :)
_a
> I think you stand to meet some significant resistance here. One of PEAR's
> goals
> is synergy and non-replication. You'll effectively be giving PEAR its second
> database abstraction layer, as well as some other things..
>
> The exposure is good though.
>
> John
>
> On Thu, 12 Jul 2001, Alex Black wrote:
>
>> hi all,
>>
>> I'm going to establish a subdir in the pear core cvs: binarycloud/
>>
>> I'm _not_ going to move primary development to php cvs, but from now on I
>> intend to maintain a fairly up-to-date synch to the pear repository.
>>
>> :)
>>
>> _alex
>>
>>
>>
>> --
>> alex black, ceo
>> en...@tu...
>>
>> the turing studio, inc.
>> http://www.turingstudio.com
>>
>> vox+510.666.0074
>> fax+510.666.0093
>>
>>
>>
>> _______________________________________________
>> binarycloud-dev mailing list
>> bin...@li...
>> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>>
>>
--
alex black, ceo
en...@tu...
the turing studio, inc.
http://www.turingstudio.com
vox+510.666.0074
fax+510.666.0093
|
|
From: David W. <dwe...@po...> - 2001-07-12 22:46:23
|
I was just thinking today that the Request class is a prime candidate for inclusion with PEAR. Also spent much of the day getting up to speed with Metabase :) -dave >For those of you interested why I decided to do this, for a couple reasons: > > -I am very much interested to see their reaction > -We adhere to the coding standards, so "why not?" > -We may end up merging some of the classes, but if we'' only do that if >we get the features we need - so I'm happy to do that. (I.e. we had >discussed adding some things to PEAR_Error, instead of writing a binarycloud >error class from scratch.) > -Those doing pear are competent, experienced coders, and it can never >hurt to have 'em looking at the code. > >It's sort of a whim, very much a political experiment. We'll see what we >see, eh :) > >_a -- David Weingart dwe...@po... The foot can split wood, but it can't split a watermelon. |
|
From: Alex B. <en...@tu...> - 2001-07-12 23:14:47
|
That's a good point :) > I was just thinking today that the Request class is a prime candidate > for inclusion with PEAR. > > Also spent much of the day getting up to speed with Metabase :) Yep, I like :) > -dave > >> For those of you interested why I decided to do this, for a couple reasons: >> >> -I am very much interested to see their reaction >> -We adhere to the coding standards, so "why not?" >> -We may end up merging some of the classes, but if we'' only do that if >> we get the features we need - so I'm happy to do that. (I.e. we had >> discussed adding some things to PEAR_Error, instead of writing a binarycloud >> error class from scratch.) >> -Those doing pear are competent, experienced coders, and it can never >> hurt to have 'em looking at the code. >> >> It's sort of a whim, very much a political experiment. We'll see what we >> see, eh :) >> >> _a -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X