OZONE Asylum
Forums
Server-Side Scripting - Oh my!
Planning a PHP CMS
This page's ID:
28078
Search
QuickChanges
Forums
FAQ
Archives
Register
Edit Post
Who can edit a post?
The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.
Your User Name:
Your Password:
Login Options:
Remember Me On This Computer
Your Text:
Insert Slimies »
Insert UBB Code »
Close
Last Tag
|
All Tags
UBB Help
functional languages are something different altogether: don't want to despise warmage, but am commited to saying the truth, what you are calling -functional- is -sequential- instead. functional languages are characterized by the fact every construct is a function. LISP, ML, and XSL to an extent are functional languages, characterized by a functional coding style. they do not understand things as global scope or variables, for example, and are a completely different approach to programming, largely based on recurrence, instead of iteration (for example, there is no real list iterator in list - foreach doesn't exist as is - instead, you recursively process a list until it is empty). For the sake of correctness, on to.. er.. correcting more? -------------------------------------------------------------- "I would not recommend that you being by shooting for the moon"... and yet, I recommend the opposite altogether: plan large for scalability. Let me explain: if you've already given ten minutes thinking about the future of your app, you've prepared yourself to be able to expand it, and yet all you will implement is the necessary - until you want to implement more - then, you'll already have prepared your whole app to move on and upwards (instead of grafting some code on top of something that wasn't really meant to welcome it). For example, my go game project is coming to an end. Originally, and in the report and plan, we had classes for a 3d display, and classes for interaction with the internet go game server. These two features won't exist when we deliver the app, but if we had to implement them, they have theyre niches waiting for them and could be coded-plucked in within no time. -------------------------------------------------------------- Side note on UML: it is not intended only for OOP, it is mainly intended as a "universal modelling language" for ALL things software design, and include specs that cover even interaction between developers, you can diagram anything under UML specs that concerns a software design project. The closer you'll get from an UML quickstart certainly is the design pattern tut pointed out by DL. -------------------------------------------------------------- Object-relational? That's a new one too. Objects have relationships because that's how life is, but relational modelling is slightly different from Object oriented modelling, and older. You can use UML for both, but relational in terms of data structure means tables and queries, objects in terms of data structures means objects, properties and methods. Object databases exist and are completely different from relational databases: don't know what the buzz words "object relational" are supposed to mean, but it doesn't pertain to software design, sadly. -------------------------------------------------------------- Fast prototyping: now what's that again? It's close to development methodologies of the 70's. More recently, the UP methodology recommends this instead... - got your BIG plan and BIG overview? Divide it into sub-steps that will be usable as individual applications. Here, for instance, CMS=> news module, users accounts module, this module, that module.... Build everyone as if it was a stand-alone app - while respecting the initial big picture. Put each step in prod, test it, debug it. Analysis 40%, implementation 10%, debugging 40%, that's the balance of a well prepared big project. ...if the hare recommends you to stress, hear the tortoise: start by having all the needed weapons in stock, don't, don't, don't rush things -EVEN if this is just a little thing, the further you look from your current position, and it only takes a look, the easier it will be for you to run the distance in all possible ways. I am sorry again, but I won't ever refrain from correcting my mates when they speak nonsense again, I may have misunderstood your points Mage, but I find 95% of your above post irrelevant at best. Lat but not least: if UML gives you the creeps and sounds cryptic, -d-e-s-i-g-n patterns tut, plain perfect for a starter, and you can freely trade UML for XML. Lay out an xml page that "pictures" your future CMS and it's "actors", no need for it to be valid XML. In facts, professional, large scale development tools now propose both UML diagrams and XML diagrams to model things. A single xml document is often enough to act as a diagram, overview, and backbone for a whole app.
Loading...
Options:
Enable Slimies
Enable Linkwords
« Backwards
—
Onwards »
Maximum Security
OZONE
DHTML/Javascript
Server-Side Scripting - Oh my!
CSS - DOM - XHTML - XML - XSL - XSLT
Stupid Basic HTML
Visual Therapy
Photoshop
Photoshop Pong, Anyone?
***WARNING*** BIG SIG APPROACHING
Photography
3D Modelling & Rendering
Multimedia/Animation
Print Graphics
Holding Pens
Philosophy and other Silliness
Outpatient Counseling
Site reviews!
Mad Scientists' Laboratory
Getting to know the Grail