5 users online. Create an account or sign in to join them.Users
Piano Sonata
This is an open discussion with 27 replies, filed under Ensembles.
Search
Hello,
Can I make a archive like this one : http://test.tamarawobben.nl
Roelof
Has anything been decided during the meetup about using this for the upcoming 2.3 release?
I'm looking to add a blog to my existing Symphony installation and found this ensemble by searching discussions here. I like the Piano Sonata, but have two questions.
Are there any simpler blog implementations that I should look at? It's a trick question, I know, since it can only be as-simple-as-possible. At the least, I imagine a blog would contain article creation, commenting, archive management, and probably tags of some form. Piano Sonata looks awesome, but it might take me a while to get my head around all the back-end admin structure that goes into it.
Asking really the same thing another way, is there a recommended way to integrate this ensemble into an existing Symphony installation? I can install Piano Sonata into a subdirectory and tell the parent install to ignore that directory via htaccess, but then they're essentially two unrelated installations. I guess that what I want, technically, is database sharing (so content is accessible across the two later). Should I just give Piano Sonata a different table prefix and have it install to the same database? Is there a way (an extension, say) to access tables with different prefixes?
@Anhedonia: I don't think there is a way to integrate two different Symphony installations. I would just install the Ensemble separately using a different database and copy / paste any of the patterns to your own project.
Remie: I've considered doing that, but am concerned about making a mistake in the translation. Generally, manually copying existing work (a complete, published Ensemble) doesn't make sense. It duplicates effort, is error-prone, and just generally tedious. It seems that the general problem has been discussed, but I'm dismayed that there's no current working solution.
It's actually being discussed/debated at length in #1002. Admittedly the discussion tails off in places and gets a bit sidetracked with political bullshit, but the general concept has been researched and thought about thoroughly from a theoretical perspective.
Thanks, brendo, for the note. I had looked at that issue briefly (and will read through it fully when I get time). I'm glad that you guys have the vision to even have such things on the road-map. It's certainly a non-trivial plan, so understandably a long discussion. Being new to Symphony, I didn't want to do the manual re-creation if there's already a better, idiomatic way, hence my original question here.
Create an account or sign in to comment.
I'd be happy to rejig this template about, such as add @fontface options, more JavaScript etc...