pwired

How long did it take to find those colors for the menu, text bar, backgrounds and fonts ?

They all fit well together.

Photoshop has a way of recording every step you do in your editing that you can save as a script.

You can export this script for playback the exact same edit steps in another photoshop install.

Of course photoshop has nothing to do with processwire cms but what about a script that records

all steps you do in editing a local copy of your website on your laptop. Then export the script and

play it back on the live server. Would such a script work as part of the processwire core with

export - import - playback possibility ?

Perhaps time would be better spent discussing our own workflows so at least people have some ideas they can draw from.

I simply open 2 pages in firefox. One for the local website copy on my laptop and a second page for the live server. Everything I edit in the local firefox page I copy in the on-line firefox page.

A tip. When you click on the number of each post (upper right corner of the post box) it gives you the direct link of the post so you can share it easily.

thanks for this tip.

Welcome to processwire

http://processwire.com/videos/

http://processwire.com/talk/topic/2768-processwire-23-testing/page-4#entry30618

(post #75)

Thanks, looks like one of the better places to learn js.

Thanks diogo, I forgot to mentioned that.

Here is more to read:

http://processwire.com/talk/topic/1031-thinking-about-switching/

(Post #7)

since MODX Evo is end of life.

Hi Peter, such statements are not true anymore since March 19. Modx just released evo 1.0.9., improved and php 5.4 compatible.

http://modx.com/blog/2013/03/19/modx-evolution-1.0.9-restarts-the-little-engine-that-could/

I have to be carefull with my words this time because my last post about modx went wrong.

But here is my view on processwire, maybe it will serve you in some way. When it comes to interfacing, processwire has building blocks for designers, developers, coders and clients. I just love it that you can enter processwire from anywhere you want and start using the skills you already have. It stays closer to the core and doesn't use things like ExtJS and pagetrees but jQuery and pagefields and communicates directly with the database, so it works easy, fast and scalable.

I was originally going to build it from scratch, in PHP, but am now wondering if PW might be able to handle it.

Definitely not build it from scratch, processwire is a huge timesaver compared to that. With processwire you can fill in your own customized php with inline php, functions and modules.

From this brief description, could PW handle a completely customized interface and application like this?

Did you have a look at pw's api ? http://processwire.com/api

Much can be done already with the api

I'd just like to debunk this FUD, cause that's what it is.

I want to apologize to everybody if I raised any FUD with a line in my post. So, I re-edited the line "Modx is going to push the same kill switch on revo like they did on evo and are putting all their bets on modx_3." And changed it into: Modx decided to deprecate evo and will do the same with revo when modx_3 has been released.

I don't agree there's difference between an Evo and Revo user profile either.

It's no secret that over the years modx evo has attracted a large group of designers with little coding experience, because modx evo was just perfect for them. This group has become frustrated when modx decided to stop evo development and let it deprecate for php 5.4. This is one reason that a lot of them have found their way to processwire.

I'm a front end guy who knows HTML,css,a little jquery and am learning PHP (slowly). I've mainly been creating sites in MODX Revo for the past couple if years.

That's funny because that is a typical evo profile not revo.

Just how scalable is PW and do I need to learn PHP?

These questions are already answered x times in the processwire forums and also in the modx forums
Long story short: processwire is what revo should have become - fast - scalable - time saving - and above all =>
the architecture of processwire makes it accessable for designers - developers - coders and easy for clients.
Modx decided to deprecate evo and will do the same with revo when modx_3 has been released.
But the modx_3 roadmap seems lost track in time. Their isn't any news about it since may 2012.
http://modx.com/blog/2012/05/25/clarity-focus-and-simplicity/
Welcome to processwire - a future ready cms.

Requirements: processwire 2.3

Small detail I know but in the modules it reads 2.x

Can't wait to see that Visual Heatmap of the tracked clicks. Great addon to the modules.

Yes -- and have you also noticed how "they" try to escape discussions that processwire is what revo should have become. Some of them try to escape by putting processwire as a simple cms or that in the end any cms will do the job. Yeah right. But, and here comes the but. Right now revo is their supposed starred cms but more and more it leaks out that revo is a fail. Complicated front end, slow directory tree, confusing user rights, and slow back end that doesn't even work on an ipad. The only thing for modx that could change the cms game is their modx_3. Only, since may 2012 nothing new is published about the modx_3 roadmap, state of development or estimated release date in 2013 for modx_3. We'll see how this is going to end. In the mean time more and more modx evo refugees are in da house

would there be a way to do that but without putting it into the template file? In other words, can the Settings page control the CSS file, either directly, or using some javascripty thing?

That would be an interesting alternative to edit your css and also your js ? I remember modx evo was doing this trick also by using a document in the site tree. I guess the same could be done with a page field in processwire. Checking on it.

I feel with this guy... I like this system it's so clever and smooth! But for non-coders, it's very very difficult. Which is a pitty, because it's so worth for more people to like and use it!

That is only because php looks unfamiliar to a designer who thinks that php is only for experienced coders. That was my cms thinking also for a long time. Until I saw how easy you can mix html and php tags in Processwire. After playing for a while with simple php tags in processwire your opinion will change. The thing with php (and any other programming language) is that you "have to get into it". Just start with the PW tutorials and first learn to use simple php tags like <?php echo $page->title; ?> Here is a good start http://processwire.com/api/templates/ Later on you can learn something more like a for each in php. Check this post also

http://processwire.com/talk/topic/2994-learning-php/#entry29499

Thanks for the replies. It's one of those tips for a newbie that would otherwise take a lot more time to find out.

Hi Soma, could you be more specific where in PW to remove this global flag from title ?

Thanks

After too many hours busy with the same site, start to feel groggy and inspiration dries up, I need to see again

how relative everything is and give my head a fresh reboot:

I didn't realize they were stopping with modx revo? What will their product be then?

It will be Modx 3, coded from scratch but inheriting the best of evo and revo, and will be released in 2013

(exact date unknown)

Quote from Ryan Trash:

Nothing in software is permanent or perpetually supported. Adobe does not support the versions of software that were released when Evo was released. Nor does MS with it's Operating Systems. At some point Evo will be deprecated and go on pure and security patch support, then eventually no support at all. Same for Revo.

no php 5.4 for Evo, but security patches yes

concentration on MODX 3 (expected in 2013)

will MODX 3 based on Revo 2.*? No! complete rewrite

upgrade tool Evo --> Revo? no

http://forums.modx.com/thread/?thread=82674&page=1

http://forums.modx.com/thread/82830/evo-revived#dis-post-457048

I'm trying to be here as much unbiased and objective as I can, but apart from too much complexity and bloatware in revo, it doesn't make sense to migrate to revo and then migrate a second time to modx 3.

But I have to give credit where credit is due. I really learned a lot from modx during my days with evo and am going to miss some real professional and friendly modx'ers who always are there to help upgrade your skills.

Great project, well done with processwire. You didn't mention anything about the Email Image Module and letting party people / guests / visitors make pictures with their mobile phone and send directly to the website.

Was it not part of the plan ? Heck, the possibilities are endless. Event organizers / DJ's / can put an emailaddress on their trucks / or where visitors enter the party / inside the party room / set up a best picture award / etc. etc.

Next big thing can be a Streamed Malware module (Ryan ?) that would have it's place in http://store.di.net/collections/software See the potential ?

my 5 cents to keep on going relaxed behind my laptop

Then you could just use [urltemplates] anywhere in text fields of your choosing. The sky is the limit, you can define as many tags as you like representing every combination of php/js/html you wish.

That's really interesting. Could this also be used for a simple javascript [slideshow] or [news-scroller] ?

2 years ago fell in love with modx evo - great for designers. Then modx bluntly decided to stop with it (no longer compatible with php 5.4). Now they also decided to stop with modx revo very soon. So I saw my self no choice but start walking the cms desert with google. Seduced by many and playing with getsimple cms. When I read about PW's api inspired by jquery, and no bloatware like ExtJS in the backend it got my interest. The forum helped me to understand later on that PW's pages are like containers. The abstraction layer of PW is such that it gives you direct access to your own custom php and html tags. Both designers and coders can use their skills with PW.

Just perfect !

This is an interesting thread that touches on the difference between PW and other cms'es. Usually a cms is defined by it's rules and dashboard that you first have to learn before you can make websites with it. Advantage: it shows you defined ways of working and you'll know what to do. Disadvantage: you are bound to it's rules and dashboard and sooner or later this will limit your creativity. PW can make a developer with little coding experience float in it's open potential sometimes not knowing where to go. Look how this still pulls my leg with PW, so I can understand what DZoneRick is saying in his posts. But I prefer it this way over other cms'es because coding skills can always be learned. I really hope that PW will never build in out of the box fancy cms ways/rules on it's future roadmap, ending up just another cms. I'm not an experienced coder (yet) but I think DZoneRick can use .inc blocks or <?php include 'content.php'; ?> to accomplish throw away content where he needs it.

In Pw your fields ARE the template variables, just more flexible. Who stops you from adding html/css/js into a textarea field in ProcessWire?

Yes, you are right about that. It´s just that I´m porting 2 of my websites to PW, seeing how it was done with template variables in modx evo, that´s why I came up with it. Actually, I appreciate your reply because I didn´t

see it, in that so obvious comparison. I guess I still have to get used on switching to my new work in PW.

You can enter any php code in text and use eval like modx, but that's horrible practice not shining.

Yup, but not everybody is a high skilled coder like you are Soma. For the time being I have to do it that way