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 am triying to wrap my head around where Ext Designer fits into my workflow. It seems like an awesome tool for prototyping and doing mockups, but what happens later in the project? Can you re-export projects? Is there some best practice for setting things up to make it so designer can be used later?
Are there any docs or tutorials on how you might handle some of these issues?
That's an accurate description of the Designer. It will become more powerful in future versions, keeping you in the Designer more than in Code, but in general we're not aiming to completely replace an IDE. So yes, be sure if you want to edit the behavior or configuration of a component, to do so in its ".js" file and not in the ".ui.js" file, as the ".ui.js" file is overwritten on exports.
Netbeans and Eclipse don't offer the platform that Sencha required to build the Designer via "eating our own dog food", that is, with Ext JS, HTML, and CSS...without going to extensive lengths. The program also would have been around 150MB unnecessarily. We don't want to require Netbeans or Eclipse, the idea is to remain IDE agnostic.
You can do a plug-in which relies on IDEs infrastructure and just send your code.
I'm convinced that ExtJS is a excellent framework and has a lot of potential but the lack of main stream Java IDE support and the lack of "official" server integration tuturials (less with J2EE) leads to painful adoption.
May be you are rigth having the designer IDE agnostic but to be more "appealing" to Java developers it should be fast track tutorials or simple eclipse or netbeans plugins to provice something like "ExtJS Project facet".
The Designer runs on an embedded browser, it would have taken some work to fit into an IDE. But again, we didn't want to force a user into Eclipse or assume they already had it...even if it was only used for the Designer (e.g., their normal dev tool is Visual Studio) it would have been *way* more complicated and simply overkill. Not that the IDE doesn't offer a good starting point...but Ext JS does too, and the Designer is written completely in Ext JS. And on that point, one of our main goals was to write the Designer in Ext JS itself.
With that said, better project integration has been suggested by other users and we're taking this feedback very seriously to work on this in future releases, yet maintain our promise to remain IDE agnostic.
As a Java coder, have you checked out Ext GWT yet?
> The Designer runs on an embedded browser, it would have taken some work to fit into an IDE
Maybe less than you think. JBoss tools JSF editor uses XUL and there is some initiatives to do the same in Netbeans.
> ...but Ext JS does too, and the Designer is written completely in Ext JS
Interesting - What about subscrition to "hosted" designer? This way only the developer uses latest designer and maybe is more appealing (at least to me) to developers if price downs a little.
> With that said, better project integration has been suggested by other users and we're taking this
> feedback very seriously to work on this in future releases
May be not just designer but project/page templates or project facets on java IDEs for ExtJS alone.
> As a Java coder, have you checked out Ext GWT yet?
Someone suggested before but I didnt go that way because I think ExtJS is better than Ext GWT: gadgets, support, maturity and, comming from MVC (JSF), I feel more natural configuration objects than object instantation. Also, even if I'm JEE developer, ExtJS allows me to change my server code to other platform (php or NET) if needed.