Difference between Reddot CMS 6.0 and later versions
Eyeshoe
We are planning on migrating sites from Reddot CMS 6.0 to Reddot CMS
9.0, Pls give in your suggestions about the common challenges faced
during such migrations. Are there any key points to keep in place for
such tasks?
Looking forward to your inputs!
Cheers
Eyeshoe
Ingo Hillebrand
i once saw a list of abbreviations for all RedDot-Elements. Can any one
provide me the link or a selfmade list? The aim i am following is to
create and or to meet international standard.
Thanks in advance,
Ingo
Gavin Cope
When creating and naming placeholders we recommend the following naming convention followed up an underscore then the name of the element (example: anc_linkname):
anc Anchor
area Area
att Attribute
brs Browse
con Container
db Database
frm Frame
hdl Headline
hit Hit List
img Image
info Info
list List
med Media
opt Option List
pjc Project Content
smp Site Map
stf Standard Field
dat Standard Field - date
num Standard Field - numeric
txt Text
xfr Transfer
xcms XCMS Project Content
--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
Richard Hauer (5 Limes)
the original training course some of us did way back when RedDot was a
company not just a distant memory of the name of some software.
Differences highlighted with a *
anc Anchor
ar Area *
brs Browse
con Container
db Database
hit Hit List
img Image
lst List *
opt Option List
pjc Project Content
smp Site Map
stf Standard Field
dat Standard Field - date
num Standard Field - numeric
txt Text
xms XCMS Project Content *
General programmic practice suggests that prefixes are most often
found in non-typed languages, where the prefix can be used to identify
type to a consumer of the variable - this is known as hungarian
notation (I believe because of the sz that prefixes strings which
stands for "null terminated string" where the null string in also
represented as '\0' i.e. zero and hence "z". I think it was
accidentally also invented by a Hungarian).
Microsoft's naming convention recommendations for .Net Framework
programming suggest that Hungarian notation is not required, because
the editor makes it easy to determine the type at design-time, and the
framework prevents inappropriate use of type casts at runtime (i.e. it
is a type-safe language).
I would suggest that RedDot (or whatever you want to call it) is more
like a type-safe language than not, since we have icons identifying
the type of each placeholder and the runtime manages conversions where
they are allowed anyway. This makes it a bit redundant to identify
placeholders by type in the CMS (by using silly prefixes). So, in the
absence of allowing spaces in the name I would suggest that we only
really need camel-case naming for elements and that the whole prefix
system could be entirely abandoned.
Examples:
ye olde name -> new sexy name
------------------ ---------------------
lst_Navigation -> NavigationPages
stf_PageTitle -> PageTitle
inf_PageCreated -> PageCreated
I don't really see how the prefix is adding any value...
HTH.
Regards,
Richard Hauer
====================
5 Limes Pty Limited
www.5Limes.com.au
PS. While saying this, actually, we are still using the prefixes in
our real projects... all I'm suggesting is that it's probably
unnecessary (and always has been).
> > i once saw a list of abbreviations for all RedDot-Elements. Can any one
> > provide me the link or a selfmade list? The aim i am following is to
> > create and or to meet international standard.
>
> > Thanks in advance,
> > Ingo
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "RedDot CMS Users" group.
> > To post to this group, send email to reddot-c...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
Gavin Cope
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
markus giesen
know which element you are working on.
For example when you use a list you have to know that there is a list
blockmark required..
Or when reading a MyElement with RenderTags you search for a reason
why you can't get any value until you realise it's an info element
(which can't be read by Render Tags)
Also my oldschool list from 2008:
10 RedDot Elements and naming conventions: http://bit.ly/5mpUKz
Took me a while to understand why you english guys prefer for a
"Container" the abbreviation con_ instead of cnt_
Innocent me...
On 13 Dez., 11:24, Gavin Cope <gavin.c...@gmail.com> wrote:
> Personally, I think the prefixes are very useful because at a glance, you
> can tell immediately what type of placeholder you're dealing with. Granted,
> there are some instances that are easy such as <a
> href="<%easy_to_identify_placeholder%>">Link</a> but there are others where
> there are numerous possibilities and without a prefix, the only way to tell
> what they are is to open them for editing. Using your example of "PageCreated".
> What is that? An info placeholder? A standard field? Does it contain text or
> a date? With an inf_ in front, you immediately know it's an info placeholder
> and add "date" on the end and you know within half a second exactly what
> that placeholder is going to return.
> In the end, I guess it really comes down to what you're used to and what
> you're more comfortable with.
>
> Cheers,
>
> G.
>
markus giesen
because I have worked on projects where people just use their native
language (German, French, Hindi) to name an element. THAT is confusing
guys! Elements should always be in English!
> can tell immediately what type of placeholder you're dealing with. Granted,
> there are some instances that are easy such as <a
> href="<%easy_to_identify_placeholder%>">Link</a> but there are others where
> there are numerous possibilities and without a prefix, the only way to tell
> what they are is to open them for editing. Using your example of "PageCreated".
> What is that? An info placeholder? A standard field? Does it contain text or
> a date? With an inf_ in front, you immediately know it's an info placeholder
> and add "date" on the end and you know within half a second exactly what
> that placeholder is going to return.
> In the end, I guess it really comes down to what you're used to and what
> you're more comfortable with.
>
> Cheers,
>
> G.
>
kimdezen
consistantly stick to it within every project that you build. It will
save you a whole lot of time and stress in the long run...
I would argue that it would be best to stick to the old 'RedDot'
naming standard that has been adopted by a lot of developers - that
way if your project is picked up by another developer they will
understand whats going on straight away.
Ingo Hillebrand
In our projects we stick to a naming convention, but sometimes it differs
from what other RedDot developers use in their code. That makes it a
little bit annoying when i have to adopt my code-example to the
reddot-almost-standard.
Greetings,
Ingo
Ken Capps
Gavin Cope
Ingo
--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
markus giesen
On 17 Dez., 12:06, Gavin Cope <gavin.c...@gmail.com> wrote:
> Oh and another reason I just thought of. Without those placeholder prefixes,
> the Placeholders drop-down list in the content class editor would be soooo
> confusing once you had more than a handful of placeholders in your template.
>
> :)
>
> Cheers,
>
> Gavin
>
> 2009/12/14 Ingo Hillebrand <I...@shift8.de>
>
>
>
> > Thanks for all your answers!
>
> > In our projects we stick to a naming convention, but sometimes it differs
> > from what other RedDot developers use in their code. That makes it a
> > little bit annoying when i have to adopt my code-example to the
> > reddot-almost-standard.
>
> > Greetings,
> > Ingo
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "RedDot CMS Users" group.
> > To post to this group, send email to reddot-c...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > reddot-cms-use...@googlegroups.com<reddot-cms-users%2Bunsubscrib e...@googlegroups.com>
rodger1984
Hi guys,
I got out-of-memory errors when publishing a page with a list to which over 4, 000 pages were connected. But as I checked there was plenty of free memory when the publishing was running. Are there any ways other than reducing pages connected to the list to solve this? Any advice would be appreciated!
Here is the publishing log:
|
Thanks,
Rodger
rodger1984
sorry,wrong subject.
--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-users+unsub...@googlegroups.com.