binarycloud-dev — development list for binarycloud

RE: [binarycloud-dev] sync is done

[Andreas A. <a.a...@th...>]

Hi

> i thought i'd be the first to report that the Query_Example no longer
> works after this last CVS sync.
>
> Warning: Supplied argument is not a valid MySQL result resource in
> /home/jason/r2/binarycloud/build/en/ext/metabase/metabase_mysql.php on
> line 166

Guess, datasources has been overwritten. Debug should output errors beacuse
I used CaptureError() in case of errors and CaptureMessage() for
informations messages. But Debug does not output errors properly so you dont
get a descriptive err message.


Andi

Re: [binarycloud-dev] Revised entity definition xml

[John D. <jo...@we...>]

I think it makes most sense in the lister/editor definition for that entity.
These are presentation-oriented, whereas the entity definition was never really
meant to be. 

I'm not quite sure what you mean by default, every field has only one control
associated with it, which is determined based on the type. I could see
associating user-defined controls with user-defined types, or assigning a
custom control to a certain field. But in general it seems like type controls
aren't something people will have to do anything for when writing their editor,
only overriding with their custom field controls if necessary.

My $.02

John

On Tue, 21 Aug 2001, alex black wrote:

> >
> > > I like having the control definition in there, I think it's nice and
> > > convenient (and it gives you iron fisted control over default
> presentation)
> > >
> >
> > The entity definition really has nothing to do with presentation. I think
> even
> > the ptype is in the wrong place. These things are all meaningless to an
> XML
> > client, for example. Also, having a control definition inline like that
> means
> > it cannot be reused. I think that's evil :)
> 
> How would you do it?
> Assume the following:
>     -You want a default ui control assigned to each entity field
>     -you want to be able to assign them easily
> 
> where :)?
> 
> _a
> 
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
> 
> 

-- 

John Donagher
Application Engineer, Intacct Corp.

Public key available off http://www.keyserver.net
Key fingerprint = 4024 DF50 56EE 19A3 258A  D628 22DE AD56 EEBE 8DDD

Re: [binarycloud-dev] Is BinaryCloud ideal for me?

[alex b. <en...@tu...>]

> >Cool, and without even knowing more I can tell you that R2 with
> >EntityManager will save you untold amounts of time :)
>
> Can you give me an example?

Well, you won't have to write nearly as much sql.
All of your validation is taken care of for you implicitly by defining
entities and using the associated tools

(long list)

> >for example, you could build a single module that was responsible for
> >presenting 'farmer info' under different circumstances: a list of
farmers,
> >or a farmer detail, or a form for editing a farmer's information. - all
in
> >one module, which would accept a paramter for the 'mode' to use.
>
>  From the documentation, a module is a class that has an Init() and an
> Output() method. So, in your example, a 'mode' parameter would be passed
to

Init() is deprecated, it's the constructor now.

> Init() telling it what type of data I want to display. Init would query
the
> db using EntityManager to get the desired data.

yep

> Output() might then use some template from TemplateManager to build the
> presentation and output that as a bunch of HTML.

yep

> Am I on the right track?
>
> >tools like these don't exist anywhere else in the php community.
>
> It all sounds good, it's just that I'm still confused as to the steps I
> would take to build an application using bc, from start to finish. It
seems
> I have to create an XML database definition, create some modules with app
> logic, create some page definitions to build HTML content to display to
the
> user, and then do something with EntityManager and QueryManager to manage
> database interactivity.
>
> Where does UI Manager fit in?

It would look something like this:

    -Define a set of entity definitions in xml
    -That would automatically build a default set of queries, and DB schema.
     -Create modules with any logic you need, request or post date through
the EntityManager, use the FormBuilder and TableBuilder classes fro modules
to create presentation, etc.
    -Create page defs to embed the modules in pages.

So, yes, you are essentially correct.

_a

Re: [binarycloud-dev] PageDefBuilder

[alex b. <en...@tu...>]

> Ah. This was it. I was assuming the PageDefBuilder would build the
> entire page definition, not work with it if it existed.

I don't see a reason why it couldn't/shoudn't do both.

> >         -it uses the request_uri class to determine the forum name, and
puts
> > the ForumList module into the page def.
> >         -user clicks 'post' or soemthing, and gets sent to the 'normal
forum
> > post page elsewhere in htdocs.
>
> Sounds like the PageDefBuilder is going to need a few libraries.  What,
> besides handling URI's will it need to accommodate?
> And what would be example syntax of the url->module mapping?

I imagine it would actually take a 'custom' library for each case... it
would only really supervise the process.

So you'd write your own class that gets variables, etc and PageDefBuilder
would give you a simple way of assigning those values.

_a

> (it's now 68.33% clear in my mind)
> =]
>
> jason
>
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>

Re: [binarycloud-dev] Revised entity definition xml

[alex b. <en...@tu...>]

>
> > I like having the control definition in there, I think it's nice and
> > convenient (and it gives you iron fisted control over default
presentation)
> >
>
> The entity definition really has nothing to do with presentation. I think
even
> the ptype is in the wrong place. These things are all meaningless to an
XML
> client, for example. Also, having a control definition inline like that
means
> it cannot be reused. I think that's evil :)

How would you do it?
Assume the following:
    -You want a default ui control assigned to each entity field
    -you want to be able to assign them easily

where :)?

_a

Re: [binarycloud-dev] Is BinaryCloud ideal for me?

[Gerry K. <ge...@mc...>]

Thanks for your comments, Alex - some questions below.
Gerry

At 09:14 AM 14/08/01 -0700, you wrote:
> >
> > One example of how this system would be used is for the Agriculture
> > program. They work with thousands of farmers. Each farmer will have a
> > profile containing family, health, economic data. Each year, information
> > will be entered on projects to improve the farmer's health and economic
> > situation, e.g., growing a high-yield rice crop.
>
>Cool, and without even knowing more I can tell you that R2 with
>EntityManager will save you untold amounts of time :)

Can you give me an example?


>for example, you could build a single module that was responsible for
>presenting 'farmer info' under different circumstances: a list of farmers,
>or a farmer detail, or a form for editing a farmer's information. - all in
>one module, which would accept a paramter for the 'mode' to use.

 From the documentation, a module is a class that has an Init() and an 
Output() method. So, in your example, a 'mode' parameter would be passed to 
Init() telling it what type of data I want to display. Init would query the 
db using EntityManager to get the desired data.

Output() might then use some template from TemplateManager to build the 
presentation and output that as a bunch of HTML.

Am I on the right track?

>tools like these don't exist anywhere else in the php community.

It all sounds good, it's just that I'm still confused as to the steps I 
would take to build an application using bc, from start to finish. It seems 
I have to create an XML database definition, create some modules with app 
logic, create some page definitions to build HTML content to display to the 
user, and then do something with EntityManager and QueryManager to manage 
database interactivity.

Where does UI Manager fit in?

>best,
>
>_alex

Re: [binarycloud-dev] PageDefBuilder

[jason <ja...@gr...>]

Alex Black wrote:
>         -you create a normal page def for each page, but include
> PageDefBuilder.

Ah. This was it. I was assuming the PageDefBuilder would build the
entire page definition, not work with it if it existed.


>         -it uses the request_uri class to determine the forum name, and puts
> the ForumList module into the page def.
>         -user clicks 'post' or soemthing, and gets sent to the 'normal forum
> post page elsewhere in htdocs.

Sounds like the PageDefBuilder is going to need a few libraries.  What,
besides handling URI's will it need to accommodate?
And what would be example syntax of the url->module mapping?

(it's now 68.33% clear in my mind)
=]

jason

Re: [binarycloud-dev] Revised entity definition xml

[John D. <jo...@we...>]

On Mon, 20 Aug 2001, Alex Black wrote:

> 
> Is there any other place that ptype is used?
> 

I don't think so.

> I like having the control definition in there, I think it's nice and
> convenient (and it gives you iron fisted control over default presentation)
> 

The entity definition really has nothing to do with presentation. I think even
the ptype is in the wrong place. These things are all meaningless to an XML
client, for example. Also, having a control definition inline like that means
it cannot be reused. I think that's evil :)

John

-- 

John Donagher
Application Engineer, Intacct Corp.

Public key available off http://www.keyserver.net
Key fingerprint = 4024 DF50 56EE 19A3 258A  D628 22DE AD56 EEBE 8DDD

[binarycloud-dev] make errors with xml2php

[Alex B. <en...@tu...>]

