Been away for a few (4+) weeks - just wanted to ask OliG about the progress of implementing this scheme in next release - the ability to paginate different contentparts within a presentation scheme - (i have to think) - is really new - so if phpWcms supports this in the future - this could be a real breakthrough for not just the system - but for cms systems in general....
Hi Oliver
In principle -- this might be a great place to explore AJAX (frontend) -
Since my code is suboptimal (i agree) - this leaves open a better solution...
Which
paginates contentparts
AND refreshes fur (800 x 600 oder 1280 x 768) parameters
Scenario
(1) the user clicks on article.....
(2) sees the article with 'built - in" wcms pagination....
(3) uses a phpwcms navbar, and clicks....
(4) and gets 'ajax-refreshed' at (800 x 600 oder 1280 x 768) compliant page
the end experience would be like 'turning pages in a book'
ROBUST SIMPLE EFFICIENT USER-FRIENDLY
your thoughts?
postcript:
obviously the print feature would have
to strip out the pagination code and
show/display a fully printable single page
I like AJAX very much - but most times for backend only. In general you have to be sure that users have JavaScript enabled or it might fail. OK - can be handled by working around using the classical way.
For many webpages out there "page visits" are very important - so you have to be sure that a real page load happens.
Guessing you already have a long term strategy for the backend such as
...drag n drop to change ordering of categories, articles and contentparts
...opening / closing of '+' and '-' icons
My interest using AJAX on paginated contentparts is experimental really - since I am doing a research project - may try to find a way (aka hack) to do this - just to get user feedback - 'page visit' would be in place - even thinking bookmarking url with paginated info would be possible - so basically a limited use of AJAX.
BTW - I took a second look at Typo3 and still contend that despite its power - the gui - backend is still overly confusing
Your approach is far more intuitive and represents a better design solution...
phpwcms should not become a clone of Typo3 - it's there so no need to be complex as Typo3.
AJAX needs more work than just hacking the code. It has to be well projected and always asked: is it neccessary.
If you think about Ajax - first think about realizing your paginating by combined "hide/show layer". It's safe in case of disabled JavaScript because hiding can be done by simple CSS.
see www .br es so .de /103.100.0.0.1.0. phtml and "send a friend" form. Visit the page with JS enabled/disabled.
Oliver
Last edited by Oliver Georgi on Wed 13. Dec 2006, 13:34, edited 3 times in total.