Fork me on GitHub

eclipse and zikula  Bottom

  • hello

    i m using eclipse 3.2, which is quite old.

    I would like to know if it's possible with recent version of eclipse :
    - to create a project for zikula core
    - in the module directory, to check out for a module (in order to synchronize it later)


    which version , is the 3.5 stable?

    thanks



    edited by: mumuri, datetimebrief
  • Hi, I've been using Eclipse 3.5. Personally, I used the Galileo edition for PHP, then I added the necessary plugins for SVN, CSS, JavaScript, etc.

    The SVN plugin is great. If you're not an SVN expert, it makes things much simpler for you.

    After that, you can checkout the core or any module and do what you want with it.

    Personally, I'd never go back to any other method of doing work on Zikula - specially if you want to work on stuff like lang strings. The multi-file search and replace is a dream. HTH.
  • A couple of links to get you going:

    http://www.poweredbypulse.com/download_linux.php

    http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/galileo/SR1/eclipse-PHP-galileo-SR1-linux-gtk.tar.gz

    (I'm a Linux user, so you might need to choose the distribs for Windows if that's your OS...)
  • Little update: I'd recently installed a new hard disk, so I needed to re-install my Eclipse.

    When I originally installed, I used the base Galileo from eclipse.org and then installed additional plugins to arrive at my perfect installation (or 'stack'). So I had to deal with the various dependencies and install everything in the right order ('don't put on the roof until you've built the walls'). Even so, Eclipse was quite forgiving of my various first-timer mistakes and I got a working installation running perfectly, after a little patient work.

    This time around, I used the Pulse version, which I'd recommend to you. I got my additional stuff installed with zero hassle, and it all worked perfectly for me under Linux.

    Again, I'd recommend Eclipse to anyone planning to do any work on the Zikula code base. It's a perfect tool for the job.

    IIRC, Drak, Zikula's lead dev, uses Zend Eclipse, the commercial, deluxe version suitable for a professional developer.

    But the distribs I linked to above are excellent. Eclipse.org offerings are totally-FOSS. Pulse gives you a free path and a payable path.

    Ubuntu Linux also offers you totally pain-free installation via the Ubuntu Software Center. But then you will have to install any desired add-ons yourself.

    My personal choice next time around will be the Pulse path.
  • I've been using Zend Studio for Eclipse which is a slightly more featured version of Eclipse PDT. However I recently started using NetBeans for PHP. It's also java based (if you use linux you are better using sun-java6-jre). From a PHP IDE stand point, NetBeans 2.8 does everything that Eclipse PDT does - including version control integration, tracker integration, unit test, debugger and so on (and it's just 25MB over 350MB of Eclipse PDT). For me, one major advantage of NetBeans over Eclipse is the diff tool - it's just way nicer and NetBeans appears to be much lighter weight too on the computer.

    Drak

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • Thanks for the NetBeans tip. Let me add that Eclipse is a very nice tool for PHP development. I have used it for years on Mac OS X and it works like a charm. You can even get the debugger working with a bit of pain.

    How difficult is it to get the debugger going on NetBeans?



    edited by: Paustian, datetimebrief
  • Sure, I love Eclipse, and I love Zend Studio for Eclipse even more, but NetBeans is was easier to get working, including for the debugger. They also cleverly have an Eclipse keyboard map so you can continue to use all the same shortcuts (Options -> Keymap-> choose Eclipse).

    Drak

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • hello

    you didn't reply, can we do checkout for zikula and a checkout in the module directory for each module in order to synchronise it later ?

    thank's in advanced
  • There are (at least) two different possible approaches:

    1st approach:
    * Checkout the core into a project
    * Checkout the modules into other (separate) projects
    * Add a dependency to the core project in the modules project settings

    2nd approach:
    * Checkout the core into a project
    * Edit the SVN properties of the modules folder
    * Add the repositories you want to incorporate as SVN externals
    * Update

    Both of them have different effects. I suggest you to try it out in practice to decide which one better fits to your need.

    Edit: this is for Eclipse, don't know NetBeans that much.

    --
    Guite | ModuleStudio
  • 3rd approach (under linux):
    * create a new project 'zikula-core', pointing to the zikula-core repository, and make a checkout of the trunk
    * create other projects for specific modules the same way
    * add symlinks within the zikula-core/modules directory to your separate projects

    If you use the subversive plugin: create a new SVN > repository location, pointing to the zikula core (https://code.zikula.org/svn/core). You can then easily switch between trunk and some branch using Project (right-click) -> Team -> Switch...

    In my case: I like it if the SVN-plugin in eclipse shows that I have an unchanged working copy (so without all the '>' signs). This tells me that any module is running without any modifications to the core. But, this is completely personal.

    --
    -- Teb
    -- Dutch Zikula Community


    Support questions in a Personal Message will be ignored. Use the forums at all times!
  • thanks for the information
  • I do it very simply:

    Code

    # checkout core into a folder trunk
    svn checkout https://code.zikula.org/svn/core/trunk trunk

    # checkout individual modules into modules folder
    cd trunk/modules
    svn checkout https://code.zikula.org/svn/content/trunk content
    svn checkout https://code.zikula.org/svn/foo/trunk foo


    This works because we have SVN:ingore setup. You can develop directly in the modules folder and commit as normal since all the SVN information is in the subfolders and all extra modules are ignored by the core SVN.

    Saying that, I've personally ditched subversion for GIT which flat out kills any reason to use subversion at all.

    Drak

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak

This list is based on users active over the last 60 minutes.