Im considering to build a CMS for NGO organisation.
This organisation takes care of managing football torunaments in several
cities in my country.
The CMS should have:
_admin control panel for about 5 levels of authorization
_tornament management panel for planning
_football teem management panel
_football player profile management panel
_fotball match statistics
_livescore transmission
_news and post control panel
_ and others connected with football tournaments
There are two people responsible for this project. Coder and designer.
There is a need two seperate user interface from data model & control
logic.
What is your opinion?
Which strategy is better: RUBY or (PHP5+PEAR+SMARTY)?
IS it possible (with a use of RUBY) clearly seperate user interface from
data model & control logic?
_fotball match statistics
IS it possible (with a use of RUBY) clearly seperate user interface from
data model & control logic?
I think you should take a look at Ruby on Rails[1]. It’s a
view-model-controller web application framework written in Ruby. It’s
infinitely easier (and dare I say, better) than any PHP solution.
You were thinking of a web application, right? I took it for granted
because you mentioned PHP, which is mainly used in webapps.
What is your opinion?
Which strategy is better: RUBY or (PHP5+PEAR+SMARTY)?
IS it possible (with a use of RUBY) clearly seperate user interface from
data model & control logic?
This is an interesting question to raise on this mailing list. The
answers may be a little bit biased Even if it sounds a little like
bait, it’s good enough that I may fall for it:
My opinion is biased, of course: coming from PHP (I too was young
once, and needed the money badly), I only can say that using Ruby (I’d
even suggest using Ruby on Rails: http://www.rubyonrails.com/ ) is
clearly better than using PHP and the unimaginable bloat that is
smarty. Details are way too offtopic.
It’s even near impossible not to use MVC separation in RoR without
jumping through hoops in a way that’s not pleasant. At all.
I know nothing about PEAR or SMARTY, but though I’d put in my cent’s
worth.
A novice user of Ruby and RoR, I’d swear by these. This is the
cleanest and most fun framework I’ve seen for a while.
I’m no fan of PHP and early experiences with the language back in 99
put me off it completely. However, PHP has come a long way since
then and one bit of PHP based technology that has impressed me is “Code
Igniter”
(http://codeigniter.com/) which provides much of the same
functionality as RoR (I think it was inspired by RoR).
If you are starting from nothing, I’d still go for RoR, but then you
are posing the question in a forum with a clear leaning
[snip]
What is your opinion?
Which strategy is better: RUBY or (PHP5+PEAR+SMARTY)?
IS it possible (with a use of RUBY) clearly seperate user interface
from
data model & control logic?
Although this question has been well answered, I thought I’d add my
opinion anyway.
I’m a recent convert from PHP to Ruby, and without a doubt Ruby (and
Ruby on Rails) is the way to go.
The only downside I’ve found with Ruby/RoR compared with PHP is that
the PHP documentation is really amazing. The commented documents are
wonderful, and there’s still nothing quite like it (for Ruby, or
anything else for that matter). Although the ruby community is
making good strides on this front.
But in the long run, I think you’ll find that Ruby/RoR is worth the
effort and you’ll be a much happier programmer. I can’t tell you how
much I hate writing ‘$this->’ these days… Get a book, it’s worth
it. I really like Pragmatic Programmers’ stuff.
Also I think you’ll find the ruby community is a bit nicer (probably
because our language helps keep us happy). The PHP lists and
channels are often too quick to yell ‘RTFM!!’ at you.
_football teem management panel
What is your opinion?
Which strategy is better: RUBY or (PHP5+PEAR+SMARTY)?
If I were building something form the ground up, I’d favor Ruby.
But there my already be something that does pretty much what you want,
and that can be a great benefit. Look around. Go search rubyforge.org
and sourceforge.org (for example).
IS it possible (with a use of RUBY) clearly seperate user interface from
data model & control logic?
Absolutely. I’d argue that, all things being equal, this is better done
in Ruby than PHP, but you can write good and bad code in either
language. I Ruby, though, has a cleaner syntax.
You should do little more research before posting. Have a look at
Rails or Nitro.
These are good places to start. I’ve also been poking around into
IOWA, too.
[snip]
What is your opinion?
Which strategy is better: RUBY or (PHP5+PEAR+SMARTY)?
IS it possible (with a use of RUBY) clearly seperate user interface
from
data model & control logic?
Although this question has been well answered, I thought I’d add my
opinion anyway.
I’m a recent convert from PHP to Ruby, and without a doubt Ruby (and
Ruby on Rails) is the way to go.
The only downside I’ve found with Ruby/RoR compared with PHP is that
the PHP documentation is really amazing. The commented documents are
wonderful, and there’s still nothing quite like it (for Ruby, or
anything else for that matter). Although the ruby community is
making good strides on this front.
But in the long run, I think you’ll find that Ruby/RoR is worth the
effort and you’ll be a much happier programmer. I can’t tell you how
much I hate writing ‘$this->’ these days… Get a book, it’s worth
it. I really like Pragmatic Programmers’ stuff.
Also I think you’ll find the ruby community is a bit nicer (probably
because our language helps keep us happy). The PHP lists and
channels are often too quick to yell ‘RTFM!!’ at you.
IMHO, part of the reason PHP’s documentation is great is that it’s
not auto-generated. Tools are great, but they lack a certain element
that a flesh-and-blood editor provides. A ruby documentation team
would be a great thing.
On that note, I like to write. Is anyone actively working on core
ruby documentation? If so, I’d like to help. If not, consider this
a call to action!
-Mat
IMHO, part of the reason PHP’s documentation is great is that it’s not
auto-generated. Tools are great, but they lack a certain element that
a flesh-and-blood editor provides. A ruby documentation team would be
a great thing.
On that note, I like to write. Is anyone actively working on core
ruby documentation? If so, I’d like to help. If not, consider this a
call to action!
-Mat
I’m of the same opinion – PHP is a lousy language, but the manual
IMHO, part of the reason PHP’s documentation is great is that it’s not
auto-generated. Tools are great, but they lack a certain element that
a flesh-and-blood editor provides. A ruby documentation team would be
a great thing.
Hey, what a great idea.
On that note, I like to write. Is anyone actively working on core ruby
documentation? If so, I’d like to help. If not, consider this a call
to action!
The only downside I’ve found with Ruby/RoR compared with PHP is that the
PHP documentation is really amazing. The commented documents are
wonderful, and there’s still nothing quite like it
I’m of the same opinion – PHP is a lousy language, but the manual works
extremely well. We really ought to take a look at it and try to make one
for Ruby, perhaps even avoiding rDoc (yes, I’m aware of rannotate, but
I’m not sure it’s quite enough.)
Oh cool. Sorry for my R-ingTFM first there. I suppose I’ll grab a CVS
copy and give it a shot!
Sweet. Thanks.
Some quick tips: There is a ruby-doc mailing list for questions about
doc’ing Ruby, and when you have something, but no contact person to send
it to, make a patch of your doc changes and post it on the ruby-core
list (yes, Yet Another Mailing List).
Please see http://ruby-doc.org/stdlib/status.html
doc’ing Ruby, and when you have something, but no contact person to send
“You harmonize; then you customize.”
Wilson Pickett
Hi James,
Do you have a link to the CVS of where to download these files? The
status
pages says to get the files from CVS but I can’t find a link
Even if it sounds a little like