This is just a quick heads up that I’m going to be making the 1.2
branch of the engines plugin the official release in the very near
future. If you’re planning on using the engines plugin with Rails 1.2,
I’d really appreciate it if you could test the current branch with
your 1.2 application:
Check out the UPGRADING notes for what to be wary for, and post any
bugs back to the Collaboa site, http://dev.rails-engines.org (login:
anon, password: engines).
If you’re stuck on Rails 1.1.6 or lower (and I’m sure there are many
who are), don’t try to install this release. It won’t work. It should
actually complain gracefully, but there are no guarantees.
Furthermore, if you’re linking to the http://svn.rails-engines.org/plugins/engines tag via SVN externals,
you MUST update your link to either freeze at the current revision, or
switch to a specific tag. Alternatively, look at the Piston tool for
locking down your version of the engines plugin to a known-working
revision.
This is unbelievably important - ignore at your PERIL.
If you’re stuck on Rails 1.1.6 or lower (and I’m sure there are many
who are), don’t try to install this release. It won’t work. It should
actually complain gracefully, but there are no guarantees.
I should also add that it looks like the “login engine” and “user
engine” won’t be joining us on the journey to 1.2. Only ever really
intended as a demonstration of the sort of thing the engines plugin
might enable, they rapidly became the two planks which the engines
plugin was nailed to by many people in the Rails community.
If you’re stuck on Rails 1.1.6 or lower (and I’m sure there are many
who are), don’t try to install this release. It won’t work. It should
actually complain gracefully, but there are no guarantees.
I should also add that it looks like the “login engine” and “user
engine” won’t be joining us on the journey to 1.2. Only ever really
intended as a demonstration of the sort of thing the engines plugin
might enable, they rapidly became the two planks which the engines
plugin was nailed to by many people in the Rails community.
Without the login/user engine plus engines are nothing but plugins based
on the post above…and going through the rails-engine site … I have
hard time to understand what is it good for? I mean you can make a “gem”
and share application … code sharing between apps can be a plugin… I
am sorry could you please provide some explanation?
Furthermore the rails-engine site seems to be outdated any plans on
updating the pages/screencast at the time of 1.2 engine launch
If you’re stuck on Rails 1.1.6 or lower (and I’m sure there are many
who are), don’t try to install this release. It won’t work. It should
actually complain gracefully, but there are no guarantees.
I should also add that it looks like the “login engine” and “user
engine” won’t be joining us on the journey to 1.2. Only ever really
intended as a demonstration of the sort of thing the engines plugin
might enable, they rapidly became the two planks which the engines
plugin was nailed to by many people in the Rails community.
I think this is quite sad, as sharing engine-code the Open Source
way is in my view still a superior use. Eventhough I do agree that the
login_engine was crap in terms of the coding & session-handling. Still
it could have been fixed… And nevertheless I do bilieve that sooner
or later as the Rails community grows shared engines will re-emerge.
Anyway I am happy to have jumped ship last week to an OpenID provider.
For me it’s - for now - farewell engines
Still many thanks anyway for having engines and the login engine
around for as long as it lasted!
I think this is quite sad, as sharing engine-code the Open Source
way is in my view still a superior use. Eventhough I do agree that the
login_engine was crap in terms of the coding & session-handling. Still
it could have been fixed… And nevertheless I do bilieve that sooner
or later as the Rails community grows shared engines will re-emerge.
I think “crap” is a bit strong!
The reason they’re not being publicly migrated up to 1.2 compatibility
is threefold:
they smell bad and people have developed - for whatever reason -
negative feelings towards them;
they distract from the point of the engines plugin, which is to
make it easy for YOU to develop powerful plugins; and
so that other people can fill the void with their own open-source
plugins, using the engines plugin enhancements if they feel it’s
useful. We’ll be writing our own replacement internally, which may or
may not be released.
Also, in case you hadn’t picked up on it, no such thing as an “engine”
anymore. The login_engine would have to become the “login plugin”, if
anyone tweaks it to work with engines 1.2
On Wed, 24 Jan 2007 13:57:06 +0100, Wybo W. wrote:
I should also add that it looks like the “login engine” and “user
engine” won’t be joining us on the journey to 1.2. Only ever really
intended as a demonstration of the sort of thing the engines plugin
might enable, they rapidly became the two planks which the engines
plugin was nailed to by many people in the Rails community.
I think this is quite sad, as sharing engine-code the Open Source
way is in my view still a superior use.
I’d still love for someone to help me work on Hark (an
authentication-only,
partial replacement for LoginEngine), where “help” may be as simple as
“integrate and give feedback”. I have it partly coded and up at http://svn.jay.fm/public/hark, but at the moment I have no projects
using
it, and I’m loathe to try releasing a library that I don’t even use!
Without the login/user engine plus engines are nothing but plugins based
on the post above…and going through the rails-engine site … I have
hard time to understand what is it good for? I mean you can make a “gem”
and share application … code sharing between apps can be a plugin… I
am sorry could you please provide some explanation?
While it’s possible to share all of this stuff in a normal plugin, you
need work hard to do it sensibly. Having the engines plugin installed
along side them makes it really easy, and provides a bunch of
mechanisms for developers to do so.
Furthermore the rails-engine site seems to be outdated any plans on
updating the pages/screencast at the time of 1.2 engine launch
I’ve begun updating the site (you’ll see references to “installing an
engine” disappear, for example). I may produce a new screencast too,
unless someone else beats me to it. Hint, hint.
login_engine was crap in terms of the coding & session-handling. Still
it could have been fixed… And nevertheless I do bilieve that sooner
or later as the Rails community grows shared engines will re-emerge.
I think “crap” is a bit strong!
A bit too, yes, but not a whole lot
I mean storing an object in the session, instead of it’s id, and the
form_input function…
may not be released.
I doubt the first point outside the Rails core group…
The second point is somewhat true, although I still see code-
sharing as the main benefit of engines, and this is give and
take.
The third is valid, still I think there should be FOSS login-
engines available. See my next post.
Also, in case you hadn’t picked up on it, no such thing as an “engine”
anymore. The login_engine would have to become the “login plugin”, if
anyone tweaks it to work with engines 1.2
The conceptual difference could still be usefull, engines being
full stack, model to view, and plugins focussing more on a single
level… (that could mean having an engine consisting of 3 or
more plugins)…
Wybo
–
J *
~
–
:
History, Informatiekunde (computer linguistics, IR, webtech) and
Philosophy
Also, in case you hadn’t picked up on it, no such thing as an “engine”
anymore. The login_engine would have to become the “login plugin”, if
anyone tweaks it to work with engines 1.2
I guess the bigger question for some of us (myself included) that
have dependencies on this is: what now?
Pull the code into my project and maintain it myself? And for me,
it’s not just login engine, but also user engine. I suppose I’ll just
roll it into my app and make the necessary changes.
I think this is quite sad, as sharing engine-code the Open Source
way is in my view still a superior use.
I’d still love for someone to help me work on Hark (an authentication-only,
partial replacement for LoginEngine), where “help” may be as simple as
“integrate and give feedback”. I have it partly coded and up at http://svn.jay.fm/public/hark, but at the moment I have no projects using
it, and I’m loathe to try releasing a library that I don’t even use!
I am extremely busy this month, but after it I will have a look. Still
OpenID has also caught my interest, both because it allows further
specialization (you can leave account-issues to a third party) and
also the posibillity of an identity shared across many sites.
If you don’t need to upgrade to Rails 1.2… you’re fine. Just ensure
the new engines and rails releases. Document it a bit. Hell, maybe
even share it with the world…
Yah, I plan on using 1.2 some point soon. Although when is dependent
on when my hosting provider upgrades. No huge rush tho.
As for options 1 & 2, this is what I planned to do and yah,
everything is svn’d (I actually have the properties set to update the
engines code in my tree when i do an up). Not sure tho if I’ll have
much time to invest in a plugin (would be nice tho) as I’m focused on
getting our app features done, which is why I chose the engines in
the first place ;). But who knows? I’ll see how things go and if it’s
something that can be done, then maybe I or someone else will take a
shot at it. Thx again,
I guess the bigger question for some of us (myself included) that
have dependencies on this is: what now?
Pull the code into my project and maintain it myself? And for me,
it’s not just login engine, but also user engine. I suppose I’ll just
roll it into my app and make the necessary changes.
What I’d recommend you do depends on your plans with Rails.
If you don’t need to upgrade to Rails 1.2… you’re fine. Just ensure
that any externals are properly locked-down to tags, or secured with
Piston.
If you ARE upgrading to Rails 1.2, you have two basic options:
copy the controllers, models and so on into your own app.
take a dump of the current login/user engines and import it into
your own repository - you are all using version control, right? Then
update them to work with Rails 1.2 as plugins that play nicely with
the new engines and rails releases. Document it a bit. Hell, maybe
even share it with the world…
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
