What toolkits/modules should I be looking at if I want to use TG2 to
build a CRUD UI to an in-house system.
The in-house system is not a database but the functionality
requirements for the UI are very CRUD-like. I already have a python
module that supplies such methods as get/set/list/create/delete for
the various entities.
Basically, I'm looking for CRUD toolkit that will allow me to supply
my own get/set/list/create/delete methods, and it turn spit out basic
tables/forms.
(I am came across Sprox, and posted a similar message to their group,
but it's pretty low traffic and has not passed moderation yet...)
Or you can extend Sprox with another data provider if you want to wire
it all up to some kind of introspection engine for your in house data
thing. I don't have a doc for that... But you can look at the code
for the existing one ;)
On Thu, Nov 19, 2009 at 1:51 PM, AFO <allen.fow...@yahoo.com> wrote:
> Hello,
> What toolkits/modules should I be looking at if I want to use TG2 to
> build a CRUD UI to an in-house system.
> The in-house system is not a database but the functionality
> requirements for the UI are very CRUD-like. I already have a python
> module that supplies such methods as get/set/list/create/delete for
> the various entities.
> Basically, I'm looking for CRUD toolkit that will allow me to supply
> my own get/set/list/create/delete methods, and it turn spit out basic
> tables/forms.
> (I am came across Sprox, and posted a similar message to their group,
> but it's pretty low traffic and has not passed moderation yet...)
> -- AF
> --
> You received this message because you are subscribed to the Google Groups "TurboGears" group.
> To post to this group, send email to turbogears@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/turbogears?hl=.
1) For a normal web-based UI app, what advantage does RestController
give in comparison to the standard TG2 Controller?
2) Are there any tutorials for ToscaWidgets used without SQLAlchemy?
3) What is the "tmpl_context" variable I see floating around in the
tutorials?
4) Can Sprox and/or ToscaWidgets generate a "view-only record details"
page? (That is, a display of the details laid out like the
traditional "edit" page, but not using form fields to display the
values.)
Thank you,
:)
On Nov 19, 8:52 pm, Mark Ramm <mark.mchristen...@gmail.com> wrote:
> Or you can extend Sprox with another data provider if you want to wire
> it all up to some kind of introspection engine for your in house data
> thing. I don't have a doc for that... But you can look at the code
> for the existing one ;)
> On Thu, Nov 19, 2009 at 1:51 PM, AFO <allen.fow...@yahoo.com> wrote:
> > Hello,
> > What toolkits/modules should I be looking at if I want to use TG2 to
> > build a CRUD UI to an in-house system.
> > The in-house system is not a database but the functionality
> > requirements for the UI are very CRUD-like. I already have a python
> > module that supplies such methods as get/set/list/create/delete for
> > the various entities.
> > Basically, I'm looking for CRUD toolkit that will allow me to supply
> > my own get/set/list/create/delete methods, and it turn spit out basic
> > tables/forms.
> > (I am came across Sprox, and posted a similar message to their group,
> > but it's pretty low traffic and has not passed moderation yet...)
> > -- AF
> > --
> > You received this message because you are subscribed to the Google Groups "TurboGears" group.
> > To post to this group, send email to turbogears@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/turbogears?hl=.
However, the definition "class RestController(DecoratedController)"
seems a bit sparse.
Where is the real definition?
> 2) Are there any tutorials for ToscaWidgets used without SQLAlchemy?
Still not found. But it's really sprox that's so tightly bound to SA.
> 3) What is the "tmpl_context" variable I see floating around in the
> tutorials?
Still not sure.
> 4) Can Sprox and/or ToscaWidgets generate a "view-only record details"
> page? (That is, a display of the details laid out like the
> traditional "edit" page, but not using form fields to display the
> values.)