hi Andris,

I'm getting this:

alex@core htdocs> make
/bin/sh: /home/alex/r2/binarycloud/build/en/htdocs: is a directory
make: *** [xml_page_def] Error 126
alex@core htdocs> 

I had a look at the makefiles, and I can't quite see what's wrong yet.

I've included them here, have a look.

best,

_alex

Re: [binarycloud-dev] Revised entity definition xml

[Alex B. <en...@tu...>]

> On Mon, 20 Aug 2001, Alex Black wrote:
> 
>>> I'm unclear on the above uicontrol element. You shouldn't need anything like
>>> that since it can be determined based on your field descriptions..
>> 
>> What about, for example, a password field?
>> You're putting that in a text field in the database, and doing some simple
>> validation on it like "can't contain tags or +8bit chars" but you aren't
>> explicitly marking it as "password"
>> 
> 
> Right .. so the way we have dealt with that thus far is you leave type set as
> 'text' and you have another type field (ptype) set as 'password', which means
> that the password control will be used as opposed to a generic text control
> for
> display/editing purposes, but internally the data is still stored as text.

Is there any other place that ptype is used?

I like having the control definition in there, I think it's nice and
convenient (and it gives you iron fisted control over default presentation)

_a

Re: [binarycloud-dev] sync is done

[Alex B. <en...@tu...>]

> 
> While this makes sense in theory, let me try and approach this from a
> different angle.
> 
> My train of thought is blocked by a lingering question on how modules
> will be distributed once BC is mainlined.

Tarballs with a simple installer.
There will be a distribution-packing utility that tars files assuming
binarycloud/ as the root of the tar.

> Are page definition (bcp.xml) files to be included with the module
> package?  While the easy answer may be "yes, why not",
> it also makes sense to allow for modules to be dropped in the module
> directory by themselves, so that the site-owners can add the new module
> to their _already existing_ page definitions where they see fit.

Yes, the pages will be included in the modules distro tarballs. You _should_
have a functional installation of a module that you can run in a browser
right after installation (including db setup + make)

And if you want to delete, move, etc htdocs (or module files) you can.

> The problem I see with replacing the $gPageDef declaration in the page
> definition is:
> 
> (begin scenerio)
> Let's say, my forum app uses this new PageDefBuilder to parse incoming
> URI's.  So this would mean that my forum app module package would
> contain a 'uri definition file' like you described.
> 
> Now, on my _already existing_ page definition where I have a navigation
> module, content management, whatever, I want a forum to appear at the
> bottom.  I would have to lose my existing $gPageDef array to make room
> for the new module which uses the PageDefBuilder.  Something just
> doesn't make sense here.
>
> My first idea/proposal here would be to create a new public method in
> $Page that gets passed the necessary info to handle the incoming URI and
> load up the right module.
> 
> I think this was a bit wordy, but it took some writing before my
> thoughts were clear.

That's effectively the same thing as PageDefBuilder. You could have
PageDefBuilder build only _part_ of your page definition (say, the 'forum'
group). :)

> To sum.. instead of a PageDefBuilder to replace the $gPageDef array, we
> add a $Page->BuildDynamicModule which acts as a gateway to launch a
> multi-module application, and the appropriate module is determined by
> comparing the incoming URI to an XML definition file in the module
> directory.

I still prefer the idea of PageDefBuilder, because page definitions to not
have to be built 100% - you can run it simply to _add_ some modules to a
page definition....

