cmfcollectorng-develop Mailing List for CMFCollectorNG
Status: Alpha
Brought to you by:
ajung
Menu
▾
▴
cmfcollectorng-develop — Developers list
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(7) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Helge T. <he...@te...> - 2004-02-16 11:07:25
|
You should take a look at PloneCollectorNG in the Collective on SF.
On Sat, 14 Feb 2004 15:23:15 +0100, Balazs Ree <re...@re...> wrote:
> Hello,
>
> Recently I attempted to set up a plone2.0 site with CollectorNG. (I am
> using CVS version of plone from the 2.0 branch). My first interest was
> to get hands on a good issue collector that I can use for tracking my
> own projects, on plone sites, with internationalized content.
>
> When trying to setup the CVS HEAD version, I run into a few (minor)
> problems that I solved. Later I started to work a little bit more on it;
> I wanted the email notification work in a multilingual environment. Then
> there were a few little things that I preferred to play with (let's say,
> for fun), and I did them, too.
>
> I have chosen to share the patches on this list in the hope that it
> might be useful for the development of the collector. No idea what other
> work is being done on this area of CollectorNG/Plone2 and how this would
> fit in. However this is a bunch of patches that needs to be reviewed and
> sorted out first; some of them solve bugs and others represent slight
> enhancements.
>
> As a result of this I've got a setup working fine with plone2.0 - I did
> not do extensive testing in real usage.
>
> Here are the issues that I worked on:
>
> 1. The Install.py seems to be inadequate for Plone as it only installs
> under CMF. I made a quick hack that makes installation possible in plone
> and occasionally it also adds the collectorng_plone skin. Yet the
> workflow needs to be added and set manually. (This should be added too
> but as I am not very experienced with the plone installation process, I
> could not figure that out easily.)
> Also the installation should be handled separately on CMF or Plone,
> because with by patch the plone-less installation would be broken.
>
> 2. Looking at all the three skins, the collectorng_plone skin looked the
> most useful, so I only focused on that.
> I fixed one usability error: at the issue view the comments are
> displayed too wide, attempted to put "pre: {width: auto;}" to the css.
> (Other issue: in this skin it would be good to widen the description
> field in the issue view, but it is not important and I don't know how to
> do that.)
>
> 3. Also, "css is not found" because it references it as
> collectorng_stylesheet, without the .css extension - but in the skin it
> is with the extension. Workaround: "customize" the stylesheet manually
> into portal_skins/custom, and rename it to extension-less. Why is this,
> is beyond my knowledge.
>
> 4. fixed add issue template to also fetch name into the data sheet of
> the new issue automatically, not only the email.
>
> 5. About the email notification.
> Date header must be added.
> Also, I think all the content encoding of the email notifications sent
> out should be in UTF-8 as it best matches the overall policy of plone
> (and it works.) Should not be a problem nowadays with modern mailers but
> a must in a non-English environment.
> But again, I don't know how this would affect or break plain CMF usage
> where I guess the content encoding is not always UTF.
> (Or maybe the mail encoding could be parametrized - and of course the
> best would be if it could figure out a minimal charset by itself - like
> the evoluton mailer does it, for example - try ASCII first, then a
> one-byte codepage, then UTF as fallback. But for this a general-purpose
> python package would be handy which I have not heard of.)
>
> 4. Modified a bit the incoming email processing, too; so that I can
> specify location on a per collector basis (configurable by the
> abbreviation of the collector), and are not tied to put all the
> collectors of a site into one folder. Maybe the setup for this has to be
> done in a little fuzzy way, sigh.
>
> 5. Other issues with email submission:
>
> - charset handling at new issues and followups,
>
> - trim the automatically attached signature from the end, as I
> thought about a better possibility in the following:
>
> - anonymous mail source: I made mail name and address stored with
> each transcript, and displayed instead of the username which is in this
> case insignificant. So instead, something like 'Email submission from
> "John Doe" fo...@ba...' is displayed. (Another possibily for improvement
> would be to identify the plone user based on email address, but this can
> be used only for info, as addresses can be easily faked / or even
> authenticate users based on PGP-signature, but I doubt anyone really
> would want to use this.)
>
> ---
>
> So beware: at least the installer and possibly the email encoding stuff
> might break plone-less (plain CMF) behaviour
>
> Patches included. Please feel free to comment.
>
--
Helge Tesdal
|
|
From: Balazs R. <re...@re...> - 2004-02-14 14:25:53
|
Hello,
Recently I attempted to set up a plone2.0 site with CollectorNG. (I am
using CVS version of plone from the 2.0 branch). My first interest was
to get hands on a good issue collector that I can use for tracking my
own projects, on plone sites, with internationalized content.
When trying to setup the CVS HEAD version, I run into a few (minor)
problems that I solved. Later I started to work a little bit more on it;
I wanted the email notification work in a multilingual environment. Then
there were a few little things that I preferred to play with (let's say,
for fun), and I did them, too.
I have chosen to share the patches on this list in the hope that it
might be useful for the development of the collector. No idea what other
work is being done on this area of CollectorNG/Plone2 and how this would
fit in. However this is a bunch of patches that needs to be reviewed and
sorted out first; some of them solve bugs and others represent slight
enhancements.
As a result of this I've got a setup working fine with plone2.0 - I did
not do extensive testing in real usage.
Here are the issues that I worked on:
1. The Install.py seems to be inadequate for Plone as it only installs
under CMF. I made a quick hack that makes installation possible in plone
and occasionally it also adds the collectorng_plone skin. Yet the
workflow needs to be added and set manually. (This should be added too
but as I am not very experienced with the plone installation process, I
could not figure that out easily.)
Also the installation should be handled separately on CMF or Plone,
because with by patch the plone-less installation would be broken.
2. Looking at all the three skins, the collectorng_plone skin looked the
most useful, so I only focused on that.
I fixed one usability error: at the issue view the comments are
displayed too wide, attempted to put "pre: {width: auto;}" to the css.
(Other issue: in this skin it would be good to widen the description
field in the issue view, but it is not important and I don't know how to
do that.)
3. Also, "css is not found" because it references it as
collectorng_stylesheet, without the .css extension - but in the skin it
is with the extension. Workaround: "customize" the stylesheet manually
into portal_skins/custom, and rename it to extension-less. Why is this,
is beyond my knowledge.
4. fixed add issue template to also fetch name into the data sheet of
the new issue automatically, not only the email.
5. About the email notification.
Date header must be added.
Also, I think all the content encoding of the email notifications sent
out should be in UTF-8 as it best matches the overall policy of plone
(and it works.) Should not be a problem nowadays with modern mailers but
a must in a non-English environment.
But again, I don't know how this would affect or break plain CMF usage
where I guess the content encoding is not always UTF.
(Or maybe the mail encoding could be parametrized - and of course the
best would be if it could figure out a minimal charset by itself - like
the evoluton mailer does it, for example - try ASCII first, then a
one-byte codepage, then UTF as fallback. But for this a general-purpose
python package would be handy which I have not heard of.)
4. Modified a bit the incoming email processing, too; so that I can
specify location on a per collector basis (configurable by the
abbreviation of the collector), and are not tied to put all the
collectors of a site into one folder. Maybe the setup for this has to be
done in a little fuzzy way, sigh.
5. Other issues with email submission:
- charset handling at new issues and followups,
- trim the automatically attached signature from the end, as I
thought about a better possibility in the following:
- anonymous mail source: I made mail name and address stored with
each transcript, and displayed instead of the username which is in this
case insignificant. So instead, something like 'Email submission from
"John Doe" fo...@ba...' is displayed. (Another possibily for improvement
would be to identify the plone user based on email address, but this can
be used only for info, as addresses can be easily faked / or even
authenticate users based on PGP-signature, but I doubt anyone really
would want to use this.)
---
So beware: at least the installer and possibly the email encoding stuff
might break plone-less (plain CMF) behaviour
Patches included. Please feel free to comment.
--
Bala'zs REE'
|
|
From: Andreas J. <an...@an...> - 2003-05-12 07:39:18
|
Not yet :-) --On Montag, 12. Mai 2003 9:33 Uhr +0200 danielle <dan...@wa...> wrote: > Hi, is there anybody somewhere working on a French translation of the > CMFCollectorng's po file ? thanks > > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Cmfcollectorng-develop mailing list > Cmf...@li... > https://lists.sourceforge.net/lists/listinfo/cmfcollectorng-develop |
|
From: danielle <dan...@wa...> - 2003-05-12 07:33:23
|
Hi, is there anybody somewhere working on a French translation of the CMFCollectorng's po file ? thanks |
|
From: Steve N. <ste...@yo...> - 2003-02-04 13:56:34
|
On Tue, 04 Feb 2003 13:47:18 +0100 Andreas Jung wrote: > CMFCollectorNG is *NOT* hosted on cvs.zope.org! The problem with > collector_issue_up > is just a mis-spelling of an action that is already fixed within the > CVS. Hi, I realise it's not hosted at cvs.zope.org but since I couldn't find it browsing the CMFCollectorNG CVS on the web as a quick fix I did a google for it and found it on the old CMFCollect. I'll learn about CVS and do a CVS update from now on. > > > > Question on best use of CMFCollectorNG if you have time. Two of us > > work together and we have three different sites we are developing. > > What is the best way to integrate CMFCollectorNG into these? > > 1. One CMFCollectorNG instance in each CMF site with someway of > > viewing issues from all sites in one area? > > 2. One CMFCollectorNG for all sites using "Topic" to categorise the > > issues for each site? > > 3. Other? > > No idea. It depends on your requirements. Ok, I assume one CMFCollectorNG can be setup to search/view all the items from other CMFCollectorNG's running on the same ZODB which is I think what I want. I'll get my partner to look at it, he is more technical than I am. Thanks for your reply and have a great day. Steve. |
|
From: Andreas J. <an...@an...> - 2003-02-04 12:47:24
|
--On Dienstag, 4. Februar 2003 12:46 +0000 Steve Nicholson <yah...@yo...> wrote: > Hi guys > I'm trying out CMFCollectorNG 0.2Beta1, I've found > "collector_issue_up.py" is missing from the skins, I used a copy from > http://cvs.zope.org/*checkout*/CMF/CMFCollector/skins/collector/collector > _issue_up.py?rev=1.1&sortby=log This is required when selecting "browse" > from the menu after viewing a ticket item. This wasn't needed in > CMFCollectorNG 0.2Alpha1, I assume it's due to finishing the English UI > update. CMFCollectorNG is *NOT* hosted on cvs.zope.org! The problem with collector_issue_up is just a mis-spelling of an action that is already fixed within the CVS. > > Question on best use of CMFCollectorNG if you have time. Two of us work > together and we have three different sites we are developing. What is > the best way to integrate CMFCollectorNG into these? > 1. One CMFCollectorNG instance in each CMF site with someway of viewing > issues from all sites in one area? > 2. One CMFCollectorNG for all sites using "Topic" to categorise the > issues for each site? > 3. Other? No idea. It depends on your requirements. -aj |
|
From: Steve N. <yah...@yo...> - 2003-02-04 12:41:33
|
Hi guys I'm trying out CMFCollectorNG 0.2Beta1, I've found "collector_issue_up.py" is missing from the skins, I used a copy from http://cvs.zope.org/*checkout*/CMF/CMFCollector/skins/collector/collector_issue_up.py?rev=1.1&sortby=log This is required when selecting "browse" from the menu after viewing a ticket item. This wasn't needed in CMFCollectorNG 0.2Alpha1, I assume it's due to finishing the English UI update. I'm not very familiar with CMF yet so not sure how much I can help with sorting things out. Let me know if there is anyway I can help. There was a problem in 0.2Alpha I saw when trying it. When editing an issue all selectable fields defaulted back to the first item in the list, looks like it's fixed in 0.2Beta1 version. Question on best use of CMFCollectorNG if you have time. Two of us work together and we have three different sites we are developing. What is the best way to integrate CMFCollectorNG into these? 1. One CMFCollectorNG instance in each CMF site with someway of viewing issues from all sites in one area? 2. One CMFCollectorNG for all sites using "Topic" to categorise the issues for each site? 3. Other? Having separate CMFCollectors for each site is a good idea but I would like to be able to go to one page to view the issues I need to be working on rather than 3 different ones. As we do more sites and bring in other persons involvement I would like to integrate these into the same system. Thanks for any advice you can offer on this. Good work on CMFCollectorNG, thanks for releasing it and please let me know if there is anything I can do to help with it. Steve. |
|
From: Andreas J. <an...@an...> - 2003-01-12 09:44:29
|
I forgot to mention that I am going to make an 0.20 alpha release today from your branch. Except some missing translations the stuff is stable enough for an alpha and would like to get some more input from the english speaking community. ANdreas --On Sonntag, 12. Januar 2003 10:13 +0100 Andreas Jung <an...@an...> wrote: > Helge, > > thanks for your excellent and hard work ;-) > Your work is escpecially valuable since Sidnei proposed > to CMFCollectorNG for new.zope.org. But disagreed until now because > there was no english version yet. And it would be cool to have > CMFCollectorNG running on new.zope.org. > > >> I've finally done some work on i18n now. >> >> The branch is tesdal-i18n-branch if anyone wants to take a look. >> >> Translating the German words isnt't that hard, you get a lot of help from >> the code, variables, the old collector and babelfish. Finding all the >> strings, changing templates and keeping track of changes in all files >> (I've made German potfile as I went along) was a lot more work. >> >> For pointers on how to set up i18n in CMF, you can take a look at >> http://plone.org/development/i18n/howto >> >> I briefly tested the German translation and it seems to translate, >> although I really haven't done a lot of testing. >> >> >> On to the dirty details: >> >> I've pretty much done the templates in the collectorng directory. >> >> What currently remains is: >> >> - Translating some help text, don't remember exactly which file it's in. >> > > the stuff is in the config files. I will take this over. > >> - Templates in the collectorng1 directory > > this directory contains mostly the german versions of some CMF skins. > > >> - The popcalendar.js.dtml in collectorng has to be transformed to zpt, >> german text has to be found and translated >> < operators have to be handled >> Maybe consider a calendar popup like the one Plone uses, less JS. > > Is there something we can rip from Plone directtly? > >> >> - Find and translate all the exceptions in the Python files. >> Exceptions like "sometext %s" % variable are harder to translate... >> Maybe call translation service/Localizer directly, Wankyou might have >> got this working in his NeoPortal. > > Have to check that. >> >> - Make the CollectorNGProperties.render method a macro instead to enable >> translation. > > You mean to implement render() as PyScript? >> >> - I'm not even sure if I have tested all the templates, some might be >> broken. > > Hopefully not. > > Thanks a lot, > Andreas > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Cmfcollectorng-develop mailing list > Cmf...@li... > https://lists.sourceforge.net/lists/listinfo/cmfcollectorng-develop --------------------------------------------------------------------- - Andreas Jung http://www.andreas-jung.com - - EMail: andreas at andreas-jung.com - - "Life is too short to (re)write parsers" - --------------------------------------------------------------------- |
|
From: Andreas J. <an...@an...> - 2003-01-12 09:14:07
|
Helge, thanks for your excellent and hard work ;-) Your work is escpecially valuable since Sidnei proposed to CMFCollectorNG for new.zope.org. But disagreed until now because there was no english version yet. And it would be cool to have CMFCollectorNG running on new.zope.org. > I've finally done some work on i18n now. > > The branch is tesdal-i18n-branch if anyone wants to take a look. > > Translating the German words isnt't that hard, you get a lot of help from > the code, variables, the old collector and babelfish. Finding all the > strings, changing templates and keeping track of changes in all files > (I've made German potfile as I went along) was a lot more work. > > For pointers on how to set up i18n in CMF, you can take a look at > http://plone.org/development/i18n/howto > > I briefly tested the German translation and it seems to translate, > although I really haven't done a lot of testing. > > > On to the dirty details: > > I've pretty much done the templates in the collectorng directory. > > What currently remains is: > > - Translating some help text, don't remember exactly which file it's in. > the stuff is in the config files. I will take this over. > - Templates in the collectorng1 directory this directory contains mostly the german versions of some CMF skins. > - The popcalendar.js.dtml in collectorng has to be transformed to zpt, > german text has to be found and translated > < operators have to be handled > Maybe consider a calendar popup like the one Plone uses, less JS. Is there something we can rip from Plone directtly? > > - Find and translate all the exceptions in the Python files. > Exceptions like "sometext %s" % variable are harder to translate... > Maybe call translation service/Localizer directly, Wankyou might have > got this working in his NeoPortal. Have to check that. > > - Make the CollectorNGProperties.render method a macro instead to enable > translation. You mean to implement render() as PyScript? > > - I'm not even sure if I have tested all the templates, some might be > broken. Hopefully not. Thanks a lot, Andreas |
|
From: Helge T. <he...@te...> - 2003-01-12 02:59:27
|
I've finally done some work on i18n now. The branch is tesdal-i18n-branch if anyone wants to take a look. Translating the German words isnt't that hard, you get a lot of help from the code, variables, the old collector and babelfish. Finding all the strings, changing templates and keeping track of changes in all files (I've made German potfile as I went along) was a lot more work. For pointers on how to set up i18n in CMF, you can take a look at http://plone.org/development/i18n/howto I briefly tested the German translation and it seems to translate, although I really haven't done a lot of testing. On to the dirty details: I've pretty much done the templates in the collectorng directory. What currently remains is: - Translating some help text, don't remember exactly which file it's in. - Templates in the collectorng1 directory - The popcalendar.js.dtml in collectorng has to be transformed to zpt, german text has to be found and translated < operators have to be handled Maybe consider a calendar popup like the one Plone uses, less JS. - Find and translate all the exceptions in the Python files. Exceptions like "sometext %s" % variable are harder to translate... Maybe call translation service/Localizer directly, Wankyou might have got this working in his NeoPortal. - Make the CollectorNGProperties.render method a macro instead to enable translation. - I'm not even sure if I have tested all the templates, some might be broken. And probably more... check it out to test and fix. I probably won't have much time until next weekend, but I hope it's enough for people to get started. -- Helge |
|
From: Andreas J. <an...@an...> - 2003-01-09 19:19:34
|
Hi Kevin, --On Donnerstag, 9. Januar 2003 11:02 -0800 Kevin Teague <kt...@bc...> wrote: > Hi, > > I am working on an alternate skin for CollectorNG for use with my web > site. There are a few reasons for this: > > * I want to maintain consistency with my web site, and it has a > slightly different layout and look and feel than stock CMF or Plone CMFCollectorNG does work again with the standard main_template of CMF and it will work with Plone (90% done). The current collector_template has been used in my company. I any case I would like to see that skins should be i18n-aware. > * I'd like to have a slightly simpler tracker product, so I'm not using > the deadline section or the subcategories Why can't you use standard HTML comments inside the skins? > * To integrate my installation of the CollectorNG with the rest of the > site. For instance, I am already storing a users contact information > elsewhere, so that information does not need to be provided when the > submit a bug. Well, the current approach is driven by the need of the project I wrote CMFCollectorNG for ;-) But I think it is a suitable solution for most cases. > > We also have a support staff at work who use an older non-CMF tracker > (ZShrink) which we've written a custom user interface for. This other > tracker uses CMFMail to allow you to submit issues via email. The user > interface is very simple and streamlined, and allows things like > changing the priority and assignment of multiple issues in one form. > Eventually I would like to migrate this user interface on top of > CollectorNG if possible. Christian Theune is already working on such a solution for CMFCollectorNG. However I have not seen any code yet. > Further down the road, I also might use the stock CollectorNG user > interface if our developers want to take advantage of fields such as the > deadline, subcategory, etc. > Don't understand... > I am wondering if there any major changes planned under the hood of > CollectorNG that would break alternate skins? Not really. The current HEAD is pretty stable and don't plan any major changes in the near future. > And if alternate skins are provided, I wonder if provisions for choosing > which skin is used for each CollectorNG instance should be a part of > CollectorNG or if that decided from elsewhere in the portal? I am not very familiar with the skin tool and the skin selection schema. In my understanding you can control the order of the skins through the skins tool and/or through siteaccess rules(?). > I'll probably have something workable sometime next week, and I'll email > out a URL for it then, and can consider making this alternate skin > usable outsite of my site if there is any demand for it. Ok, but will focus on an i18n aware skin (tesdal@irc is working on the staff). Cheers, Andreas |
|
From: Kevin T. <kt...@bc...> - 2003-01-09 19:02:48
|
Hi, I am working on an alternate skin for CollectorNG for use with my web site. There are a few reasons for this: * I want to maintain consistency with my web site, and it has a slightly different layout and look and feel than stock CMF or Plone * I'd like to have a slightly simpler tracker product, so I'm not using the deadline section or the subcategories * To integrate my installation of the CollectorNG with the rest of the site. For instance, I am already storing a users contact information elsewhere, so that information does not need to be provided when the submit a bug. We also have a support staff at work who use an older non-CMF tracker (ZShrink) which we've written a custom user interface for. This other tracker uses CMFMail to allow you to submit issues via email. The user interface is very simple and streamlined, and allows things like changing the priority and assignment of multiple issues in one form. Eventually I would like to migrate this user interface on top of CollectorNG if possible. Further down the road, I also might use the stock CollectorNG user interface if our developers want to take advantage of fields such as the deadline, subcategory, etc. I am wondering if there any major changes planned under the hood of CollectorNG that would break alternate skins? And if alternate skins are provided, I wonder if provisions for choosing which skin is used for each CollectorNG instance should be a part of CollectorNG or if that decided from elsewhere in the portal? I'll probably have something workable sometime next week, and I'll email out a URL for it then, and can consider making this alternate skin usable outsite of my site if there is any demand for it. -- -- Kevin Teague Genomics Web Developer BC Genome Sciences Centre http://www.bcgsc.ca |
|
From: Andreas J. <an...@an...> - 2002-12-07 13:22:52
|
Hi,
I just came across a problem using CMFCollectorNG together with
Zope (HEAD), CMF(HEAD) and Python 2.2.2. There seems to be a major
pickling problem with Python 2.2.2. The problem does not occur
with Python 2.1.3. So I strongly recommend to use Python 2.1.3 instead.
(means you can't run CMFCollectorNG against the Zope HEAD for now).
Cheers,
Andreas
---------------------------------------------------------------------
- Andreas Jung http://www.andreas-jung.com -
- EMail: andreas at andreas-jung.com -
- "Life is too short to (re)write parsers" -
---------------------------------------------------------------------
|
|
From: Oliver P. <to...@fo...> - 2002-12-06 10:26:14
|
Oops, sorry
On Fri, 6 Dec 2002, Andreas Jung wrote:
> Oliver,
>=20
> would you please join the developers mailing list?
>=20
> As a general rule, please work on branches. Merges with the HEAD
> should be discussed on the developers list.
>=20
> Thanks,
> Andreas
>=20
> --On Freitag, 6. Dezember 2002 01:31 -0800 to...@us...=
=20
> wrote:
>=20
> > Update of /cvsroot/cmfcollectorng/CMFCollectorNG/config
> > In directory sc8-pr-cvs1:/tmp/cvs-serv19030/config
> >
> > Modified Files:
> > =09issue_config.py
> > Log Message:
> > Added new category customer and attributes for this category.
> >
> >
> > Index: issue_config.py
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > RCS file: /cvsroot/cmfcollectorng/CMFCollectorNG/config/issue_config.py=
,v
> > retrieving revision 1.1.1.1
> > retrieving revision 1.2
> > diff -C2 -d -r1.1.1.1 -r1.2
> > *** issue_config.py=093 Dec 2002 17:51:23 -0000=091.1.1.1
> > --- issue_config.py=096 Dec 2002 09:31:52 -0000=091.2
> > ***************
> > *** 220,222 ****
> > --- 220,294 ----
> > category=3D'effort',
> > ),
> > +
> > + CollectorNGProperty('customer_name',
> > + description=3D'Name des Kunden',
> > + type=3D'text',
> > + default=3D'',
> > + used=3D0,
> > + mandatory=3D0,
> > + category=3D'customer',
> > + ),
> > +
> > + CollectorNGProperty('customer_address',
> > + description=3D'Adresse des Kunden',
> > + type=3D'text',
> > + default=3D'',
> > + used=3D0,
> > + mandatory=3D0,
> > + category=3D'customer',
> > + ),
> > +
> > + CollectorNGProperty('customer_city',
> > + description=3D'Stadt des Kunden',
> > + type=3D'text',
> > + default=3D'',
> > + used=3D0,
> > + mandatory=3D0,
> > + category=3D'customer',
> > + ),
> > +
> > + CollectorNGProperty('customer_zip',
> > + description=3D'Postleitzahl des Kunden',
> > + type=3D'text',
> > + default=3D'',
> > + used=3D0,
> > + mandatory=3D0,
> > + category=3D'customer',
> > + ),
> > +
> > + CollectorNGProperty('customer_phone',
> > + description=3D'Telefonnummer des Kunden',
> > + type=3D'text',
> > + default=3D'',
> > + used=3D0,
> > + mandatory=3D0,
> > + category=3D'customer',
> > + ),
> > +
> > + CollectorNGProperty('customer_fax',
> > + description=3D'Faxnummer des Kunden',
> > + type=3D'text',
> > + default=3D'',
> > + used=3D0,
> > + mandatory=3D0,
> > + category=3D'customer',
> > + ),
> > +
> > + CollectorNGProperty('customer_room',
> > + description=3D'Zimmer des Kunden',
> > + type=3D'text',
> > + default=3D'',
> > + used=3D0,
> > + mandatory=3D0,
> > + category=3D'customer',
> > + ),
> > +
> > + CollectorNGProperty('customer_building',
> > + description=3D'Geb=E4ude des Kunden',
> > + type=3D'text',
> > + default=3D'',
> > + used=3D0,
> > + mandatory=3D0,
> > + category=3D'customer',
> > + ),
> > )
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Cmfcollectorng-cvs mailing list
> > Cmf...@li...
> > https://lists.sourceforge.net/lists/listinfo/cmfcollectorng-cvs
>=20
>=20
>=20
>=20
> ---------------------------------------------------------------------
> - Andreas Jung http://www.andreas-jung.com -
> - EMail: andreas at andreas-jung.com -
> - "Life is too short to (re)write parsers" -
> ---------------------------------------------------------------------
>=20
---
---
Oliver Pabst .-------------------------.=20
mailto:ol...@sy... : :=20
phone :+49 681 56600600 : project department : SYBCOM GmbH =
=20
fax :+49 681 56600660 : : http://www.sybcom.de =
=20
|
|
From: Andreas J. <an...@an...> - 2002-12-06 10:20:16
|
Oliver,
would you please join the developers mailing list?
As a general rule, please work on branches. Merges with the HEAD
should be discussed on the developers list.
Thanks,
Andreas
--On Freitag, 6. Dezember 2002 01:31 -0800 to...@us...=20
wrote:
> Update of /cvsroot/cmfcollectorng/CMFCollectorNG/config
> In directory sc8-pr-cvs1:/tmp/cvs-serv19030/config
>
> Modified Files:
> issue_config.py
> Log Message:
> Added new category customer and attributes for this category.
>
>
> Index: issue_config.py
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> RCS file: /cvsroot/cmfcollectorng/CMFCollectorNG/config/issue_config.py,v
> retrieving revision 1.1.1.1
> retrieving revision 1.2
> diff -C2 -d -r1.1.1.1 -r1.2
> *** issue_config.py 3 Dec 2002 17:51:23 -0000 1.1.1.1
> --- issue_config.py 6 Dec 2002 09:31:52 -0000 1.2
> ***************
> *** 220,222 ****
> --- 220,294 ----
> category=3D'effort',
> ),
> +
> + CollectorNGProperty('customer_name',
> + description=3D'Name des Kunden',
> + type=3D'text',
> + default=3D'',
> + used=3D0,
> + mandatory=3D0,
> + category=3D'customer',
> + ),
> +
> + CollectorNGProperty('customer_address',
> + description=3D'Adresse des Kunden',
> + type=3D'text',
> + default=3D'',
> + used=3D0,
> + mandatory=3D0,
> + category=3D'customer',
> + ),
> +
> + CollectorNGProperty('customer_city',
> + description=3D'Stadt des Kunden',
> + type=3D'text',
> + default=3D'',
> + used=3D0,
> + mandatory=3D0,
> + category=3D'customer',
> + ),
> +
> + CollectorNGProperty('customer_zip',
> + description=3D'Postleitzahl des Kunden',
> + type=3D'text',
> + default=3D'',
> + used=3D0,
> + mandatory=3D0,
> + category=3D'customer',
> + ),
> +
> + CollectorNGProperty('customer_phone',
> + description=3D'Telefonnummer des Kunden',
> + type=3D'text',
> + default=3D'',
> + used=3D0,
> + mandatory=3D0,
> + category=3D'customer',
> + ),
> +
> + CollectorNGProperty('customer_fax',
> + description=3D'Faxnummer des Kunden',
> + type=3D'text',
> + default=3D'',
> + used=3D0,
> + mandatory=3D0,
> + category=3D'customer',
> + ),
> +
> + CollectorNGProperty('customer_room',
> + description=3D'Zimmer des Kunden',
> + type=3D'text',
> + default=3D'',
> + used=3D0,
> + mandatory=3D0,
> + category=3D'customer',
> + ),
> +
> + CollectorNGProperty('customer_building',
> + description=3D'Geb=E4ude des Kunden',
> + type=3D'text',
> + default=3D'',
> + used=3D0,
> + mandatory=3D0,
> + category=3D'customer',
> + ),
> )
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Cmfcollectorng-cvs mailing list
> Cmf...@li...
> https://lists.sourceforge.net/lists/listinfo/cmfcollectorng-cvs
---------------------------------------------------------------------
- Andreas Jung http://www.andreas-jung.com -
- EMail: andreas at andreas-jung.com -
- "Life is too short to (re)write parsers" -
---------------------------------------------------------------------
|
|
From: Helge T. <he...@te...> - 2002-12-04 22:33:11
|
Thanks for the offer Kevin. I don't have the full overview of what needs to be done yet, but hopefully I will soon. I've created a branch (tesdal-i18n-branch) where I'll be working on the i18n stuff. So far it seems like the biggest job is changing the templates and getting the structure right. Translating from German to English should be pretty quick. -- Helge ----- Original Message ----- From: "Kevin Teague" <kt...@bc...> To: <cmf...@li...> Sent: Wednesday, December 04, 2002 9:34 PM Subject: [Cmfcollectorng-develop] i18n of CMFCollectorNG to English > Hello, > > An English translation of CMFCollectorNG would be good, since I work in > an English speaking office :) > > Andreas said that a Helge Tesdal would be leading the i18n for > CMFCollectorNG. Is there anything I can do to help with the translation? > > I don't have too much experience with i18n, but I do have lots of > experience with Zope/CMF/Plone. I also don't speak any German, but I do > know a couple German/English speakers that I can ask for translation > help if need be. |
|
From: Kevin T. <kt...@bc...> - 2002-12-04 20:35:08
|
Hello, An English translation of CMFCollectorNG would be good, since I work in an English speaking office :) Andreas said that a Helge Tesdal would be leading the i18n for CMFCollectorNG. Is there anything I can do to help with the translation? I don't have too much experience with i18n, but I do have lots of experience with Zope/CMF/Plone. I also don't speak any German, but I do know a couple German/English speakers that I can ask for translation help if need be. -- -- Kevin Teague Genomics Web Developer BC Genome Sciences Centre http://www.bcgsc.ca |
|
From: <aj...@us...> - 2002-12-04 19:49:15
|
Update of /cvsroot/cmfcollectorng/CVSROOT
In directory sc8-pr-cvs1:/tmp/cvs-serv29714
Modified Files:
loginfo
Log Message:
changed to -cvs
Index: loginfo
===================================================================
RCS file: /cvsroot/cmfcollectorng/CVSROOT/loginfo,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** loginfo 4 Dec 2002 12:23:12 -0000 1.2
--- loginfo 4 Dec 2002 19:49:11 -0000 1.3
***************
*** 27,30 ****
! CVSROOT $CVSROOT/CVSROOT/syncmail %{sVv} cmf...@li...
! DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} cmf...@li...
--- 27,30 ----
! CVSROOT $CVSROOT/CVSROOT/syncmail %{sVv} cmf...@li...
! DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} cmf...@li...
|
|
From: <aj...@us...> - 2002-12-04 12:24:11
|
Update of /cvsroot/cmfcollectorng/CMFCollectorNG In directory sc8-pr-cvs1:/tmp/cvs-serv18503 Modified Files: LICENSE.txt Log Message: updated Index: LICENSE.txt =================================================================== RCS file: /cvsroot/cmfcollectorng/CMFCollectorNG/LICENSE.txt,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** LICENSE.txt 3 Dec 2002 17:51:22 -0000 1.1.1.1 --- LICENSE.txt 4 Dec 2002 12:24:08 -0000 1.2 *************** *** 2,5 **** --- 2,7 ---- PloneBatch.py is published under the Gnu Public License GPL + and included with kind permission. + and included with kind permission. The email package is (C) by the Python Software Foundation |