Today I am happy to bring you the second alpha release of the brand new Doctrine MongoDB Object Docu[...]

In preparation of the next ORM Beta Release in the next days we already released Doctrine DBAL 2.0.0[...]

My last post brought up a lot of questions on the differences between document-oriented and relation[...]

Hi, my name is Bulat S. (my last name won't make it any easier, but in case you were wonde[...]

Guys from editor infrastructure asked me to help him to test new editor infrastructure that brings up also line wrapping features. Probably you remembered that this feature was enabled during NetBeans 6.9 development, but because it introduced many problems and there wasn't time to stabilize it enough, it's not in NetBeans 6.9 available. 

We would like to stabilize the new infrastructure as much as possible before it will be switch on to be be available by default.You can enable the feature in development build through command line option: -J-Dorg.netbeans.editor.linewrap=true . Do it only with a development build, even if the optoin works in NetBeans 6.9, the new infrastructure is not stable enough there.

So I would like to ask you, if you use a latest development build, run the build with the mentioned option. You can start NetBeans from command line with the option or place the option in the ${nb_dir}/etc/netbeans.conf file (add into netbeans_default_options).

When you started NetBeans with this, there should be Line Wrapping option in the formatter.

When you find out an issue with it, please report it in our Bugzilla. For such issue the product should be Editor, component Painting & Printing and please mark all reports with the status whiteboard: linewrap so we can easily track them. The tentative plan is to enable this again for M1 of NetBeans 6.10 but this all depends on the additional feedback and testing.

Thanks for your help with this.

The Doctrine MongoDB Object Document Mapper includes a fluent object oriented API for building queri[...]

One major advantage to using something like MongoDB is the fact that it is schema-less. We can store[...]

The Doctrine ActiveEntity Extension is just an experiment, nothing that will be developed much[...]

The CakePHP development team is happy to announce the release of CakePHP 1.3.3[1]. 1.3.3 is a maintenance release for the 1.3 branch and contains bugfixes and optimizations for features found in 1.3.

If you access a collection of Entity A pointing to Entity B, Doctrine2 always initializes the comple[...]

Today, I would like to show you several improvements we have implemented in our PHP support. Have a look at the following picture, can you see any of them?

I think that most of you have noticed that:

• PHP projects with framework(s) are annotated with framework icon (together with improved tooltip)
• PHP frameworks tell project which files are important
• we have new icons for INI files and Include Path node

 

That's all for today, as always, please test it and report all the issues or enhancements you find in NetBeans Bugzilla (component php, subcomponent Project). Please notice that if you write a comment here but do not report a bug or enhancement, nothing will probably happen ;)

I have made a "branch" of the sphinx behavior ( http://bakery.cakephp.org/articles/view/sphinx-behavior ), and make a component and a behavior that uses this component. I have also add more features like the geosearch filter. Motivation: i have a many to many relation, lets imagine that i have a product with a bunch of many to many relation, example; a product that is of various categories and have states(used,new,etc) and is for (sell,rent,etc) and could be in many provinces and could be pay in varios ways (paypal, visa, etc). And i wanna get the provinces of the products who are for rent and new, this is a complex and slow query with a lot of inners joins that could be transform really rapid think using sphinx, for that we need to work the all the results of the SphinxApi::RunQuery

The aim is pull data from your database through JSON and REST-like services from CakePHP. I have used CakePHP 1.3.2 and Dojo Toolkit 1.4.2.

I was taking a look at ZenTest a while ago, especially the autotest functionality. As stated in the ZenTest site, autotest: Improves feedback by running tests continuously. Continually runs tests based on files you’ve changed. Get feedback as soon as you save. Keeps you in your editor allowing you to get stuff done faster. To add more bang to your buck, you can get continuous notifications from growl every time you save a file, alerting you if any of your previous test cases have failed. Googling around I wanted to see if this can be tied into testing with CakePHP. If I did a horrible job googling and there is already something out there that mimics this functionality please send me a link. Anyways, I stumbled across Watchr. Watchr is a tool that monitors a directory tree, and triggers a user defined action whenever an observed file is modified. At that point trigger a CakePHP test suite command line argument and send the results to growl. And there we have it, continuous testing with growl notifications on CakePHP using Watchr.

Small helper that you can use to output valid, minified and clean (x)HTML automatically!

How to install an Intrusion Detection System to protect your CakePHP application from hackers

You will often come across the requirement to display aggregate values of data that can be computed [...]

Today, I would like to introduce an improvement that is related to PHP files which do not belong to any PHP project. In NetBeans, these files can be not only opened but also run or even debugged. Just open a file, right click in the file content and choose Run File (SHIFT + F6) and the following dialog appears:

As you can see, one can provide script parameters, change working directory or even specify PHP parameters (useful, for example, if one wants to change PHP include path). If one runs the script always with the same parameters, it is useful to remember these settings so the IDE does not ask you again.

Similarly, if one wants to debug an opened file (CTRL + SHIFT + F5):

As you can see, the same dialog is used.

One more note - because the files do not belong to any PHP project, running (or debugging) is done only via the PHP command line interpreter (can be found in Tools > Options > PHP > General). This means that the output can be reviewed in the Output window:

That's all for today, as always, please test it and report all the issues or enhancements you find in NetBeans Bugzilla (component php, subcomponent Project). Please notice that if you write a comment here but do not report a bug or enhancement, nothing will probably happen ;)

This release contains following changes:

• Feature #61: Real-time Console Output
• Feature #66: JSON Support

This release updates the internal PEAR library.