[Pimki-users] register as developper for Pimki
nicolas.delsaux at gmail.com
Tue Nov 14 15:03:23 EST 2006
On 11/14/06, Assaph Mehr <assaph at gmail.com> wrote:
> > Oh my god, it's alive, it's ALIVE :-)
> bwahahahaha! :-D
Once again, i put the list in copy, for the sake of memory.
> Thanks. It stretches my graphic design skills to the max....
I may provide here a little knowledge, since I made myself (with
obvious display bugs) my blog stylesheet.
> Yep. When you're ready to submit a patch just update your copy,
> resolve conflicts if any and re-run the tests. Use svn diff to create
> a patch and send it to me.
> > Do you think it could be added, since I find this system really cleaner ?
> The current footnote mechanics are using textile (RedCloth) - there is
> no specific support for them. If you want to add a special chunk...
Let me guess ... If I want that chunk, I can just ... code it :-))
> Tried the site and got a 500 error. Let me know if you want me to take a look.
Should be corrected now.
Take a look at http://nicolas-delsaux.homelinux.net/leblog/show/Pimki+2
There is a bottom link for features proposals.
> To be more inline with the rest of the chunks syntax it should
> probably be something like:
> at the start and a simple
> to end the section. This easily allows using other languages, like
> [code[java]]. I use the double brackets for links, and the
> [keyword[parameters]] syntax for "macros". There are already some
> special such constructs, like:
> [bliki[thread]] - links to bliki threads
> [>other web[page name]] - links to pages on other webs
> [!my-macro[params...]] - macro expansion (planned :)
Suggestion included in feature !
> So i want to keep the same syntax. Note that I was still playing with
> the advanced syntax in the trunk, so it may change a little. Once I
> have something I like I'll make sure everything conforms.
And you'll make sure I can merge my changes with ease ?
> Not sure what you're after, but if you want to put plain text
> "objects" and later reference them then definitely yes.
[sf[isbn]]227363847495 for retrieving book info
[sf[title][sf for fetching nearby titles
[sf[person]] for a person name
All managed with chunks and page dynamic creation.
> You also need to be a bit careful when adding the chunk into the
> processing order. The "engine" part is the markup engine
> (textile/markdown etc). So for the syntax-highlight chunk it should be
> before the engine, and it should mask it's content from further
I believe i can get inspired reading existing code, like, say, ...
I've already notice i only have to insert my class name in the
PRE_ENGINE_ACTIONS array (in the revision class).
> This should obviously be replaced with a call to CodeRay ;-)
In the final iteration, yes ;-)
> You can easily cache the results, as they will not change between page
> rendering (unlike links, which need to be resolved each time as the
> page may have been created/deleted etc).
Let's use cache in v. 2
> We all started there :)
Never forget I also begin in Rails ...
> I thought about chunks as plugins, but because the processing order
> for chunks is VERY important I am not sure this is the proper way to
> go. If someone already hacks the source, they can easily just add the
> extra call at the right place to add the new chunk, which is a lot
> simple and less error prone (at least until I have hundreds of people
> writing customisations....)
I'm OK with that, provided you never get that developper crowd.
> Check your regexp, check where you added the chunk etc. Start with
> testing the chunk as stand-alone, then as part of page processing.
How can I test correctly my chunk ?
> Looking forward to it! :)
You shouldn't hope so. Anyway ... to be continued ...
N'imprimez ce mail que si vous ne savez pas le lire sur l'écran : les
électrons se recyclent bien, le papier, beaucoup moins bien.
More information about the Pimki-users