Re: [fp-dev] Fwd: FlatPress

[NoWhereMan <now...@fl...>]

>> ---------- Forwarded message ----------
>> From: Tari Akpodiete <tar...@gm...>
>> Date: 24-nov-2006 8.37
>> Subject: FlatPress
>> To: sa...@gm...
>>
>>
>> greetings Samy:
>>
>> oh, i have already emailed the FlatPress link to several SPHPB-using
>> friends. one of them - http://www.cyberware.ca - made a great gallery
>> plug-in, and i got him to adapt it to work with LightBox JS. it's
>> only implemented on some of his gallery pages right now, for example
>> - http://www.cyberware.ca/blog/gallery.php?_cat=people - and it's a
>> work in progress, but i bet it would work on FlatPress too!

Hi Tari,

Welcome to FP ^_^


>> i would like to suggest the incorporation of a REAL editor, for
>> example, the very robust and free Tiny MCE -
>> http://tinymce.moxiecode.com/ - pppBlog (which mixes SPHPblog and
>> TFTgallery together) - http://tiedemann.ifastnet.com/pppblog/ -has
>> put in FCKeditor - http://www.fckeditor.net - but one can choose to
>> use the regular editor or the enhanced one.


Yes, I'm already working on this. The problem at the moment is that pppBlog 
just wraps the output (xhtml) of these cool WYSIWYG editors into 
[html][/html] tags; this tag, while handy, still forces the conversion of 
special html chars such as <, >, & into entities (then out into the entry 
txt), which are then reconverted back into normal char while parsing and 
doing output. As you can understand this is a behaviour that could be 
accepted for a few lines of html, while it is IMO a real waste of CPU time 
if becomes the *rule*, so [html] tags everywhere, always.
What I'm currently working on is adding a special field, fp-proprietary, 
called MARKUP, where FP will save infos about the markup plugin which is in 
use currently. Old versions will default to bbcode, to retain compatibility, 
while new ones will let you choose. Unfortunately I still have to fix some 
problem with entities, but it is already "in the pipeline" ;)
Once done, you could choose to use an XHTML markup, and eventually the 
beloved TinyMCE or FCKeditor :)

>>
>> also, it would be GREAT to have links that use words rather than a
>> combo of nonsensical characters and numbers. for example:
>>
>> http://www.reallygoodfriend.com/steve-irwin-has-died/
>>
>> instead of
>>
>> http://www.reallygoodfriend.com/index.php?entry=entry060904-041522
>>
>> and real permalinks.


This is something which should be discussed. using the "nonsensical" chars, 
give us the freedom to point directly to the entry file, and so we avoid 
searching for the title through our index (we use a cached index for titles, 
categories, and entry IDs). I could maybe hash the titles, but then I should 
add a further field to the cache, which is already big in my opinion...

>> it is nice to hear how themes can be made in what seems like a
>> simpler fashion. i was actually planning on developing some themes
>> for SPHPB. i suppose that there will soon be a tutorial on how to do
>> so for FlatPress, and i'm looking forward to that. maybe you can
>> also make a tutorial on how to port themes from other blogging
>> systems.

I guess this could be a work for Hydra :p she's good at converting themes, 
now :)

>> one thing i find very frustrating about SPHPB is that there is ZERO
>> documentation, so it is hard to look things up when there is a
>> question.

Yes, I do understand you. I would *love* writing docs; seriously, I like to 
write. But time is soooo little :(

>> already, i see some things explained on -
>> http://flatpress.nowhereland.it -
>> so that is encouraging. i'm a writer, and i'd be glad to contribute
>> in that
>> area if i can, once i learn more, of course.

How could I refuse?? :D
For me, you're in :P