Wednesday, November 26, 2008
Thursday, September 18, 2008
Friday, August 15, 2008
Project's name is ZPortal and from now on it is managed under Google Code. One important fact is that the "Z" prefix indicates the framework we used to build this portal, which is Zend Framework.
As an introduction to this post I want to point on the difference between "Horizontal information" which is information that anybody has and use vs. "Vertical information" which is information that only you or your organization has. In the Enterprise2.0 era we try to take advantage of these two types of information and bring it to the user (employee) so he has much more power in his daily work. Previous solutions like Wiki are not sufficient these days as they discard the horizontal layer and lack of integration points.
So what is all about? it is about Enterprise2.0. ZPortal is a system of Web-based technologies that provides rapid and agile collaboration, information sharing, and integration capabilities in the extended enterprise. For those who are not familiar with the term Enterprise2.0 but know something about Web2.0 I recommend reading this post that compares between the two methods. Actually from a user point of view ZPortal is similar to iGoogle with small differences. First the authentication method is against Microsoft Exchange Server (it can be replaced by any authentication technique but of course this is the common way thee days) second you can add internal feeds from your company as this system runs behind the company's firewall. Third you can extend this portal to your company needs.
If I'd try to depict my environment at office I would do it like this:
Finally, I want to thank two people who are not at Zend anymore but helped allot toward this project - Seva Lapsha and Yuval Kuck.
for more details visit the new ZPortal site - http://code.google.com/p/zportal/
Saturday, May 24, 2008
There are three more things that worth mentioning here:
- I do think that PHP developers can (and should) try and contribute to this project although the core development is in Java, since trivalley this project is solely designated for them.
- PHPEclipse people that did great on this project, should think about a way to integrate their work and help us so we will unite the forces on one platform.
- Since people need to have some knowledge about our platform, we should supply basic design documents. The following two articles can be used for this end, ASTView and Abstract Syntax Tree.
Thursday, April 03, 2008
See you next time!
Saturday, March 15, 2008
Though I am a speaker there, I am pretty wait to hear and see some of the Eclipse fellows. Like those from the Data tools platform and from the Web tools platform.
Also there are many sessions that I am eager to attend-
1. Getting started with RAP development - develop rich, AJAX-enabled web applications using the same development model as RCP.
2. Developing Python IDE on top of Eclipse DLTK Project - a set of frameworks designed to build full featured development environments for dynamic languages.
3. Getting Started with OSGi
4. Mylyn: code at the speed of thought
5. What can the WTP Snippets View do for me?
6. Eclipse Command Language
and a link to the EclipseCon sessions
Friday, February 22, 2008
Taken from Ohloh's Eclipse PDT page
So what's keeping us busy these days?
1. Revising Modeling Techniques – Its time to catch up Eclipse's standards. We have decides that our previous modeling technique is getting oldish. So naturally we are targeting JDT's concepts with adaptation to the php dynamic binding nature (given by the DLTK project).
2. Code Manipulation – sometimes the editor should generate new code or even rewrite an existing code. This is an excellent mechanism for such kind of tasks. Also a great advantage is that we catching up JDT's standards on these capabilities as well so many of JDT's features are quickly portable to php.
3. UI enhancements – this is the part that our community should be most happy to hear about. Since infra was enhanced , more and more UI features are available. Taking for example mark occurrences, override indicators, better code completion, fast searching, quick fixes and more.
Exit Execution Paths are marked in PDT 1.1 Editor
5. Unit testing – Well... maybe it won't be an interest of any of our users but still it is worth mentioning. We have tripled our unit testing to provide stability and regression testing to PDT. It seems that it also makes the whole development cycle more fun to us!