I was getting increasingly worried reading this thread that MODx could go the way of all the other CMSs and converge on a folder/page or category/item format simply to appeal to end-end users (by that I mean my clients). As a web developer I use modx because it has the best of both worlds and gives me the flexibility I need to build different sites that behave in different ways.
Btw, the new interface looks great. Both design and functionality have been nicely simplified.]]>
You’re obviously part-way through this Ryan as in r1902, sometimes the container icons are folders, sometimes they’re documents
, on the first show of the document tree, the icons are folders - it’s only when you expand them do they change to a document.Feel free to close this bug if need be as I now realise it’s WIP (work in progress
)On a slight tangent, there a couple other bugs in the tree/manager: http://modxcms.com/bugs/task/643]]>
If "folders" no longer exist and instead we have container documents, then I think it would be better to swap the folder icon used in the document tree for simply a document icon. I think that using the folder icon increases confusion because it looks like a folder and nothing else. I.e. can’t have content.
Andy
Thanks Andy... I’ve been meaning to do that and appreciate the reminder.
]]>Andy
]]>
MODx is not targeted at users that are not familiar with web development. This means our intended audience is either experienced web developers or technically adept web designers who’ve at least looked at PHP scripts a few times. That’s not to say we don’t welcome "newbies", but we do politely request that they allow us to continue to refine our core and associated add on code before they give much "final" consideration to the fresh out of the box newbie experience. We’ve added many things and are slowly taking away and moving them around for a more streamlined experience.
* modX allready define a lot of brand new uses of classical terms... all this is very confusing, very difficult to get in
* instead of defining absolute concept, could you define the use they aim to ? it’s would be much more eays to understand/translate ?
as a framework, I’m asking modX to :Both of those are what MODx does now. If you need a folder/container, just look at the icon. The behavior of the "folders" in MODx is not consistent with directories/folders on a filesystem for Web Servers, nor is it consistent with the behavior of folders in Windows Filemanager or the Mac OS X Finder. Hence the change in terminology. Click the help icon next to the folder for an explanation I hope you find bearable.
* make web pages (writing content or including other application)
* as a redactor, when I’ve got a lot of page of one type, I want to sort them in one "folder" or anything that make me easy to find things I’m looking for
* as a visitor, I’m expecting, when entering such a collection of pages, an "index" or something that let me read either page1, page 2 .... either directly page 5 if I want to resume my readingIt the developer’s responsibility to enable any such behavior. MODx does not make constraints here. You may need to be more firmly in our intended audience in order to pull this off every time, but it’s entirely possible. Today, MODx isn’t for lazy people.
* as a webadmin, I may want to developp (in the index page of one collection) special search fonction to make my visitor find the right page the most convenient way for him. If I could find standard index for some standard collection that would be great as I’m lazy
I don’t really understand what you’re saying. MODx development has always been functionality first then a surprising amount of discussion about how to describe things. This may not all be public, but there is a much larger picture here than what it seems on the surface... there’s three different versions in development now (0.9.5, 0.9.7 and 1.0), in fact.
* as any role, as everybody is lazy ? I’m awaiting some standard scheme for not getting my brain tired
for conclusion I would say :
[tt]find an aim, build a tool and then define a word for it [/tt]
instead of
[tt]trying to find a definition/word to what is developped in modX[/tt]
Some decisions are based on what is coming in the future, IOW.]]>Quote from: rthrash at Oct 18, 2006, 06:20 PM
Pont, please see the thread where this was discussed in full. http://modxcms.com/forums/index.php/topic,7721.msg54007.html#msg54007
Edit : @Zi : Thanks for moving piwaille’s post from its original location
]]>Quote from: rthrash at Oct 18, 2006, 06:51 PM
Having had lots of discussions with users accustomed to opening folders and expecting it to go to the index file or just show things, I respectfully have to disagree.
As a quite newbie, I do have to put my opinion in this discussion....
I do understand your point of vue... but
* modX allready define a lot of brand new uses of classical terms... all this is very confusing, very difficult to get in
* instead of defining absolute concept, could you define the use they aim to ? it’s would be much more eays to understand/translate ?
as a framework, I’m asking modX to :
* make web pages (writing content or including other application)
* as a redactor, when I’ve got a lot of page of one type, I want to sort them in one "folder" or anything that make me easy to find things I’m looking for
* as a visitor, I’m expecting, when entering such a collection of pages, an "index" or something that let me read either page1, page 2 .... either directly page 5 if I want to resume my reading
* as a webadmin, I may want to developp (in the index page of one collection) special search fonction to make my visitor find the right page the most convenient way for him. If I could find standard index for some standard collection that would be great as I’m lazy
* as any role, as everybody is lazy … I’m awaiting some standard scheme for not getting my brain tired
for conclusion I would say :
[tt]find an aim, build a tool and then define a word for it [/tt]
instead of
[tt]trying to find a definition/word to what is developped in modX[/tt]
]]>