Databases
StackOverflow2013
Postsdbo
PODynamic form building / metaprogramming / PHP
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODynamic form building / metaprogramming / PHP
    primarykey
    data
    text
    <p>I'm looking for design ideas about creating dynamic forms.</p> <p>What I currently have is a bunch of models with a few properties / variables for example:</p> <pre><code> class Group extends IDKModel { /** * @Form */ public $title; /** * @Form(validation="{my validation rules here}") */ public $permissions; } </code></pre> <p>In that example the Form PHPAnnotation defines it as a form element and the validation array will have built in validation rules in it. Now the problem I'm having is I have no idea how to implement conditionals. </p> <p>For example, how to show $permissions only if a user is an admin. How to show $title if time of day is past 12:00 GMT. Basically any kind of conditional. </p> <p>Taken from #php at irc.quakenet.org:</p> <pre><code>[10:50] &lt;ramirez&gt; i would not try to stick all of the meta-info under one attribute [10:50] &lt;ramirez&gt; it'd be much cleaner to do something like [10:50] &lt;ramirez&gt; @FormElement [10:51] &lt;ramirez&gt; @Validator(params) [10:51] &lt;ramirez&gt; etc [10:52] &lt;ramirez&gt; anyways, I would probably do something like.. @Filter(name="Group",value="admin,editor") [10:53] &lt;ramirez&gt; then for each filter you want to implement, you'll create a class like "Model_Filter_Group", which would be used for eg. the above filter [10:53] &lt;ramirez&gt; that class in this case would simply explode the groups by comma and see if user is in any of those groups [10:54] &lt;ramirez&gt; you can use that for any kind of filtering, eg: @Filter(name="PastTime", value="12:00") </code></pre> <p>Anyone have a simpler idea?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPeeter
    1. USPeeter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COFor one, try not to mix form presentation logic with validation logic. This is not a simple question, but I do have a solution. Its just quite big and I don't know where to post it.
      singulars
      1. PODynamic form building / metaprogramming / PHP
      1. USPetah
    2. COWhy should form presentation logic be seperate from validation logic? What I'm considering is having 3 different types of PHPAnnotations: @Form, @Validation, @Filter where @Form defines it as a form element, @Validation has all the rules for validating it and @Filter will handle presentational logic.
      singulars
      1. PODynamic form building / metaprogramming / PHP
      1. USPeeter
    3. COBecause thats not what you do in the design patterns I have learned. I think you should not use annotations all together.
      singulars
      1. PODynamic form building / metaprogramming / PHP
      1. USPetah
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload