Quote from: lossendae at Aug 01, 2009, 09:01 AM
On the Package Management : Will it be able to tell us if a new version is available and propose to get the release note to see if we need it, or if the last version break compatibilies or bring new features?
Well, you can already check for updates on a Package by clicking "Check for Updates". However, providing that level of detail on upgradability will - honestly - depend on the Component developers.
With templates: I think it would be nice for the Revolution 2.1 that if we click on the template link on the accordion, we ban see screenshots of available templates (provided by the templates creator)
"Available templates"? You mean all the other templates by that author? Well, that creates a few questions:
1. Where would we get that list from? The default modxcms.com provider? In 2.0.0, templates dont store the ’author’ of them; though we could remedy that for 2.1.
2. How would the screenshots show up? Where would they go?
3. What template link are you talking about?
The manager layout have a lot of repeating places: For examples if i select System setting, the table remind a second time that i’m on the setting page. Plus, the layout is not the same everywhere, sometime we have table header sometimes not, sometimes the content is wrapped, sometimes not, if needed, i can provide screenshot to explain further
Yeah, you might need to provide a few ss’s and examples - I’m not totally sure what the problem is here.
The new drap & drop feature is particulary awesome, however, we can’t see visually where will paste the code (sometimes we think that we put in in the right place, but tags appears on the line above or under
It pastes it wherever your cursor (the typing cursor, not mouse) is. We tried making it drop where the mouse cursor is, but that’s impossible right now b/c RTE’s use iframes.
I think that it would be nice to put Uncategorized item in an uncategorized folder (accordion)
You mean Elements without Categories? I think we discussed this before, and nixed the idea; but we can definitely vote on it later. You could open a new thread on the forums for discussion about this.
Maybe you can give the possibility to view the doc(read me) for snippets in the context menu (accordion)
This would have to wait for 2.1, or possibly 2.0.1/2, as right now once you install Packages, their Elements/Resources don’t necessarily store the Package they’re installed from - and therefore the readme/license of the Package isn’t related to the, say snippet, that is installed. We definitely want to resolve this in future versions.
Buttons on grids are not easily identifiable unless we hover them. I know that it’s a ExtJs issue with their theme.
We’re definitely open to solutions to this if anyone has any.
On system settings, it may be interesting to put next page link on the header too.(interesting for any autoheighted long grid)
That’s again a ExtJS issue.
Regarding this last comment, i know that MODx is professional oriented, but i’ve read the article regarding Making A Better Open Source CMS provided by Ryan. I find it funny that’s while MODx is good in almost every point, it failed in those two:
- Make it easy to get started
- Stop it with the jargon already
The first point is a matter of tutorial sources, but also very dependant on the second.
Once known, all the jargon seems easy to work with, but at first sight, it’s nearly impossible without documentation to have a precise idea of what some names and terminology implies in the new backend.
Personally, I don’t think we have that big of a problem with the jargon issue; we introduced a lot of new features in Revolution, and had to call them *something*. I mean, how else would you describe a Context? Or a Lexicon? We definitely understand the issue that there is a lot of new terminology in Revolution, but we’re not exactly sure on how to simplify that.
If you have a problem with specific terms, let’s open a thread (or use an existing one) and discuss them specifically and see where other users stand on it.
On your first point, we definitely agree right now that Revolution is a bit hard to jump into initially. We’re open to ideas on how to streamline that process on the backend; and we’ve been working heavily on the
official documentation to get people started. We also need help in this area; community engagement in Revolution has been minimal at best (which is disappointing, but we realize this is related to many factors, some of which are the complexity of the code/system).
Thanks for your comments lossendae. They are very well-thought and we appreciate you sharing them.
☆ A M B ☆
