Menu
▾
▴
binarycloud-dev — development list for binarycloud
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
(57) |
May
(287) |
Jun
(166) |
Jul
(286) |
Aug
(273) |
Sep
(254) |
Oct
(144) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Alex B. <en...@tu...> - 2001-05-17 01:54:25
|
> > We've got a gut who just started on contract who showed me some XSLT stuff > with some of our data feeds that come via XML. I was super impressed. heh, ditto. One of the things we're doing with r2 is the ability pass an entity definition to a form builder, and have a layout and all the correct form fields constructed _for_you_. I'm going to construct a library of xslt for form elements, which can be called by FormBuilder to construct forms based on generated XML. :) _a -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |
|
From: <gr...@i7...> - 2001-05-17 01:26:58
|
We've got a gut who just started on contract who showed me some XSLT stuff
with some of our data feeds that come via XML. I was super impressed.
Cheers,
Graeme
Alex Black
<en...@tu...> To: binarycloud-dev <bin...@li...>
Sent by: cc:
bin...@li...urc Subject: [binarycloud-dev] xslt
eforge.net
17/05/2001 11:07 AM
Please respond to binarycloud-dev
hi all,
who here has done anything with xslt?
I want to make available all the resources I have so people will understand
what reasons we have for using it, why it is so powerful, and why (here we
go) all distro binarycloud r2 modules will use xslt exclusively for all
presentation.
If anyone's interested, I'll put up some code examples.
_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
|
|
From: Alex B. <en...@tu...> - 2001-05-17 01:08:25
|
hi all, who here has done anything with xslt? I want to make available all the resources I have so people will understand what reasons we have for using it, why it is so powerful, and why (here we go) all distro binarycloud r2 modules will use xslt exclusively for all presentation. If anyone's interested, I'll put up some code examples. _alex -- 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-05-16 17:52:31
|
>>> I think it's better treat it as a optional module, because some people > may >>> not want to brother with it, and wanna to make things simple and easy. >>> >>> Ronald >> >> I agree. this is not something I would force on a developers, _unless_ > they >> wanted to include the module code in the binarycloud distro, in which case > I >> would require that the code not depends on register_globals. > What I think is, include the module in BC distro, but treat it as a > optional > module for BC user. That is how it woudl be done. Note, thuogh that the above is still true: I would require any modules which would be distrobited with binarycloud to use Request, so users could install and configure a secure installation without problems. I.e. you can write your own code with register_globals, but if you want to distribute it as part of BC, you have to remove then dependency on register_globals. -a -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |
|
From: TAO R. <ron...@ho...> - 2001-05-16 08:29:35
|
> > I think it's better treat it as a optional module, because some people may > > not want to brother with it, and wanna to make things simple and easy. > > > > Ronald > >I agree. this is not something I would force on a developers, _unless_ they >wanted to include the module code in the binarycloud distro, in which case I >would require that the code not depends on register_globals. What I think is, include the module in BC distro, but treat it as a optional module for BC user. > >I'm doing the last bit of thinking re: the naming stuff, and will publish >updated docs with "the decision" > >thanks all, for the input :) > >_alex _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. |
|
From: Alex B. <en...@tu...> - 2001-05-15 19:17:11
|
>> Totally agree with you. But for people that don't like this, maybe the the >> trailing_ thing is an alternative. $myOutside_ (?myOutside.=value) > I think it's better treat it as a optional module, because some people may > not want to brother with it, and wanna to make things simple and easy. > > Ronald I agree. this is not something I would force on a developers, _unless_ they wanted to include the module code in the binarycloud distro, in which case I would require that the code not depends on register_globals. I'm doing the last bit of thinking re: the naming stuff, and will publish updated docs with "the decision" thanks all, for the input :) _alex -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |
|
From: TAO R. <ron...@ho...> - 2001-05-15 02:52:52
|
>Totally agree with you. But for people that don't like this, maybe the the >trailing_ thing is an alternative. $myOutside_ (?myOutside.=value) I think it's better treat it as a optional module, because some people may not want to brother with it, and wanna to make things simple and easy. Ronald _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. |
|
From: Andreas A. <a.a...@th...> - 2001-05-14 10:56:17
|
Hi Alex, > The most secure wat to get input from the outside world is referencing: > $HTTP_POST_VARS[var], $HTTP_GET_VARS[foo], etc Well this is the way I do all my projects. It's the most secure but also more effort. I check the $HTTP_*_VARS arrays and reference the variables to internal globals if required. More work, but possibly highest security. > So, I thought it might be a good idea to make all "external" variable access > pass through this single point, and in doing so, I could: Performing a type check or something (isEmail, isNumber, etc.) and on success return the reference. > I sort of liked that, it's a little inconvenient, but it's much more secure. I'm with you. > thoughts? Totally agree with you. But for people that don't like this, maybe the the trailing_ thing is an alternative. $myOutside_ (?myOutside.=value) Andi |
|
From: Andreas A. <a.a...@th...> - 2001-05-14 10:44:54
|
Hi 1.) Variable and method names: mixed case with lower case leading, with leading or trailing underscores to signify private or global. > e.g. $userName seems to be favored and $_userName for a local and > "private" variables, $userName_ for global and for "public". I'm with you. But there is still the problem with the extra namespace for variables from the outside. So with the underscore there is a clear distinction between globals from the outsite $myName_ (passed in the url via script.php?myName.=value) and "internal" globals like $myName. On the other hand we have a "namespace" for varibales that are, and functions that should be considered as privat: $_privateName and _privateMethod();. So I would only use the leading "_" for private methods/vars and the trailing "_" for globals from the outside. Possibly a good solution I think (and there are not to many _'s than prepending or appending to each and every variable/mehtod). Andi |
|
From: Jim H. <ji...@ha...> - 2001-05-14 07:21:03
|
Why not use PHP itself? It can be invoked through the web server as well, e.g. /bc_install.php or bc_make.php Php surely easier than VBS > >I have no idea if the Makefile would work on Win, as I > haven't done any > >testing. I think it's probably safe to assume that r2 will need a > unix-esque > >machine to run on. > > > How about if we use VBS in windows, but it's absolute unsafe |
|
From: Peter B. <re...@f2...> - 2001-05-14 07:16:07
|
At 02:14 PM 5/13/01 -0700, you wrote: >Sadly, function names are not case sensitive in php, so one has to be a >bit careful. They will be shortly - see http://www.zend.com/zend/week/week36.php I quote: TLK: variable, class and function naming Since PHP 2, the language has always regarded variable names to be case sensitive, while functions and classes are not. It appears that either PHP 4.1 or PHP 5 will break compatibility with this previous functionality, and regard everything as case sensitive. Logically, this makes more sense, and most of the core developers have already noted their excitement at the prospect. The changeover will also result in a boost in speed, since converting cases will not be necessary. For those who prefer the old way, there will be a compatibility mode .ini option. HTH! Peter. --oOo-- Narrow Gauge on the web - photos, directory and forums! http://www.narrow-gauge.co.uk --oOo-- Peter's web page - Scottish narrow gauge in 009 http://members.aol.com/reywob/ --oOo-- |
|
From: TAO R. <ron...@ho...> - 2001-05-14 02:19:44
|
>It's harder to do it, but certainly possible. You can't run create_db for >obvious reasons, and you need to make sure that the database you _do_create >uses the same name: binarycloud_db. > >Note, though that r2 will require access to non-module php on the command >line, because all of the Makefiles are php. That's going to be harder to >find on a shared hosting box with that config available, if you have no >ability to develop your stuff on a local linux/bsd/etc box. > >I have no idea if the Makefile would work on Win, as I haven't done any >testing. I think it's probably safe to assume that r2 will need a unix-esque >machine to run on. > >The best way to run things would be: > -local development machine (any cheap pc hardware will do, redhat or >similar) > -virtualhost (shared hosting) setup, with php 4.0.4+, we can control ini >setting from within Init. > How about if we use VBS in windows, but it's absolute unsafe _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. |
|
From: alex b. <en...@tu...> - 2001-05-14 02:07:03
|
> Hello,
>
> I have just tried to install r1b on my windows2k apache, php, mysql.
>
> Firstly I'd like to comment / ask whether the installation can be done
> on a shared web hosting i.e. no root access, can only create mysql db
> through a 'web control panel' interface.
> It seems that Creade db schema insists on creating a db and subsequently
> failed because I did not use the root mysql access.
It's harder to do it, but certainly possible. You can't run create_db for
obvious reasons, and you need to make sure that the database you _do_create
uses the same name: binarycloud_db.
Note, though that r2 will require access to non-module php on the command
line, because all of the Makefiles are php. That's going to be harder to
find on a shared hosting box with that config available, if you have no
ability to develop your stuff on a local linux/bsd/etc box.
I have no idea if the Makefile would work on Win, as I haven't done any
testing. I think it's probably safe to assume that r2 will need a unix-esque
machine to run on.
The best way to run things would be:
-local development machine (any cheap pc hardware will do, redhat or
similar)
-virtualhost (shared hosting) setup, with php 4.0.4+, we can control ini
setting from within Init.
> Secondly, I have a debug message:
>
> PHP Warning The length of the needle must not be 0 file:
> h:/projectwebs/bc/binarycloud/core/lib/bread_crumbs_and_tabs.lib line 40
>
>
> This is because BC_DOCROOT is indeed empty because I tried to put it
> where my apache docroot is and the doc said don't change if it's in
> docroot.
Yes, this is a sort-of-not-bug which is a result of me not testing a patch I
received enough.
I will send you the breadcrumbs lib which doesn't use BC_DOCROOT.
> I will keep playing with it and ask some more :)
great :)
_alex
|
|
From: Jim H. <ji...@ha...> - 2001-05-14 01:44:41
|
Hello, I have just tried to install r1b on my windows2k apache, php, mysql. Firstly I'd like to comment / ask whether the installation can be done on a shared web hosting i.e. no root access, can only create mysql db through a 'web control panel' interface. It seems that Creade db schema insists on creating a db and subsequently failed because I did not use the root mysql access. Secondly, I have a debug message: PHP Warning The length of the needle must not be 0 file: h:/projectwebs/bc/binarycloud/core/lib/bread_crumbs_and_tabs.lib line 40 This is because BC_DOCROOT is indeed empty because I tried to put it where my apache docroot is and the doc said don't change if it's in docroot. I will keep playing with it and ask some more :) Cheers, Jimmy |
|
From: alex b. <en...@tu...> - 2001-05-14 01:35:43
|
actually, might as well ressurect this idea:
a while ago, I considered adding another core class, called "vars" or
something, which would be used this way:
-turn off global variable registration for php. i.e. if you do:
/index.php?foo=hello
you _cannot_ access:
$foo
in a script.
I can see everyone scratching their heads.
The most secure wat to get input from the outside world is referencing:
$HTTP_POST_VARS[var], $HTTP_GET_VARS[foo], etc
PHP already has a means of determining the variable order, usually it's GPCS
(get post cookie session).
The problem with that is it can dump strange stuff into your environment
that you don't necessarily know about. We would provide a similar means of
ordering this stuff, but abstracted into a class so nothing would actually
make it into the environment until it was requested.
So, I thought it might be a good idea to make all "external" variable access
pass through this single point, and in doing so, I could:
-impose some checks on the input
-make sure that _no_ user input would _ever_ be in the environment my
code is running without my explicitly including that input via:
$Var->getVar('foo'); or the like.
I sort of liked that, it's a little inconvenient, but it's much more secure.
Also, you could add some intelligence to getVar like:
getVar('string', 'foo'), and getVar would check that the requested
variable was a simple string (containing no - <? ?> or < > pairs, etc)
that may be a bit overboard, but it would certainly be secure.
thoughts?
this is pretty easy to do, btw. and because of the way r2 pages are
designed, we could just make it an option that loads only if a page
explicitly requests it.
(this can already be donw with auth, perm, and session - so unlike
binarycloud r1, binarycloud r2 will be usable without a database, assuming
you don't use modules or core components that require queries.)
maybe I'll write that into the spec for core and mark it as "to do" see if
anyone is interested in doing it.
_alex
|
|
From: TAO R. <ron...@ho...> - 2001-05-14 01:20:27
|
>In light of the recent discussions about variable and method naming
>conventions I'd like to add my suggestions based on what I've used in
>numerous large projects in C++, Java, and lately in PHP that tend to
>feel quite natural for at least a few pockets of programmers laboring in
>unlabeled buildings in a few urban centers:
>
>
>1.) Variable and method names: mixed case with lower case leading, with
>leading or trailing underscores to signify private or global.
>
>e.g. $userName seems to be favored and $_userName for a local and
>"private" variables, $userName_ for global and for "public".
I would say for public just named like $myName rather than $myName_,
because it seem much more easy and convenicnce for people who progam
with BC API
>
>Sadly, function names are not case sensitive in php, so one has to be a
>bit careful.
>
>
>
>2.) Getters and setters:
>
>I agree with Aderhold re: getProperty() and setProperty(...) seem quite
>natural.
>
>
>
>It's too bad that php doesn't support function overloading, it would be
>nice to be able to define setter and getter functions as:
>
>$obj->name_() - gets name value, name($stringVarHere) - sets name value
>$obj->name_($someName_); sets the $_name property of $obj to equal
>$someName_
>
>It would be nice if binary cloud allowed this convention also.
>
>
>
>One simple workaround to the overloading problem:
>
>class test
>{
>var $_name="not set";
>
>function name_($val)
for the function prototype, should be like setMe($foo1 = '', $foo2 = '')
otherwise if user do not provide anything while calling the method,
PHP engine give him any error response
>{
> if(isset($val))
> $this->_name=$val;
> else
> return $this->_name;
>}
>
>}
>/* exercise class test */
>$obj=new test;
>$tvar=$obj->name_(null);
>echo "obj name is $tvar<br>";
>$obj->name_("set");
>$tvar=$obj->name_(null);
>echo "obj name is $tvar<br>";
>
>
>
>The above are just my own thoughts - I wanted to add my vote to the
>discussion. Thank you.
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
|
|
From: alex b. <en...@tu...> - 2001-05-14 01:13:38
|
> feel quite natural for at least a few pockets of programmers laboring in
> unlabeled buildings in a few urban centers:
heh
> 1.) Variable and method names: mixed case with lower case leading, with
> leading or trailing underscores to signify private or global.
This is certainly the standard for Javascript, and indeed many other
languages.
> e.g. $userName seems to be favored and $_userName for a local and
> "private" variables, $userName_ for global and for "public".
I've never seen the latter. Though it is interesting, and would still work
with the "global variable concept" I presented before. PHP Replaces the .
with an _ regardless of where it is in the name.
> Digression on associating private/local with leading underscore - we
> read code from left to right and somehow the underscore being located to
> the left seems to connote something that is more restricted or internal.
I agree here.
> Whereas a trailing underscore seems to imply something "further out" or
> global or public. At least for many programmers I've worked with. This
> seems to agree with the
I don't quite agree there, but at the same time I do like the fact that it
solves the "private methods vs. public variables, that's counterintuitive"
problem.
> 2.) Getters and setters:
>
> I agree with Aderhold re: getProperty() and setProperty(...) seem quite
> natural.
as does any other verb-noun combination:
checkPermissions
logIn
collectGarbage
etc.
> It's too bad that php doesn't support function overloading, it would be
> nice to be able to define setter and getter functions as:
>
> $obj->name_() - gets name value, name($stringVarHere) - sets name value
> $obj->name_($someName_); sets the $_name property of $obj to equal
> $someName_
>
> It would be nice if binary cloud allowed this convention also.
While I agree, I'm a little reticent to add a feature like that when I have
a feeling that Zeev and friends will be adding it themselves.
However, I do see the point.
more thinking to do...
_alex
> One simple workaround to the overloading problem:
>
> class test
> {
> var $_name="not set";
>
> function name_($val)
> {
> if(isset($val))
> $this->_name=$val;
> else
> return $this->_name;
> }
>
> }
> /* exercise class test */
> $obj=new test;
> $tvar=$obj->name_(null);
> echo "obj name is $tvar<br>";
> $obj->name_("set");
> $tvar=$obj->name_(null);
> echo "obj name is $tvar<br>";
>
>
>
> The above are just my own thoughts - I wanted to add my vote to the
> discussion. Thank you.
|
|
From: alex b. <en...@tu...> - 2001-05-14 01:05:00
|
> What does he have against PEAR? In principle, I think nothing. In practice I have seen him flam them (quite eloquently, actually) about their not invented here/ivory tower approach. I have to say that I agree with much of his opinion. > Also, can you give me a link o a PHP manual page describing the ?.foo=bar > -> $_foo = "bar"; behaviour? http://www.php.net/manual/en/language.variables.external.php#language.variab les.external.dot-in-names :) _alex |
|
From: A B. <ab...@ab...> - 2001-05-13 21:14:36
|
In light of the recent discussions about variable and method naming conventions I'd like to add my suggestions based on what I've used in numerous large projects in C++, Java, and lately in PHP that tend to feel quite natural for at least a few pockets of programmers laboring in unlabeled buildings in a few urban centers: 1.) Variable and method names: mixed case with lower case leading, with leading or trailing underscores to signify private or global. e.g. $userName seems to be favored and $_userName for a local and "private" variables, $userName_ for global and for "public". Digression on associating private/local with leading underscore - we read code from left to right and somehow the underscore being located to the left seems to connote something that is more restricted or internal. Whereas a trailing underscore seems to imply something "further out" or global or public. At least for many programmers I've worked with. This seems to agree with the http://www.thyrell.de/info/downloads/CodeGuide.pdf document. Sadly, function names are not case sensitive in php, so one has to be a bit careful. 2.) Getters and setters: I agree with Aderhold re: getProperty() and setProperty(...) seem quite natural. It's too bad that php doesn't support function overloading, it would be nice to be able to define setter and getter functions as: $obj->name_() - gets name value, name($stringVarHere) - sets name value $obj->name_($someName_); sets the $_name property of $obj to equal $someName_ It would be nice if binary cloud allowed this convention also. One simple workaround to the overloading problem: class test { var $_name="not set"; function name_($val) { if(isset($val)) $this->_name=$val; else return $this->_name; } } /* exercise class test */ $obj=new test; $tvar=$obj->name_(null); echo "obj name is $tvar<br>"; $obj->name_("set"); $tvar=$obj->name_(null); echo "obj name is $tvar<br>"; The above are just my own thoughts - I wanted to add my vote to the discussion. Thank you. |
|
From: Peter B. <re...@f2...> - 2001-05-13 20:54:45
|
At 12:39 PM 5/13/01 -0700, you wrote: >I would choose and adhere to >one standard for Init and the Core classes, but metabase uses its own >standards (manual _really_ dislikes PEAR), etc. anyway. What does he have against PEAR? Also, can you give me a link o a PHP manual page describing the ?.foo=bar -> $_foo = "bar"; behaviour? Thanks, Peter. --oOo-- Narrow Gauge on the web - photos, directory and forums! http://www.narrow-gauge.co.uk --oOo-- Peter's web page - Scottish narrow gauge in 009 http://members.aol.com/reywob/ --oOo-- |
|
From: alex b. <en...@tu...> - 2001-05-13 19:41:34
|
> Methods: setName() or set_name() > privat class methods: _setName() or _set_name() > Variables (global) , as discussed before: $_varName or $_var_name > Variables (other): $varName or $var_name > Classnames: Auth, ExecutionTimer I think the only place where there's actually a difference is naming caps standards, i.e. Public_Function as opposed to publicFunction or PublicFunction. I need to look at some of the incoming code (EntityManager, etc) before giving you a refined opinion on this. I'm leaning towards a lax standard that says "whatever you want" for naming caps. I would choose and adhere to one standard for Init and the Core classes, but metabase uses its own standards (manual _really_ dislikes PEAR), etc. anyway. I like the form: "verbNoun", like "setVariable" or "checkPermissions" just fine, but I think the decision will be made by the incoming code. _alex |
|
From: Andreas A. <a.a...@th...> - 2001-05-13 19:19:26
|
Hi Alex, > The private method thing is a standard. Agreed. This is also the I use it. > /index.php?.foo=hello and get in php: $_foo > which is quite useful, because you have a good way of always identifying > what came in frmo the user, as opposed to "internal" variables. Ok, good point. I did not consider that. Actually I was not aware that the dot is translated to an undescore. Never used that this way. > It's _very_ important to have a variable naming domain that identifies user > input, in my opinion. Yuup. Better than only importing variables formerly defined as valid user vars. Ok got that. $_global is good, at the cost of strange looking, but thats worth it. > But again, for those of you with suggestions, etc please speak up. Some of > the code it written, but I'm happy to change it. Ok. My suggestion is to use straight forward naming of methods and varnames: Methods: setName() or set_name() privat class methods: _setName() or _set_name() Variables (global) , as discussed before: $_varName or $_var_name Variables (other): $varName or $var_name Classnames: Auth, ExecutionTimer Personally I prefer the setName and $_varName, $varName case. Becaus the seperations is more clear. Usage of "_" only for the extra "namespace" and for private class methods, not for seperation. But thats personal taste I guess. Important is to have a standard. > heh, your app framework is called storm - which is the name of the > binarycloud admin interface. Yes, the name is borrowed (hope you don't kill me for that ;-)). Actually, it's not a full working framework. Currently it's a colletion of libs I need for smaller projects (metabase, smarty, template abstraction, session abstraction, some language specific files) as a intermediate until bc r2 is usable :-) I also see why you find the $_global_variable_name standard yucky, because you have it defined just the opposite in your docs. Hehe ;-) > convention. I have used .var with good results, it's easier to track the > security of a codebase. Ok, you convinced me in this point. Andi |
|
From: alex b. <en...@tu...> - 2001-05-13 18:21:21
|
> Cool. Great work. But think the code conventions are a bit confusing (to > me). For example. The mehtod names are named like: "Set_Name". The > uppercase/lowercase thing seperates engough, so why add a "_"? and why start > with a capital letter (classnames already start with a capital letter). To > me it's more smooth to name functions that way: > > public: setName(); ( $obj->setName() vs. $obj->Set_Name() ) > private: _setName(); > > or that way: > > set_name(); > _set_name(); > > You alread do: $_my_variable_name vs. $_myvariablename. That should be in > line with the other naming conventions. I'm actually open to changing those, assuming there is a general consensus here on what they _should_be. > Also the global vairable naming. Varibale names starting with a _ are > global. On the other hand methods starting with a _ should be considered as > private!? Could be a bit confusing - ok its another context but not very > linear, in my mind. The private method thing is a standard. The reason for the global standard (and yeah, I thought of that, i.e. it might be a little strange) is because you can put: /index.php?.foo=hello and get in php: $_foo which is quite useful, because you have a good way of always identifying what came in frmo the user, as opposed to "internal" variables. It's _very_ important to have a variable naming domain that identifies user input, in my opinion. > At the this is not really as important as other topics. It's important the > the conventions (no matter in what form they are applied) are constantly > used. > > So what does the community think? Right, funnily enough it's almost more important that there _is_ a standard :) But again, for those of you with suggestions, etc please speak up. Some of the code it written, but I'm happy to change it. Also, in the near future, I will push the r2 core cvs out to binarycloud.com, where I will continue development pubically. For those interested in participating, I'll set up accuonts for pserver. There will be a running install of binarycloud r2 w/MySQL on that box. > -- > BTW: I'm working on a set of code standards for our internal projects. They > are heavyly based on PEAR and the Java Code Standards which I think are a > good base to work with. We "ported" them to PHP. You can download them here: > http://www.thyrell.de/info/downloads/CodeGuide.pdf heh, your app framework is called storm - which is the name of the binarycloud admin interface. I also see why you find the $_global_variable_name standard yucky, because you have it defined just the opposite in your docs. This is one of the few things I consider to be quite important, actually: some simple, easily identifyable "this is coming from the outside" naming convention. I have used .var with good results, it's easier to track the security of a codebase. _alex |
|
From: alex b. <en...@tu...> - 2001-05-13 17:59:55
|
> I am wondering if there is a simple step by step short tutorial on how
> to use binarycloud ?
There is not, as yet. That's one of the things I will be adding with r2.
> How many people apart from the author have managed to understand and use
> it?
A number, there are at least 50 functioning installations of the system out
there. Probably more than that given the number of downloads.
In any case, if you're having trouble getting a good feel for what's going
on, feel free to ask questions on the list, that's what it's here for.
Some good places to start:
/user/conf/defined_constants.conf (this is where all configuration
constants go)
/user/conf/file_permissions.conf (this is the array of URIs used by the
permissions system, to control access to the skeleton site)
/user/mod/static_pages/static_pages.php (this is a very simple module)
/path/to/htdocs/index.php (a very simple "page")
best,
_alex
|
|
From: alex b. <en...@tu...> - 2001-05-13 17:55:55
|
r2 "core" i.e. the basic auth, perm, dispatch etc will be available fairly soon, I expect within the month. the Managers and other stuff (while some of that code exists and is in production) are harder to put a target date on, but I'd say not too long after that. also, keep in mind that almost everything I'm doing with r2 is additive - I'm not scrambling the whole system and doing things completely different. best, _alex ----- Original Message ----- From: "Jim Harlindong" <ji...@ha...> To: <bin...@li...> Sent: Sunday, May 13, 2001 1:52 AM Subject: RE: [binarycloud-dev] R1 or r2? > I just don't want to spend time to learn it only to relearn another > thing again.... When can r2 be usable? > > Thanks > > > > > I suggest you download binarycloud r1b, and set that up. > > > > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > http://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
5 messages has been excluded from this view by a project administrator.
