Here in this article, I'll introduce you some early features of ZK Visual Editor view(a.k.a VE View). The future release version's look & feel might be different and have more features.
Live Demo
Here we play a scenario of using VE to show all these features.
Features
Zul Editor Selection Detection
While mouse select different element of ZK component, the VE's focus frame will change.
Outline View Selection Detection
While selected component in Editor view is changed, the VE's focus frame will also change.
Document Changed Detection
While user editing the zul document, VE will response current visual result immediately.
Summary
According to recent posts of forum and our customer's feed back, ZK Studio develope team started thinking on WYSIWYG Editor since 0.8.2 released. After two weeks working, we have already finished our POC(proof of concept) stage, and will be more focused on implementing this important new feature.
If you have any ideas or suggestions please feel free to post it to our forum ZK Studio Forum.
And if you are not using ZK Studio yet, please follow these two links below:
Day after day, I'm really happy. ZK Team always been convinced that would reach this point.
Congratulations
David Cheung
2008-10-09
GREAT!! I can sell my colleague to use ZK now ! ^o^
Jack
2008-10-09
Wow!
CmaniaC
2008-10-09
WOOOOOWW... that really great, amazing work, that's the definitive "long AWAITED feature"..
htang
2008-10-09
Congratulations!!!!
I can't wait any longer for this feature. With this, we can pass the interface design to real front-end designer, and we can focus more on the backend to develop more great stuffs.
aliyu musa aliyu
2008-10-10
can we have same thing on netbeans please cos it is cool to have it for multiple development environments
You can combine Netbeans with Eclipse; using a minimal Eclipse install and saving .zul-, or .jsp files from Eclipse above. Just seperate the .zul, or .jsp code from the java code; as much as possible or within a set pattern. i.e. Unary Interface modeling: Javascript to ZK, Activity modeling (in Java BbD- ): ZK, Object Behaviours: Java, Component Modeling: Java. Call the functions in the Java objects from the Activity models in ZK as 'print' placeholders.
The ZK system really helps developers who focus only on system design and -patterns. Before ZK it took weeks or even months to develop an interface alone, whereas coding a good DB/API/BP/AI module takes only an hour; because thinking is in patterns. With ZK, you can even encapsulate javascript tested modules and deploy them. Eclipse is good for testing the interface, and then Netbeans can deploy the application; that's the way, until Netbeans supports the interface. I can fully understand that Netbeans is an attractive system to develop ZK applications with.
