RHansmann / Kirby-2.0---inheritance-of-blueprints

Modification for implementing inheritance of blueprints in Kirby 2.0
1 stars 0 forks source link

Cool #1

Open xypaul opened 9 years ago

xypaul commented 9 years ago

Hey dude,

Good work. I like what you have done.

Just thinking if there is any chance you could implement the structure as shown here: https://github.com/getkirby/panel/issues/92 by robjames

I find that structure much easier to use :)

Thanks and good luck :+1:

RHansmann commented 9 years ago

Hi Paul,

okay, I will try to implement this in the next 2 weeks. Hope You have enough time. It will be a bit more complicated than the current solution because there is no PHP function to merge. I will have to program this manually, so it will take little time. The current solution I will keep, because this ist he more convenient way if grouping of fields will be implemented.

Best regards

Reinhard

Von: Paul Knittel [mailto:notifications@github.com] Gesendet: Dienstag, 7. Oktober 2014 01:45 An: RHansmann/Kirby-2.0---inheritance-of-blueprints Betreff: [Kirby-2.0---inheritance-of-blueprints] Cool (#1)

Hey dude,

Good work. I like what you have done.

Just thinking if there is any chance you could implement the structure as shown here: getkirby/panel#92 https://github.com/getkirby/panel/issues/92 by robjames

I find that structure much easier to use :)

Thanks and good luck https://assets-cdn.github.com/images/icons/emoji/unicode/1f44d.png

— Reply to this email directly or view it on GitHub https://github.com/RHansmann/Kirby-2.0---inheritance-of-blueprints/issues/1 . https://github.com/notifications/beacon/6756013__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcyODI1ODI5OSwiZGF0YSI6eyJpZCI6NDQ5NjMyMTF9fQ==--6a14b2279d092a5774a51a4365f30118c22b757a.gif

xypaul commented 9 years ago

@RHansmann thanks for the quick response. Looking forward to see the results :)

RHansmann commented 9 years ago

I figured out some restrictions if I will implement this the way as rob james has specified. It will be much more flexibel to keep it the way I've implemented it currently. Would it be okay if I keep it as it is, but add a new parameter to specifiy before or after which field the fields should be inserted? This will make it easier to implement recursive embedding of blueprint files later on.

RHansmann commented 9 years ago

Hey Paul,

presse have a look to my Commune. Tx.

Regals Reinhard

---- Paul Knittel schrieb ----

Reopened #1.

— Reply to this email directly or view it on GitHub.

{"@context":"http://schema.org","@type":"EmailMessage","description":"View this Issue on GitHub","action":{"@type":"ViewAction","url":"https://github.com/RHansmann/Kirby-2.0---inheritance-of-blueprints/issues/1#event-175499712","name":"View Issue"}}