Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 36

Thread: Trying out a new route...

  1. #21
    Join Date
    Jul 2010
    Posts
    19

    Default

    That will be very good because you did a very good work with Bluebell. I'm not in the Spring RCP, it's just my opinion.

    Quote Originally Posted by julio.arguello View Post
    Perhaps you'll find usefull this post:
    http://forum.springsource.org/showth...544#post351544

    Bluebell demos are now online. It will be a pleasure for me to collaborate with Spring RCP guys.

  2. #22

    Default Valkyrie

    in response to the question: we can port Valkyrie to Spring RCP (in effect, creating a 2.0 version, as this'll break about every RCP code out there) or let Valkyrie live on as a project on it's own (perhaps merging it with Bluebell?). In that case there the second question: what to do with Spring RCP?

    Valkyrie should take on a life of it's own especially if the port will break existing applications.

  3. #23
    Join Date
    Mar 2007
    Location
    Oudenaarde
    Posts
    294

    Default

    Quote Originally Posted by miked_musician View Post
    in response to the question: we can port Valkyrie to Spring RCP (in effect, creating a 2.0 version, as this'll break about every RCP code out there) or let Valkyrie live on as a project on it's own (perhaps merging it with Bluebell?). In that case there the second question: what to do with Spring RCP?

    Valkyrie should take on a life of it's own especially if the port will break existing applications.
    I agree, this does bring up that question. Porting Valkyrie to RCP would in essence just be a rename, as most of the code is incompatible with the current RCP codebase.
    MSN: PM me please
    Skype: doclo_lieven

    Spring Rich Client Project Lead

  4. #24
    Join Date
    Sep 2010
    Posts
    19

    Default

    How much Spring RCP code is there "out there"?
    Make it version 2.0. Anyone with existing code just keeps using what they already have.
    If they want some particular new feature only in v2 then they will have to fix their code to match the new version.
    Keep a branch available for fatal bug fixes to be back ported to if necessary.

  5. #25
    Join Date
    Jul 2010
    Posts
    19

    Thumbs up

    I'm agree with this point. Will no be the first project doing that.

    Quote Originally Posted by opticyclic View Post
    How much Spring RCP code is there "out there"?
    Make it version 2.0. Anyone with existing code just keeps using what they already have.
    If they want some particular new feature only in v2 then they will have to fix their code to match the new version.
    Keep a branch available for fatal bug fixes to be back ported to if necessary.

  6. #26
    Join Date
    Mar 2007
    Location
    Oudenaarde
    Posts
    294

    Default

    Well, there is also another reason. Spring RCP used the org.springframework package in its code. As Spring RCP isn't really a part of SpringSource (none of the current developers are SpringSource employees and there hasn't been involvement of SpringSource employees for a couple of years), some of us were wondering whether this was a good idea.
    Valkyrie was made without any link to SpringSource and I think until SpringSource shows a genuine interest in it's development, the packaging should reflect the current situation. Repackaging is only a small step, so it can be done really quickly. I think the main point should be to make Valkyrie stand on it's own and prove itself out there.
    There is a large userbase out there, I have noticed this over the last year. Most of them keep themselves below the radar. In essence, whether the next generation would be called Spring RCP of Valkyrie, the amount of work would remain the same. Back ports would be a lot of work, as the architecture has changed quite a bit. It would be like porting JSF 2 features to JSF 1.2.
    We also wouldn't be the first framework or product to change names in order to reflect large changes.
    MSN: PM me please
    Skype: doclo_lieven

    Spring Rich Client Project Lead

  7. #27

    Default

    Hi guys,
    did you come to a decision?
    We would be very pleased to use Bluebell-SpringRCP-Valkyrie - the name here is not so central, let's call it your solution - for our small open-source project at http://sourceforge.net/projects/jttslite/ but we still don't see any release yet.
    In the last weeks we tried putting together some single libraries, such as bsaf and beanfabrics or jgoodies binding, but the added value of your solution would be huge.
    So the question is: what's going on? Do you have any due date or scheduled milestone release?

    Cheers
    Davide

  8. #28
    Join Date
    Nov 2011
    Posts
    1

    Default

    Hi Lieven, Can I download valkyrie with maven or needs to be installed manually?

    Thanks and regards.

  9. #29

  10. #30

    Default

    hi, i really can't find much information about this valkyrie project, can someone point me to a link or forum?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •