Well, I will try to experiment a bit with both plugins/generators and
components and see where it leads me. Ill will get back to this thread..
Michael Koziarski wrote:
On 12/31/05, Abdur-Rahman Advany <[EMAIL PROTECTED]> wrote:
Generating code is something I have never liked. Its good for b
On 12/31/05, Abdur-Rahman Advany <[EMAIL PROTECTED]> wrote:
> Generating code is something I have never liked. Its good for basic
> setup but hard to maintain. One of the benefits of components is that it
> would be easy to update them...
Conversely, generated code is easy to modify.
The assumpti
Generating code is something I have never liked. Its good for basic
setup but hard to maintain. One of the benefits of components is that it
would be easy to update them...
Deirdre Saoirse wrote:
On Dec 30, 2005, at 5:08 AM, Abdur-Rahman Advany wrote:
Thnx for the responds, but I think peop
On Dec 30, 2005, at 5:08 AM, Abdur-Rahman Advany wrote:
Thnx for the responds, but I think people are misunderstanding me.
However, there are cases where you just need to make a component to
hide the complexity of implementation (thats the case with for
example fckeditor). It would just b
Hi,
Thnx for the responds, but I think people are misunderstanding me. I
have read a lot of the blogs (including davids) about rails and I
understand his hesitation to resist the development of highlevel
components. I have learned a lot by making a component based framework,
it just doesn't w
To answer Abdur's question - as I understand it, the core team want to
keep the plugin system very simple, and while there are some
mechanisms to handle plugin 'dependencies' (the private method
'load_plugin', for example - I can't find the Ticket that discusses
this in its comments), there has als
On Dec 29, 2005, at 10:47 PM, Nathaniel S. H. Brown wrote:
I still stand behind my recommendation. David may be the seed by
which Rails
has flourished, but it is not necessarily, and it is not beneficial to
follow blindly where other paths have great rewards.
[...]
I understand where Davi
; Of Deirdre Saoirse
> Sent: December 29, 2005 10:36 PM
> To: rails-core@lists.rubyonrails.org
> Subject: Re: [Rails-core] Components and Plugins
>
> On Dec 29, 2005, at 8:57 PM, Nathaniel S. H. Brown wrote:
>
> > You can always write a plugin for this sort of thing. I
&g
On Dec 29, 2005, at 8:57 PM, Nathaniel S. H. Brown wrote:
You can always write a plugin for this sort of thing. I plan on
doing just
that for the tinymce editor in the new year.
http://rails-engines.rubyforge.org
You have seen this, right?
http://weblog.rubyonrails.org/articles/2005/11/11/
~
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Abdur-Rahman Advany
> Sent: December 29, 2005 4:47 PM
> To: rails-core@lists.rubyonrails.org
> Subject: [Rails
Plugins can come with a generator. Thats the most user friendly way to do
what you want.
On 12/29/05, Abdur-Rahman Advany <[EMAIL PROTECTED]> wrote:
> Hi,
>
> At this moment, a lot of people are writing plugin's and helpers where
> you would expect components to do the job. I don't think the compo
Hi,
At this moment, a lot of people are writing plugin's and helpers where
you would expect components to do the job. I don't think the components
are powerfull enough, they don't provide the nessary tools for extending
core functionality (you always have to write components AND plugins or
ma
12 matches
Mail list logo
