binarycloud-dev — development list for binarycloud

[binarycloud-dev] ugh, module caching is done

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

agh, just spent an hour hunting a stupid bug....

but, finally, I can go eat lunch. and Module caching works.

so, now you can cache page output by request uri and variable value, and
cache module output by name, optionally uri, and variable value.

I'll do a sync now.

_a

RE: [binarycloud-dev] Charlie's back...

[Charlie K. <Ch...@Al...>]

Well Alex, it's good to be back. 
One can only take so much vacation :)

Charlie

[binarycloud-dev] Charlie's back...

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

hi all,

he probably won't love this but I thought I should tell you all that the
primary coders on binarycloud r1 has just subscribed to the list...

welcome back, Charlie :)

best,

_alex

Re: [binarycloud-dev] "it begins"

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

ok, good.

so, I'm going to do some synchs today, and start cleaning the EntityManager.
if possible I will check in QueryManager today. (I think that might actually
be possible)

----------

What needs to be done to Querymanager:
    -PHPDoc'ing (some mods, it's already mostly compliant)
    -Integration with datasource definitions, some minor changes to the api
to support a datasource id.

    -Extremely minor changes to hook up metabase.

This should not be very much work, none of those tasks is particularly
complex. :)

> Alex Black wrote:
>> I'd like to get a sense of who is up for some serious work associated with
>> this project, completing modifications and new code to and for the manager
>> classes.
> 
> i've been dreaming about a stable binarycloud-1.0 for some time now, so
> count me in. =] i'm very interested in the entity manager esp. with it's
> relationship to database schemas.
> 
> jason

best,

_alex

Re: [binarycloud-dev] entity definition format

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

> -- Quoting the R2 draft spec --
> Default ui controls are assigned to each entity based on its type
> declaration, which means the system is capable of generating default
> forms.

Oh, really!

Heh, apparently I have already thought of this! :)

> To facilitate such a great feature, it would be required to define these
> markup values in the entity definition.  I would like to see the
> defaults defined here, as you mentioned, but tolerant for overriding
> values in the templates.

Which is exactly what I had envisioned. I don't view it as a 'breach of
style' to have UI components associated with fields in an entity definition.

Imagine defining a set of xml files, and being able to basically say "ok,
make me a set of database tables and default modules + pages" and _bing_ a
default site is built for you, which you can take and customize to fit the
application.


> jason
> 
> 
> Andreas Aderhold wrote:
>>>> 2. i noticed <maxlength> which i can forsee being used for setting a
>>>> maxlength in a input field (HTML), and for possibly determining the
>>>> field length in the database.  (is this correct?)  BUT, there was no
>>> 
>>> Correct on both accounts.
>>> 
>>>> LENGTH value anywhere.  if HTML forms are to be built on the entities,
>>>> having a MAXLENGTH as well as a LENGTH would be desired.
>>> 
>>> Yes, I see your point. I was toying with the idea of associating
>>> UI controls with each field type. That may still happen, so:
>>> <!-- look here -->
>>>             <uicontrol>
>>>                 <name>TextField</name>
>>>                 <params>
>>>                     <length>20</length>
>>>                 </params>
>>>             </uicontrol>
>>>         </field>
>> Hmm. But isn't that markup stuff something for the template engine/up to the
>> designer? I'm not quite sure if integrating the UI stuff with the entities
>> is wise or not.
>> Imagine you use the size/length attribute of an input field within more
>> contextes. So you have a from_a with size="20" is fine, in form_b using the
>> same entitiy size="20" does not fit, you need size="40" in form_c you need
>> style="width: 80px" and the so on...
>> Ok, maybe you can override this in the template and the etydef values are
>> defaults or whatever. Anyway, I think markup stuff does not belong here.
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
> 

Re: [binarycloud-dev] "it begins"

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

