Leandro Lucarella <[EMAIL PROTECTED]> writes:
> "future" TG components. Right now I don't really know what to use: SA or
> SO? Kid or Genshi? SA and Genshi are the future, as they say, so I really
> prefer going with this two (I don't want to "port" my app in the future or
> reach to a moment when I realize SO or Kid are not powerfull enought). On
So you have to give us more information. If you know how to use SA and
Genshi, then go with them. You'd have some extra steps to get things working
(e.g. using "${ET(my_widget())}" instead of "${my_widget()}" to display
widgets on your templates) but things work. You'd miss CatWalk with SA. If
you don't use it, then there's no problem (I don't use it even with SO, so
this wouldn't matter to me...).
> the other hand, if I use this 2 components, I have less documentation (at
> least about TG integration), I have less comunity support (I guess there
> is more people using SO and Kid), and I have less "features" (I still
> depend on Kid for existing widgets, I have no Catwalk, and I don't know
> what other cool features are not implemented using Genshi/SA, what about
> FastData for example?) which can be pretty important to me because I will
FastData is experimental even for SO + Kid. You'd have to work on them
anyway.
> probably need a very quick working prototype, at least for the CRUD part
> of the application.
It isn't all that hard to get this to your application. It is a bit harder to
get a good implementation for something generic as FastData aims to be. ;-)
> I don't even know if TG now uses ToscaWidgets or it keeps its own Widgets
> implementation, and in the last case, I have the same problem with widgets
> (I guess ToscaWidgets will be the future if they are not used in 1.0, and
> I think this is the case because there is no Debian package
> python-toscawidgets yet ;).
They will be future. They are not 1.0.
> Well, my question then is: what do I do? :)
Either decide on your own or roll your specs here so that we can advise you.
Just guessing or giving random answers might cause you more harm than good.
> What I'm missing using any of the "future" components? How much unpleasant
> my life will be if I stick to the "future" components? How much limited
> are the actual "standard" components and how hard/easy will be to "port"
> and old app to the new components when they become the new "standard"
> ones?
We'll try to maintain as much backwards compatibility as possible. You'll be
able to use Kid when Genshi becomes default. And you'll be able to use SO
when SA becomes default.
Moving from Kid to Genshi is documented at its website. There are plenty of
resources for SA on its website as well and using it with TG isn't all that
hard (just go with plain SA instead of ActiveMapper...).
> I hope this is not too much to ask =)
It is too little to advise a project decision. It is not too much just for
chatting.
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
