Hi, Please design it the way that the functionality could be reused in a web interface rather then a commando line script.
Best regards,
Björn Dieding
Content & Commerce made easy
GMT +01:00 Hannover, Germany
Björn Dieding
Phone: +49 (511) 5904576
Mobile: +49 (151) 12169868
Email: [EMAIL PROTECTED]
PayPal: [EMAIL PROTECTED]
MSN: [EMAIL PROTECTED]
YIM: bdieding
AIM: BjoernDieding
ICQ: 176927179
SKYPE: BjoernDieding
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:components-
> [EMAIL PROTECTED] On Behalf Of Andreas Schamberger
> Sent: Monday, July 14, 2008 7:02 PM
> To: Derick Rethans
> Cc: Components
> Subject: Re: [Components] Roadmap for the next release
>
> Hi,
>
> I'm quite busy at the moment but I took the time today to write a quick
> requirements document for a ezlupdate.php script.
>
> Most of the required functionality is already in the script I posted
> some time ago. Therefore it shouldn't be too much work to add the rest.
>
> Are there any design rules for a command line script in ezc?
> I guess a look at existing scripts should be enough (e.g. the
> PersistentObjectDatabaseSchemaTiein)?
>
> Regards
> Andi
>
> Derick Rethans schrieb:
> > On Tue, 24 Jun 2008, Derick Rethans wrote:
> >
> >> On Tue, 24 Jun 2008, Andreas Schamberger wrote:
> >>
> >>> I'm missing the translation string extraction for templates in the
> Roapmap.
> >>> I can offer to finish the ezlupdate.php that I started to a complete
> command
> >>> line script that also has the ability to create the neccessary TS
> files for
> >>> new languages.
> >> Ah, sorry - I forgot about this :-/ I'd greatly appreciate it of you
> >> could help us with this one. I'll add an issue to the tracker for it
> >> though.
> >
> > I added an issue now: http://issues.ez.no/IssueView.php?Id=13236&;
> > Perhaps we can kick start this off by creating a requirements document?
> >
> > regards,
> > Derick
smime.p7s
Description: S/MIME cryptographic signature
-- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
