Turkiyenin en sevilen filmlerinin yer aldigi porno internet sitemiz olan ve sex tarzi bir site olan sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir.
Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.
I think Sencha are in something of a Catch-22 - damned if they provide dates and don't make them, damned if they don't provide dates at all. Given the debacle that was the 4.0 release, I can appreciate Sencha not wanting to be burned again.
I also think that a normal customer response to this would be to ask for smaller point releases, so as to lower sensitivity to dates - smaller, more frequent updates obviates the need for dates, to some degree.
The problem here, is that 4.0 performance was so bad that it forced the team to go back to the drawing board on the layout engine. While I can't and won't speak for the team, or anyone at Sencha, I can imagine that it would be nearly impossible to turn out small releases while this refactoring took place (and remember, it needs to take place just to fulfill the performance promises of 4.0!)
With all of that said, I hope Sencha gets it right, and not fast. Unfortunately for me, I no longer have the luxury of being an early adopter or tester, as I've blown major delivery schedules over 4.0. I eagerly await whatever results...
I agree with your thoughts with regards to major rewrites etc, its very difficult to post a date and stick to it.
Now however, we have moved past preview and into Beta mode, it should be feasible that there is a weekly build with x issue resolutions included. Some incremental progress will be very well received I'm sure.
I also still stress that there is an opportunity here to engage the community further and have them actually assist in this process. whether a weekly update or 6 monthly update, if the community is at the end of the pipeline receiving the drop, they will offer little more value than pointing out something doesn't work and sending it back.
If you can gear the development pipeline to include the community along the way, having community submit fixes for issues, and test cases for faults etc, that is how you drive yourself out of a messy situation like this.
I guarantee the community contains many experts in different areas of the code base, who will provide valuable input if given the opportunity.
In development, a bundle has the same folder structure that the application. I use
Ext.Loader for use the new dynamic dependency loading capability.
In production, could I use the newly-introduced Sencha SDK tools to obtain all clases in a single file. Then, I have one file to load for a bundle. Could be use asynchronous loading to load these bundles in my app on demand.
I was working to extend Ext.application from MVC to HMVC.
I show an example builded with HMVC architecture.
The application contains bundles, its has the same folder structure like application.
The bundle's controllers has the same application bus event.
The bundles have optional main view to be injected in application viewport (shell) by a defined placeholder. (I use Ext.ComponentQuery to view-discovery, view-injection).