Here's what we have so far (may be a bit ambitious)
GENERATOR
-> address performance issues w/ and w/o encoding
-> plugin architecture + sample plugins
-> allow encoding on a field level (instead of project level)
-> simple data integrity checks (specify fields that must be !=
'<empty>')
-> code cleanup
-> compliance with strict mode in PHP5/MySQL5
FIXES
-> getlist must return all records if no conditions are supplied
SETUP
-> plugin management (?)
-> allow mangement of children/sibling via the interface
Thanks in advance for your suggestion(s)
Regards,
The POG Team
If by example i need to join objects ... example:
select * FROM user as t1, photo as t2 WHERE t1.userId=t2.userId AND
t1.type=normal AND t2.type=jpg
1) Customizable local generators
Have the local generators save the generated files directly into a
specified directory.
2) Setup integrates the generator
Jump from a set up tool to a local generator, make a new object, object
is saved to a specified directory, and go back to the setup which
checks all the objects again and then lets you continue managing them.
What I would like to be able to do is customise the naming convention
for the id field. Currently it's table name + "id" but I would like
table name + underscore + id so the items table goes from itemsid to
items_id.
I know someone will say just search and replace automatically but then
why have a car if you have legs, it just makes life easier.
I thank you.
Lumsden
So POG 3 should abide by that law. If any feature is added like changing the
naming convention and such will break our code and I personally would not
like to see any feature which will make pog not backwards compatible with
existing versions.
Regards,
Paris Paraskeva
Managing Director
M.E. & E. UnitedWorx Ltd
33, Apostolou Pavlou Avenue, Office 103, 8046 Paphos, Cyprus
Tel.: +357 26220707, +357 26221313, Mob.: +357 99575501
Fax.: +357 26221002
pa...@unitedworx.com
www.unitedworx.com
The information contained in this email message(and any attachments) is
legally privileged and confidential information intended only for the use of
the addressee(s) listed on this email. If the reader of this message is not
the intended recipient you are hereby notified that any dissemination,
distribution or copy of this email is strictly prohibited. If you have
received this email in error, please notify us by telephone or email on the
contact details shown on the end of this email. Thank you.
I thank you.
Lumsden
__________ NOD32 2008 (20070125) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
Thanks,
Brian
I create some quite long winded tables. I often edit them and instead
of entering the whole table again, it would be good if POG could read
the original statement it produced, create all the attributes and set
the types. Then I could simply tinker with a couple of settings and
press Generate.
Hardly mission critical but could be useful. Might also be a start on
the road to reverse engineering?
Cheers
Lumsden
Or pressing modify table from within setup should also do the same
thing...although there are some issues with very long tables (thus
url) and IE. Ffox should be able to handle it though..
Joel
Again many thanks.
Cheers
Lumsden
ie: a user owns a list of contacts, but the list of contact's are user
objects, so user would be a parent and a sibling (parent
differentiates who owns the list)
{Owner} ?
a) the owned objects' type could be any other object type including
the same as the owner object
b) the owned objects' type could be aliased to something relevant to
the type of ownership ( like Eidolon's example of a contact list of
users )
I'm not sure if this is possible or how it would be done, but it would
be an awesome built in feature.
Hi Eldolon,
Joel and I talked about this a couple of years ago, but it wasn't
smooth to implement at that time (and not totally necessary for what
we were doing), however, I think this would be possible (and, I think,
relatively simple) as a plug-in extension - and would be terribly
useful at times.
Since XML is "supported" with PHP 5 - the plugin model would be the
right fit for the solution too.
-Mark
On Jan 31, 10:09 am, "arhodes" <alice.rho...@gmail.com> wrote:
> I agree with Eidolon. It would be useful to have an owner relationship
< snip >
Right now it takes a POG or an array of POGS as the first argument,
boolean to recurse through parent/child/sibling/owner (hacked in,
based on the column being called owner_fieldname), and a whitelist of
fields, which will be an array of arrays so that you can filter what
columns you need (ie, array("user" => array("username","password"),
details => array("email"))
:)
as Mark mentioned, the plugin feature that we'll officially 'propose'
in a few days, will, imho, work very nicely with custom code like
yours Eidolon, and converting your final framework into a POG plugin
should be quite straightforward.
There are a few ways to 'customize' the POG code - object inheritance,
plugins, direct code modification..etc. While inheritance, direct code
modification are currently being used by many developers, there is no
real easy way to share functionality among different objects/projects/
developers. The plugin piece is meant for exactly this type of code,
where the function(s) perform something that's not tied to the
business logic, and can be shared among developers and objects.
We should be able to officially propose a plugin architecture for
review/criticism in the coming days.
regards,
Joel
On Feb 1, 2:08 am, "Eidolon" <eido...@idealsound.ca> wrote:
PogParentClass
+ - - - - PogObject1
+ - - - - PogObject2
+ - - - - PogObject3
Its name would be some standart name we choose and this class would be
empty by default, so no change to working of existing objects at all.
Class file would be included in every zip file.
The advantage I see - in PHP 5 functions you can force argument to be
a POG object, for example:
function someFunction(ParentPogClass $somePogObject){
... code ...
}
You can add your own methods to all pog objects with ease
...
What do you think about it?
I didn't yet find time to post the new model 3.0 will have on the
forum... but will do so soon.
Thanks for the feedback
Joel
I'd like to make my tables in another tool so that i can set up
default values and other stuff like extra indexes etc.
Another thing might be to support innodb tables which is better for
referential integrity and transactions.
love POG btw!