Fork me on GitHub

Status of Clip/PageMaster  Bottom

Go to page 1 - 2 - 3 [+1]:

  • I'm just wondering if we can get a status report on Clip/PageMaster. I go to the Cozi and the source is last dated August 3, 2010. I go to the Github page and the source is last dated August 18, 2010. Word has it that it is on the way, but where exactly is the proper place to get it?

    The Cozi page has a link to download 0.4.2. But even though the Github source is 15 days newer, it will not install in Zikula 1.3 ("invalid structure") and the filename is "zikula-modules-Clip-0.4.1-103-g0fbb203", which leads one to believe it is version 0.4.1.

    What and where is the real and latest dev download? Is there one? I would really like to test with Zikula 1.3 so I can have a head start on the many projects I plan to use this for.

    --
    Harness Technology
  • I'm getting concerned. My development has been stalled once again. I understand that it's in pre-release form, but it's been unusable for too long.
  • Development of code under GIT is not like SVN because commits can be made offline. This allows one to create actual working branches and not branches that may be broken at some commit. Mateo has been working extensively on the 'doctrine' branch which brings all the new Zikula 1.3 features + relations into Clip.

    There will be an update about this soon.

    Drak

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • Hi all
    As said on the mailing list, the GIT folder needs to be renamed to 'PageMaster' instead Clip because the code functions are not renamed yet. I'll finish and commit the last stuff to get the Doctrine relations running tomorrow I hope, I got some fatigue in front of the computer lately.

    Greetz

    --
    - Mateo T. -
    Mis principios... son mis fines
  • Cool, thanks for the updates, guys. Looking forward to playing around with all the new goodies!

    --
    Harness Technology
  • Super duper. I have lots of ideas I need to doink around with.
  • nestormateo

    I'll finish and commit the last stuff to get the Doctrine relations running tomorrow I hope,
    Greetz


    When this is ready, is this the right place to find it?
    http://github.com/zi…ules/Clip/downloads

    --
    Damon
    Catamaran Sailing at TheBeachcats.com
  • Until we actually release Zikula 1.3.0, no module can be released that is Zikula 1.3.0 specific because, Zikula 1.3.0 is still a development version and anything can (and in a few cases will) be changed. The official place for all released modules will continue to the extdb however RC releases may be available from each module's github diownload page (these are generated automatically when a module is tagged). Clip may make it's way onto the continuous integration server also.

    Regards,

    Drak

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • CI for Clip would be nice,
    even when github already provides the "Download Source" button at the top.

    Now I'm figuring out the clip_formrelation plugin to handle the relations in the edit form, and IMO, the modern way to manage the relations nowadays is with a Javascript AutoCompleter. Any objections to rely on Javascript for this? Manual IDs or a fixed selector are not too good options IMHO.

    I was expecting different behaviours on Doctrine 1.2 and that gave me a little surprise, and this is the last thing to get sorted. Opinions please? icon_smile

    --
    - Mateo T. -
    Mis principios... son mis fines
  • There are times when I've had to remove javascript from some modules for some reason or another. Not sure why I'd want to do it in Clip, but you never know. If I were paying you I'd require a solution that would work in any browser. But I'm not, so... :)
  • I'm with bronto, there needs to be a non-java fall back.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • Better yet, how about a non-javascript fall back?

    --
    Harness Technology
  • Don't make me stalk you next time I see you're in the Rose City Wendell. I may have to Gibbs slap ya :)

    --
    Home Page | Find on Facebook | Follow on Twitter
  • I think we had some discussions about this a long time ago and it's more and more relevant today than ever: that for administrative tasks, requiring JS is not unacceptable any more. There are literally dozens of services now which require Ajax capabilities. A JS fallback is always nice but not a 100% must. I think the better compromise in this situation is that, in order to get the features up and working, first let's follow Mateo's recommendation and have the JS stuff, then work on a JS fallback in a later milestone since lack of JS fallback could not be seen as a blocker.

    Regards,

    Drak

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • I hadn't thought of this in terms of admin vs. non-admin. I agree it is reasonable to have higher requirements for admin tasks, although it is not desirable. I say, "proceed" Mateo. We can deal with non-js later.

Go to page 1 - 2 - 3 [+1]:

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