I just wanted to announce my latest plugin: LegacyInterop The 5 second video, minus the video, looks like this: $ ./script/plugin install svn://lirp.rubyforge.org/var/svn/lirp/trunk/legacy_interop $ echo LegacyInterop.act_as_dotnet >> config/environment.rb Done! Agile! Pragmatic! The plugin includes support for a large number of legacy systems, all using the "act_as" pattern. act_as_dotnet act_as_java act_as_php act_as_sh act_as_perl So for all those complaining about their bosses imposing a platform on them.. I say: be free, be agile, use LegacyInterop. Warning: void where prohibited. -- Posted via http://www.ruby-forum.com/.
Sebastian Delmont wrote:> I just wanted to announce my latest plugin: LegacyInterop > > The 5 second video, minus the video, looks like this: > $ ./script/plugin install > svn://lirp.rubyforge.org/var/svn/lirp/trunk/legacy_interop > > $ echo LegacyInterop.act_as_dotnet >> config/environment.rb > > Done! Agile! Pragmatic! > > The plugin includes support for a large number of legacy systems, all > using the "act_as" pattern. > > act_as_dotnet > act_as_java > act_as_php > act_as_sh > act_as_perl > > So for all those complaining about their bosses imposing a platform on > them.. I say: be free, be agile, use LegacyInterop.Interesting, if I understand correctly. Please explain a little more what you can do with that. Sa?a Ebach
Sascha Ebach wrote:> Sebastian Delmont wrote: > >> I just wanted to announce my latest plugin: LegacyInterop >> >> The 5 second video, minus the video, looks like this: >> $ ./script/plugin install >> svn://lirp.rubyforge.org/var/svn/lirp/trunk/legacy_interop >> >> $ echo LegacyInterop.act_as_dotnet >> config/environment.rb >> >> Done! Agile! Pragmatic! >> >> The plugin includes support for a large number of legacy systems, all >> using the "act_as" pattern. >> >> act_as_dotnet >> act_as_java >> act_as_php >> act_as_sh >> act_as_perl >> >> So for all those complaining about their bosses imposing a platform on >> them.. I say: be free, be agile, use LegacyInterop. > > > Interesting, if I understand correctly. Please explain a little more > what you can do with that. >I think Sebastian''s joking...... pretty funny too. b
On 2/20/06, Sebastian Delmont <sd@notso.net> wrote:> I just wanted to announce my latest plugin: LegacyInterop > > The 5 second video, minus the video, looks like this: > $ ./script/plugin install > svn://lirp.rubyforge.org/var/svn/lirp/trunk/legacy_interop > > $ echo LegacyInterop.act_as_dotnet >> config/environment.rb > > Done! Agile! Pragmatic! > > The plugin includes support for a large number of legacy systems, all > using the "act_as" pattern. > > act_as_dotnet > act_as_java > act_as_php > act_as_sh > act_as_perl > > So for all those complaining about their bosses imposing a platform on > them.. I say: be free, be agile, use LegacyInterop. > > Warning: void where prohibited. > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >So what does it actually do? -- Kyle Maxwell Chief Technologist E Factor Media // FN Interactive kyle@efactormedia.com 1-866-263-3261
act_as_dotnet act_as_java act_as_php act_as_sh act_as_perl ;) -- Posted via http://www.ruby-forum.com/.
> I think Sebastian''s joking...... pretty funny too.If he did, I fell for it ;) Sa?a Ebach
Oh, I''m serious!!! or as serious as you can be when you''re playing with route recognition and generation. Sascha Ebach wrote:>> I think Sebastian''s joking...... pretty funny too. > > If he did, I fell for it ;) > > Sa?a Ebach-- Posted via http://www.ruby-forum.com/.
Sebastian Delmont wrote:> Oh, I''m serious!!! or as serious as you can be when you''re playing with > route recognition and generation.Huh. Well I''ll be. Sorry about that Sebastian. Ok, what exactly does your plugin do? b> Sascha Ebach wrote: > >>>I think Sebastian''s joking...... pretty funny too. >> >>If he did, I fell for it ;) >> >>Sa?a Ebach > > >
LegacyInterop.act_as_dotnet makes all your pages and links use the "aspx" extension. LegacyInterop.act_as_java makes all your pages and links use the "jsp" extension. LegacyInterop.act_as_php, act_as_sh, etc... they all work as expected. Still not implemented are several features, like error pages, http headers, response delays, simulated vulnerabilities, etc, etc. We could use a hand implementing those. Ben Munat wrote:> Sebastian Delmont wrote: >> Oh, I''m serious!!! or as serious as you can be when you''re playing with >> route recognition and generation. > > > Huh. Well I''ll be. Sorry about that Sebastian. Ok, what exactly does > your plugin do? > > b-- Posted via http://www.ruby-forum.com/.
Sebastian Delmont wrote:>LegacyInterop.act_as_dotnet makes all your pages and links use the >"aspx" extension. > >LegacyInterop.act_as_java makes all your pages and links use the "jsp" >extension. > >LegacyInterop.act_as_php, act_as_sh, etc... they all work as expected. > >Still not implemented are several features, like error pages, http >headers, response delays, simulated vulnerabilities, etc, etc. We could >use a hand implementing those. > > >This is usefull and makes sense, when... ?!? Matthi am just curious about...
When your dumb boss tells you "but we need to use php". Or when you want to keep the competition in the dark about the strategic advantages of using Rails. Or just because you just wanted to explore the routing code and had nothing better to do. matthibcn wrote:> Sebastian Delmont wrote: > >>use a hand implementing those. >> >> >> > This is usefull and makes sense, when... ?!? > > Matthi > > am just curious about...-- Posted via http://www.ruby-forum.com/.
You seem to be the right to aks this: How do I set up a generic route point at /blabla/somestuff.txt where somestuff could be the id of an actual stuffing ,-) On Monday, February 20, 2006, at 6:41 PM, Kris Leech wrote:>act_as_dotnet >act_as_java >act_as_php >act_as_sh >act_as_perl > >;) > >-- >Posted via http://www.ruby-forum.com/. >_______________________________________________ >Rails mailing list >Rails@lists.rubyonrails.org >http://lists.rubyonrails.org/mailman/listinfo/railsMikkel Bruun www.strongside.dk - Football Portal(DK) nflfeed.helenius.org - Football News(DK) ting.minline.dk - Buy Old Stuff!(DK) -- Posted with http://DevLists.com. Sign up and save your time!
The easiest way to deal with extensions is to create a route like
/blabla/:id/content.txt
Routing doesn''t like extensions very much in the variable parts of
routes. It just considers them part of the :id.
You can also use "/blabla/:id", and have your model add
".txt" to it''s
id''s by defining the to_param method. (i.e. def to_param;
"#{id}.txt";
end) and having your actions (or the find method for the model) take
care of removing the "txt".
Mikkel Bruun wrote:> You seem to be the right to aks this:
>
> How do I set up a generic route point at /blabla/somestuff.txt
>
> where somestuff could be the id of an actual stuffing ,-)
>
> On Monday, February 20, 2006, at 6:41 PM, Kris Leech wrote:
>>_______________________________________________
>>Rails mailing list
>>Rails@lists.rubyonrails.org
>>http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
> Mikkel Bruun
>
> www.strongside.dk - Football Portal(DK)
> nflfeed.helenius.org - Football News(DK)
> ting.minline.dk - Buy Old Stuff!(DK)
--
Posted via http://www.ruby-forum.com/.
d2ce0ca4c245e801fad36bde15f386a7 <a href="http://13.ceonotorizlaba.info/prestitofilettino/"> prestitofilettino </a> http://13.venecettizenzeta.info/immaginiditramonti/ <a href="http://6.venecettizenzeta.info/karcherk397m/"> karcherk397m </a> <a href="http://1.sesepokukluggi.info/testicanzonianastasia/"> testicanzonianastasia </a> http://7.guentojungh.info/curarelacne/ <a href="http://13.ilisapatrokko.info/guadagnaresms/"> guadagnaresms </a> <a href="http://19.silicatokirpicho.info/ufficioleeds/"> ufficioleeds </a> http://18.silicatokirpicho.info/manicottoindustriale/ <a href="http://11.iliobaratrontomena.info/conceriaanguillaproduzione/"> conceriaanguillaproduzione </a> <a href="http://20.silicatokirpicho.info/ristoranteborgosangiovanni/"> ristoranteborgosangiovanni </a> http://17.draeraunutri.info/viaggioeuropacapitale/ <a href="http://9.iliobaratrontomena.info/liguriaaereafoto/"> liguriaaereafoto </a> <a href="http://16.ceonotorizlaba.info/portalistudenti/"> portalistudenti </a> http://4.silicatokirpicho.info/flatlibero/ <a href="http://13.sesepokukluggi.info/prelievoarterioso/"> prelievoarterioso </a> <a href="http://16.ilisapatrokko.info/compravenditamobileusatogenova/"> compravenditamobileusatogenova </a> http://3.guentojungh.info/centroassistenzasmeg/ <a href="http://12.sesepokukluggi.info/casavinicolatrentino/"> casavinicolatrentino </a> <a href="http://5.guentojungh.info/ricettapescesale/"> ricettapescesale </a> http://17.iliobaratrontomena.info/canzoneluciobattisti/ <a href="http://16.guentojungh.info/autonoleggioscandiano/"> autonoleggioscandiano </a> <a href="http://4.skollotueda.info/ufficiorothenburgobdertauber/"> ufficiorothenburgobdertauber </a> http://8.draeraunutri.info/volorosenheim/ <a href="http://18.sesepokukluggi.info/tuttobenigniroberto/"> tuttobenigniroberto </a> 1d2a54e199a4afa520b7c52000cbb9f3 -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---