> Hi,
> 
>> I'm going to start putting EntityManager and its associated infrastructure
>> into CVS.
> Wow, that was damned fast :-)
> 
>> I'd like help getting all of those tools:
>>     -into the code standards
>>     -cleaned (entitymanager needs to have about 3/4 of the methods just
>> _removed_, we need to go through that code in detail to verify what is
>> necessary and what is not.
> Once I understood the code I can do something.
> 
>> QueryManager is pretty much ready out of the box, I'd like to have a
>> functional QueryManager by the end of next week (and I think
>> that's doable).
> Huuuuuu. Great.
> 
>> Anyway: for those of you interested in doing some heavy lifting
>> with me, let me know.
> Here I volunteer to help bringing the stuff up and running.
> 
> Andi

Fantastic.

Re: [binarycloud-dev] entity definition format

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

> Hmm. But isn't that markup stuff something for the template engine/up to the
> designer? I'm not quite sure if integrating the UI stuff with the entities
> is wise or not.

It would never be a requirement. The reason it could be useful, is you could
pass an entity name into a default module, and get a complete form out (the
module would use entitytmanager to get data, and pass that data to the
editor) or list, etc.

If the entity carried what UI components it should use, there would be no
"extra" information needed.

You can make some basic assertations about a field, i.e. "this is usually
going to be a textbox that's 20 chars long." if you don't explicitly define
that 'format' then the default is assumed and you can continue about your
business.

Editor also makes pretty good "guesses" about what UI components to use if
they aren't defined.

> Imagine you use the size/length attribute of an input field within more
> contextes. So you have a from_a with size="20" is fine, in form_b using the
> same entitiy size="20" does not fit, you need size="40" in form_c you need
> style="width: 80px" and the so on...
> Ok, maybe you can override this in the template and the etydef values are
> defaults or whatever. Anyway, I think markup stuff does not belong here.

a) there isn't markup there
b) yes, that part is "overridable"

>>> 3. could you explain a field PATH a bit?
>> path is sort of like the way you ref a table.field_name in sql:
>> location.locationid is an entity path that points to a field in an entity.
>> it could also be a sql table_name.field_name path - it's intentionally
>> similar.
> Extremely nice.
> 
> <required>
> Antoher question. Does the <required /> tag mean "not null" in the database
> only or with the form? I think this should not be combined, caus there are
> applications you have the db-field defined "not null" (requried) but no
> input value coming from the ui whatever, not required or not present.
> </required>

Usually, yes. Not always.

For example, you may want to have a entity posts always contain data, but
some other source is posting data that has fields missing. I can see use in
having separate "settings" for the database and the app.

best,

_alex

Re: [binarycloud-dev] "it begins"

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

> On Wed, 15 Aug 2001, Alex Black wrote:
> 
>> 
>> Next Monday, I'm going to check in initial, cleaned copies of:
>> 
>>     -EntityManager
>>     -Querymanager
>>     -UIControls
>>     -Template
>>     -OwnedObjectManager
>>     -ManagerFactory
>>     -HierarchicalEntityManager
>>     -ent2qry
>> 
> 
> Saweet.
> 
> You will want to do bring in the Editor at the same time I think, because the
> EntityManager is a rather difficult piece of code to test without an Editor or
> a Lister. Since the Lister is in the midst of a rebuild, I'd say don't bother
> with that..

Good point.


>> I'd like help getting all of those tools:
>>     -into the code standards
>>     -cleaned (entitymanager needs to have about 3/4 of the methods just
>> _removed_, we need to go through that code in detail to verify what is
>> necessary and what is not.
>> 
> 
> Haha, come on! It will only be 25% as cool..

:)

_a

Re: [binarycloud-dev] "it begins"

[Jason H. <jc...@ey...>]

Alex Black wrote:
> I'd like to get a sense of who is up for some serious work associated with
> this project, completing modifications and new code to and for the manager
> classes.

i've been dreaming about a stable binarycloud-1.0 for some time now, so
count me in. =] i'm very interested in the entity manager esp. with it's
relationship to database schemas.

jason

Re: [binarycloud-dev] entity definition format

[Jason H. <jc...@ey...>]

-- Quoting the R2 draft spec --
Default ui controls are assigned to each entity based on its type
declaration, which means the system is capable of generating default
forms.



To facilitate such a great feature, it would be required to define these
markup values in the entity definition.  I would like to see the
defaults defined here, as you mentioned, but tolerant for overriding
values in the templates.


jason


Andreas Aderhold wrote:
> > > 2. i noticed <maxlength> which i can forsee being used for setting a
> > > maxlength in a input field (HTML), and for possibly determining the
> > > field length in the database.  (is this correct?)  BUT, there was no
> >
> > Correct on both accounts.
> >
> > > LENGTH value anywhere.  if HTML forms are to be built on the entities,
> > > having a MAXLENGTH as well as a LENGTH would be desired.
> >
> > Yes, I see your point. I was toying with the idea of associating
> > UI controls with each field type. That may still happen, so:
> > <!-- look here -->
> >             <uicontrol>
> >                 <name>TextField</name>
> >                 <params>
> >                     <length>20</length>
> >                 </params>
> >             </uicontrol>
> >         </field>
> Hmm. But isn't that markup stuff something for the template engine/up to the
> designer? I'm not quite sure if integrating the UI stuff with the entities
> is wise or not.
> Imagine you use the size/length attribute of an input field within more
> contextes. So you have a from_a with size="20" is fine, in form_b using the
> same entitiy size="20" does not fit, you need size="40" in form_c you need
> style="width: 80px" and the so on...
> Ok, maybe you can override this in the template and the etydef values are
> defaults or whatever. Anyway, I think markup stuff does not belong here.

RE: [binarycloud-dev] entity definition format

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

Hi Alex,

> > 2. i noticed <maxlength> which i can forsee being used for setting a
> > maxlength in a input field (HTML), and for possibly determining the
> > field length in the database.  (is this correct?)  BUT, there was no
>
> Correct on both accounts.
>
> > LENGTH value anywhere.  if HTML forms are to be built on the entities,
> > having a MAXLENGTH as well as a LENGTH would be desired.
>
> Yes, I see your point. I was toying with the idea of associating
> UI controls with each field type. That may still happen, so:
> <!-- look here -->
>             <uicontrol>
>                 <name>TextField</name>
>                 <params>
>                     <length>20</length>
>                 </params>
>             </uicontrol>
>         </field>
Hmm. But isn't that markup stuff something for the template engine/up to the
designer? I'm not quite sure if integrating the UI stuff with the entities
is wise or not.
Imagine you use the size/length attribute of an input field within more
contextes. So you have a from_a with size="20" is fine, in form_b using the
same entitiy size="20" does not fit, you need size="40" in form_c you need
style="width: 80px" and the so on...
Ok, maybe you can override this in the template and the etydef values are
defaults or whatever. Anyway, I think markup stuff does not belong here.

> > 3. could you explain a field PATH a bit?
> path is sort of like the way you ref a table.field_name in sql:
> location.locationid is an entity path that points to a field in an entity.
> it could also be a sql table_name.field_name path - it's intentionally
> similar.
Extremely nice.

<required>
Antoher question. Does the <required /> tag mean "not null" in the database
only or with the form? I think this should not be combined, caus there are
applications you have the db-field defined "not null" (requried) but no
input value coming from the ui whatever, not required or not present.
</required>

Andi

RE: [binarycloud-dev] "it begins"

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

Hi,

> I'm going to start putting EntityManager and its associated infrastructure
> into CVS.
Wow, that was damned fast :-)

> I'd like help getting all of those tools:
>     -into the code standards
>     -cleaned (entitymanager needs to have about 3/4 of the methods just
> _removed_, we need to go through that code in detail to verify what is
> necessary and what is not.
Once I understood the code I can do something.

> QueryManager is pretty much ready out of the box, I'd like to have a
> functional QueryManager by the end of next week (and I think
> that's doable).
Huuuuuu. Great.

> Anyway: for those of you interested in doing some heavy lifting
> with me, let me know.
Here I volunteer to help bringing the stuff up and running.

Andi

Re: [binarycloud-dev] "it begins"

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

On Wed, 15 Aug 2001, Alex Black wrote:

> 
> Next Monday, I'm going to check in initial, cleaned copies of:
> 
>     -EntityManager
>     -Querymanager
>     -UIControls
>     -Template
>     -OwnedObjectManager
>     -ManagerFactory
>     -HierarchicalEntityManager
>     -ent2qry
> 

Saweet.

You will want to do bring in the Editor at the same time I think, because the
EntityManager is a rather difficult piece of code to test without an Editor or
a Lister. Since the Lister is in the midst of a rebuild, I'd say don't bother
with that..

> I'd like help getting all of those tools:
>     -into the code standards
>     -cleaned (entitymanager needs to have about 3/4 of the methods just
> _removed_, we need to go through that code in detail to verify what is
> necessary and what is not.
> 

Haha, come on! It will only be 25% as cool..

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] Practical use of r2

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

On Wed, 15 Aug 2001, Phillip Smith wrote:

> 
> 
> Specifically, there is an existing open source project [ Ministry of
> Truth - http://mot.sourceforge.net ] that is no longer being actively
> maintained.  I am giving serious thought to picking up development
> because I've not found any other software that fills the same niche,
> and because I've spoken with the original author who has encouraged me to
> do so. The problem with this is that I am not comfortable with the way its
> idea/essence is currently implemented, and would really want to rebuild it
> from the ground up (the TODO and feature list is long, and it seems pointless
> to try re-inventing the wheel with what's there).  For those that don't
> care to visit the website, MOT currently allows one to group db tables/fields
> relationally into larger more useful things (e.g project tracking,
> hardware/software inventory, etc.), all without having to know anything about
> html/php/sql (given that it was originally written in 1998 and includes its
> own built-in XML parser, it's still an impressive and usable piece of
> software).
> 

There is actually some overlap as far as which capabilities each project
provides. I think we've implemented a lot of MoT's lower-level functionality,
but there are definetly key pieces missing, notably user (read: web based)
creation and management of tables (which means user creation of entities). At
this point all entities are created by the developer at development time.
That's a pretty big jump.  

I could almost see MoT as filling two roles: both the role in which it is
currently used, and for actually simplifying development of binarycloud
applications, by allowing developers to create tables and entities through a
nice interface. 


Here is the MoT features list, with my comments after each:

The ability to create and modify databases, tables, fields, and permissions,
all from a point and click, web interface. 

(jd: I've never thought of having an entity represent a tablespace as opposed
to a table. I'm going to have to think about this, but it would probably make
an interesting extension)

Support for links between tables. Jobs may be linked to users, equipment, and
software. People may be linked to department, companies, contacts, and
machines. 

(jd: entities are structured objects. One entity can nest another, partially or
fully, so this is part of what r2 will provide with the entitymanager. Giving
users the ability to define their own entities would be another interface that
doesn't exist now, however)

Support for multiple users and read, add, and modify permissions for each user
for each table. 

(jd: the permissions system conceptualized for bc is amazing, incorporating
very complex session management and a notion of roles (user-created definitions
of permissions). it's also vaporware at the moment)

Support for sorting and restricting every table to a fully configurable set of
fields (sort a list of jobs by priority, close date, or tech, or restrict the
same list of jobs to a specified contact). 

(jd: this is completely provided for by our lister class, another forthcoming
part of r2. It also does filtering on a per-field level)

Support for actions, which are custom scripts automatically fired by specified
database actions (adds, modifications, etc.). This is immensely helpful for
implementing things like email notification and timestamping. 

(jd: we have the notion of events in the entitymanager, which are
add()/delete()/set()/get() etc.. A developer can associate functions to be
called with a specific entity's events. The way we do this now is by
subclassing and extending the base entitymanager for that specific entity. This
might be too heavy-handed so another approach may be necessary, hrmm..)

Basic support for writing custom sql queries. This will eventually include a
custom query page but is very helpful now in the creation of actions. A sample
mot_sql query that joins three tables together and grabs a value from the third
table looks like: select {People}.[email] from {Jobs} <Users> <Personal
Information> where {Jobs}.[id] = $row_id 

(jd: we have a standard set of queries associated with every entity that are
generated as part of a developer's 'make' process. There isn't a clean way to
do custom entity-related queries right now, but this only requires minor
re-engineering. Instead of having people write custom queries, it would be much
cooler to have them write XML-based views, at least for selects)

Support for importing and exporting database schemas. 
(jd: no idea. I hate databases anyway. Especially Oracle.)

Support for database-specific help files. All you have to do is write the text. 
(jd: see above)

(jd: just kidding. We currently can export any entity to XML, and from there an
XSL transform takes it to CSV or PDF. Pretty fucking slick. You can export
either lists or single objects.)

Basic searching capabilities. 
(jd: not something we've ever needed in our application, so I haven't really
thought about this. you can effectively 'search' a lister with filters, but not
more than one entity at a time..)

CSS support for configuring the interface. 
(jd: no idea)


I think there is a good synergy between these two pieces of software. I
definetly think you'd get more (as long as you're willing to wait :)) out of
binarycloud than you would out of something like Horde.. 

-- 

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] "it begins"

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

hi all,

I'm going to start putting EntityManager and its associated infrastructure
into CVS. Many of the supporting classes are going to require very little
work to get them functioning within binarycloud, the notable, 2000 line
exception to that is EntityManager.

I'd like to get a sense of who is up for some serious work associated with
this project, completing modifications and new code to and for the manager
classes.

I'd like to have a functioning set of managers in 6 weeks, I think that's
entirely doable if I have help - and there is certainly the talent on this
list to do it :)

Next Monday, I'm going to check in initial, cleaned copies of:

    -EntityManager
    -Querymanager
    -UIControls
    -Template
    -OwnedObjectManager
    -ManagerFactory
    -HierarchicalEntityManager
    -ent2qry

I'd like help getting all of those tools:
    -into the code standards
    -cleaned (entitymanager needs to have about 3/4 of the methods just
_removed_, we need to go through that code in detail to verify what is
necessary and what is not.

QueryManager is pretty much ready out of the box, I'd like to have a
functional QueryManager by the end of next week (and I think that's doable).

Anyway: for those of you interested in doing some heavy lifting with me, let
me know.

best,

_alex

Re: [binarycloud-dev] entity definition format

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

> the entity declaration makes good sense to me, though i have a few
> questions and concerns.
> 
> 1. within <field>, your example showed TEXT and POINTER.  could we get a
> list of these 'application' types w/ descriptions?

don't exist yet.
I imagine email, text, dna_sequence, phone_number, date, etc.
It would be extensible with user 'types' - we'll have a set of default ones
that come with the system. They'd be simple classes that do validation.

> 2. i noticed <maxlength> which i can forsee being used for setting a
> maxlength in a input field (HTML), and for possibly determining the
> field length in the database.  (is this correct?)  BUT, there was no

Correct on both accounts.

> LENGTH value anywhere.  if HTML forms are to be built on the entities,
> having a MAXLENGTH as well as a LENGTH would be desired.

Yes, I see your point. I was toying with the idea of associating UI controls
with each field type. That may still happen, so:


        <field>
            <name>furbee_type_id</name>
            <label>Furbee type ID</label>
            <desc>The id of the type of furbee</desc>
            <path>furbee_type_id</path>
            <required>true</required>
            <type>
                <dbtype>int</dbtype>
                <!--
                note the "pointer" type
                this field is a pointer to another entity, and a
                foreign key in the database
                -->
                <type>pointer</type>
                <!--
                form above, the entity name to use for requesting
                data from this pointer
                -->
                <entity>furbee_type</entity>
                <maxlength>20</maxlength>
                <format>/[\w\s_\-\.]{0,20}/</format>
            </type>
<!-- look here -->
            <uicontrol>
                <name>TextField</name>
                <params>
                    <length>20</length>
                </params>
            </uicontrol>
        </field>


> 3. could you explain a field PATH a bit?

path is sort of like the way you ref a table.field_name in sql:
location.locationid is an entity path that points to a field in an entity.
it could also be a sql table_name.field_name path - it's intentionally
similar.

the idea is to be able to ask FormBuilder to make you a form for an entire
entity, or just a set of fields in that entity by passing in entity paths.

> .. beautiful sh*t you have going on here. =]

thanks :)

This isn't all mine, I was on the right track but odysseas, john donagher,
and john campbell are the masterminds behind the original entitymanager.

I'm making tweaks to some of the design so it's less application specific,
and more "metabase integrated" if that makes sense.

:)

_alex

> jason

Re: [binarycloud-dev] entity definition format

[Jason H. <jc...@ey...>]

the entity declaration makes good sense to me, though i have a few
questions and concerns.

1. within <field>, your example showed TEXT and POINTER.  could we get a
list of these 'application' types w/ descriptions?

2. i noticed <maxlength> which i can forsee being used for setting a
maxlength in a input field (HTML), and for possibly determining the
field length in the database.  (is this correct?)  BUT, there was no
LENGTH value anywhere.  if HTML forms are to be built on the entities,
having a MAXLENGTH as well as a LENGTH would be desired.

3. could you explain a field PATH a bit?


.. beautiful sh*t you have going on here. =]

