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-09-25 00:09:18
|
yes, I know that looks inconsistent, but it's a function of how metabase does its schema detinition format. I like to use only true/false. (thus the <required> value). Metabase's field defs need <notnull>1</notnull> or <notnull>0</notnull> so I'm not being schitzo, I'm trying to satisfy metabase while maintaining standard as best I can :) btw: true/false is the gold standard everywhere for booleans. _a > > A 'little' thing i noticed as i was looking at the entity definition > again... > > I'm noticing a slight indifference to boolean values. > > Here we see true/false: > > <!-- must this field be valid to do a post of this entity? --> > <required>true</required> > > Yet here we use 0/1: > > <!-- is this the default field in the db table? --> > <default>0</default> > <!-- can the field be null? --> > <notnull>1</notnull> > > > While the parser does not care, it sure would be nice to have a standard > boolean value. > The above example may be the only case, but I would imagine that there > are other places where this is true. (no pun intended) > > jason > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
|
From: Andreas A. <a.a...@th...> - 2001-09-24 22:53:00
|
Hi Jason, > While the parser does not care, it sure would be nice > to have a standard boolean value. I agree. I'd vote for true/false to promote readability. Andi |
|
From: jason <ja...@gr...> - 2001-09-24 22:27:21
|
A 'little' thing i noticed as i was looking at the entity definition again... I'm noticing a slight indifference to boolean values. Here we see true/false: <!-- must this field be valid to do a post of this entity? --> <required>true</required> Yet here we use 0/1: <!-- is this the default field in the db table? --> <default>0</default> <!-- can the field be null? --> <notnull>1</notnull> While the parser does not care, it sure would be nice to have a standard boolean value. The above example may be the only case, but I would imagine that there are other places where this is true. (no pun intended) jason |
|
From: Andreas A. <a.a...@th...> - 2001-09-24 20:37:38
|
Hi Andris, did you or can you modify the XMLUtils to support attributes? I thought of the following: <tag id="moo" name="HelloWorld" package="hello_world"> <child var="value" var2="value2" /> </tag> array( 'id' => "moo", 'name' => HelloWorld", 'package' => "hello_world", 'child' => array( 'var' => "value", 'var2' => "value2", ), ); This would save lotta work with the Bcc*Compiler classes. 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 > |
|
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: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: alex b. <en...@tu...> - 2001-09-24 16:55:03
|
I'll make the changes today and sync to sourceforge. _a ----- Original Message ----- From: "jason" <ja...@gr...> To: <bin...@li...> Sent: Sunday, September 23, 2001 6:22 PM Subject: Re: [binarycloud-dev] Multi-site make > > Yes please. This would allow me to begin current projects (notice the > plural) that I've been stalling because of these changes. > > thanks > > > Alex Black wrote: > > If you intend to start making the changes, let me know and I'll do the > > directory restructuring sooner rather than later :) > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
|
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: 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: 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: 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: jason <ja...@gr...> - 2001-09-24 01:20:33
|
Yes please. This would allow me to begin current projects (notice the plural) that I've been stalling because of these changes. thanks Alex Black wrote: > If you intend to start making the changes, let me know and I'll do the > directory restructuring sooner rather than later :) |
|
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: Alex B. <en...@tu...> - 2001-09-24 00:32:16
|
hi jason,
I'm going to check something similar into CVS this week, but here's the jist
of the spec for Multi-site make.
First, I'm going to change the directory structure shortly (egh, can't wait
for subversion) to match the following:
binarycloud/user/default (a default install used for configs and common
files)
binarycloud/user/bcdev (the 'development' user tree where we'll test
modules, etc. (this will be the current user/tree))
and eventually (later later :) we'll have a user/sample site which is
some cute application we can build quickly to show off the capabilities of
the system.
----------
Assuming that structure, you can get a basic multi-site make going fairly
quickly, it would involve:
-changing the build tree to reflect:
build/site_name/lang_code/(current normal contents of a lang
directory)
-looping through the site directories (except default) doing makes
-----
That would _work_ but obviously leaves a lot to be desired:
-we'd need a ./configure script at source root after this was done to
set make targets for each site, so you could run make 'site_name'. While we
we're at it, ./Configure could do a ton of other nice things like
automatically set some environment variables, check that php -q was
available, set file permissions, etc etc etc. (I'll make a list)
-it would be very nice to have a MakeConf.xml in user/site_name/conf/
which would be used by ./Configure to generate a Makefile.in for each site.
I've got a sample on my home machine which I'll clean up and check into cvs.
It's basically a bunch of flags like "zend encode" "strip comments" "use
shared core" etc etc.
-we'd want to build a tree comparison script which would check that all
files in user/default/ existed in user/site_name/ and would include any
missing files in the build (but not move them into the site_name's source
tree.)
As you can see, this starts to be an undertaking, but I think we can start
simple and work our way up to something _very_ cool.
Let me know if you have any specific questions about any of that stuff.
If you intend to start making the changes, let me know and I'll do the
directory restructuring sooner rather than later :)
best,
_alex
--
alex black, ceo
en...@tu...
the turing studio, inc.
http://www.turingstudio.com
|
|
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: Alex B. <en...@tu...> - 2001-09-22 21:32:25
|
>> Not really, because you're actually building logic with MetaL, whereas we're >> just doing string replacement that's supported by logic that figures out >> what to replace with. > > Actually that is precisely what the MetaL compiler module named template > does. You just say that there is some template data in a file and that you > want to clip some data from it and have some data replaced with variable > values that are specified in your program. > > Need examples? Hmmm... yes, that would be great. >> I.e. we have a tag for putting the correct language version of a string >> based on the current language code, or putting in a bunch of code for a >> static module call from page, etc. > > Those would be done with MetaL by passing variable values that would > represent the data that you want to replace in the the template. Ok. > >> I need to spend a little time with MetaL to get more comfortable with it, >> but I don't think what we're doing crosses. > > Yes, I think you could save yourself a lot of development effort if you > look closer into MetaL and realize that it does already what you need. > > What you are trying is one of the things that MetaL template can do, which > is replacing data within template data. MetaL can also replace template > data with code generated by some other module. To benefit from MetaL > power, obviously you don't need to use everything that it is capable of. Indeed, though I was not thinking that MetaL did that. hmmmmm _a |
|
From: Manuel L. <ml...@ac...> - 2001-09-22 20:45:25
|
Hello Andreas, On 22-Sep-01 17:11:01, you wrote: >Hi Manuel, Alex, >> I need to spend a little time with MetaL to get >> more comfortable with it, but I don't think what >> we're doing crosses. >Where can I get MetaL? I just read about it in the phpclasses list. Is it >public right now? Not yet. I am preparing to open it when I feel it is ready to demonstrate the concept: generate code in more than one language that implement the same program. I am almost right up to the point to demonstrate that concept in PHP, Java and Perl. Meanwhile, I have opened the project to a limited group of developers so they can evaluate the usability of the language before I release it to the world and make some criticisms and improvement suggestions. MetaL will be Open Source anyway so everybody will be able to use it, but if you or anybody feel you would like to evaluate it and provide some feedback, I can grant you access to the developers mailing list and the CVS repository. Just mail me privately. Regards, Manuel Lemos Web Programming Components using PHP Classes. Look at: http://phpclasses.UpperDesign.com/?user=ml...@ac... -- E-mail: ml...@ac... URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp -- |
|
From: Manuel L. <ml...@ac...> - 2001-09-22 20:45:23
|
Hello Alex, On 22-Sep-01 17:05:39, you wrote: >>> what does everyone think about being able to create 'handler classes' for >>> custom tags which will be interpreted by the system at make-time? >> >>> I'm thinking of people who will want to create strange variants of the >>> lang keyer, or add some other special set of logic that would be >>> convenient to store in a tag. >> >> Isn't this what MetaL does: assign tags a function that is implemented by >> component that translates that into data or code that is generated at make >> time? >Not really, because you're actually building logic with MetaL, whereas we're >just doing string replacement that's supported by logic that figures out >what to replace with. Actually that is precisely what the MetaL compiler module named template does. You just say that there is some template data in a file and that you want to clip some data from it and have some data replaced with variable values that are specified in your program. Need examples? >I.e. we have a tag for putting the correct language version of a string >based on the current language code, or putting in a bunch of code for a >static module call from page, etc. Those would be done with MetaL by passing variable values that would represent the data that you want to replace in the the template. >I need to spend a little time with MetaL to get more comfortable with it, >but I don't think what we're doing crosses. Yes, I think you could save yourself a lot of development effort if you look closer into MetaL and realize that it does already what you need. What you are trying is one of the things that MetaL template can do, which is replacing data within template data. MetaL can also replace template data with code generated by some other module. To benefit from MetaL power, obviously you don't need to use everything that it is capable of. Regards, Manuel Lemos Web Programming Components using PHP Classes. Look at: http://phpclasses.UpperDesign.com/?user=ml...@ac... -- E-mail: ml...@ac... URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp -- |
|
From: Manuel L. <ml...@ac...> - 2001-09-22 20:45:21
|
Hello Alex, On 22-Sep-01 17:12:22, you wrote: >>>> Actually what I had in mind is to have a SOAP interface in the PHP >>>> Classes site, not in binarycloud site. That would work for any classes in >>>> there. >> >>> Cool, that would be nice. >> >> Yes, but would it work to be useful for you? >I don't do that many updates from PHPClasses: I'm subscribed to your >releases/updates list and grab files as I need them. Yes, I just thought that making it possible to do it programatically you could update your repository automatically without spending much time and effort. >I would actually be more interested in your package-request _code_ for >phpclasses than the feature itself :) Basically it would be a subclass of SOAP server class that I have already developed and made available in the PHP Classes site. The subclass would figure what you are asking from the request data parsed by the SOAP server base class and generate a response. Regards, Manuel Lemos Web Programming Components using PHP Classes. Look at: http://phpclasses.UpperDesign.com/?user=ml...@ac... -- E-mail: ml...@ac... URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp -- |
|
From: Alex B. <en...@tu...> - 2001-09-22 20:11:59
|
> Hello Alex, > > On 21-Sep-01 17:26:25, you wrote: > >>> Actually what I had in mind is to have a SOAP interface in the PHP Classes >>> site, not in binarycloud site. That would work for any classes in there. > >> Cool, that would be nice. > > Yes, but would it work to be useful for you? I don't do that many updates from PHPClasses: I'm subscribed to your releases/updates list and grab files as I need them. I would actually be more interested in your package-request _code_ for phpclasses than the feature itself :) >>> Anyway, I think that in a few months you will want to switch from CVS to >>> SubVersion and you would change only in your end. > >> I've been keeping tabs on SubVersion... it will be nice :) > > Talking about SubVersion, did you noticed Tigris.org? It looks like it > could do what Sourceforge does except that it seems cleaner. If you want > to host Sourceforge in a machine of yours it requires major Linux hacks and > it is very hard to put it to work. Has anybody tried to host Tigris on > machine of you own? I have not, that's an interesting point. I'll have a look. _a > > Regards, > Manuel Lemos > > Web Programming Components using PHP Classes. > Look at: http://phpclasses.UpperDesign.com/?user=ml...@ac... > -- > E-mail: ml...@ac... > URL: http://www.mlemos.e-na.net/ > PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp > -- > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
|
From: Andreas A. <a.a...@th...> - 2001-09-22 20:11:22
|
Hi Manuel, Alex, > I need to spend a little time with MetaL to get > more comfortable with it, but I don't think what > we're doing crosses. Where can I get MetaL? I just read about it in the phpclasses list. Is it public right now? Andi |
|
From: Alex B. <en...@tu...> - 2001-09-22 20:05:18
|
> Hello Alex, > > On 21-Sep-01 20:30:00, you wrote: > >> what does everyone think about being able to create 'handler classes' for >> custom tags which will be interpreted by the system at make-time? > >> I'm thinking of people who will want to create strange variants of the lang >> keyer, or add some other special set of logic that would be convenient to >> store in a tag. > > Isn't this what MetaL does: assign tags a function that is implemented by > component that translates that into data or code that is generated at make > time? Not really, because you're actually building logic with MetaL, whereas we're just doing string replacement that's supported by logic that figures out what to replace with. I.e. we have a tag for putting the correct language version of a string based on the current language code, or putting in a bunch of code for a static module call from page, etc. I need to spend a little time with MetaL to get more comfortable with it, but I don't think what we're doing crosses. best, _alex > Regards, > Manuel Lemos > > Web Programming Components using PHP Classes. > Look at: http://phpclasses.UpperDesign.com/?user=ml...@ac... > -- > E-mail: ml...@ac... > URL: http://www.mlemos.e-na.net/ > PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp > -- > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
|
From: Andreas A. <a.a...@th...> - 2001-09-22 20:04:48
|
Hi Alex, just commited the stuff, I'm in hurry so just a very brief overview: + base/mod/bcc/* + Make integration of example user/htdocs/compilertest.html. This will become complilertest.php in the build tree. just run make. it should work. Andi |
|
From: Manuel L. <ml...@ac...> - 2001-09-22 20:00:11
|
Hello Alex, On 21-Sep-01 20:30:00, you wrote: >what does everyone think about being able to create 'handler classes' for >custom tags which will be interpreted by the system at make-time? >I'm thinking of people who will want to create strange variants of the lang >keyer, or add some other special set of logic that would be convenient to >store in a tag. Isn't this what MetaL does: assign tags a function that is implemented by component that translates that into data or code that is generated at make time? Regards, Manuel Lemos Web Programming Components using PHP Classes. Look at: http://phpclasses.UpperDesign.com/?user=ml...@ac... -- E-mail: ml...@ac... URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp -- |
5 messages has been excluded from this view by a project administrator.
