You are correct that we don't support foreign keys very well or create drop-downs, etc. where appropriate. The biggest reason for this is because no one has taken the time to add this functionality. If we had a good example of how to do this for a UI (and what metadata we should use to determine the control type), I don't think it would be too difficult to add. Of course, patches are more than welcome - we'd be happy to add this functionality.
Matt On 1/15/08, mschipperheyn <[EMAIL PROTECTED]> wrote: > > Hi, > > I've used Appfuse to create my default web interface screens. Looks good but > it just creates the input type=text fields. Foreign keys are not created > like pulldowns, many to many not as double multiselects. This does happen in > the example screens for the User. I realize it's probably meant to work this > way: just provide the scaffolding to continue on. But it would be really > nice and probably quite easy to generate these basic elements as well. This > would provide an improved scaffolding but more importantly would make the > generated backoffice screens actually work (when foreign keys etc are > involved) and would allow you to use Appfuse to create a sort of default > backoffice for your site really easy. > > Just a wish. I'm curious if anything like this is in the works. > > [BTW. I believe I sent a post like this before, but couldnt find it so sent > it again.] > > Cheers, > > Marc > -- > View this message in context: > http://www.nabble.com/Appfuse-default-appfuse%3Agen-screens-tp14841559s2369p14841559.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
