From: Alex B. <en...@tu...> - 2001-09-24 00:06:36
|
hi all, Did a bit of thinking about how we should go about getting Entitymanager and its brethren up and running, and "I have a plan": Have a look at the attachments: the xml entity 'source' and php 'target. Let's make sure that's final (as far as I'm concerned, it is) Assuming that we don't have anything else to discuss re: the entity declaration format, we should build in support for entity declarations in xml2php. After there's a functioning make infrastructure, which follows this process: -Find all *.ent.xml files, copy to temp directory. -Make all *.ent.xml -> *.ent -Copy content of temp directory to build directory. We can begin to build EntityManager using the php format as reference. That should happen something like this: -Build unctional Get(), Add(), Delete(), GetList(), etc methods for simple entities (no entity pointers, no processors or validators, etc). Only select, insert, update, delete capability for a simple recordset. -Once that's complete, documented and tested - go on to support: -basic validation (type, maxlength, etc) -processors -validators -GetPath() -entity pointers/references (hierarchical entity structures) After the second generation EntityManager is complete and working properly with all subclasses (base set of processors & vaidators + Querymanager) we should create ent2schema, which would make entity declarations into metabase schema files. At this point the system would be functional for 'advanced' data management but would lack presentation tools like FormBuilder, ListBuilder, etc. Those would be next: -Take existing 'editor' code, use it to construct FormBuilder. -Construct / Modify any necessary UI controls needed by FormBuilder. -Take existing 'lister' code, use it to construct ListBuilder -Same as above, build all necessary UI controls. Obviously both of these things (and the other builders) will require careful design, but all in good time :) ------ I'd like to get people's thoughts on that plan... but here's the sequence of events that I see from here: -Complete bcc & tag modules -Complete Multi-site make -Create simple test dataset for a test entity. (populated schema file) -Create a 'shell' entity manager and a small set of modules designed each to test insert, update, delete, select capabilities of entity manager. -Complete and test basic methods necessary to get and post data to the DB. -Add validator support to entitymanager, build a couple sample validators based on existing code (avalances of it :) -Add processor support to entityManager, and samples -Finish off other complex additions: entity pointers, etc. Thoughts? best, _alex |
From: jason <ja...@gr...> - 2001-09-24 01:14:10
|
While the entity tags are being finalized, I wanted to mention this suggestion. With the risk of adding pretensious bloat, I thought that it may be good to have a built in help system for specific entity/formbuilder(?) tags. This would be most useful when building a form where one can see helpful information relating to the field. (terminology reference, tool-tips, whatever). A few examples come to mind for something like this but like I said, this may be too "wishy". jason Alex Black wrote: > Have a look at the attachments: the xml entity 'source' and php 'target. > Let's make sure that's final (as far as I'm concerned, it is) |
From: Andreas A. <a.a...@th...> - 2001-09-24 11:55:27
|
Hi, >it may be good to have a built in help system for specific >entity/formbuilder(?) tags. This would be most useful when >building a form where one can see helpful information >relating to the field. >(terminology reference, tool-tips, whatever). A few examples >come to mind for something like this but like I said, this >may be too "wishy". There is already a field description tag within the <entitiy:fields> section that can be used as tooltip, helptext or whatever. But thats a good point, there's missing one for the whole enitity. I propose to add something like this: <entity:desc>furbees entity demonstrating xml schema definiton of entities</entity:desc> Andi |
From: alex b. <en...@tu...> - 2001-09-24 16:57:26
|
----- Original Message ----- From: "Andreas Aderhold" <a.a...@th...> To: <bin...@li...> Sent: Monday, September 24, 2001 4:48 AM Subject: RE: [binarycloud-dev] EntityManager Roadmap > Hi, > > >it may be good to have a built in help system for specific > >entity/formbuilder(?) tags. This would be most useful when > >building a form where one can see helpful information > >relating to the field. > >(terminology reference, tool-tips, whatever). A few examples > >come to mind for something like this but like I said, this > >may be too "wishy". > > There is already a field description tag within the <entitiy:fields> section > that can be used as tooltip, helptext or whatever. But thats a good point, > there's missing one for the whole enitity. > > I propose to add something like this: > > <entity:desc>furbees entity demonstrating xml schema definiton of > entities</entity:desc> I agree. I'll add that. |
From: alex b. <en...@tu...> - 2001-09-24 16:54:35
|
> While the entity tags are being finalized, I wanted to mention this > suggestion. With the risk of adding pretensious bloat, I thought that > it may be good to have a built in help system for specific > entity/formbuilder(?) tags. This would be most useful when building a > form where one can see helpful information relating to the field. > (terminology reference, tool-tips, whatever). A few examples come to > mind for something like this but like I said, this may be too "wishy". Ah. Yep. Thinking.... I think we should use the 'description' tag within a field def for that purpose. Actual technical descriptions can do in comments in the xml. _a > jason > > Alex Black wrote: > > Have a look at the attachments: the xml entity 'source' and php 'target. > > Let's make sure that's final (as far as I'm concerned, it is) > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
From: Gerry K. <ge...@mc...> - 2001-09-24 03:02:35
|
> hi all, > > Did a bit of thinking about how we should go about getting > Entitymanager and its brethren up and running, and "I have a plan": > > Have a look at the attachments: the xml entity 'source' and php > 'target. > Overall, looks good, but just wondering why the declaration of fields is not nested within <database> and <table>. Gerry > > best, > > _alex -- IT Specialist | "Do not repay anyone evil for evil. If your enemy MCC | is hungry, feed him; if he is thirsty, give him Bangladesh | a drink. Do not be overcome by evil, | but overcome evil with good." - Bible ----------------------------------------- This email was sent using SquirrelMail. "Webmail for nuts!" http://squirrelmail.org/ |
From: alex b. <en...@tu...> - 2001-09-24 16:56:06
|
> Overall, looks good, but just wondering why the declaration of fields is > not nested within <database> and <table>. Because entity fields do not directly correspond with table definitions. So, for example, you can completely forego the entity:table section and just use the entity path to database field mappings below. _a |
From: Gerry K. <ge...@mc...> - 2001-09-25 02:47:18
|
>> Overall, looks good, but just wondering why the declaration of fields >> is not nested within <database> and <table>. > > Because entity fields do not directly correspond with table > definitions. So, for example, you can completely forego the > entity:table section and just use the entity path to database field > mappings below. > > _a > So, if the tables are not listed, then does Metabase create a table based on the entity definition? I'm not clear on how the entity field to database field mapping happens automagically. Gerry -- IT Specialist | "Do not repay anyone evil for evil. If your enemy MCC | is hungry, feed him; if he is thirsty, give him Bangladesh | a drink. Do not be overcome by evil, | but overcome evil with good." - Bible ----------------------------------------- This email was sent using SquirrelMail. "Webmail for nuts!" http://squirrelmail.org/ |
From: Alex B. <en...@tu...> - 2001-09-25 18:35:59
|
> So, if the tables are not listed, then does Metabase create a table based on > the entity definition? I'm not clear on how the entity field to database > field mapping happens automagically. We will be able to generate metabase schema definitions from entity definitions, but I don't (can't) force a 1:1 correspondence with entity field names and table column names. The short answer is that if you build something relatively simple with binarycloud you will almost certainly have a 1:1 field correspondence, but if you're building something more complex you'll need more entities to provide you with 'views' of your data. _alex |
From: Gerry K. <ge...@mc...> - 2001-09-27 03:47:28
|
> We will be able to generate metabase schema definitions from entity > definitions, but I don't (can't) force a 1:1 correspondence with entity > field names and table column names. > > The short answer is that if you build something relatively simple with > binarycloud you will almost certainly have a 1:1 field correspondence, > but if you're building something more complex you'll need more entities > to provide you with 'views' of your data. > So _how_ does binarycloud figure out the mapping from entity to tables and fields? Sorry if I'm not getting something rather obvious. Gerry > _alex > > -- IT Specialist | "Do not repay anyone evil for evil. If your enemy MCC | is hungry, feed him; if he is thirsty, give him Bangladesh | a drink. Do not be overcome by evil, | but overcome evil with good." - Bible ----------------------------------------- This email was sent using SquirrelMail. "Webmail for nuts!" http://squirrelmail.org/ |
From: alex b. <en...@tu...> - 2001-09-27 17:12:09
|
Have a look at the bottom of that sample entity definition: if there is not a 1:1 field correspondence, you need to define a field map. that's shown at the bottom in entity:schema. _a ----- Original Message ----- From: "Gerry Kirk" <ge...@mc...> To: <bin...@li...> Sent: Wednesday, September 26, 2001 7:51 PM Subject: Re: [binarycloud-dev] EntityManager Roadmap > > We will be able to generate metabase schema definitions from entity > > definitions, but I don't (can't) force a 1:1 correspondence with entity > > field names and table column names. > > > > The short answer is that if you build something relatively simple with > > binarycloud you will almost certainly have a 1:1 field correspondence, > > but if you're building something more complex you'll need more entities > > to provide you with 'views' of your data. > > > So _how_ does binarycloud figure out the mapping from entity to tables and > fields? > > Sorry if I'm not getting something rather obvious. > Gerry > > > _alex > > > > > -- > IT Specialist | "Do not repay anyone evil for evil. If your enemy > MCC | is hungry, feed him; if he is thirsty, give him > Bangladesh | a drink. Do not be overcome by evil, > | but overcome evil with good." - Bible > > > ----------------------------------------- > This email was sent using SquirrelMail. > "Webmail for nuts!" > http://squirrelmail.org/ > > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
From: Andreas A. <a.a...@th...> - 2001-09-24 12:14:21
|
Hi Alex, >Let's make sure that's final (as far as I'm concerned, it is) For me it's too. Except for the <entity:desc> tag. What do you think adding this? (see other mail). > declaration format, we should build in support for entity > declarations in xml2php. Agreed. What do you think of making all this (<entity:>, xml confis, queries, etc) part of bcc at a later point? So we can just run bcc over every textfile, it will detect what file it is (based upon name or internal grammatical criteria), and run the related compilers for each tag. >I'd like to get people's thoughts on that plan... but here's the >sequence of events that I see from here: > > -Complete bcc & tag modules > -Complete Multi-site make Agreed. This should be done before. I've similar intentions like Jason. Use the system as soon as possible, even is there is no advanced data handling (entity). And therefore Make should work, caus I hate copying the files over and over and writing php in templates. But entitymanager is very important too. So making bcc work for very basic tags that don't require much related handling (module, js, url, href, and maybe img) first and doing then multi-site make should happen before etymanager (at least from my point of view). > -Create simple test dataset for a test entity. > (populated schema file) > -Create a 'shell' entity manager and a small set > of modules designed each to test insert, update, > delete, select capabilities of entity manager. > -Complete and test basic methods necessary to get > and post data to the DB. > -Add validator support to entitymanager, build a > couple sample validators based on existing code > (avalances of it :) > -Add processor support to entityManager, and samples > -Finish off other complex additions: entity pointers, etc. Agreed. Andi |
From: alex b. <en...@tu...> - 2001-09-24 16:59:13
|
> What do you think of making all this (<entity:>, xml confis, queries, etc) > part of bcc at a later point? So we can just run bcc over every textfile, it > will detect what file it is (based upon name or internal grammatical > criteria), and run the related compilers for each tag. I agree. BCC should eventually handle all tags, and xml2php :) I'll write that down somewhere... > >I'd like to get people's thoughts on that plan... but here's the > >sequence of events that I see from here: > > > > -Complete bcc & tag modules > > -Complete Multi-site make > > Agreed. This should be done before. I've similar intentions like Jason. Use > the system as soon as possible, even is there is no advanced data handling > (entity). And therefore Make should work, caus I hate copying the files over > and over and writing php in templates. Good. > But entitymanager is very important too. So making bcc work for very basic > tags that don't require much related handling (module, js, url, href, and > maybe img) first and doing then multi-site make should happen before > etymanager (at least from my point of view). I agree there. I would like to be structurally complete before the Managers are started. > > -Create simple test dataset for a test entity. > > (populated schema file) > > -Create a 'shell' entity manager and a small set > > of modules designed each to test insert, update, > > delete, select capabilities of entity manager. > > -Complete and test basic methods necessary to get > > and post data to the DB. > > -Add validator support to entitymanager, build a > > couple sample validators based on existing code > > (avalances of it :) > > -Add processor support to entityManager, and samples > > -Finish off other complex additions: entity pointers, etc. > > Agreed. > > > Andi > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |