morishani - 09 January 2009 01:50 PM

Hi, I’m currently using Zend Studio as my development environment.

But once I saw espresso, Damn, It’s all so tidy - even when it’s beta.

But without smart code sense, it is useless for real developers, my question is - will it be smart and good as Zend studio’s?
Can it be done with the current framework that you build for the sugars?

I looked over the thread and I saw the performance issue, Zend studio resolved that with a simple hidden ’.project’ file, I think you can do that too.

B.T.W - I really love the way it synchronize with the server.

I don’t think there’s any major technical reasons why it can’t be dynamic, but I do think that there are more important things to add to it beforehand.

alexgordon - 09 January 2009 01:53 PM

morishani - 09 January 2009 01:50 PM

Hi, I’m currently using Zend Studio as my development environment.

But once I saw espresso, Damn, It’s all so tidy - even when it’s beta.

But without smart code sense, it is useless for real developers, my question is - will it be smart and good as Zend studio’s?
Can it be done with the current framework that you build for the sugars?

I looked over the thread and I saw the performance issue, Zend studio resolved that with a simple hidden ’.project’ file, I think you can do that too.

B.T.W - I really love the way it synchronize with the server.

I don’t think there’s any major technical reasons why it can’t be dynamic, but I do think that there are more important things to add to it beforehand.

Cool Thanks for the fast response.

morishani - 09 January 2009 01:50 PM

I looked over the thread and I saw the performance issue, Zend studio resolved that with a simple hidden ’.project’ file, I think you can do that too.

The problem with this, is source control. If you use git, or SVN, or any similar system, you’ll have to do one of two things when your project management tool uses this “hidden file” system:

* You could have the system “ignore” the hidden file - however, if you did so, every person checking out the repository would have to re-generate the file the first time they opened the project
* You could have the system not “ignore” the hidden file - in this case, however, every time you change *any* file in your project, it’s likely to change the codesense data, so the hidden file will be updated, so you’ll have to check in one extra file every time you change any file in the project. This quickly clutters the change history in the SCM, and is really annoying.

Neither case is really ideal - not to mention, that no matter what you do, it will be “delayed”, in that any change you make in a file, will not instantly update the hidden file, which means the codesense will be out of date, and thus auto-completion will work inconsistently with the content of your file.

There are lots of problems to be overcome, and I admit that I very much don’t know the solution to them. I don’t know if anybody does. The advantages and disadvantages will have to be weighted and considered, before a solution is decided upon.