Pmachine to EE - Is there a way to smooth the transfer
Posted: 11 August 2004 10:31 AM   [ Ignore ]  
Summer Student
Total Posts:  10
Joined  06-07-2002

I am very, very familiar with pmachine. I can do just about anything with it, and have used it for the longest time. This, in essence, is my problem with EE.

The biggest feature in pmachine, for me, is the ability to design a site any way I want, and plug in the pmachine tag that I want to use, anywhere I want to use it. When I try to work with EE I find it extremely difficult to customize, and the new code is much harder for me to grasp. Now, from what fans of EE is telling me, using EE is easier than pmachine, and for some reason I have a “block” in my head that prevents me from getting my head around EE.

As anyone ever put together a strategy, a method, for pmachine pros to make the transition to EE? I think it would be great if someone wrote a piece TO pmachine users, on how to “think” about EE, what mental adjustments you need to make, and how the concept is different.

If not a piece, about just some suggestions on how to work with EE from a pmachine perspective?

Thanks!

Profile
 
 
Posted: 11 August 2004 02:34 PM   [ Ignore ]   [ # 1 ]  
Administrator
Avatar
RankRankRankRankRank
Total Posts:  2541
Joined  12-21-2001

Exhales….

I’ll give this a whack.

In pMachine, a page is an HTML file that has embedded “pMachine tags” (which are really just PHP function calls).  With the exception of the pMachine tags, your pages are not terribly different than old-fashioned static pages. 

This approach means that in pM you have to work in two places to design your site:  1.  In the HTML files.  2. In the control panel.  If you want to change the layout of your weblog entries you have to log-into the control panel and make the change in the template.  If you want to alter your page design you have to do it using Dreamweaver or a text editor, then FTP the changed file to your server.  Back and fourth.

EE, in contrast, is entirely virtual. EE doesn’t utilize “pages” in the same sense that pM does.  You’ll never upload “pages” to your server.  EE uses templates that represent entire pages.  These templates are stored in the database.  This is an important concept. 

In pM, templates are really “template fragments” - parts of pages.  In EE, however, templates are entire pages.  Initially it’s a little more complex to understand how templates work in EE, but once you do you’ll find that managing your site is much (much, much) faster.

Furthermore, unlike pM, in EE there are not very many global weblog preferences.  Most preferences are specified in the tags themselves.  This allows almost infinite possibilities.

For example, in pMachine, the code that shows your weblog entries is this:

<?php weblog_entries($id,“weblog”); ?>

To change what the above tag displays requires you to log-into the CP, find the template that corresponds to it, and update it.  Then, you have to go to your preferences page and update it’s preferences. 

In EE, your weblog tag instead looks like this:

{exp:weblog:entries}

<h1>{title}</h1>

<p>{body}</p>

{/exp:weblog:entries}

This tag contains everything you need so you no longer have to make changes in separate places.  You do everything within the tag itself.

For example, what if you want to show your most recent 10 entries, in descending order, sorted by the most recent comment? 

In pM you would specify this in the preferences page.

In EE you’ll specify it in the tag itself:

{exp:weblog:entries limit=“10” order=“desc” order_by=“recent_comments”}

<h1>{title}</h1>

<p>{body}</p>

{/exp:weblog:entries}

The ability to specify preferences at the tag-level opens up immeasurably more options.  Instead of having lots of different tags that are essentially variations, like in pM, you have one tag that can be used in an almost infinite variety of ways.

What if you want to show only entries authored by “Joe”?

{exp:weblog:entries author=“joe”}

Or entries shown by a single month:

{exp:weblog:entries display_by=“month”}

Etc…

Think about the implications of the this kid of tag.  It’s much more flexible.

And portable.  Since everything is in once template, it becomes very easy to archive templates or swap them with others.

There is a lot more I could say, so I’ll try to follow up later.  I’m sure other people have opinions as well.

 Signature 
Profile
MSG
 
 
Posted: 11 August 2004 07:03 PM   [ Ignore ]   [ # 2 ]  
Research Assistant
Avatar
RankRankRank
Total Posts:  838
Joined  04-24-2002

All I can add to this is that I was also very familiar with pMachine, having used it since it’s early days.  However, once I actually got to play around with an early version of EE, my eyes were opened to how much flexibility and power was missing from pMachine.  Now I can’t stand having to go back and work on a client’s site I made that still runs on pMachine.  It’s awkward and clunky in comparison.  Not to knock what pMachine (Pro) is.  It’s a great little app, but EE is on a wholly different level.

 Signature 

chrisruzin.netTextMate EE BundleTextMate EE Developer Bundle • Pro Network member
“The greatest barrier to success is the fear of failure.” - Sven Goran Eriksson

Profile
 
 
   
 
 
Post Marker Legend
New Topic New posts Hot Topic Hot Topic with new posts New Poll New Poll Moved Topic Moved Topic Sticky Topic Sticky topic
Old Topic No new posts Hot Old Topic Hot Topic with no new posts Old Poll Old Poll Closed Topic Closed Topic Announcement Announcements
Theme
Change Theme
Visitor Statistics
The most visitors ever was 1149, on July 16, 2007 09:33 AM
Total Registered Members: 64914 Total Logged-in Users: 17
Total Topics: 81868 Total Anonymous Users: 18
Total Replies: 440130 Total Guests: 154
Total Posts: 521998    
Members ( View Memberlist )
Newest Members:  smilepolitelyrvmcleodbjmohrAqua193Bios Elementmjpoteetguimogranwelshmrcfthenetmonkey