1 2 Previous Next 22 Replies Latest reply on Mar 10, 2009 7:50 AM by kukeltje Go to original post
      • 15. Re: oryx and jbpm
        heiko.braun

        ok, let's aim at thursday 2pm (GMT+1). I'll meet you in the chatroom:
        irc.codehaus.org#jbpm

        • 16. Re: oryx and jbpm

          Sorry for some reason the forums never let me know there was a response to this thread so I missed the chat if you needed me there.

          • 17. Re: oryx and jbpm

            Any results or logs available from the chats?

            • 18. Re: oryx and jbpm
              kukeltje

              Eiki,

              Best is to subscribe to the dev mailinglist to receive posts to this forum.

              Yes we missed you a lot... no just kidding. It was kind of fruitful and I posted a new topic kind of related to this. But a short summary would be

              Tom has two big reservations and one minor
              - One is time (the july 1st deadline for 4.0.0.GA)
              - Is it realy needed? Don't customers always use their own ui framework anyway?
              - The minor one is backwards compatibility (shouldn't we support what is there now?)

              The first is valid. If you want to do new things you should do them fairlly well (docs, how to embed in your own application, examples , an editor? etc)
              The second one is kind of depending on what you provide I think. People using struts, velocity or whatever will not quickly als embed. jsf, certainly if what is provided out of the box is kind of limited. For an 'independent' technology like XForms that might be different, so I think that argument is not realy valid.

              We did not realy talk about editors or the XForms engine, but I do admit to Toms argument that the Orbeon site is more mature. That does not say anything about the engine and/or editor though

              • 19. Re: oryx and jbpm

                Alright so no decision on wether or not to implement jdpl editor yet? Perhaps we will just start then fairly soon on our own. We will probably focus on jpdl 3 to start with and get that working with our extensions.

                cheers
                -Eiki

                • 20. Re: oryx and jbpm
                  kukeltje

                  the jpdl editor was not going to be subject of discussion in this 'meeting'. Forms was the topic

                  • 21. Re: oryx and jbpm

                    Hehe ok, my misunderstanding then. In my view xforms editor is out of scope for jpbm but a proper web based jpdl editor is not.

                    • 22. Re: oryx and jbpm
                      kukeltje

                      well, if xforms is chosen to be the next forms technology for jBPM, an editor is *not* out of scope. Maybe not in scope for 4.0.0.GA, but not much later

                      1 2 Previous Next