Well I have additional ideas... For example whatever the internal API looks like you could provide helper functions that can convert from a standard into the structures used by the internal API.
A certain array can get converted into the internal structure
A certain XML can get converted into the internal structure
E.g. if you want to store it for later use you can again export it from
internal format to XML
SimpleXML could be of help too.
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:[EMAIL PROTECTED] On Behalf
> Of David Coallier
> Sent: Wednesday, March 05, 2008 3:52 PM
> To: Björn Dieding
> Cc: [email protected]
> Subject: Re: [Components] ezc Graph - Gantt charts. Raise your opinions
> and thestate of art.
>
> On Tue, Mar 4, 2008 at 5:58 PM, Björn Dieding <[EMAIL PROTECTED]> wrote:
> > Ok to give you some more help look at the image I attached from ms
> project. It is way more complex then yours. Think about how you can
> configure/fill your chart. Your import data could become quite complex due
> all the options associated to one row of data.
> >
> > In concrete:
> >
> > Data should be come from a numeric array or iterator. If you use the
> name of the data row as a key for this array you end up in problems since
> not all chars are allowed as an array key.
> >
> > One data row should be a php object / structure.
>
> I agree with you here the biggest challenge is not the code itself but
> making it's api usuable :) Finding a good format for the dataset is
> crucial.
>
> Any special ideas ? If not I'll try to come up with something. I
> especially like your iterator idea, could be much simpler and cleaner
> (a bit slower though but still solid)
>
> --
> David,
> Re-read what you are replying.
smime.p7s
Description: S/MIME cryptographic signature
-- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