jason

[binarycloud-dev] entity definition format

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

hi all,

this is a large xml file, sorry... but this is a near-final entity
definition format for r2.

have a read, let's discuss this and get it final :)

best,

_alex

--------------------------------

<entity>

    <!--
    the name of the entity
    -->    
    <name>furbees</name>
    
    <!--
    db-related stuff for compatibility with metabase.
    this allows for auto-generation of metabase schema
    files from entity definitions
    -->
    <database>
        <!--
        the db name to use when creating
        tables or databases
        -->
        <name>binarycloud_db</name>
        <!-- create the database? -->
        <create>0</create>
        
        <!-- the table this entity references -->
        <table>
            <!-- table name -->
            <name>furbee</name>
            <!-- an index declaration for the primary key -->
            <index>
                <name>furbee_id</name>
                <unique>1</unique>
                <field>
                    <name>furbee_id</name>
                </field>
            </index>
        </table>
        <!-- a database sequence for the primary key -->
        <sequence>
            <name>furbee_id</name>
            <start>1</start>
            <on>
                <table>furbee</table>
                <field>furbee_id</field>
            </on>
        </sequence>
    </database>
    

    <!--
    field definitions are the 'heart' of an entity
    these definitions carry all of the information
    necessary to create schemas, do validation,
    and label fields in html.
    -->
    <fields>
        <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>
            <type>
                <!-- is this the default field in the db table? -->
                <default>0</default>
                <!-- can the field be null? -->
                <notnull>1</notnull>
                <!-- what is the simple, 'database' type of this field? -->
                <dbtype>text</dbtype>
                <!-- what is the complex 'application' type of this field?
