- under consideration
- composed title fields
- make tagging possible
- Enable Trackbacking
- online installation procedure
- Spam filter for comments
- logout
- when the URL of a link is very long, it goes out of the content pane
- permanent links
- use prototype.js?
- show range not between numbers but by specifying the number of entries to show
- offer Ajax
- Back-Button makes Search Option Symbol Swap
- Baptise Qdig Elements and set Maxwidth for Gallery
- mark internally if data has been changed and ask with JS on every action that leaves the page
- When page is not in menu, show submenu on page
- operators for search options
- server side gzip compression
- FCKeditor-Plugin for multimedia files?
- idea: log changes
- FCK editor breaks lines such that not all options are visible
- display order index in list view
- make every field searchable
- FK queries
- reconsider _sys_field options
- make references in table of content to foreign-key related entries implicit (per link)
- template for individual entries
- PP duplicates bits of entries
- a code beautifying style
- Show no "show index" when only one article shown
under consideration
is there a way of getting a complex title field?
That would be nice for some tables that don't have anything in a single field that would suffice as a title.
Maybe putting it [_all_] together as option. Then all would be the title - a good compromise? Could sthg like that be a better default?
Another idea: use fillafromb option to give the user the power to compose the title himself. He clicks the fields together as a comma separated list and ion this order will the fields be shown.
We'd need
- another system table for the associations (tablename,entryid,tagid) and one for tags (id,name)
- a display on the showing side ("this item belongs to...") and a list of tags that select all entries tagged by that tag. A box with all tags there are (indicate by a priority so the skin can adjust font size?) The problem: How to show entries of different structure on one page? That sounds like executing one SQL-statement that goes over the tag table to get the pagename and ids. Then, group them by table and execute a statement on each. writeEntries() should be able to merge the resultsets somehow.
- a display on the editing side (existing tags as checkboxes, text field for new ones) - includes all the SQL saving, getting etc
07.07.06 made it "in progress" - it's essential these days
21.07.2006
there is also the purpose of going public when tagging. Here is a link to an FCKeditor plugin that might be really interesting.
24.07.2006
new again. I value HTML Templates higher for the moment :-(
25.07.2006
if tags get used in the URL, there is a security problem!
maybe I should generally do ini_set("register_globals", 0)
Find out what could be affected...
16.09.2006
now it is "in progress" again. here is a short, but more exhaustive todo-list:
-tag-table (tagid,tagname)
-relation-table (pagename,pageid,tagid)
-adjust search to accept GET-Requests
-adjust search to work with tags
-give tagging to editing
-adjust $entity for pages so that formfield can be click-filled
-fill $entity-field with tags for that entry before displaying tag-div
-display tag-div
-write help text
-adjust Feeding to work with tags
(-make a page where Feeds can be clicked together
or: explain that thing better and insert another bug for it
)
-the showing-side of it (see first entry to this bug)
Use this Perl-Script to do it.
Requires CGI, understanding + testing, RDF for posts.
The tagging-bug should maybe be done in advance...
Check also out Ping-o-matic
Ask the user which database to use and give language choice.
Then curse him to chmod some dirs and delete the script.
02.03.2006
there is code for that in the wordpress code (I don't remember the exact place). Maybe we could let index.php do that. Then we don't need to delete anything, the code needs to mark somehow that it has been done - maybe by changing the value of some boolean var in the config PHP ?
22.01.2007
maybe I can find a php application installer someone else wrote? Like here. Or here.
(it's for Wordpress originally - here is a PHP5 class built from it)
The savest way is to just close the browser window...
Permanent links are a cool feature, better and more informative than PHP urls with "nr" param...
That could be a configurational option, like the editDate field in the XML.
Maybe we could go for URLs like http://www.url.de/bugs?permanent-link
(the example shows that it maybe enough to specify a field that should be transformed to a permanent link...)
problem: can a parameter without a value be recognized in PHP?
06.12.2005 - if the bug gets done that eliminates the name of the page param, we have a problem with this bug here...
because we are now going for URLs like http://www.url.de?permanent-link. That interferes with the procedure that takes the first param to be the page.
One quick idea is to say: http://www.url.de/perm/?permanent-link with an index.php waiting in the perm - directory to resolve that param and look it up in a system table where the real URL is stored, then redirect.
("perm" could also be called "archive" or something smart...)
Read how to make Ajax calls with it.
It is difficult, though, to fill the previous-link then, when we do not know how far we're gonna show...
I could offer Ajax Events to be attached to form fields. That way, PolyPager moves a lot more in the direction of a (still very slim) web application engine.
Also, I could directly use the outcome to make a few adjustments to the Admin area.
Requirements:
-an Ajax-Engine (js-wise) - I like the one of brandspankingnew.com
-a possibility to attach Ajax-Events to fields.
For a field (in the admin area for _sys_fields), the user selects the event(clicked,onchange,...), the target-HTML-id (to replace the HTML content - how would that work with selectboxes and fields...?), and the URL to call for results (with the actual value attached) - the user could use any PHP(or other)-Script he wants
Is there more we need to offer (submits, ...)?
-some of those events could be used for PolyPager itself: maybe interlink skins with templates?
requieres more thought.
by Jan, 31.12.2006
Only happens with keyword, not with dropdown things.
by Jan, 1.1.2007
There is nothing wrong with the HTML, it seems to be something the browser does (to make it convinient when you come back to a site). Firefox will obviously keep text fields enabled. Safari, for instance, will still have the text field enabled when you come back with the back-button, but also the javascript button, so it works fine there.
The question: How to get Firefox to return to a valid state here? And: Any experience on IE?
-nic- 08.01.2007
IE 5 just closes the whole search option field when you return and doesn't remember anything, so fine here.
-j- 9.1.2007
While learning php anyway to be able to fix it: Also get rid of the strange "Don't wrap only one or two images" thing.
15.01.2007
Good Luck :-) By admins, you mean skin editors, right?
15.1.2007
By Admins I mean...mostly...myself. But "Skin Editor" would be fine, too. I'll need the luck. And probably a good deal of advice.
15.1.07 (later)
Line 147: approx. maxwidth
Line 1719: default width
Between 1721 & 1727 something happens. If I comment it out images dont break the border but are being displayed in rows of 4 - 1 - 4 - 1 - .... Not what I wanted to achieve.
Setting all values to "0" had the same effect.
Commenting 1813ff out disables wrapping altogether.
What happens here (1797f)?
if ($thumbs_wrap > ($thmb_row['maxwidth'] * ($thmb_row['softwrap'] / 100))
&& $wrapped == FALSE)
Changeing it to
if ($thumbs_wrap > ($thmb_row['maxwidth'])
&& $wrapped == FALSE)
seemed promising but did not do anything.
Changeing it to
if ($thumbs_wrap > ($thmb_row['maxwidth'] * ($thmb_row['softwrap'] / $thmb_row['softwrap']))
&& $wrapped == FALSE)
did change something but I forgot what.
HELP. I can't do it. Not tonight. Can't be that hard to locate the thing that says "only wrap images when there are more than one" and then set it to "more than zero".
Softwrap function is wrong anyway. It works like this:
"If wrapping would lead to a row with only one image, then just keep the image in the row above."
This MUST lead to chaos sooner or later. It should read (if you think it is such a bad thing for a thumbnail to be all alone in a row -- which I don't):
"If wrapping would lead to a row with only one image, then wrap before the last image of the last row."
S**t
16.1.07
I don't get it. There is definitely enough room in row one for another thumb, qdig decides to break the border instead.
16.01.07
Yes it can be hard to understand code, especially when you haven't written it yourself. I don't know what those variables mean, what they store, so I can't jump in here.
I don't even know what a softwrap is...
16.1.07
I guess "softwrap" means that the gallery is smart in wrapping. So it will not just calculate the width of all thumbs in one row and wrap them, as soon as value > maxwidth but calculate something obscure instead to make sure everything looks nicely -- not just one thumb in a row for instance. You can set a softwrap value somewhere (see above) and that gets used in the obscure calculation. But I do not understand how.
Somewhere you said, Qdig still gets maintained. Maybe I'll just write the guy an email and ask him for a
$disable_softwrap == TRUE
(or however a programmer would write it) option. And if he is working on the code anyway, he maybe could christen those html elements as well... We'll see.
16.01.07
Problem is, it's been much work to customize qdig for use with PP. A new version of qdig means work for me. Better ask him what would need to be done in our code.
When the page is not in the menu, the submenu entries MUST be accessible someway.
Make links just under the headline of them.
shouldn't be too hard...
It would be cool to be able to say "> X" when searching for something that is numerical.
For things that are not, say the bug status, there could be an "and" option (needs to be JS then, lotta work...)
24.07.2006
JS is needed for option lists, so that you'd have the possibility to request another option list to make one more choice.
After all, I think that is not sooo important.
One thing that is important would be to allow several keywords in the keyword search. Those could easily be selected by PHP and used to enrich the query (and the function keyword()) would have to be updated, but mostly that's OR statements.
So I would be happy with numerical operators and several keywords!
To get faster speed for all text-file transfers, use compression.
http://www.httprevealer.com/usage_gzip.htm tells something about it.
Here are further Google hits.
And here it reads how to do it: Add two lines to .htaccess (is that a problem to be generated? it's interesting because I could hide the admin-directory that way...)
Or is that built-in into my server? And if, should I make it a default anyway?
05.12.2005 - yes it is built in, but everywhere? I'll decrease priority to 4...
It would be nice if I could insert a media player (with some Java Script) to play a specified media file in tinymce.
If there is no plugin, I could write it myself :-)
19.01.2006 - now for FCKeditor of course...
21.07.2006 -
Malte
well, in here is some code that Malte gave me. The HTML in there is just horrible, horrible ... horrible.
But that Java Script that enables a Flash Player is indeed working. Within the zip is a ACDC mp3 - click on readme.html and you'll see it. The Flash-file doesn't look like it will be looking nice on every output, just on Malte's :-(
I'd really like to make it a FCKeditor - plugin, but maybe I could use that in PolyPager some other way... another option is Flash-Upload in FCKeditor...
Movie Plugin
here is a plugin to get Movies in.
This would be another point for PolyPager being a distinctively structural tool.
difficult question: what and how to log. the action code has to retrieve the old data (again - showing is over then) and then compare...
Maybe there is an option in FCK editor that helps with that...
22-06-2006 I didn't see one, but lets wait for Version 2.3 (Bug 134)
12-07-2006 FCKeditor tries to put in one line what is in one of those subarrays in fckconfig.php. I would have to observe that behavior more. All in one subarray doesn't seem to work really well...
they should get a textfield for fields that should be searchable.
The user could fill that field with the same technique he can for hidden fields.
to search for FKs generates a lot of queries - is there an easy way to save that? sessions? ugh... maybe provide an option to turn that feature off?
do all options in _sys_fields always make sense (especially for singelpages)?
- control the stylesheet even more (as skin author)
- insert javascript to track site access better (as user, for example with a service like feedburner.com)
But it's only one function that's involved (writeEntry()), so it should be possible.
21.02.2007
I don't get it.
-jan-
21.02.2007
Let's at least sign when we write sthg so it's visible.
I mean a template like the one we have, only now it specifies the HTML around an entry, you know:
<div class="show_entry">
<a class="target" id="whatpp-it-does"></a>
<div class="_sys_sections_heading">
<div class="title">
<a class="entry_title_link" href="?about&nr=56">what it does</a>
</div>
</div>
<div class="_sys_sections_bla">
<div class="value">
....
I haven't thought much about it, but it has some advantages...
- I post this entry
<p>Well, well, well, heute lernen wir, liebe Kinder, bei »Uncle Jan's merry <abbr title="Do it Yourself">DIY</abbr>« etwas darüber, was Elektrik und Brot verbindet. Stellt Euch mal vor: Seit Wochen fällt bei Euch daheim immer mal wieder ein Halogenstrahler aus. Im Bad wird es dunkler und dunkler, und in der Küche steigt das Verletzungsrisiko, aber alle sind zu faul, Strahlerersatz zu beschaffen. Was tun?</p>
<p><strong>Onkel Jan rät:</strong><br />
Tiefgekühltes (vorgeschnittenes) Brot nehmen und ordentlich auf die Arbeitsplatte hauen. Das trennt nicht nur die Brotscheiben, sondern es macht auch, daß die (an der Decke befestigten!) Strahler wieder gehen.</p>
- I want to correct some mistakes in the source. As soon as I click on "source" in FCK the entry looks like this:
<p>Well, well, well, heute lernen wir, liebe Kinder, bei »Uncle Jan's merry <abbr title="Do it Yourself">« etwas darüber, was Elektrik und Brot verbindet. Stellt Euch mal vor: Seit Wochen fällt bei Euch daheim immer mal wieder ein Halogenstrahler aus. Im Bad wird es dunkler und dunkler, und in der Küche steigt das Verletzungsrisiko, aber alle sind zu faul, Strahlerersatz zu beschaffen. Was tun?</abbr>« etwas darüber, was Elektrik und Brot verbindet. Stellt Euch mal vor: Seit Wochen fällt bei Euch daheim immer mal wieder ein Halogenstrahler aus. Im Bad wird es dunkler und dunkler, und in der Küche steigt das Verletzungsrisiko, aber alle sind zu faul, Strahlerersatz zu beschaffen. Was tun?</p>
<p><strong>Onkel Jan rät:</strong><br />
Tiefgekühltes (vorgeschnittenes) Brot nehmen und ordentlich auf die Arbeitsplatte hauen. Das trennt nicht nur die Brotscheiben, sondern es macht auch, daß die (an der Decke befestigten!) Strahler wieder gehen.</p>
- Also works when I just open the entry and save again without doing anything in between
I have to answer here as comment does not work again:
You mean when I first created the entry on my site? I always write the entries in the editor first and than add little things in the source (like &ndash, «, p-structure)
Let's use the Code beautyfier from here for this.
todo:
-
<link href="prettify.css" type="text/css" rel="stylesheet" />
<script type="text/javascript" src="prettify.js"></script> - Add
onload="prettyPrint()"to the document's body tag.
Just a matter of aesthetics: Do we really need the "show index" link when there is only one article being displayed?
Or should it stay in case someone uses it to style stuff relying on it being there?
Or is it too much work anyway, work that could easily put into something more valuable?