So, let's consider the possibilities:

    1) you want to run the forum 'alone' in its own location:
        forums/index.php
        -you create an apache alias for forum/* to forum/index.php
        -you create a 'request uri' class which is used by PageDefBuilder to
parse the request uri and build an array in $gPageDef.
        -You run $gPageDef through Page and get output.

    2) You want to have a forum for every single page on your site (hey,
possible right? :)

        -you create a normal page def for each page, but include
PageDefBuilder.
        -it uses the request_uri class to determine the forum name, and puts
the ForumList module into the page def.
        -user clicks 'post' or soemthing, and gets sent to the 'normal forum
post page elsewhere in htdocs.


I don't see a reason why that wouldn't work...

best,

-alex

Re: [binarycloud-dev] Revised entity definition xml

[Alex B. <en...@tu...>]

>> Now's the time for suggestions/comments/flames/rants/etc :)
> 
> You left out compliments.  This is looking nice and creamy.

:)

Re: [binarycloud-dev] Revised entity definition xml

[John D. <jo...@we...>]

On Mon, 20 Aug 2001, Alex Black wrote:

> > I'm unclear on the above uicontrol element. You shouldn't need anything like
> > that since it can be determined based on your field descriptions..
> 
> What about, for example, a password field?
> You're putting that in a text field in the database, and doing some simple
> validation on it like "can't contain tags or +8bit chars" but you aren't
> explicitly marking it as "password"
> 

Right .. so the way we have dealt with that thus far is you leave type set as
'text' and you have another type field (ptype) set as 'password', which means
that the password control will be used as opposed to a generic text control for
display/editing purposes, but internally the data is still stored as text.

John

-- 

John Donagher
Application Engineer, Intacct Corp.

Public key available off http://www.keyserver.net
Key fingerprint = 4024 DF50 56EE 19A3 258A  D628 22DE AD56 EEBE 8DDD

Re: [binarycloud-dev] Revised entity definition xml

[jason <ja...@gr...>]

> Now's the time for suggestions/comments/flames/rants/etc :)

You left out compliments.  This is looking nice and creamy.

Re: [binarycloud-dev] Revised entity definition xml

[Alex B. <en...@tu...>]

> On Mon, 20 Aug 2001, Alex Black wrote:
> 
>> 
>>     <!--
>>     This is the UI control that will be used by the FormBuilder class
>>     as a default. In this case, an <input type="text" size="20"> would
>>     result.
>>     -->
>>     <uicontrol>
>>         <name>TextField</name>
>>         <params>
>>             <size>20</size>
>>         </params>
>>     </uicontrol>
>> 
>> </field>
>> 
> 
> Overall I like it a lot. Things like validation functions I would like to see
> optionally associated with (user-defined) types for reusability's sake.

Exactly: I want a set of 'default' validation classes that come with the
system, but if you want to make your own, you can.

>Also,
> I'm unclear on the above uicontrol element. You shouldn't need anything like
> that since it can be determined based on your field descriptions..

What about, for example, a password field?
You're putting that in a text field in the database, and doing some simple
validation on it like "can't contain tags or +8bit chars" but you aren't
explicitly marking it as "password"

_a

Re: [binarycloud-dev] sync is done

[jason <ja...@gr...>]

While this makes sense in theory, let me try and approach this from a
different angle.

My train of thought is blocked by a lingering question on how modules
will be distributed once BC is mainlined.

Are page definition (bcp.xml) files to be included with the module
package?  While the easy answer may be "yes, why not",
it also makes sense to allow for modules to be dropped in the module
directory by themselves, so that the site-owners can add the new module
to their _already existing_ page definitions where they see fit.

The problem I see with replacing the $gPageDef declaration in the page
definition is:

(begin scenerio)
Let's say, my forum app uses this new PageDefBuilder to parse incoming
URI's.  So this would mean that my forum app module package would
contain a 'uri definition file' like you described.

Now, on my _already existing_ page definition where I have a navigation
module, content management, whatever, I want a forum to appear at the
bottom.  I would have to lose my existing $gPageDef array to make room
for the new module which uses the PageDefBuilder.  Something just
doesn't make sense here.

My first idea/proposal here would be to create a new public method in
$Page that gets passed the necessary info to handle the incoming URI and
load up the right module.

I think this was a bit wordy, but it took some writing before my
thoughts were clear.

To sum.. instead of a PageDefBuilder to replace the $gPageDef array, we
add a $Page->BuildDynamicModule which acts as a gateway to launch a
multi-module application, and the appropriate module is determined by
comparing the incoming URI to an XML definition file in the module
directory.

jason




Alex Black wrote:
> One of the things I would like to do is build a "PageDefBuilder" class which
> is capable of accepting some rules from a 'definition file' so you could do
> something like this:
> 
> setup an alias for htdocs/forum/* to htdocs/forum/index.php, which would
> allow you to receive requests like forum/post/1928374.
> 
> The page in htdocs/index.php would not contain module definitions: it would
> import PageDefBuilder, which would import a file from your module dir which
> tells it how to build up the module list (in this case, based on the request
> uri), put that array into $gPageDef - then import & run Page->BuildPage();
> 
> That would make your urls elegant (you can parse the request uri into an
> array which will tell you what modules to use, and still retain the ability
> to cache those module's output)

Re: [binarycloud-dev] Revised entity definition xml

[John D. <jo...@we...>]

On Mon, 20 Aug 2001, Alex Black wrote:

> 
>     <!--
>     This is the UI control that will be used by the FormBuilder class
>     as a default. In this case, an <input type="text" size="20"> would
>     result.
>     -->
>     <uicontrol>
>         <name>TextField</name>
>         <params>
>             <size>20</size>
>         </params>
>     </uicontrol>
> 
> </field>
> 

Overall I like it a lot. Things like validation functions I would like to see
optionally associated with (user-defined) types for reusability's sake. Also,
I'm unclear on the above uicontrol element. You shouldn't need anything like
that since it can be determined based on your field descriptions..

John

-- 

John Donagher
Application Engineer, Intacct Corp.

Public key available off http://www.keyserver.net
Key fingerprint = 4024 DF50 56EE 19A3 258A  D628 22DE AD56 EEBE 8DDD

[binarycloud-dev] Revised entity definition xml

[Alex B. <en...@tu...>]

hi all,

have a look at the attachment, I've made some revisions to the declaration
xml for the entity.

you'll notice some 'major' changes, in particular:

    <!--
    the manager which should be imported by EntityManager.
    the role of an individual Entity Manager is to check
    the data before a post to the DB happens. It allows
    developers to write complex rules for an entity into
    a class.
    -->
    <entity:manager>FurbeesManager<entity:manager>

I think that explains it: basically a class that will house complex rules
(inter-field relationships) for an entity. Not necessary in most cases, so
it's optional.

I've changed the field definition, it's more simple now because some things
have been 'moved out':

<field>
    <!-- the field name -->
    <name>furbee_id</name>
    <!-- the field label, or "full name" -->
    <label>Furbee ID</label>
    <!-- the description of the field -->
    <desc>Unique ID for ever Furbee</desc>
    <!-- the path in the entity -->
    <path>furbee_id</path>
    <!-- must this field be valid to do a post of this entity? -->
    <required>true</required>
    <!-- is this the default field in the db table? -->
    <default>0</default>
    <!-- can the field be null? -->
    <notnull>1</notnull>
 
*** note that 'type' is no longer an array, but is now just the <dbtype> tag
renamed.

    <!-- what is the simple, 'database' type of this field? -->
    <type>int</type>
    <!-- the maximum number of chars allowed in input fields and posts -->
    <maxlength>20</maxlength>
    <!--
    should whitespace be trimmed from the
    input before it is validated and processed?
    -->
    <trim>true</trim>
    <!-- a regex pattern which will be run against input -->
    <format>/[\s\w_\-\.]{1,20}/</format>


*** hopefully this is clear: processor classes will be passed field
contents, and return the contents of that field after running it through
some conditioning code.

    <!--
    Processors are classes which will contidion the input somehow.
    In this example, the class CharEntitiesProcessor would be
    imported by EntityManager and passed the input for this field.
    It would return the input run through htmlspecialchars() or maybe
    a custom method for encoding xml/html character entities.
    -->
    <processors>
        <processor>CharEntitiesProcessor</processor>
    </processors>

*** Validators allow devs to write complex application specific validation
classes for input, and allow "us" (binarycloud core) to build a complete set
of simple 'normal' validators for things like email addresses, phone
numbers, dates, etc. A lot of that code exists already, of course.

    <!--
    Validators are classes which are imported by entityManager
    as requested and run again input. There will be a default
    set of validators like EmailValidator, DNASequenceValidator, etc.
    These validators will be passed the input of the post in the
    sequence they are declared. Each validator will be run against
    the input, and return true or false. If false, entitymanager will
    return an error.
    -->
    <validators>
        <validator>FASTA_DNASequenceValidator</validator>
        <validator>NoTagsValidator</validator>
    </validators>

    <!--
    This is the UI control that will be used by the FormBuilder class
    as a default. In this case, an <input type="text" size="20"> would
    result.
    -->
    <uicontrol>
        <name>TextField</name>
        <params>
            <size>20</size>
        </params>
    </uicontrol>

</field>


I'm liking this now because it has a nice set of default 'simple' validation
rules (maxlength, trim, regex, etc) and plugs for validation of any
complexity in the form of classes. That combined with 'processors' I think
makes this as flexible as it needs to be.

Now's the time for suggestions/comments/flames/rants/etc :)

best,

_alex


--
alex black, ceo
en...@tu...

the turing studio, inc.
http://www.turingstudio.com

vox+510.666.0074
fax+510.666.0093

Re: [binarycloud-dev] QueryManager

[John D. <jo...@we...>]

Sounds like Andi got it working on Oracle without the hacks, so hopefully they
aren't necessary..

John

On Mon, 20 Aug 2001, Alex Black wrote:

> can you give me an idea of what kind of hacks besides lob?
> 
> _a
> 

-- 

John Donagher
Application Engineer, Intacct Corp.

Public key available off http://www.keyserver.net
Key fingerprint = 4024 DF50 56EE 19A3 258A  D628 22DE AD56 EEBE 8DDD

Re: [binarycloud-dev] sync is done

[Alex B. <en...@tu...>]

oh, good! :)

> 
> Apologies -- i was in a bit of a hurry.
> 
> CVS simply overwrote some configured stuff. doh.
> 
> It does work.
> jason
> 
>>> i thought i'd be the first to report that the Query_Example no longer
>>> works after this last CVS sync.
>>> 
>>> Warning: Supplied argument is not a valid MySQL result resource in
>>> /home/jason/r2/binarycloud/build/en/ext/metabase/metabase_mysql.php on
>>> line 166
>> 
>> hrm...
>> 
>> I haven't tested any of this, I'll do that and see what I see.
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
> 

Re: [binarycloud-dev] sync is done

[jason <ja...@gr...>]

Apologies -- i was in a bit of a hurry.

CVS simply overwrote some configured stuff. doh.

It does work.
jason

> > i thought i'd be the first to report that the Query_Example no longer
> > works after this last CVS sync.
> >
> > Warning: Supplied argument is not a valid MySQL result resource in
> > /home/jason/r2/binarycloud/build/en/ext/metabase/metabase_mysql.php on
> > line 166
> 
> hrm...
> 
> I haven't tested any of this, I'll do that and see what I see.

Re: [binarycloud-dev] sync is done

[Alex B. <en...@tu...>]

> 
> i thought i'd be the first to report that the Query_Example no longer
> works after this last CVS sync.
> 
> Warning: Supplied argument is not a valid MySQL result resource in
> /home/jason/r2/binarycloud/build/en/ext/metabase/metabase_mysql.php on
> line 166

hrm...

I haven't tested any of this, I'll do that and see what I see.

andreas?

> as for the document root side,  i have a question as to handle this.  i
> know either way will work, but i'm wanting to stay as conforming as
> possible while BC is still under development.
> 
> should i have this...:
> build/en/htdocs/forum/index.php      <- builds/imports
> build/en/htdocs/forum/list.php      <- builds/imports ForumList.php
> build/en/htdocs/forum/read.php      <- builds/imports ForumRead.php
> .
> .
> etc.
> which is working fine, although all the gPageDef is redundant.
> 
> OR this...:
> build/en/htdocs/forum/index.php      <- a switch looking for $mode which
> builds/imports the desired module such as ForumIndex.php,ForumList.php,
> etc...
> 
> this seems like a trivial question to ask, but i'm not exactly sure how
> module distribution is to be handled in the future.
> 
> i hope this is clear enough for a response.

yes, it is.

One of the things I would like to do is build a "PageDefBuilder" class which
is capable of accepting some rules from a 'definition file' so you could do
something like this:

setup an alias for htdocs/forum/* to htdocs/forum/index.php, which would
allow you to receive requests like forum/post/1928374.

The page in htdocs/index.php would not contain module definitions: it would
import PageDefBuilder, which would import a file from your module dir which
tells it how to build up the module list (in this case, based on the request
uri), put that array into $gPageDef - then import & run Page->BuildPage();

That would make your urls elegant (you can parse the request uri into an
array which will tell you what modules to use, and still retain the ability
to cache those module's output)
------

That's sort of fancy, but it makes your 'external face' to the world very
orderly and clean (and if your forums are public, search engine friendly,
not to mention easily memorable and bookmarkable.

Barring the above, the other way, i.e. a separate page with some duplicative
$gPageDef stuff is I think the best way to go.

If you're into it, you're welcome to build a PageDefBuilder class :) I'll
help :)

best,

_alex

Re:Re: [binarycloud-dev] QueryManager basically working

[Manuel L. <man...@uo...>]

Hello,

>>> I had to do a quick hack to the metabase_mysql driver to support
>> _ProcessResult properly (added GetColumnNames($result), to driver).
>> We have to modifiy the other metabase drivers (mSQL,PostgreSQL) too or=
 the
>> QueryManager (as I did in _GetNumCols). But I don't like abstraction t=
here,
>> it's cleaner to have a standard metabase installtion that supports the
>> following functions for fetching column names and count for a executed=
 query
>> (or something similar):
>>=20
>> MetabaseGetNumCols($database, $result)
>> MetabaseGetColNames($database, $result)
>>=20
>> This should be no problem. All DBMS as well as PHP support the functio=
nality
>> to archive this - it just has to be done. However for the moment it wo=
rks
>> for OCI and mysql (with the patch).
>
>Ok, cool.
>
>I think manuel is now subscribed to the list... manuel, what do you thin=
k?

Sounds good. Just send me the patches and I=B4ll integrate them in Metaba=
se.


Regards,
Manuel Lemos

RE: [binarycloud-dev] entity definition format

[Andreas A. <a.a...@th...>]

Hi  John,

> This seems like an example of a multi-lined "owned object".  I
> didn't go back and read the original mail, so I hope this is useful.
> There would be 3 entities: user, userinterest, interest.
Jepp, exactly.

> The owned object would be "userinterest", with a parententity of user.
> In the parent entity, you
> define how a parent relates to it's "owned objects" like this:
>
> 'ownedobjects' => array (
> 	'fkey'		=> 'PATH1', // from userinterest
> 	'invfkey'	=> 'PATH2', // from user
> 	'entity'	=> 'userinterest', // the ownedobject entity
> 	'path'		=> 'USERINTERESTS', // how to reference
> from the parent object
> )

Cool.

> Once all the meta data work is done, then all the linking of user and
> userinterests will be done automatically (thanks to ent2qry).  There will
> also be a ready made multiline UI for choosing interests to
> associate with this user (assuming the user layout file is correct).

Absolutely fantastic.

Andi

Re: [binarycloud-dev] sync is done

[jason <ja...@gr...>]

i thought i'd be the first to report that the Query_Example no longer
works after this last CVS sync.

Warning: Supplied argument is not a valid MySQL result resource in
/home/jason/r2/binarycloud/build/en/ext/metabase/metabase_mysql.php on
line 166



on a side note, i wanted to ask for a recommendation as to how to
implement a simple application under BC in regards to how to handle a
single module that uses multiple classes/libraries.  for example, i've
got a forum application underway with the following structure.

build/en/user/mod/forum/lib/Forum.php    <-  the required library
(included by the other files)
build/en/user/mod/forum/ForumIndex.php	 <-  forum listing, default page.
build/en/user/mod/forum/ForumList.php    <-  lists the messages in a
forum
build/en/user/mod/forum/ForumRead.php	 <-  displays a thread
build/en/user/mod/forum/ForumPost.php	 <-  to post a thread/reply

now, these classes each contain a constructor, and Output() method.  so
far so good, no troubles...

as for the document root side,  i have a question as to handle this.  i
know either way will work, but i'm wanting to stay as conforming as
possible while BC is still under development.

should i have this...:
build/en/htdocs/forum/index.php	  <- builds/imports 
build/en/htdocs/forum/list.php	  <- builds/imports ForumList.php
build/en/htdocs/forum/read.php	  <- builds/imports ForumRead.php
.
.
etc.
which is working fine, although all the gPageDef is redundant.

OR this...:
build/en/htdocs/forum/index.php	  <- a switch looking for $mode which
builds/imports the desired module such as ForumIndex.php,ForumList.php,
etc...

this seems like a trivial question to ask, but i'm not exactly sure how
module distribution is to be handled in the future.

i hope this is clear enough for a response.

jason




Alex Black wrote:
> Sync to sourceforge is done, you can update your checkouts :)