Yes it will take some time to get everything promoted but that shouldn't stop users from using the sandbox stuff now. The Dojo stuff especially needs to be heavily discussed before we promote it. We'd like to figure out a few best practices for all of this Ajax stuff and stick with them in all of our components.
Sean On 4/19/06, Werner Punz <[EMAIL PROTECTED]> wrote: > Philippe Lamote schrieb: > > Well the problem is that the sandbox components are very experimental > > and often under heavy code fluctuation und to make things worse, mostly > > undocumented yet. > > > > -- Everybody understands. Suffices to add a disclaimer? (like always > > with "betas") > > > > So if you use them use them with care and have in mind that some of this > > stuff might break in the near future. > > One vendor has integrated them in his product, which is not a good idea, > > using them at that state in a big project would mean a huge money loss > > for those who use them and maybe not find them the same way or totally > > altered at the next major release. > > -- Well, I guess they were convinced a rework with cool components is > > better than no/lesser components and a not-so-impressed client. Good > > clients understand software lives.It also allows them to get feedback > > already and then integrate the feedback with the final of the components > > later on. A defendable path no? > > > > but all this aside: > > the components are very cool ;-) > > -- XXX Yeah man, that's why we want to get our hands on them!!When they > > compile, ship'em!! ;-) > > > Well one of the big things coming after the next tomahawk stable is to > push some of the sandbox components down into the main Tomahawk. > It already is a shame that the sandbox almost has become as big as > Tom itself. The first component as it seems will be or already is the > Calendar component. > The ajax stuff will probably go down into the main core once we have > moved towards Dojo 0.3. > > My personal feeling is that our supportive codebase (the entire > intialization api) now is stable enough, thanks to a few really > complicated implementations that it wont break in the near future. > > Once dojo is down in tom a few components will follow... > >