-->
                <type>text</type>
                <!--
                if you don't understand the difference between dbtype and
type,
                an email address is put in a text field in a db, but must be
                validates as an email address.
                -->
                <!-- the maximum number of chars allowed in input fields and
posts -->
                <maxlength>20</maxlength>
                <!-- a regex pattern which will be run against input -->
                <format>/[\s\w_\-\.]{1,20}/</format>
                <!--
                note that type declarations will carry some regex from the
system
                by default, for example we will have an "email" type which
                automatically does validation for you.
                -->
            </type>
        </field>
        <field>
            <name>furbee_type_id</name>
            <label>Furbee type ID</label>
            <desc>The id of the type of furbee</desc>
            <path>furbee_type_id</path>
            <required>true</required>
            <type>
                <dbtype>int</dbtype>
                <!--
                note the "pointer" type
                this field is a pointer to another entity, and a
                foreign key in the database
                -->
                <type>pointer</type>
                <!--
                form above, the entity name to use for requesting
                data from this pointer
                -->
                <entity>furbee_type</entity>
                <maxlength>20</maxlength>
                <format>/[\w\s_\-\.]{0,20}/</format>
            </type>
        </field>
    </fields>

    <!--
    this should only be required to map old schemas to entities -
    under normal circumstances the fields should match names
    the entsource field is the path to the entity field, the
    dbtarget is the path to the database field.
    -->
    <schema>
        <map>
            <entsource>furbee_type_id</entsource>
            <dbtarget>furbee.furbeetypeid</dbtarget>
        </map>
    </schema>

</entity>

Re: [binarycloud-dev] CVS cache stuff and xmlutils missing

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

yes, I didn't sync last night, I need to do a major sync... later today I'll
mail the list re: that.

_a

> Hi Alex,
>
> the cache stuff (CacheManager etc) and the xmlutils seem to be missing in
> the sf cvs. At least the dont checkout and they don't show with the cvsweb
> interface at sf.
>
> Andi

Re: [binarycloud-dev] Practical use of r2

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

> Specifically, there is an existing open source project [ Ministry of
> Truth - http://mot.sourceforge.net ] that is no longer being actively
> maintained.  I am giving serious thought to picking up development
> because I've not found any other software that fills the same niche,
> and because I've spoken with the original author who has encouraged me to
> do so. The problem with this is that I am not comfortable with the way its
> idea/essence is currently implemented, and would really want to rebuild it
> from the ground up (the TODO and feature list is long, and it seems
pointless
> to try re-inventing the wheel with what's there).  For those that don't
> care to visit the website, MOT currently allows one to group db
tables/fields
> relationally into larger more useful things (e.g project tracking,
> hardware/software inventory, etc.), all without having to know anything
about
> html/php/sql (given that it was originally written in 1998 and includes
its
> own built-in XML parser, it's still an impressive and usable piece of
> software).

Sounds cool.
Also sounds like it has great potential for integration with metabase,
because of metabase's xml schema definition format.

> r2 would appear to be a candidate for a new MOT framework (other
> possibilites might be Horde [ http://www.horde.org/ ]), but I have
concerns
> about how to create a distributable "product" based on it (MOT will
continue
> to be strictly GPL, of course).  I'm having difficulty envisoning how I
> would incorporate it in such a way as to minimize the setup requirements
for
> my user base.  For some, getting Apache and PHP installed is enough of a
> hurdle (not everyone uses .rpm or .deb based systems).  Would I say "you
> need Apache, PHP (plus all it's special dependencies), and r2 .. after you
> fight with that, you use MOT as a plug-in", or is there a recommended way
I
> could easily encapsulate r2's overhead into my configuration system?  I
would
> like to be able to say "Here's MOT.  Run the installer." once they have
> met the Apache/PHP requirement.

Oh, yeah, you could do that. It would require you to set up a stable config
you like of r2, do a build from the source tree, and distribute the build
tree with your installer.

It's entirely doable, keep in mind that the current r2 codebase is in
development, so it's not exactly focused on simple installation :)

> Second, how viable is r2 as a development platform right now?  Obviously
> it's still under heavy development, but is it becoming mature enough to
> start building production-quality applications?  I expect that it will
take

It's ready, now.
However: you will not have access to some of the more advanced tools that
will be available for the system in the next month or so. (EntityManager,
QueryManager, TableBuilder, FormBuilder)

> me a few weeks to spec out what I will include as part of the initial
rewrite
> of MOT (its existing functionality plus a subset of the TODO), so my
question
> is more focused on the "stable" parts of r2.  In other words, which
> components of MOT can I concentrate on re-implementing now using the least
> changing parts of r2?  The website/documentation doesn't give a clear
> indication of what's complete and what's not.. guess I can always dive
> in and find out though.

The module spec and page render pipeline are both mature. What remains is
extensions to the make system, and integrating managers + builders.

> Looking at the mailing list archives, I see that some of my questions
> are answered (lots of recommendations from Alex to use r2 over r1 at this
> point).  The recent "BC quick-start guide" thread is helpful, but I don't
> see anyone trying to use BC for something like this (most uses seem to be
> for custom website projects rather than a self-contained, portable web
> application).  Correct me if I'm wrong.

You are correct, but the system is designed to support any php app, so you
won't have a problem.

> Just to be clear, I'm not in a major hurry here.  If I was, then I would
go
> ahead and consider r1 and worry about the conversion issues later.  I get
> the feeling though that I will be able to plan my goals around r2's
> development cycle, and that enough of r2 is complete now.  It would be

Yes, you are correct.
R2, even at this stage, is more mature than r1. r1, while is is a functional
system, is almost an experiement: most of the code is procedural, the tools
aren't mature, etc.

R2 is much more heavily "designed" and while some of the code is still a
moving target, the system is stable and partially functional. You can build
modules for it, now.

> helpful to have some idea on the overall status and usability of specific
r2
> sections (documentation on all this once r2 is finished is great, but I
> would still like to start developing now), and I would appreciate general
> feedback from anyone who is currently using it to do productive things.
>
> Thanks in advance (I tried getting subscribed to bc-general to post
> this there instead, but sourceforge seems to be eating my confirmations
> at the moment).  Also, the BC website still states that bc-dev is for dev
> and support.  Apologies if this isn't the best place for my inquiry.

Heh, I shoud change that :)

These sorts of discussions are relevant here, btw.

:)

_a

Re: [binarycloud-dev] Using CVS for r2

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

it's already there:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/binarycloud/r2/

> Have you thought about installing a web front to the CVS?  Chora, the new
> one from Horde.org looks very nice - they are now using it on cvs.php.net
> and very good it is too.

Yeah, I like chora a _lot_, I wish they would use it on sf.net.

anyway, I'm going to establish a new cvs.binarycloud.com soon, and that will
have chora on it.

_a

[binarycloud-dev] CVS cache stuff and xmlutils missing

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

Hi Alex,

the cache stuff (CacheManager etc) and the xmlutils seem to be missing in
the sf cvs. At least the dont checkout and they don't show with the cvsweb
interface at sf.

Andi

Re: [binarycloud-dev] Using CVS for r2

[Alby L. <al...@th...>]

I was just kidding, there's nothing to be wary of. It really an easy install
that can be removed easily if you don't want it there - with nothing changed
in your system.

Alby

----- Original Message -----
From: "Peter Bowyer" <re...@f2...>
To: <bin...@li...>
Sent: Wednesday, August 15, 2001 3:24 AM
Subject: Re: [binarycloud-dev] Using CVS for r2


> At 05:16 PM 8/14/01 -0400, you wrote:
> >Dont be such a wimp Peter, the worst that'll happen is you'll learn
> >something.
>
> Yes I realise I'll learn something... however, I have 7.6 GB of data on my
> HD and only backups of 500Mb, so I can't afford to lose it :-)
>
> I also do not have a working knowledge of the Registry, so it hinders me a
> little (!) if I need to fix something :-(
>
> >Seriously though, its easy and if you mess up its easy to fix.
> >I've installed it several times, and its hasn't done anything to my
machine.
>
> I'll give it a go when I've got 3-4 hours to download the components (11Mb
> I think you said??)
>
> Peter.
>
>
> ---oOo---
> Do you sendcard? PHP e-card script supporting 9 databases!
> http://www.sendcard.f2s.com/
> ---oOo---
>
>
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>

RE: [binarycloud-dev] Using CVS for r2

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

Hi Alex,

> but what about _not_ using wincvs at all with cygwin, just using
> command-line cvs co -P pserver:... blah
Well that's the best compromise In my optinion. Under win as well as with
linux the best is command line and Emacs.

> but yeah, I'm definitely voting for "or should I just get a linux box?" :)
Harr harr, well that's the very best you can do :-)

Andi

Re: [binarycloud-dev] Practical use of r2

[TAO R. <ron...@ho...>]

>Greetings.
>
>I've been lurking on this list for awhile now, and have an interest
>in BC's capabilities.  I consider myself to be an intermediate PHP
>developer, and am contemplating the possibility of using r2 as the
>framework for a project.
>
>Specifically, there is an existing open source project [ Ministry of
>Truth - http://mot.sourceforge.net ] that is no longer being actively
>maintained.  I am giving serious thought to picking up development
>because I've not found any other software that fills the same niche,
>and because I've spoken with the original author who has encouraged me to
>do so.
I haven't read all details in that site, but I think the concept it quite
close the this product, PHPLens(http://phplens.com/)

roni

_________________________________________________________________
在 http://explorer.msn.com.tw/intl.asp 免費下載 MSN Explorer